ORACLE STARTUP ORA-00600 ORA-24324 ORA-01041

OS:REDHAT AS 4.6

DB:ORACLE 10.2.0.1

 

SQL> startup nomount
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
SQL> startup
ORA-24324: service handle not initialized
ORA-01041: internal error. hostdef extension doesn't exist
SQL>

---

vi /etc/hosts

add

--------------------------------------------------------------------------------------------------------------

--------------------------------------------------------------------------------------------------------------

METALINK:

Startup Database Produces ORA-00600: [Keltnfy-Ldminit] [ID 336447.1]

In this Document

Symptoms

Cause

Solution

References

---

Applies to:

Oracle Server - Enterprise Edition - Version 10.2.0.1 to 10.2.0.3 [Release 10.2]
Information in this document applies to any platform.
***Checked for relevance on 09-Jun-2010***

Symptoms

An startup nomount on Oracle 10g Release 2 database produces the following exception in alert log

Starting up ORACLE RDBMS Version: 10.2.0.1.0.
Errors in file /opt/oracle/10.2/admin/ORCL/udump/ORCL_ora_535.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
USER: terminating instance due to error 600
Instance terminated by USER, pid = 535

Cause

The problem is related to get the host information.

In this case, ldmInit()/sldmInit() is failing with error 46 : LDMERR_HOST_NOT_FOUND

The following exception may also occur :

LDMERR_SOSD_INIT  OSD init failed to be specific in these OSD failures
LDMERR_BAD_ADDR   bad address when system call gethostname failed
LDMERR_HOST_NOT_FOUND    gethostbyname system call fails
LDMERR_NO_SUPPORT   when specific address type is not supported

Development has fixed two bugs so far regarding this issue

Bug:5438154 - ORA-600[KELTNFY-LDMINIT]  STARTING THE DB 

Release Notes: 
ldmInit returned LDMERR_HOST_NOT_FOUND for the machine huge alias list/address list 
Workaround: 
reduce the alais list of the machine

Note:5486074.8 - ORA-600 [KELTNFY-LDMINIT] WHEN DNS IS NOT AVAILABLE

Release Notes: 
Internal error is raised by the Server Generated Alert subsystem when it can not determine Host Name or 
Network Address. This can be caused by DNS server being unavailable. 

Refer to the Note above for version that contains these fixes.

Solution

The patch for 5486074 will not fix any underlying error from gethostbyname(), it just change the internal error to a warning message :    

"Warning: keltnfy call to ldmInit failed with error 46"

You will still need to fix the network configuration issue.  
These are the check you can do verify the host information 

• Check permission on /etc/hosts

  $ ls -l /etc/hosts
  -rw-r--r-- 2 root root 194 Oct 17 2006 /etc/hosts

• Check if /etc/hosts file is correctly configured

( all of this on one line ).

• Check the hostname:

$ hostname
$ ping `hostname`

Make sure you are able to ping the hostname
  

• Check if /etc/nodename is correctly configured 

• If you have DNS setup, ping is not a tool to diagnose DNS problem. A better tool to use is nslookup, dnsquery, or dig.

$ nslookup
$ nslookup
$ nslookup

The forward and reverse lookup should succeed and return consistent address/info.      

• Check nsswitch.conf

$ more nsswitch.conf
hosts: files dns

Make sure host lookup is also done through the /etc/hosts file and not just dns.  
It is recommended that FILES come first before DNS.   

• Also, check the resolv.conf. This makes sure that the DNS is working properly.

---

References

NOTE:5486074.8 - Bug 5486074 - OERI [keltnfy-ldminit] when DNS is not available
BUG:5438154 - ORA-600[KELTNFY-LDMINIT] STARTING THE DB
BUG:5486074 - ORA-600 [KELTNFY-LDMINIT] WHEN DNS IS NOT AVAILABLE

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/18914315/viewspace-740863/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/18914315/viewspace-740863/