主机名问题引发的错误 ORA-00…

Linux 5, Oracle 10.2.0.1

 

Alertlog:

 

Sat Jun 28 07:46:53 2014
Errors in file /u01/app/oracle/product/10.2.0/db_1/rdbms/log/prod_ora_17824.trc:
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], []
USER: terminating instance due to error 600
Instance terminated by USER, pid = 17824

 

Solution:  Setup命令，编辑DNS，重新修改了主机名

 

 

参考文档:

Startup Database Produces ORA-00600: [Keltnfy-Ldminit] (文档 ID 336447.1)

转到底部

---

修改时间:2014-2-7类型:PROBLEM

In this Document Symptoms Cause Solution References Applies to: Oracle Database - 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 10-Jan-2014*** Symptoms *Symptoms Briefly describe the symptoms of the problem. Remember to delete any customer specific information 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. To prevent the ORA-600 error, you can upgrade to any supported version of the database or apply the  10.2.0.4 patch set. This issue is fixed in          10.2.0.4 (Server Patch Set)     11.1.0.6 (Base Release)