X86 dbca, netca give Java hotspot error if on x86_64 hardware

When you use the dbca command to create a new database, the dbca command cannot be started. The running environment is where the host machine 64bit + amd cpu, while the client is Linux 32bit + grid infrastructure (32) + Oracle database software (32. It was originally thought that the 32-bit running would be faster. I didn't expect bug 8670579 to be triggered again when dbca was executed. According to mongoel's description, similar netca would also trigger this bug.

I. Fault symptom
[Oracle @ linux1 ~] $ Dbca
#
# An Unexpected error has been detected by hotspot virtual machine:
#
# SIGSEGV (0xb) at PC = 0x9e0ea498, pid = 4242, tid = 3086584016
#
# Java VM: Java hotspot (TM) server VM (1.5.0 _ 17-b02 Mixed Mode)
# Problematic frame:
# C [libnnz11.so + 0x3c498]
#
# An error report file with more information is saved as hs_err_pid1_2.log
#
# If you wowould like to submit a bug report, please visit:
# Http://java.sun.com/webapps/bugreport/crash.jsp
#
Aborted
[Oracle @ linux1 ~] $

 

Ii. fault description
# Meatlink [ID 942076.1] provides a description of this problem, that is, the 32bit operating system and Oracle are installed on the client, while the host hardware is a 64bit platform.
# This is an Oracle bug with bug No.: 8670579

Applies:
Oracle Server-Enterprise Edition-version 11.2.0.0 and later
Linux x86

Symptoms
After successfully installing 32-bit 11gr2 (11.2.0.1.0) software onto a 32-bit Linux OS (x86) system, neither netca or dbca can be run:

Dbca error is:
#
# An Unexpected error has been detected by hotspot virtual machine:
#
# SIGSEGV (0xb) at PC = 0x9dc0c35e, pid = 8292, tid = 3086022864
#
# Java VM: Java hotspot (TM) server VM (1.5.0 _ 17-b02 Mixed Mode)
# Problematic frame:
# C [libnnz11.so + 0x3c35e]

 

Netca error is:
# An Unexpected error has been detected by hotspot virtual machine:
#
# SIGSEGV (0xb) at PC = 0xa2c2235e, pid = 8272, tid = 3086309584
#
# Java VM: Java hotspot (TM) server VM (1.5.0 _ 17-b02 Mixed Mode)
# Problematic frame:
# C [libnnz11.so + 0x3c35e]

Other problematic frame values have also been reported, and include:
[Libnnz11.so + 0x3c35e]
[Ld-linux.so.2 + 0xc1fc]

Changes
Although the Linux OS that has been installed is indeed a supported 32-bit Linux OS, the hardware that is being used is 64-bit x86_64 hardware.

Cause
You are encountering published bug 8930861, "x86 dbca, netca give Java hotspot error if on x86_64 Hardware"

You have Oracle's 32-bit 11.2.0.1.0 RDBMS Software, a supported 32-bit Linux OS, but you are on 64-bit x86_64 hardware.

The command "cat/proc/cpuinfo" shows:
Model name: quactive-core amd opteron (TM) processor 2356

 

Iii. Solutions
1. Please find out if there is any business reason that the 64-bit hardware is only running
32-bit OS. If not, then Oracle recommends that you re-install a 64-bit OS and 64-bit Oracle
Avoid published bug 8930861, "x86 dbca, netca give Java hotspot error if on x86_64 hardware"

2. If there is some business reason that you must use 64-bit hardware running a 32-bit Linux OS, then
Before you can use the 11gr2 dbca or netca tools, you will need to apply patch 8670579 "netca/dbca
Failed with hotspot virtual machine ". You need to download the 11.2.0.1.0 version of the patch
(P8670579_112010_linux.zip) and install it.

References
@ Bugs: 8670579-dbbeta: netca/dbca failed with hotspot Virtual Machine
BUG: 8930861-x86 dbca, netca give Java hotspot error if on x86_64 hardware

# Check the Local Machine
[Root @ linux1 ~] # Cat/proc/cpuinfo | grep Model
Model: 4
Model name: AMD phenom (TM) II X4 955 Processor
Model: 4
Model name: AMD phenom (TM) II X4 955 Processor

# Download the 8670579 patch and use opatch apply.
# This bug occurs when root. Sh is executed when grid infrastructure is installed. The primary cause is poor support for amd cpu and 32bit platform.
# Therefore, the host machine is installed on the 64-bit hardware platform, and the client uses 32-bit. You need to apply the patch to grid infrastructure, and then to Oracle database software.
# When you run root. Sh, you will receive the error "failed to create or upgrade OLR.

BUG: 8670579 how to implement apply, refer to: failed to create or upgrade OLR
 

 

More references

DML error logging

PL/SQL --> cursor

PL/SQL --> implicit cursor (SQL % found)

Batch SQL forall statements

Bulk collect clause for batch SQL

Initialization and assignment of PL/SQL Sets

PL/SQL Union arrays and nested tables
PL/SQL variable-length Array
PL/SQL --> PL/SQL records

SQL tuning steps

Efficient SQL statements

Parent cursor, child cursor, and shared cursor

Bind variables and their advantages and disadvantages

Use of the display_cursor function of dbms_xplan

Use of the display function of dbms_xplan

Description of each field module in the execution plan

Use explain plan to obtain the SQL statement execution plan