create RSA and DSA keys with no passphrase
Tuesday, June 24, 2008
Internal Eerror Code LibraryCacheNotEmptyOnClose
Found in
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
in any platform.
Metalink note
Note:466425.1
Note:4483084.8
Note:365103.1
Signs
ORA-600 [LibraryCacheNotEmptyOnClose] , [], [], [] [], [], [], []
Bug
4483084
Fixed in
11.1.0.6 (Base Release)
Workaround
Ignore the error as it just indicates that there are some items in the library cache when closing down the instance. The error itself occurs AFTER the database close and dismount stages so only affects the instance shutdown itself. Datafiles have been closed cleanly.
It is intended that this will be fixed in 10.2.0.5 but this has not yet been confirmed.
Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4
in any platform.
Metalink note
Note:466425.1
Note:4483084.8
Note:365103.1
Signs
ORA-600 [LibraryCacheNotEmptyOnClose] , [], [], [] [], [], [], []
Bug
4483084
Fixed in
11.1.0.6 (Base Release)
Workaround
Ignore the error as it just indicates that there are some items in the library cache when closing down the instance. The error itself occurs AFTER the database close and dismount stages so only affects the instance shutdown itself. Datafiles have been closed cleanly.
It is intended that this will be fixed in 10.2.0.5 but this has not yet been confirmed.
Sunday, June 22, 2008
Converting from Standard to Enterprise Edition
1. Install enterprise edition on a separate home
2. create pfile of the existing database and move to enterprise home
3. move the password file to enterprise home or create new password file
4. backup the database.
5. switch paths, sid, and other oracle home related properties to enterprise home
6. startup the database
7. run catalog, catproc and utlrp scripts
8. de-install the standard software
Database version must be same. (ie. if standard is on 10.2.0.3 enterprise should also be on 10.2.0.3
if versions are different then replace steps 6 and 7 with
6. startup the database in upgrade/migrate mode.
7. run catupgrd.sql script of the current patch set level
more on metalink Note:117048.1
The only way to properly convert from an Enterprise Edition back to a Standard Edition is through an Export/Import operation. This way you will get rid of all Enterprise Edition specific Data Dictionary objects, as the SYS schema objects are not exported. The Standard Edition EXP utility is preferred to be used to export the data.
After the Import in the Standard Edition database, you only need to drop all user schemas related to Enterprise Edition features, such as the MDSYS account (used with Oracle Spatial).
more on metalink Note:139642.1
2. create pfile of the existing database and move to enterprise home
3. move the password file to enterprise home or create new password file
4. backup the database.
5. switch paths, sid, and other oracle home related properties to enterprise home
6. startup the database
7. run catalog, catproc and utlrp scripts
8. de-install the standard software
Database version must be same. (ie. if standard is on 10.2.0.3 enterprise should also be on 10.2.0.3
if versions are different then replace steps 6 and 7 with
6. startup the database in upgrade/migrate mode.
7. run catupgrd.sql script of the current patch set level
more on metalink Note:117048.1
The only way to properly convert from an Enterprise Edition back to a Standard Edition is through an Export/Import operation. This way you will get rid of all Enterprise Edition specific Data Dictionary objects, as the SYS schema objects are not exported. The Standard Edition EXP utility is preferred to be used to export the data.
After the Import in the Standard Edition database, you only need to drop all user schemas related to Enterprise Edition features, such as the MDSYS account (used with Oracle Spatial).
more on metalink Note:139642.1
Subscribe to:
Posts (Atom)
