In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
Everything is normal during the RAC installation process. After shutdown and restart, the GI starts normally and the instance does not start.
[root@rac1 network-scripts] # crsctl stat res-t
NAME TARGET STATE SERVER STATE_DETAILS
Local Resources
Ora.DATA.dg
ONLINE ONLINE rac1
ONLINE ONLINE rac2
Ora.FRA.dg
ONLINE ONLINE rac1
ONLINE ONLINE rac2
Ora.LISTENER.lsnr
ONLINE ONLINE rac1
ONLINE ONLINE rac2
Ora.OCR.dg
ONLINE ONLINE rac1
ONLINE ONLINE rac2
Ora.asm
ONLINE ONLINE rac1 Started
ONLINE ONLINE rac2 Started
Ora.gsd
OFFLINE OFFLINE rac1
OFFLINE OFFLINE rac2
Ora.net1.network
ONLINE ONLINE rac1
ONLINE ONLINE rac2
Ora.ons
ONLINE ONLINE rac1
ONLINE ONLINE rac2
Cluster Resources
Ora.LISTENER_SCAN1.lsnr
1 ONLINE ONLINE rac1
Ora.LISTENER_SCAN2.lsnr
1 ONLINE ONLINE rac2
Ora.LISTENER_SCAN3.lsnr
1 ONLINE ONLINE rac2
Ora.cvu
1 ONLINE ONLINE rac2
Ora.oc4j
1 ONLINE ONLINE rac2
Ora.rac.db
1 ONLINE OFFLINE Instance Shutdown
2 ONLINE OFFLINE Instance Shutdown
Ora.rac1.vip
1 ONLINE ONLINE rac1
Ora.rac2.vip
1 ONLINE ONLINE rac2
Ora.scan1.vip
1 ONLINE ONLINE rac1
Ora.scan2.vip
1 ONLINE ONLINE rac2
Ora.scan3.vip
1 ONLINE ONLINE rac2
Check the database log immediately and find the following
[oracle@rac1 trace] $tail-200f alert_RAC1.log
USER (ospid: 3610): terminating the instance due to error 119
Instance terminated by USER, pid = 3610
Is it possible to start it by force?
[root@rac1] # srvctl start database-d RAC
PRCR-1079: unable to start resource ora.rac.db
CRS-5017: The resource action "ora.rac.db start" encountered the following error:
ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax error or unresolved network name 'rac-scan.us.oracle.com:1521'
. For details refer to "(: CLSN00107:)" in "/ u01/app/11.2.0/grid/log/rac2/agent/crsd/oraagent_oracle/oraagent_oracle.log".
CRS-5017: The resource action "ora.rac.db start" encountered the following error:
ORA-00119: invalid specification for system parameter REMOTE_LISTENER
ORA-00132: syntax error or unresolved network name 'rac-scan.us.oracle.com:1521'
. For details refer to "(: CLSN00107:)" in "/ u01/app/11.2.0/grid/log/rac1/agent/crsd/oraagent_oracle/oraagent_oracle.log".
CRS-2674: Start of 'ora.rac.db' on' rac2' failed
CRS-2674: Start of 'ora.rac.db' on' rac1' failed
CRS-2632: There are no more servers to try to place resource 'ora.rac.db' on that would satisfy its placement policy
Notice that ORA-00132: syntax error or unresolved network name 'rac-scan.us.oracle.com:1521', is mentioned in the error message, right?
Anyway, it has something to do with the Internet. Tnsping first.
[grid@rac1 ~] $tnsping rac2
TNS Ping Utility for Linux: Version 11.2.0.4.0-Production on 09-DEC-2015 00:56:12
Copyright (c) 1997, 2013, Oracle. All rights reserved.
Used parameter files:
/ u01/app/11.2.0/grid/network/admin/sqlnet.ora
Used EZCONNECT adapter to resolve the alias
Attempting to contact (DESCRIPTION= (CONNECT_DATA= (SERVICE_NAME=)) (ADDRESS= (PROTOCOL=TCP) (HOST=192.168.56.12) (PORT=1521)
OK (0 msec)
There is no problem when it comes to monitoring.
Don't worry. Take another look at tnsnames.ora.
[root@rac1 ~] # cat / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# tnsnames.ora Network Configuration File: / u01/app/oracle/product/11.2.0/dbhome_1/network/admin/tnsnames.ora
# Generated by Oracle configuration tools.
RAC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP) (HOST = rac-scan.us.oracle.com) (PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = RAC)
)
)
[root@rac1 ~] # ping rac-scan.us.oracle.com
Ping: unknown host rac-scan.us.oracle.com
This is a problem, how can the domain name I configured in DNS be unreachable? All the functions are normal during installation.
[root@rac1 ~] # nslookup rac-scan.us.oracle.com
Server: 192.168.1.1
Address: 192.168.1.1#53
* * server can't find rac-scan.us.oracle.com: NXDOMAIN
Even more problematic, how did the DNS server become 192.168.1.1?
In turn, against all the DNS configuration files, an exception was found
[root@rac1 ~] # cat / etc/resolv.conf
; generated by / sbin/dhclient-script
Nameserver 192.168.1.1
Nameserver 192.168.0.1
How did you get back to the original configuration of the operating system? This refers to another configuration file.
[root@rac2 network-scripts] # cat ifcfg-eth0
DEVICE=eth0
TYPE=Ethernet
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
NAME= "System eth0"
USERCTL=no
Did you notice the PEERDNS=yes item?
In the 5.0s DNS server is written in the / etc/resolv.conf file, but in the 6.0th era DNS can be written in / etc/resolv.conf, but at this time you need to add the PEERDNS=no configuration in the / etc/sysconfig/network-scripts/ifcfg-eth0 file, otherwise the contents of the / etc/resolv.conf file will be rewritten every time the network card is restarted.
Http://blog.chinaunix.net/uid-26495963-id-3230810.html
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.