On Sun Fire T1000/T2000 systems, an Oracle database will hang if it was installed with Java Virtual Machine (JVM) version 1.5. An Oracle database that was installed elsewhere and copied to a T1000/T2000 will likewise hang if JVM 1.5 was used for installation.

Note: Only the Oracle application is affected by this condition and can be killed with Control-C (^C) to prevent it from consuming system resources.

This issue can occur on the following platforms:

• Sun Fire T1000/T2000 systems (running Solaris 10 and Oracle 10g Release 2) without patch 118833-18

Notes:

1. This issue only occurs if Oracle JVM 1.5 was selected during installation of Oracle 10g Release 2
2. This issue has also been reported during Oracle database/instance creation.
3. T1000 requires (minimum) Solaris 10 1/06. T2000 requires (minimum) Solaris 10 3/05 HW release 2 (Solaris 8 and 9 are not supported on these platforms).
4. Oracle versions previous to 10g Release 2 are not known to be affected by this issue.

The Oracle application will appear to hang, producing no error messages. The rest of the system will be operating normally. The PID of the of the hung process can be identified using the "prstat -s cpu" command; it will be consuming CPU time on an otherwise idle system and should appear towards the top of the output.

There is no workaround to this issue. Please see the Resolution section below.

This issue is addressed on the following platforms:

• Sun Fire T1000/T2000 systems with patch 118833-18 or later

11-Jul-2006:

• Updated Relief/Workaround section

21-Jul-2006:

• Updated Contributing Factors and Resolution sections
• State: Resolved

This solution has no attachment