首页 > 代码库 > ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], []
ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], []
今天建库的时候忽然报错ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], [] 梗是让我无语,没办法只好检查参数配置,按照文档一步步检查,最后检查了下profile文件的配置 [root@servU_01 db_1]# more /home/oracle/.bash_profile # .bash_profile # Get the aliases and functions if [ -f ~/.bashrc ]; then . ~/.bashrc fi # User specific environment and startup programs PATH=$PATH:$HOME/bin export PATH export ORACLE_BASE=/u01/app/oracle export ORACLE_HOME=$ORACLE_BASE/product/10.2.0/db_1 export PATH=$ORACLE_HOME/bin:$PATH export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/lib:/usr/lib export CLASSPATH=$ORACLE_HOME/JRE:$ORACLE_HOME/jlib:$ORACLE_HOME/rdbms/jlib export NLS_LANG="SIMPLIFIED CHINESE_CHINA".ZHS16GBK export ORACLE_SID=perm stty erase ^H 发现没有错误,再次运行DBCA -> 还是报错ORA-00600: internal error code, arguments: [keltnfy-ldmInit], [46], [1], [], [], [], [], [] 最后参考metalink上信息,按照metalink上信息显示,可能是DNS或者hosts文件配置有问题,最后检查果然是是hosts文件配置不正确,修改hosts文件配置后,问题得以解决 Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.3 - Release: 10.2 to 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 getting 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 - Abstract: 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 Bug:5486074 - Abstract: 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 unaavilable. Solution The fix 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 config 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 <ip address> <fully qualified hostname> <simple or short hostname> <alias, if applicable> ( 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 <shortname> $ nslookup <long name> $ nslookup <ip address> 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.
本文出自 “O Record” 博客,请务必保留此出处http://evils798.blog.51cto.com/8983296/1420946
声明:以上内容来自用户投稿及互联网公开渠道收集整理发布,本网站不拥有所有权,未作人工编辑处理,也不承担相关法律责任,若内容有误或涉及侵权可进行投诉: 投诉/举报 工作人员会在5个工作日内联系你,一经查实,本站将立刻删除涉嫌侵权内容。