Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to solve the problem that nodes cannot get up after DG switching". The explanation content in this article is simple and clear, and it is easy to learn and understand. Please follow the idea of Xiaobian and go deep into it slowly to study and learn "how to solve the problem that nodes cannot get up after DG switching" together.

The day before yesterday, after cutting a set of rac, DG was obtained, and the database of two nodes was not up. The manual startup results are as follows:

[oracle@mssdb1 ~]$ sqlplus / as sysdbaSQL*Plus: Release 11.2.0.4.0 Production on Sat Aug 11 00:57:39 2018Copyright (c) 1982, 2013, Oracle. All rights reserved.Connected to an idle instance.SQL> startup nomountORA-00119: invalid specification for system parameter REMOTE_LISTENERORA-00132: syntax error or unresolved network name 'mssdb-scan:1821'SQL>

Check CRS resources, rac node resources, no problem, finally found that the hosts file can not be identified, the original configuration of node information directly when using IP, not alias, check the permissions of the hosts file, change permissions after solving.

[root@mssdb2 ~]# ls -l /etc/hosts-rw-r---- 1 root 675 Aug 10 16:47 /etc/hosts [root@mssdb2 ~]# chmod 644 /etc/hosts Thank you for reading. The above is the content of "How to solve the problem that the node cannot get up after DG switching". After studying this article, I believe you have a deeper understanding of how to solve the problem that the node cannot get up after DG switching. The specific usage needs to be verified by practice. Here is, Xiaobian will push more articles related to knowledge points for everyone, welcome to pay attention!

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.