Welcome to the Dell/Oracle Troubleshooting on Linux page!

This page will provide recommended actions for problems that a customer may encounter while deploying and using your Red Hat® Enterprise Linux® and Oracle® software.

Category Problem/Symptom Cause Recommended Corrective Action
Database Nodes that startup correctly with Patchset 10.2.0.1 may fail to startup with ORA-4031 errors in Patchset 10.2.0.2 RAC instances with greater than 4 Gb db_cache_sizes Set the variable set _ksmg_granule_size=16777216 in the init.ora file
Database Lock Manager Service (LMS) crash with ORA-00600 error: internal error code, arguments:
[kclastf_1], [2], []
Due to Oracle bug 5071492. See Oracle metalink Web site at:
metalink.oracle.com
Apply patch 5071492 available on the Oracle Metalink Web site.
Database The instance can terminate with ORA-600 error
[kclcls_5] in the RAC instance.
Due to Oracle bug 46392336. See Oracle metalink Web site at:
metalink.oracle.com
Apply patch 46392336 available on the Oracle Metalink Web site.
Database ERROR IN KOLMBIVG SEE LCK TRACE FILE" [LT] [LB]
KJUSERCLIENTLOCK
Due to Oracle bug 4690794. See Oracle metalink Web site at:
metalink.oracle.com
Apply patch 4690794 available on the Oracle Metalink Web site.
Database LMD0 PROCESS RECEIVED OS SIGNAL #11 Due to Oracle bug 5036588. See Oracle metalink Web site at:
metalink.oracle.com
Apply patch 5036588 available on the Oracle Metalink Web site.
Performance & Stability Red Hat Enterprise Linux exhibiting poor performance and instability. Excess use of swap space. The Oracle Systems Global Area (SGA) exceeds the recommended size.
  • Ensure that the SGA size does not exceed 65% of total system RAM.
  • Type free at a command prompt to determine total RAM and reduce the
    values of db_cach_size and shared_pool_size parameters in the Oracle paramter file accordingly.
Enterprise Manager The Enterprise Manager agent goes down or fails. The Enterprise Manager repository is not populated. Type the following to re-create the configuration file and repository for the DB console:

emca -config dbcontrol db repos recreate
OCFS System hangs while mounting or unmounting OCFS partitions Two nodes tried to unmount OCFS partitions at exactly the same time. Do not reboot more than one system at the same time.
Performance & stability Unknown interface type warning appears in Oracle alert file. Poor system performance. The public interface is configured as cluster communications (private interface). Force cluster communications to the private interface by performing the following steps on one node:
  • log in as oracle.
  • Type sqlplus "/ as sysdba" at the command prompt.
  • The SQL> prompt appears
    • Type alter system set cluster_interconnects='<private IP address on node 1>' scope=spfile sid='<SID1>' alter system set cluster_interconnects='<private IP address node2>' scope=spfile sid='<SID2>' Continue entering lines for each node in the cluster.
  • Restart the database on all nodes by typing the following:
    srvctl stop database-d <dbname>
    srvctl start database -d <dbname>
  • Open the
    /opt/oracle/admin/<dbname>/bdump/alert_<SID>.log file and verify that the private IP addresses are being used for all instances.
NETCA NETCA fails, resulting in database creation errors. The public network, hostname, or virtual IP is not listed in the /etc/hosts.equiv file. Before launching netca, ensure that a hostname is assigned to the public network and that the public and virtual IPaddresses are listed in the /etc/hosts.equiv file.
CRS CRS gives up prematurely when trying to start. Due to Oracle bug 4698419. See Oracle metalink Web site at:
metalink.oracle.com
Apply patch 4698419 available on the Oracle Metalink Web site.
CRS The Oracle Clusterware installation procedure fails. EMC PowerPath device names are not uniform across the nodes. Before you install Oracle Clusterware, restart PowerPath and ensure that the PowerPath device names are uniform across the nodes.
CRS CRS fails to start when you reboot the nodes, or type /etc/ini.d/init.crs start. The Cluster Ready Services CSS daemon cannot write to the quorum disk.
  • Attempt to start the service again by rebooting the node or typing root.sh from
    /crs/oracle/product/10.2.0/crs/.
  • Verify that each node has access to the quorum disk and the user root can write to the disk.
  • Check the last line in the file
    $ORA_CRS_HOME/css/log/ocssd.log
  • If you see clssnmvWriteBlocks: Failed to flush writes to (votingdisk), verify the following:
    - The /etc/hosts file on each node contains correct IP addresses for all node hostnames, including the virtual IP addresses.
    - You can ping the public & private hostnames.
    - The quorum disk is writable.
CRS When you run root.sh, CRS fails to start. Check and make sure you have public and private node names defined and that you can ping the node names. Attempt to start the service again by rebooting the node or by running root.sh from
/crs/oracle/product/10.2.0/crs/ after correcting the networking issues.



Back to Oracle Home
Back to Dell Center Home