Home » Infrastructure » Unix » ora-00600 error
| ora-00600 error [message #97101] |
Sun, 02 December 2001 23:09  |
wang
Messages: 3
Registered: November 2000
|
Junior Member |
|
|
hello:
I am trying to setup an Oracle Parallel Server(8.1.7) on Tru64 UNIX5.0A.
I have one database (OPS) set it up on the raw device being shared between
two nodes. I started one instance(OPS_A) of database OPS on node1 successfully. When i start the other instance (OPS_B) of database(OPS) on node2,I got the
following error,
SVRMGR> connect internal
Connected.
SVRMGR> startup
ORACLE instance started.
Total System Global Area 28541088 bytes
Fixed Size 73888 bytes
Variable Size 11517952 bytes
Database Buffers 16777216 bytes
Database Buffers 16777216 bytes
Redo Buffers 172032 bytes
ORA-00600: internal error code, arguments: [[kccsbck_first]], [[2]],
[[3469846071]], [[]], [[]], [[]], [[]], [[]]
Thanks
----------------------------------------------------------------------
|
|
|
|
| Re: ora-00600 error [message #97104 is a reply to message #97101] |
Mon, 03 December 2001 12:13  |
Melissa
Messages: 65
Registered: January 2000
|
Member |
|
|
Problem Description
-------------------
This article helps to resolve problems with the error ora-600[[kccsbck_first]].
The ORA-600[[kccsbck_first]] error occurs when Oracle detects that another
instance has this database already mounted. For some reason, Oracle already sees
a thread with a heartbeat. This could be the expected behaviour if running OPS.
In such a case the parallel_server parameter needs to be set.
In cases where Parallel Server is not linked in, this is not the expected behaviour.
WHAT TO CHECK :
---------------
1- You try to start the instance you just created
=================================================
sqlplus> startup
ORA-600[[KCCSBCK_FIRST]]
The error is recorded only on the screen and no errors are reported
in the %ORACLE_HOME%/rdbms/log/alert_%ORACLE_SID%.log.
Several other instances run fine on the box. None of them has a similar
db_name. They all run different Oracle versions.
Solution 1:
-----------
Make sure that the initSID.ora soft link points to the correct release
location.
Explanation 1
-------------
The initSID.ora in $ORACLE_HOME/dbs is pointing to a higher release of
Oracle. E.g., init.ora points to 8.1.5 instead of 8.0.5. The database
and software versions need to be synchronized.
2- You installed HACMP software
===============================
List all cluster nodes with the following:
$ $ORACLE_HOME/bin/lsnodes
The following verification doesn't show any error:
$ /usr/sbin/cluster/diag/clverify
Check HACMP interconnect network adapter configuration with the following:
$ /usr/sbin/cluster/utilities/clsif
Adapter
Type Network Net Type
Attribute Node IP Address
pfpdb3
service pfpdb3 ether
private pfpdb3 11.2.18.24
pfpdb4
service pfpdb4 ether
private pfpdb4 11.2.18.3
The
network parameter doesn't match. It has to be identical for both adapters.
cllsif on a working configuration should look like this:
Adapter
Type Network Net Type
Attribute Node IP Address
pfpdb3
service pfpdb ether
private pfpdb3 11.2.18.24
pfpdb4
service pfpdb ether
private pfpdb4 11.2.18.3
Solution 2:
-----------
Please change the HACMP interconnect network adapter configuration.
3- You are running oracle on an NT CLUSTER
==========================================
You encounter one the following errors:
ORA-00600: internal error code, arguments: [[kccsbck_first]],[[1]],[[number]]
OR
ORA-00600: internal error code, arguments: [[KSIRES_1]],[[KJUSERSTAT_not attached]]
The OPS database had been running for some time with no problems; therefore,
cluster and database configuration issues can be ruled out.
Rebooting the node itself also does not clear the problem.
Solution 3:
-----------
Reboot the entire NT cluster.
Explanation 3:
--------------
When the primary instance mounts the database, a lock is enabled that will
prevent other instances from mounting the database in exclusive mode. If there
is a problem with the status of this lock, Oracle will return either of these
errors until the entire cluster is rebooted and the locks are reinitialized.
4- Check the parameters
=======================
You encounter these 2 errors:
ORA-00600: internal error code, arguments: [[kccsbck_first]],[[1]],[[number]]
AND
ORA-00439 "feature not enabled: %s"
Solution 4:
-----------
Please check the "init.ora" to verify that the "parallel_server" option
is not set. Setting the parameter "Parallel_Server" to true in the "init.ora"
of both instances yields these errors.
You need to make sure you can start up all your Parallel Server instances in
shared mode successfully.
Explanation 4:
--------------
The new parameter "PARALLEL_SERVER" was introduced in 8.x. When this
parameter is set to TRUE, then the instance will always come up in shared
mode.
When "parallel_server=false" or not set in "init.ora", the instance will always
startup in exclusive mode. The first instance will start up successfully, but
the second or subsequent OPS instances will fail. Make sure you can start up
all your Parallel Server instances in shared mode successfully.
5- ORA-600 [[kccsbck_rtenq]] Trying to start an Oracle Parallel Server database
=============================================================================
ORA-600 [[kccsbck_rtenq]]
From the alert.log:
Mon Jan 31 08:48:41 2000
Errors in file /u01/app/oracle/admin/nps3/udump/ora_6676.trc:
ORA-00600: internal error code, arguments: [[kccsbck _rtenq]], [[1]],
[[3775228464]], [[]], [[]], [[]], [[]], [[]]
When trying to start the second node in cluster, you encounter this
error:
ORA-600 [[kccsbck_first]]
Solution 5:
-----------
Ensure the 'oracle' binary is the same across all nodes of the OPS cluster.
Specifically, check that the GROUPS are the same on each node.
For example:
Node jag2:
% ls -l oracle
oracle backup 28262400, Jan 31 1:15
Node jag1:
% ls -l oracle
oracle backup 28262400, Jan 31 1 :26
Logged in as the 'oracle' software owner...
Node jag1:
%id uid=1001, gid=13, groups=101 dba
Node jag2:
%id uid=1001, gid=13, groups =15 users, 101
Note that the primary GROUPS displayed for the oracle user are not the same
on each node of the cluster. Correct this and restart the OGMS to correct
the problem.
Explanation 5:
--------------
It is assumed that the lock management/node monitor divides up the lock domain
by unix group id. Instances with the same dbname should belong to the same
lock domain, therefore the user which starts the instance must belong to
the same groups.
6- ON STARTUP AFTER DATABASE CRASHED
====================================
You are attempting to start your database after it crashed, and are
getting the following errors on startup mount:
skgm warning: Not enough physical memory for SHM_SHARE_MMU segment of size
000000000795a000
ORA-00600: internal error code, arguments: [[kccsbck_first]], [[1]], [[3141290959]]
Solution 6:
-----------
- check if background processes for this SID are still running and kill them
with the unix kill command.
- check also if shared memory segments still exist for this instance and
remove them.
See <Note:68281.1>
- check also if the "sgadefSID" file exists in the "$ORACLE_HOME/dbs"
directory for the SID and remove it.
- check if OPS is linked in:
$ cd $ORACLE_HOME/rdbms/lib
$ ar tv libknlopt* | grep kcs
$ kcsm.o => OPS is linked in
$ ksnkcs.o => OPS is not linked in
Explanation 6:
--------------
In most cases when a shutdown abort is issued for an instance, the background
processes will die. In this case they did not. There was not enough
information to determine why the database crashed and the Oracle background
processes continued to run. Other things to check for ,in this case, are shared
memory segments that are still running for the instance that crashed, and the
"sgadefSID" file existence in the "$ORACLE_HOME/dbs" directory for the SID that
is receiving the error.
7- YOU ARE RUNNING ORACLE 8.1.5 TO 8.1.7 ON A COMPAQ TRU64 UNIX CLUSTER
=======================================================================
See <Note:137322.1>
<Note:139812.1>
8- YOU ARE CONFIGURING OPS ON COMPAQ PROLIANT NT 4.0 CLUSTER
============================================================
See <Note:158653.1>
----------------------------------------------------------------------
|
|
|
|
| Re: ora-060 error [message #98091 is a reply to message #97104] |
Sun, 08 February 2004 18:53 |
Naveen
Messages: 75
Registered: June 2001
|
Member |
|
|
HI,
I've come across this problem when i'm exporting my database. it happened in the middle of the operation and backup continued.I'm in doubt whether my backup is valid or not. Plz help me
Regards
Naveen
|
|
|
|
Goto Forum:
Current Time: Tue Apr 23 04:00:19 CDT 2024
|
] 
Blog
Search
Help
Members
Register
Login
Home
