| | Two databases with the same name on one server
You can run 2 Oracle instances with the same database name. To do that set the following
parameter(s):
Instance 1:
*.lock_name_space=DB1
*.sp_name=DB1
Instance 2:
*.lock_name_space=DB2
*.sp_name=DB2
In your oratab you would have two entries, one for DB1 and another one for DB2. db_name would be the same for both. | | More...
02/17/09 | | | | |
|
| | how to create a log file if lost?
1-Now you are facing a problem that the db doesn't open
2-log on the db as sys dba
run>cmd>sqlplus username/password as sysdba
3-alter database clear logfile group (number of the lost group file);
such as
alter database clear logfile group 2;
4- open the database
alter database open;
| |  
More...
01/13/09 | | | | |
|
| | How to run two instances with the same database name in one ORACLE_HOME
If you cloned a database and need to run both instances with the same db_name from one $ORACLE_HOME i.e.:
*.db_name=TESTDB
use the following parameters in your pfile or spfile:
*.lock_name_space=ANOTHERDB
*.sp_name=ANOTHERDB
Where ANOTHERDB is the name of the cloned sid.
Note: this has been tested with Oracle 10.1 only | | More...
09/09/08 | | | | |
|
| | How to upgrade Oracle 10.2.0.3 to 10.2.0.4
1. Shutdown database running on older version
2. Edit oratab and change ORACLE_HOME to 10.2.0.4 for the database being upgraded
3. Start the database
4. Run the upgrade assistant
$ORACLE_HOME/bin/dbua
... that's it
| | 
More...
07/14/08 | | | | |
|
| | How to drop Oracle database
Dropping database from sqlplus
1. Shutdown the database
SQL> shutdown immediate;
2. Mount exclusive and put in restricted mode
SQL> startup nomount;
SQL> alter database mount exclusive;
SQL> alter system enable restricted session;
3. Drop database
SQL> drop database; | | More...
06/04/08 | | | | |
|
|
| | WARNING: TEMP tablespace is not large enough for the upgrade
Apparently Oracle wants the default temporary tablespace to be locally managed when upgrading from 10.1 to 10.2. When running utlu102i.sql script it throughs this warning if your temp tablespace is dictionary managed:
--> SYSTEM tablespace is adequate for the upgrade.
.... minimum required size: 347 MB
WARNING: --> TEMP tablespace is not large ... | | More...
01/23/07 | | | | |
|
| | Unix permissions problem under ORACLE_HOME
Apparently this is a known Oracle bug, after installing Oracle 10.2.0 Unix permissions under ORACLE_HOME are not set correctly, so directories and files are accessible to the installation user and group (i.e. oracle:dba) but not to the reset of the world (others). If you get any of the following errors ... | |
More...
04/26/06 | | | | |
|
| | Oracle automatic memory management
In Oracle10g memory can be managed automatically by setting parameter sga_target. Oracle will then manage parameters like: db_cache_size, shared_pool_size, java_pool_size, large_pool_size. You will see new '__' parameters created by Oracle:
__db_cache_size, __shared_pool_size, __java_pool_size, __large_pool_size, these are now dynamically managed.
Check what sga_target is set to:
SQL> sho parameter sga_target
NAME ... | |
More...
04/10/06 | | | | |
|
| | Oracle Virtual Indexes - How to
Virtual index is a feature of Oracle 10 and Oracle 9. The purpose of virtual indexes is simulate the existence of an index, without actually building it, so you can explain plan as if the index existed. It is important to drop the index after you're done with it.
To build ... | | More...
11/24/05 | | | | |
|
Page 1 | 2 >> |
