In this Document

Applies to:

Purpose

The note lists most known issues in 11gR2 Grid Infrastructure (in short GI) + pre-11gR2 database environment.

Even workaround is available in some cases, it's recommended to apply patches whenever possible. Refer to note 1064804.1 for instructions to patch in mixed environment.

For CRS PSU/bundle patch information, refer to note 405820.1 for 10.2 and note 810663.1 for 11.1

Refer to note 1568834.1 for pre-12.1 database issues in 12c Grid Infrastructure environment

Details

1. Error creating or starting pre-11.2 database:

If it happens while creating database, DBCA fails with ORA-29702 and traces shows:

If it happens while starting existing database, sqlplus startup fails:

Database alert.log shows the following message:

Solution:

To start a pre11gR2 database in 11gR2 Grid Infrastructure environment, node(s) must be pinned. To pin node(s), as root execute:

To find out whether node(s) is pinned or not:

2. If datafiles are located in ASM, DBCA fails to create database with error: 

DBCA trace (10g in $RDBMS_HOME/cfgtoollogs/dbca and 11g in $ORACLE_BASE/cfgtoollogs/dbca) shows the following exception:

Solution:

Due to unpublished bug 8288940 (fixed in 10.2.0.5), DBCA will fail if database files are located in ASM. patch 8288940 is platform independent and is available for 10.2.0.3, 10.2.0.4, 11.1.0.6 and 11.1.0.7 as a .jar file and needs to be applied to database home. For other RDBMS version where there's no patch, please refer to workaround section of bug 8520511 in Database Readme Bug 8520511>

Note: pre-11.2 dbca can not be used to manage 11gR2 ASM (add/remove ASM instance, add/remove diskgroup etc)

3. SRVCTL fails to start instance if OCR is located in an ASM diskgroup or with different permission/ownership. 

The racgimon log (located in $RDBMS_HOME/log/$HOST/racg/imon_${DBNAME}.log) shows the following message:

Solution:

Due to unpublished bug 8262786, if OCR is located in ASM or with different permission/ownership, srvctl will fail to start earlier database version.Fix for unpublished bug 8262786 is included in 10.2.0.4 CRS PSU4, 10.2.0.5, 11.1.0.7 CRS PSU4, and Windows 10.2.0.4 Patch 36 and needs to be applied to database home. The workaround is to use sqlplus to start the database instead of srvctl




4. Database fails to start after restart of GI.

$GRID_HOME/log/$HOST/agent/crsd/application_/application_.log shows:

After GI restart, status of diskgroup:

Solution:

Due to unpublished bug 8448079, while stopping GI, ASM init.ora parameter asm_diskgroups will be nullified and some diskgroups will remain OFFLINE after restart of GI due to which pre-11.2 database fails to start. Fix for unpublished bug 8448079 is included in the 11.2.0.2, patch 8448079 exists for certain platform and needs to be applied to GI home. 

5. SRVCTL fails to start service

For example:

Solution:

Due to unpublished bug 8373758, pre-11.2 srvctl will fail to start a service if the service is followed by a 11gR2 new resource in "crsctl stat res" output.  In the above example, ora.eons is a new resource in 11.2 and pre-11.2 srvctl can't parse its status properly. Fix for unpublished bug 8373758 is included in 10.2.0.4 CRS PSU4, 10.2.0.5, 11.1.0.7 CRS PSU2 and needs to be applied to database home.  The workaround is to:

 Note that fix for bug 8373758 does not include fix for bug 8262786.


6. In Job Role Separation environment, DBCA fails to create database with error:

And execution of setasmgidwrap fails with:

Solution:

Due to bug 9575578, setasmgidwrap fails with pre-11.2 oracle binary. Fix for bug 9575578 is included in 11.2.0.2, patch 9575578 exists for certain platform and needs to be applied to GI home.
note 1054033.1


7. After removal of pre-11.2 CRS home, the following error reported while trying to start or stop database, or stop cluster

If GI is being stopped, the following will be reported:

Solution:

Due to bug 9257105, even upgrade finishes successfully, OCR configuration for pre-11.2 database still points to pre-11.2 CRS home. Fix for the bug is included in 11.2.0.1.2 and 11.2.0.2, unfortunately the fix itself is having regression which is being worked in unpublished bug 9678856. The workaround is to:

8. Singleton service does not failover or uniform service does not stop after local node VIP resource failed or stopped:

Solution:

Due to unpublished bug 9039498, pre-11.2 database service will not failover or stop if local public network is down. Fix for bug 9039498 is included in 11.2.0.2, 12.1 and applies to GI home.




9. DBCA/srvctl fails to add instance/database with the following error:

Solution:

Due to bug 9767810, if pre-11.2 database is not installed on all nodes of the cluster, srvctl fails to add instance/database to OCR. The bug is fixed in 11.2.0.1.2 and applies to GI home. The workaround is to copy pre-11.2db/bin/racgwrap to all nodes in the cluster, and make sure it's accessible by pre-11.2 database owner.


10. Pre-11.2.0.2 database fails if any private network fails.

It happens as pre-11.2.0.2 instance isn't aware of Redundant Interconnect feature (multiple active cluster_interconnect in "oifcfg getif"), see note 1210883.1 for more about HAIP

Solution:

As HAIP feature can not be disabled, for environment with GI 11.2.0.2 with pre-11.2.0.2 database/ASM, it's recommended to use OS level bonding solution for private network as in earlier clusterware version.


11. If OCR is located on ASM, pre-10.2.0.5 database can not get cluster interconnect even it's configured in OCR

Solution:

For 11gR2 GI + pre-10.2.0.5 database environment, it's not recommended to place OCR on ASM. Other workaround is to set init.ora parameter cluster_interconnects and ignore the warning.

12. After clusterware upgrade, ocrdump shows key "SYSTEM.ORA_CRS_HOME" is not updated to new clusterware home.

If previous clusterware home is renamed or removed, pre-11gR2 SRVM client (srvctl, DBCA, DBUA etc) fails.

In this example, /ocw/b201 is pre-upgrade clusterware home which is not updated.

Solution:

Due to bug 10231584, OCR key SYSTEM.ORA_CRS_HOME is not updated during upgrade. The workaround is to execute the following as root on any node:

13. Service does not stop/failover after stopping corresponding instance

$DB_HOME/log/$HOST/racg/imon_.log

$GRID_HOME/log/$HOST/evmd/evmd.log

Solution:

Due to bug 12340700, the following files has wrong permission:

Unpublished bug 12340700 is fixed in 11.2.0.3 and applies to GI home. The workaround is to fix the permission manually with "chmod" command and restart GI. The expected ownership and permission are:

14. 10.1 ASM or DB does not start during or after clusterware upgrade

During upgrade, OUI shows the following error:

[INS-20802] Automatic Storage Management Configuration Assistant failed.

Installation log ($ORACLE_BASE/oraInventory/logs/installActions{$TIMESTAMP}.log):

Solution:

This is caused by bug 3841387, the solution is to apply patch 9632335 to 10.1 ASM and DB home and retry. Refer to note 969254.1 Section "OUI Plug-in Failure" for retry steps, alternately ASMCA can't be executed manually to upgrade ASM.


15. pre-11.2 instance/database stops after check timed out:

$GRID_HOME/log//crsd/crsd.log

$GRID_HOME/log//agent/crsd/application_/application_.log

$DB_HOME/log//racg/imon_.log

Instance alert.log

Solution:

Due to bug 11933693 and bug 12800501, pre-11.2 database/instance will be stopped if agent check times out. The bug will not cause timeout, the cause could be slow/hang OS/DB and needs to be investigated separately.



bug 11933693 is fixed in 11.2.0.2 GI PSU3, 11.2.0.3 and above, the fix applies to GI home.
bug 12800501 is fixed in 11.2.0.2 GI PSU4, 11.2.0.3 and above, the fix applies to GI home.


16. Error creating or starting pre-11.2 database on HP-UX Itanium if hostname is longer than 8 characters:

Pre-11.2 database doesn't start after clusterware/ASM upgraded to 11.2:

Database alert.log shows the following message:

Solution:

As per the following documentation, it's unsupported to have OS hostname longer than 8 characters on hp-ux Itanium:

http://download.oracle.com/docs/cd/B28359_01/relnotes.111/b32071/toc.htm#CHDEHEIB

The solution is to deconfig and deinstall clusterware, make hostname shorter, install, config clusterware and register databases. Refer to note 942166.1 for details to deconfig, deinstall steps.

17. After clusterware upgrade to 11gR2, pre-11.2 listener may not stay online as it dumps core due to bug 10192450, refer to note 1348369.1 for details


18. ORA-12537 when connecting to pre-11.2 database/instance through 11gR2 Listener on Solaris, refer to note 975596.1 for details


19. ORA-600 [733] or ORA-15055:
 
Database instances fails to connect to the ASM instance with ORA-600 [733] when ORACLE_HOME is NFS mounted, or fail to start due to ORA-15055 "unable to connect to ASM instance"

Solution:

This is due to bug 12660458 which has been fixed in 11.2.0.3 and above, interim patch 12660458 exists for certain platform/version


20. Pre-11.2 database is NOT supported in 11gR2 Grid Infrastructure Standalone (Oracle Restart) environment

Pre-11gR2 database is not supported to be registered to 11gR2 GI Standalone, error "srvctl[nnnn]: /bin/java:  not found" can happen when registering. Refer to note  954552.1 for details.
 

21. High CPU usage if there's large number of pre-11.2 databases

Refer to note 1348202.1 for patches that need to be applied to 11gR2 GI home, and apply patch 12801833 to all pre-11.2 database homes.

22. srvctl add instance / database may fail with PRKC-1056 PRKH-1001 PRKO-2006 or PRKH-1010 PRKH-1010 if node is not pinned

Refer to note 1454446.1 for the details.

23. Pre-11.2 database service does not failover when public network is down

Pre-11.2 database service does not fail over when public network is down (VIP fails over correctly), this is due to bug 13090686 which is fixed in 11.2.0.3 GI PSU1 and 11.2.0.4, the workaround is to relocate the service manually as database owner

24. Pre-11.2 database fails to start if ORA_NLS10 is set wrongly:

If it happens while starting existing database, sqlplus startup fails:

Solution: 

The cause is environment variable ORA_NLS10 has invalid setting, once it's unset, database is able to come up 

 
 
25. Can pre-11.2 DB co-exist with 11gR2 policy managed databases on the same server?

The answer is no, refer to note 1484800.1 for details
 
 

26. Pre-11.2 DB creation fails with ORA-15045, ORA-17502, ORA-15081 when storage is on ASM

Refer to note 1384180.1 for solution

27. Pre-11.2 service does not failover upon instance crash?

This is due to bug 13879428, refer to note 1489751.1 for details.

28. Pre-11.2 DB is slow after Single Instance ASM is upgraded to 11.2.0.2 or 11.2.0.3

This is due to bug 13868167, when this happens, many css*.log is created in "$ORACLE_HOME/log//client/css*.log" with similar contents like the following: 

Bug 13868167 is fixed in 11.2.0.4, refer to note 1444483.1 for workaround.

29. Pre-11.2 service may not failover in 11gR2 GI 

This is due to misconfiguration, refer to note 1539624.1 for more details.

References