Yo may need to change your existing IP or hostname after installation for your setup
In this case I need to change my current IP to another on my standalone GI.
Operation System –> AIX 7.1
Oracle GI Version –> 12.1.0.2
Please perform the next steps after the hostname and/or IP address was updated/changed/modified in the Oracle Restart configuration:
Step 1) Configure the CSS & OHAS services as root user as follows:
[root@yourhostname]./roothas.pl -deconfig -force
Using configuration parameter file: ./crsconfig_params
[2020/02/23 09:48:06 CLSRSC-337: Successfully deconfigured Oracle Restart stack
[root@yourhostname] ./roothas.pl
Using configuration parameter file: ./crsconfig_params
LOCAL ADD MODE
Creating OCR keys for user ‘grid’, privgrp ‘oinstall’..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user ‘root’, privgrp ‘system’..
Operation successful.
CRS-4664: Node yourhostname successfully pinned.
2020/02/23 09:48:34 CLSRSC-330: Adding Clusterware entries to file ‘/etc/inittab’
yourhostname 2020/02/23 10:49:12 /u01/app/12.1.0/grid/cdata/yourhostname/backup_20160223_104912.olr 1972992864
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘yourhostname’
CRS-2673: Attempting to stop ‘ora.evmd’ on ‘yourhostname’
CRS-2677: Stop of ‘ora.evmd’ on ‘yourhostname’ succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘yourhostname’ has completed
CRS-4133: Oracle High Availability Services has been stopped.
CRS-4123: Oracle High Availability Services has been started.
2020/02/23 09:49:45 CLSRSC-327: Successfully configured Oracle Restart for a standalone server
Step 2) Please perform the next steps as oracle or grid OS user (as the Grid Infrastructure OS owner):
From DOC–> <$GI_HOME>/bin/crsctl modify resource “ora.cssd” -attr “AUTO_START=1”
[grid@yourhostname] ./crsctl modify resource “ora.cssd” -attr “AUTO_START=1” -unsupported
Step 3) Restart the OHAS stack as grid or oracle OS user (as the Grid Infrastructure OS owner):
From DOC–> <$GI_HOME>/bin/crsctl stop has
[grid@yourhostname] ./crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on ‘yourhostname’
CRS-2673: Attempting to stop ‘ora.evmd’ on ‘yourhostname’
CRS-2677: Stop of ‘ora.evmd’ on ‘yourhostname’ succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on ‘yourhostname’ has completed
Step 4) Check the CSS & OHAS state as grid or oracle OS user (as the Grid Infrastructure OS owner):
From DOC–> <$GI_HOME>/bin/crsctl start has
[grid@yourhostname] ./crsctl start has
CRS-4123: Oracle High Availability Services has been started.
From DOC–> <$GI_HOME>/bin/crsctl check has
[grid@yourhostname] ./crsctl check has
CRS-4638: Oracle High Availability Services is online
From DOC–> <$GI_HOME>/bin/crsctl check css
[grid@yourhostname] ./crsctl check css
CRS-4529: Cluster Synchronization Services is online
FromDOC–> <$GI_HOME>/bin/ crsctl stat resource
[grid@yourhostname] ./crsctl stat resource
NAME=ora.cssd
TYPE=ora.cssd.type
TARGET=ONLINE
STATE=ONLINE on yourhostname
NAME=ora.diskmon
TYPE=ora.diskmon.type
TARGET=OFFLINE
STATE=OFFLINE
NAME=ora.evmd
TYPE=ora.evm.type
TARGET=ONLINE
STATE=ONLINE on yourhostname
NAME=ora.ons
TYPE=ora.ons.type
TARGET=OFFLINE
STATE=OFFLINE
FromDOC–> <$GI_HOME>/bin/crsctl stat res -t
[grid@yourhostname] ./crsctl stat res -t
——————————————————————————–
Name Target State Server State details
——————————————————————————–
Local Resources
——————————————————————————–
ora.ons
OFFLINE OFFLINE yourhostname STABLE
——————————————————————————–
Cluster Resources
——————————————————————————–
ora.cssd
1 ONLINE ONLINE yourhostname STABLE
ora.diskmon
1 OFFLINE OFFLINE STABLE
ora.evmd
1 ONLINE ONLINE yourhostname STABLE
——————————————————————————–
Note: If the CSS & OHAS service did NOT start, then you will need to reboot the Linux/unix box and check them again.
Step 5) Recreate the default listener (LISTENER) using port 1521 (or using your desired port), thru the NETCA GUI located on the new Grid Infrastructure Oracle Home (or manually if you do not have graphical access) as grid or oracle OS user (as the Grid Infrastructure OS owner):
From DOC–> srvctl add listener
[grid@yourhostname] srvctl add listener
From DOC–> srvctl start listener
[grid@yourhostname] srvctl start listener
[grid@yourhostname] ps -ef |grep tns
grid 30605404 1 0 10:06:59 – 0:00 /u01/app/12.1.0/grid/bin/tnslsnr LISTENER -no_crs_notify -inherit
Step 6) Please create the init+ASM.ora file on the <$GI_HOME>/dbs directory with the next parameters:
[grid@yourhostname] cat init+ASM.ora
asm_diskgroups= ”
asm_diskstring= ”
instance_type=’asm’
large_pool_size=12M
Step 7) Add the ASM instance as grid or oracle OS user (as the Grid Infrastructure OS owner):
From DOC–> <$GI_HOME>/bin/srvctl add asm [grid@yourhostname] ./srvctl add asm Step 8) Enable ASM instance Auto Start as grid or oracle OS user (as the Grid Infrastructure OS owner) as follow:
From DOC–> <$GI_HOME>/bin/crsctl modify resource “ora.asm” -attr “AUTO_START=1”
[grid@yourhostname]/crsctl modify resource “ora.asm” -attr “AUTO_START=1” -unsupported
Step 9) Make sure the disks are discovered by kfod as grid or oracle OS user (as the Grid Infrastructure OS owner) as follow:
Example:
From DOC–> <$GI_HOME>/bin/kfod asm_diskstring=’ORCL:’ disks=all Or From DOC–> <$GI_HOME>/bin/kfod asm_diskstring=’/’ disks=all
[grid@yourhostname] kfod asm_diskstring=’/dev/rhdisk*’ disks=all FromDOC–> export ORACLE_SID=+ASM FromDOC–> <$GI_HOME>/bin/sqlplus “/as sysasm” SQL> startup pfile=init+ASM.ora –#init file from point #6 SQL> show parameter asm
Step 10) Validate that the candidate disks are being discovered:
SQL> select path from v$asm_disk; SQL> create spfile from pfile;
Step 11) Add the new ASM spfile and listener to the new ASM instance resource:
FromDOC–> <$GI_HOME>/bin/srvctl modify asm -p [grid@yourhostname] ./rsrvctl modify asm -p ‘+oradata/ASM/ASMPARAMETERFILE/REGISTRY.253.904564109’ FromDOC–> <$GI_HOME>/bin/srvctl modify asm -l LISTENER [grid@yourhostname] srvctl modify asm -l LISTENER
Step 12) Validate the OHAS (Oracle Restart) services start as follows:
FromDOC–> <$GI_HOME>/bin/crsctl stop has
FromDOC–> <$GI_HOME>/bin/crsctl start has
FromDOC–> <$GI_HOME>/bin/crsctl stat res
FromDOC–> <$GI_HOME>/bin/crsctl stat res -t
Step 13) Add database to CLusterware
srvctl add database -db DB_NAME_HERE -dbname DB_NAME_HERE -oraclehome /u01/app/oracle12/product/12.1.0/dbhome -spfile +ORADATA/DB_NAME_HERE/spfileDB_NAME_HERE.ora -role PRIMARY -instance DB_NAME_HERE -diskgroup ORADATA,ORAFRA,ORAREDO
Step 14) reboot Server
Reference:
How to change Hostname / IP for a Grid Infrastructure Oracle Restart Standalone Configuration (SIHA) (Doc ID 1552810.1)