Environment Description: LINUX Virtual Machine RedHat5.5 + Oracle10.2.0.1 Single Instance Library
Fault description: When startup starts the database, a ORA-00600 error is reported as follows, and cannot start
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], [], []
Sat Mar 10 21:18:00 2012
USER: terminating instance due to error 600.
Instance terminated by USER, pid = 10599
Sat Mar 10 22:28:57 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE = BR
ILAT = 18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Ksdpec: called for event 13740 prior to event group initialization
Online materials:
Description of Doc ID: Note: 5486074.8 in meatlink of Oracle: this error message is displayed when Oracle cannot determine the host name or network address.
Oracle fixed this bug in 10.2.0.4 and 11.1.0.6. On metalink of Oracle, this error may occur before 10.2.0.4.
However, the test shows that Oracle9i does not cause errors due to the modification of the hostname.
Fault analysis:
When the database cannot group the host name or NIC address, it should be because I manually modified the HOSTNAME and the virtual machine's ethernet card did not obtain the IP address due to the local network change, triggering the database version BUG.
Solution:
(1) first restart the network service, so that the network card is bound to the IP address, startup can start the database, but the alert Log is still intermittent error ORA-00600 (every several seconds) as follows:
(2) manually modify the HOSTS file so that the host name that I manually modified using HOSTNAME corresponds to the IP Address: view the alert Log to solve the problem.
[Root @ dba ~] # Cat/etc/hosts # Do not remove the following line, or various programs # that require network functionality will fail.127.0.0.1 dba.com dba: 1 localhost6.localdomain6 localhost6
Summary:
Oracle fixed this bug in 10.2.0.4 and 11.1.0.6. On metalink of Oracle, this error may occur before 10.2.0.4.