[INS-40718] Single Client Access Name (SCAN): could not be resolved. ( LDOMS & Zones)

Cause

The name you provided as the SCAN could not be resolved using TCP/IP host name lookup. Action-Provide name to use for the SCAN for which the domain can be resolved

Global Zone :
=============

# svccfg
svc:> select name-service/switch
svc:/system/name-service/switch> setprop config/host = astring: "files dns"
svc:/system/name-service/switch> select system/name-service/switch:default
svc:/system/name-service/switch:default> refresh
svc:/system/name-service/switch:default> validate
svc:/system/name-service/switch:default> exit

# svcadm refresh name-service/switch

# svcadm restart /system/name-service-cache;

then, I can resolve host using telnet/ping.

Comments

Post a Comment

Popular posts from this blog

CRS-2883: Resource 'ora.asm' failed during Clusterware stack start

Symptoms ======== root@oraprod02:~# /u01/app/12.1.0.2/grid/crs/install/rootcrs.pl -postpatch Using configuration parameter file: /u01/app/12.1.0.2/grid/crs/install/crsconfig_params 2017/11/05 15:57:38 CLSRSC-4015: Performing install or upgrade action for Oracle Trace File Analyzer (TFA) Collector. 2017/11/05 15:58:08 CLSRSC-4003: Successfully patched Oracle Trace File Analyzer (TFA) Collector. 2017/11/05 15:58:13 CLSRSC-329: Replacing Clusterware entries in file '/etc/inittab' CRS-4123: Oracle High Availability Services has been started. CRS-4133: Oracle High Availability Services has been stopped. CRS-4123: Starting Oracle High Availability Services-managed resources CRS-2672: Attempting to start 'ora.evmd' on 'oraprod02' CRS-2672: Attempting to start 'ora.mdnsd' on 'oraprod02' CRS-2676: Start of 'ora.mdnsd' on 'oraprod02' succeeded CRS-2676: Start of 'ora.evmd' on 'oraprod02' succeeded CRS-2672: Attempting to st...
Read more

How to Downgrade 19C Grid Infrastructure to 12.1.0.2

ENVIRONMENT DETAILS: 2 NODES – ambeth01 and ambeth02 Grid owner – oragrid 19C ORACLE_HOME(current) – > /u01/app/19.0.0.0/grid 12C ORACLE_HOME (old) -> /u01/app/12.1.0.2/grid/bin Check the current grid version:( check on both the nodes) [oragrid@ambeth01 ~]$ crsctl query crs activeversion Oracle Clusterware active version on the cluster is [19.0.0.0.0] [oragrid@ambeth01 ~]$ crsctl query crs softwareversion -all Oracle Clusterware version on node [ambeth01] is [19.0.0.0.0] Oracle Clusterware version on node [ambeth02] is [19.0.0.0.0] [oragrid@ambeth01 ~]$ 1. As the first step for downgrade, remove the MGMTDB. Move the MGMTDB database on node1, if its running on node2. [oragrid@ambeth01 ~]$ ps -ef|grep pmon oragrid    952 21344  0 19:38 pts/0    00:00:00 grep --color=auto pmon oragrid   8102     1  0 14:32 ?        00:00:02 asm_pmon_+ASM1 oragrid   8609   ...
Read more