ODA (Oracle Database Appliance): Deployment without DNS fails at Step 16

Asset ID:	1-72-2048836.1
Update Date:	2018-02-22
Keywords:

Solution Type Problem Resolution Sure

Solution 2048836.1 : ODA (Oracle Database Appliance): Deployment without DNS fails at Step 16

Applies to:

Oracle Database Appliance Software - Version 12.1.2.3 to 12.1.2.5 [Release 12.1]
Oracle Database Appliance - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
This is applicable to ODA software version 12.1.2.3.0, 12.1.2.4.0 and 12.1.2.5.0

Symptoms

During the deployment, if there is no DNS setup, deployment failed at Step 16 GIConfigAssists, post configuration assistants

Deployment hang in Step 16  GIConfigAssists

INFO   : 2015-05-07 17:30:32
INFO   : Step 16  GIConfigAssists
INFO   : Running post configuration assistants
INFO   : This is root, will become oracle and run: /bin/su oracle -c /usr/bin/ssh -l oracle rwsoda308c1n1 /u01/app/12.1.0.2/grid/cfgtoollogs/configToolAllCommands RESPONSE_FILE=/opt/oracle/oak/onecmd/tmp/postcfgassts.rsp > /opt/oracle/oak/onecmd/tmp/configToolAllCommands-rwsoda308c1n1-log 2>&1
INFO   : Running on the local node: /bin/su oracle -c /u01/app/12.1.0.2/grid/cfgtoollogs/configToolAllCommands RESPONSE_FILE=/opt/oracle/oak/onecmd/tmp/postcfgassts.rsp > /opt/oracle/oak/onecmd/tmp/configToolAllCommands-rwsoda308c1n1-log 2>&1
INFO   : setting CHM repo size....
INFO   : did not do scp for node: rwsoda308c1n1
INFO   : Running as root: /usr/bin/ssh -l root rwsoda308c1n1 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20150507174137.sh
INFO   : Running as root: /usr/bin/ssh -l root rwsoda308c1n2 /opt/oracle/oak/onecmd/tmp/DoAllcmds-20150507174137.sh

Changes

Your are doing a new deployment on ODA OAK v. 12.1.2.3.0, 12.1.2.4.0, 12.1.2.5.0 without DNS

Cause

This is Bug 21394146

Solution

The obvious workaround is to setup a DNS as this is also a best practice. If the DNS setup is not possible you can folow the steps below

Manual Steps

1. NETCA, as grid user issue the following command:

/u01/app/12.1.0.2/grid/bin/netca /orahome /u01/app/12.1.0.2/grid /orahnam OraGrid12102 /instype typical /inscomp client,oraclenet,javavm,server,ano /insprtcl tcp /cfg local /authadp NO_VALUE /responseFile /u01/app/12.1.0.2/grid/network/install/netca_typ.rsp /silent /silent /ouiinternal

Example:

[grid@oda101 ~]$ /u01/app/12.1.0.2/grid/bin/netca /orahome /u01/app/12.1.0.2/grid /orahnam OraGrid12102 /instype typical /inscomp client,oraclenet,javavm,server,ano /insprtcl tcp /cfg local /authadp NO_VALUE /responseFile /u01/app/12.1.0.2/grid/network/install/netca_typ.rsp /silent /silent /ouiinternal

Parsing command line arguments:
    Parameter "orahome" = /u01/app/12.1.0.2/grid
    Parameter "orahnam" = OraGrid12102
    Parameter "instype" = typical
    Parameter "inscomp" = client,oraclenet,javavm,server,ano
    Parameter "insprtcl" = tcp
    Parameter "cfg" = local
    Parameter "authadp" = NO_VALUE
    Parameter "responsefile" = /u01/app/12.1.0.2/grid/network/install/netca_typ.rsp
    Parameter "silent" = true
    Parameter "silent" = true
    Parameter "ouiinternal" = true
Done parsing command line arguments.
Oracle Net Services Configuration:
Profile configuration complete.
Profile configuration complete.
Listener "LISTENER" already exists.
Oracle Net Services configuration successful. The exit code is 0

2. Post ASM configure, as grid user issue the following command:

/u01/app/12.1.0.2/grid/bin/asmca -silent -postConfigureASM -oui_internal

Example:

[grid@oda101 ~]$ /u01/app/12.1.0.2/grid/bin/asmca -silent -postConfigureASM -oui_internal
SYS_PASSWORD_PROMPT
welcome1
ASMSNMP_PASSWORD_PROMPT
welcome1

PostConfiguration completed successfully

3. Check for the the MGMTDB (Grid Infrastructure Management Repository) presence, issuing the following command:

/u01/app/12.1.0.2/grid/bin/srvctl status mgmtdb

[grid@oda101 ~]$ /u01/app/12.1.0.2/grid/bin/srvctl status mgmtdb
Database is enabled
Instance -MGMTDB is running on node oda101

4. Get the cluster name, as grid user issue:

/u01/app/12.1.0.2/grid/bin/cemutlo -n

Example:
# /u01/app/12.1.0.2/grid/bin/cemutlo -n
oda10-c

5. Create the MGMTDB pluggable database, as grid user execute:

/u01/app/12.1.0.2/grid/bin/dbca -silent -createPluggableDatabase -sourceDB -MGMTDB -pdbName <cluster_name> -createPDBFrom RMANBACKUP -PDBBackUpfile /u01/app/12.1.0.2/grid/assistants/dbca/templates/mgmtseed_pdb.dfb -PDBMetadataFile /u01/app/12.1.0.2/grid/assistants/dbca/templates/mgmtseed_pdb.xml -createAsClone true -internalSkipGIHomeCheck -oui_internal

Example:
[grid@oda10 ~]$ /u01/app/12.1.0.2/grid/bin/dbca -silent -createPluggableDatabase -sourceDB -MGMTDB -pdbName oda10-c -createPDBFrom RMANBACKUP -PDBBackUpfile /u01/app/12.1.0.2/grid/assistants/dbca/templates/mgmtseed_pdb.dfb -PDBMetadataFile /u01/app/12.1.0.2/grid/assistants/dbca/templates/mgmtseed_pdb.xml -createAsClone true -internalSkipGIHomeCheck -oui_internal
Creating Pluggable Database
4% complete
12% complete
21% complete
38% complete
55% complete
85% complete
Completing Pluggable Database Creation
100% complete
Look at the log file "/u01/app/grid/cfgtoollogs/dbca/_mgmtdb/oda10-c/_mgmtdb.log" for further details.

Note: The PDB name (cluster_name) must be at least 1 character and at most 30 characters, should start with an alphabetical character and must include only alphabetical characters, numbers or the '_' character. It can not contains hyphen '-'. If the clsuter name is in example 'cluster-10', the PDB name must be 'cluster_10'.

6. Resize the Cluster Health Monitor repository, as root user issue

/u01/app/12.1.0.2/grid/bin/oclumon manage -repos changerepossize 3895

Example:
[root@oda101 ~]# /u01/app/12.1.0.2/grid/bin/oclumon manage -repos changerepossize 3895
The Cluster Health Monitor repository was successfully resized.The new retention is 259200 seconds.

7. Continue the ODA deploy from the step17, as root:

- ODA BM (Bare Metal)

/opt/oracle/oak/onecmd/GridInst.pl -r 17-23

- ODA VP (Virtualized Platform)

/opt/oracle/oak/onecmd/GridInst.pl -o -r 17-23

Automation Script

The above steps can be executed automatically issuing the attached perl script: nodnswa.pl.

"nodnswa.pl" is NOT supported by Oracle World Wide Technical Support.
The script has been tested and appears to work as intended.

- Move it on ODA (ODA_BASE - node0)
- Set exec permission:

chmod +x nodnswa.pl

- Run it as root:

<path>/nodnswa.pl

Example:
# ./nodnswa.pl
2015-08-29 09:11:14: I Setting up the required step
2015-08-29 09:11:14: I Executing subStep1 - NETCA
2015-08-29 09:11:19: I Executing subStep2 - Post ASM Configure
2015-08-29 09:11:28: I Executing subStep3 - MGMTDB Status
2015-08-29 09:11:29: I Executing subStep4 - Get cluster name
2015-08-29 09:11:29: I Executing subStep5 - MGMTDB Plugable database creation in progress...
2015-08-29 09:11:35: I Executing subStep6 - Resize the Cluster Health Monitor repository
2015-08-29 09:11:36: I All sub-steps have been completed, you can now proceed with the ODA deploy, issue the following command:

/opt/oracle/oak/onecmd/GridInst.pl -o -r 17-23

References

<BUG:21394146> - PLS SKIP NSLOOKUP SCAN RESOLUTION DURING DEPLOY FOR NO DNS SETUP

Attachments

This solution has no attachment