How to change Hostname / IP for a Grid Infrastructure Oracle Restart Standalone Configuration (SIHA) 11.2 and Later (Doc ID 1552810.1)

In this Document

Goal

Solution

Community Discussions

References

---

APPLIES TO:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

GOAL

This document provides (in detail) the required & mandatory steps that need to be executed after the hostname was updated/changed/modified.

If you intend to change only the IP address then we dont need to do anything such as deconfig/reconfig.

SOLUTION

 Therefore, please perform the next steps after the hostname was updated/changed/modified in the Oracle Restart configuration:

1) Configure the CSS & OHAS services as root user as follows:

# <Grid Infrastructure Oracle Home>/crs/install/roothas.pl -deconfig -forceFor 18c, <Grid Infrastructure Oracle Home>/crs/install/roothas.sh -deconfig -force
# <Grid Infrastructure Oracle Home>/crs/install/roothas.pl

# cd <12.1 Grid infrastructure Oracle Home>/crs/install
# perl roothas.sh -deconfig -force
--This removes any configuration on the system that referenced the old host name.
# cd <12.1 Grid infrastructure Oracle Home>
# ./root.shFor 12.2,<12.2 Grid infrastructure Oracle Home>/crs/install/roothas.pl                                                                                                                                          Go to the grid home's bin directory. Use the srvctl add database command with the -c SINGLE flag to add the database in an Oracle Restart configuration.
Also use the srvctl add command to add the listener, the Oracle ASM instance, all Oracle ASM disk groups, and any database services to the Oracle Restart configuration.

2) Please perform the next steps as oracle or grid OS user (as the Grid Infrastructure OS owner): 

$> <Grid Infrastructure Oracle Home>/bin/crsctl modify resource "ora.cssd" -init -attr "AUTO_START=1"  -unsupported

 NOTE: "-unsupported" is not required for 11.2 version

3) Restart the OHAS stack as grid or oracle OS user (as the Grid Infrastructure OS owner):

$> <Grid Infrastructure Oracle Home>/bin/crsctl stop has

$> <Grid Infrastructure Oracle Home>/bin/crsctl start has

4) Check the CSS & OHAS state as grid or oracle OS user (as the Grid Infrastructure OS owner):

$> <Grid Infrastructure Oracle Home>/bin/crsctl check has

$> <Grid Infrastructure Oracle Home>/bin/crsctl check css

$> <Grid Infrastructure Oracle Home>/bin/ crsctl stat resource

$> <Grid Infrastructure Oracle Home>/bin/crsctl stat res -t

Note: If the CSS & OHAS service did NOT start, then you will need to reboot the Linux/unix box and check them again.

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):

$> srvctl add listener

$> srvctl start listener

6) Please create the init+ASM.ora file on the <Grid Infrastructure Oracle Home>/dbs directory with the next parameters:

asm_diskgroups= <list of diskgroups>

asm_diskstring= '/dev/oracleasm/disks/*'  

instance_type='asm'

large_pool_size=12M

7) Add the ASM instance as grid or oracle OS user (as the Grid Infrastructure OS owner):

$> <Grid Infrastructure Oracle Home>/bin/srvctl add asm

$> <12.1 Grid Infrastructure Oracle Home>/bin/srvctl add asm

8) Enable ASM instance Auto Start as grid or oracle OS user (as the Grid Infrastructure OS owner) as follow: 

$> <Grid Infrastructure Oracle Home>/bin/crsctl modify resource "ora.asm" -init -attr "AUTO_START=1"  -unsupported

 NOTE: "-unsupported" is not required for 11.2 version

9) Make sure the disks are discovered by kfod as grid or oracle OS user (as the Grid Infrastructure OS owner) as follow:

Example:

$> <Grid Infrastructure Oracle Home>/bin/kfod asm_diskstring='ORCL:*' disks=all

Or

$> <Grid Infrastructure Oracle Home>/bin/kfod asm_diskstring='<full path ASM disks location>/*' disks=all

10) If so, then startup the ASM instance as grid or oracle OS user (as the Grid Infrastructure OS owner) as follow:

$> export ORACLE_SID=+ASM

$> <Grid Infrastructure Oracle Home>/bin/sqlplus “/as sysasm”

SQL> startup pfile=init+ASM.ora --#init file from point #6

SQL> show parameter asm

11) Validate that the candidate disks are being discovered:

SQL> select  path  from v$asm_disk;

12) Create a new ASM instance spfile:

SQL> create spfile from pfile;

13) Add the new ASM spfile and listener to the new ASM instance resource:

$> <Grid Infrastructure Oracle Home>/bin/srvctl modify asm  -p <spfile full path>

$> <Grid Infrastructure Oracle Home>/bin/srvctl modify asm  -l LISTENER

14) Validate the OHAS (Oracle Restart) services start as follows: 

$> <Grid Infrastructure Oracle Home>/bin/crsctl  stop has

$> <Grid Infrastructure Oracle Home>/bin/crsctl  start has

$> <Grid Infrastructure Oracle Home>/bin/crsctl  stat res

$> <Grid Infrastructure Oracle Home>/bin/crsctl  stat res -t

---

Community Discussions

Still have questions? Use the communities window below to search for similar discussions or start a new discussion on this subject. (Window is the live community not a screenshot)

Click here to open in main browser window

REFERENCES

NOTE:363609.1 - Preparing For Changing the IP Address, Hostname or Domain Of Oracle Database Servers
NOTE:1645523.1 - Alternative Procedure To Upgrade ASM From Release 10.2 Or 11.1 To Release 11.2.0.# or To 12.1.0.1 On Unix/Linux Configurations (Standalone) Using ASM Role separation.
NOTE:986740.1 - How to Reconfigure Oracle Restart
NOTE:1434351.1 - Alternative Way To Upgrade An ASM Standalone Configuration From Release 11.2.0.<#> to release 11.2.0.<#>.
NOTE:293678.1 - How To Reconfigure DB Control After a Hostname, Domainname or Listener Change Has Occurred On The Server
NOTE:1422517.1 - Reconfiguring & Recreating The 11gR2/12cR1 Restart/OHAS/SIHA Stack Configuration (Standalone) / How to Reconfigure Oracle Restart
NOTE:887658.1 - Reconfigure HAS and CSS for nonRAC ASM on 11.2
https://docs.oracle.com/database/121/LADBI/app_ts.htm#LADBI7947

Steps To Shutdown(stop)/Startup(start) CRS, OHAS, ASM, RDBMS & ACFS Services on a RAC Cluster 11.2 & 12.1 Configuration (Doc ID 1355977.1)

n this Document

Goal

Solution

Additional Steps Required When ACFS filesystem are involved:

Community Discussions

References

---

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]
Oracle Database - Enterprise Edition - Version 12.2.0.1 to 12.2.0.1 [Release 12.2]
Information in this document applies to any platform.
***Checked for relevance on 21-Jan-2014***

GOAL

The present document provides in detail the steps to shutdown/startup The CRS, OHAS, ASM & RDBMS Services on a RAC Cluster 11.2 & 12.1 configuration:

SOLUTION

1) Connect to node #1, then please check if the CRS/OHAS & services are enabled to autostart as follow (repeat this step on each node):

# $GRID_ORACLE_HOME/bin/crsctl config crs

2) If not, then you can enable it as follow (repeat this step on each node):

# $GRID_ORACLE_HOME/bin/crsctl enable crs

3) Shutdown the services on each node as follow:

# $GRID_ORACLE_HOME/bin/crsctl stop crs

4) Verify the services were/are down (repeat this step on each node):

# $GRID_ORACLE_HOME/bin/crsctl status resource -t

5) Then start the services on node #1 as follow (only on first node):

# $GRID_ORACLE_HOME/bin/crsctl start crs

6) Wait 1 minute, then validate the services started & diskgroups were mounted (only on first node):

# $GRID_ORACLE_HOME/bin/crsctl status resource -t

7) Then start the services on node #2 as follow:

# $GRID_ORACLE_HOME/bin/crsctl start crs

8) Wait 1 minute, then validate the services started & diskgroups were mounted on node #2:

# $GRID_ORACLE_HOME/bin/crsctl status resource -t

9) If there are more nodes in the RAC, then repeat the same steps (7-8).

10) Then check the status of the clusterware globally as follows:

# crsctl check cluster -all

Sample output:

[root@asmgrid1 ~]# crsctl check cluster -all
**************************************************************
asmgrid1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

asmgrid2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

Note 1: Alternatively, you can stop and start the cluster globally as follows:

Stop:

[root@asmgrid1 ~]# crsctl stop cluster  -all   [-f]

  

Start:

[root@asmgrid1 ~]# crsctl start cluster  -all   

  

Note 2: For 11gR2 RAC ACFS configurations please check the next information:
https://docs.oracle.com/cd/E11882_01/readmes.112/e41331/chapter11204.htm#BABIJJAF

2.9.1Oracle ACFS and Oracle Clusterware Stack Shut DownWhen attempting to shut down Oracle Clusterware, the Oracle Clusterware stack may report that it did not successfully stop on selected nodes (reference Bug 8651848). If the database home is on Oracle ACFS, then you may receive the following error:

CRS-5014: Agent orarootagent.bin timed out starting process acfsmount for action

This error can be ignored.
Alternatively, the Oracle Clusterware stack may report that it did not successfully stop on selected nodes due to the inability to shut down the Oracle ACFS resources. If this occurs, take the following steps:

• Ensure that all file system activity to Oracle ACFS mount points is quiesced by shutting down programs or processes and retry the shutdown.
• If the ora.registry.acfs resource check function times out, or the resource exhibits a state of UNKNOWN or INTERMEDIATE, then this may indicate an inability to access the Oracle Cluster Registry (OCR). The most common cause of this is a network failure. The commands "acfsutil registry" and "ocrcheck" may give you a better indicator of the specific error. Clear this error and attempt to stop Oracle Clusterware again.

For 12cR1
https://docs.oracle.com/database/121/READM/chapter12102.htm#READM135
2.12.1 Oracle ACFS and Oracle Clusterware Stack Shut Down
Some non-Oracle Grid Infrastructure usage of mount points prevents unmounts and volume disables in the kernel (reference Bug 8651848). Examples include:
Network File System (NFS)
Samba/Common Internet File System (CIFS)
If this reflects your situation, ensure that you discontinue usage of these features before trying to initiate a stack shutdown, file system unmount, or volume disable.
Additionally, certain user space processes and system processes may use the file system or volume device in a way that prevents the Oracle Grid Infrastructure stack from shutting down during a patch or upgrade.
If this occurs, use the lsof and fuser commands (Linux and UNIX) or the handle and wmic commands (Windows) to identify processes which are active on the Oracle ACFS file systems and Oracle ADVM volumes. To ensure that these processes are no longer active, dismount all Oracle ACFS file systems or Oracle ADVM volumes and issue an Oracle Clusterware shutdown. Otherwise, errors may be issued during Oracle Clusterware shutdown relating to activity on Oracle ACFS file systems or Oracle ADVM volumes which will stop the successful shutdown of Oracle Clusterware.

Additional Steps Required When ACFS filesystem are involved:

 Note 3:  If ACFS filesystems are associated with this ASM Cluster configuration, then the ACFS filesystems need to be dismounted first, this is because if you try to dismount an ACFS filesystem (or any other regular Unix/Linux filesystem)  that is being used/accessed at that time (same as a regular unix/Linux filesystem)  then you will get a “Resource Busy” error, therefore “crsctl stop crs” statement will fail as expected.

You will need to perform the following additional steps instead:


A) Dismount all the ACFS filesystems running in the cluster as follows (as root user):

# srvctl stop filesystem -d volume_device_name [-n node_name] [-f]

  

Where:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-d  <volume_device_name>  :The Oracle ACFS volume device name
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-n  <node_name>  : The name of a node

If you do not specify this option, then the utility stops the volume resource on all active nodes in the cluster.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-f  : This option stops the file system and also stops any databases or other resources that depend on this file system.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


Example:

[root@asmgrid1 ~]# df -k | grep asm
/dev/asm/volnew1-347  14680064    159700  14520364   2% /u01/app/grid/acfsmounts/acfsdgnew_volnew1
/dev/asm/vol_oh1-115  35651584   4590104  31061480  13% /u04acfs

#  srvctl stop filesystem -d  /dev/asm/volnew1-347   -f

#  srvctl stop filesystem -d  /dev/asm/vol_oh1-115   -f

  

B) Make sure the ACFS filesystem(s) was/were dismounted on all the nodes:

# df -k | grep asm

  

C) Then perform the steps described in the following document:

=)>     Steps To Shutdown/Startup The CRS, OHAS, ASM & RDBMS Services on RAC 11.2 Configuration. (Doc ID 1355977.1)

  

  

Note: To manually remount the ACFS filesystem back (CRS managed) the next statement needs to be executed as root user:

# srvctl start filesystem -d volume_device_name [-n node_name]

  

  

---

Community Discussions

Still have questions? Use the communities window below to search for similar discussions or start a new discussion on this subject. (Window is the live community not a screenshot)

Click here to open in main browser window

REFERENCES

NOTE:1609127.1 - How To Validate ASM Instances And Diskgroups On A RAC Cluster (When CRS Does Not Start).
NOTE:1355977.1 - Steps To Shutdown(stop)/Startup(start) CRS, OHAS, ASM, RDBMS & ACFS Services on a RAC Cluster 11.2 & 12.1 Configuration

NOTE:1093890.1 - Steps To Shutdown/Startup The Exadata & RDBMS Services and Cell/Compute Nodes On An Exadata Configuration

How To Relink The Oracle Grid Infrastructure Standalone (Restart) Installation Or Oracle Grid Infrastructure RAC/Cluster Installation (11.2 or 12c). (Doc ID 1536057.1)

In this Document

Goal

Solution

A) How To Relink The Oracle Grid Infrastructure Standalone (Restart) Installation.

B) How To Relink The Oracle Grid Infrastructure RAC/Cluster Installation.

Community Discussions

References

---

APPLIES TO:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

GOAL

In order to relink the Oracle Grid Infrastructure Standalone (Restart) Installation (Non-RAC) or  Oracle Grid Infrastructure RAC/Cluster Installation (11.2 or 12c)  please follow the next steps:

SOLUTION

A) How To Relink The Oracle Grid Infrastructure Standalone (Restart) Installation.

In order to relink the Oracle Grid Infrastructure Standalone (Restart) Installation (Non-RAC), please follow the next steps:

1) Stop the OHAS stack (as “grid” OS user):

[grid@dbaasm ~]$ id
uid=1100(grid) gid=1000(oinstall) groups=1000(oinstall),1100(asmadmin),1200(dba),1300(asmdba),1301(asmoper)


[grid@dbaasm ~]$ . oraenv
ORACLE_SID = [+ASM] ? +ASM
The Oracle base remains unchanged with value /u01/app/grid

[grid@dbaasm ~]$ crsctl stop has
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'dbaasm'
CRS-2673: Attempting to stop 'ora.SPFILE.dg' on 'dbaasm'
CRS-2673: Attempting to stop 'ora.db1.db' on 'dbaasm'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'dbaasm'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'dbaasm' succeeded
CRS-2677: Stop of 'ora.db1.db' on 'dbaasm' succeeded
CRS-2673: Attempting to stop 'ora.DATA.dg' on 'dbaasm'
CRS-2673: Attempting to stop 'ora.RECO.dg' on 'dbaasm'
CRS-2677: Stop of 'ora.DATA.dg' on 'dbaasm' succeeded
CRS-2677: Stop of 'ora.RECO.dg' on 'dbaasm' succeeded
CRS-2677: Stop of 'ora.SPFILE.dg' on 'dbaasm' succeeded
CRS-2673: Attempting to stop 'ora.asm' on 'dbaasm'
CRS-2677: Stop of 'ora.asm' on 'dbaasm' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'dbaasm'
CRS-2677: Stop of 'ora.cssd' on 'dbaasm' succeeded
CRS-2673: Attempting to stop 'ora.evmd' on 'dbaasm'
CRS-2677: Stop of 'ora.evmd' on 'dbaasm' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'dbaasm' has completed
CRS-4133: Oracle High Availability Services has been stopped.

2) Connect as root user (different session) and unlock the Oracle Grid Infrastructure Standalone installation as follows:

[grid@dbaasm ~]$ su -
Password:
[root@dbaasm ~]# id

uid=0(root) gid=0(root) groups=0(root),1(bin),2(daemon),3(sys),4(adm),6(disk),10(wheel)

[root@dbaasm ~]# . oraenv
ORACLE_SID = [root] ? +ASM
The Oracle base has been set to /u01/app/grid

[root@dbaasm ~]# $ORACLE_HOME/crs/install/roothas.pl -unlock
Using configuration parameter file: /u01/app/grid/product/11.2.0/grid/crs/install/crsconfig_params

Successfully unlock /u01/app/grid/product/11.2.0/grid

  

Note: On 12.1/12.2/18c releases, roothas.sh can be used instead of roothas.pl. Command to unlock the GI home is <GI home>/crs/install/roothas.sh -unlock

3) Then relink the Oracle Grid Infrastructure Standalone installation as follows (as grid user):

3.1) First of all, rename the $ORACLE_HOME/rdbms/lib/config.o file (located at the Oracle Grid Infrastructure Standalone installation) to force a regeneration:

[grid@dbaasm ~]$ ls -l $ORACLE_HOME/rdbms/lib/config.o
-rw-r--r-- 1 grid oinstall 1256 Sep 18 23:03 /u01/app/grid/product/11.2.0/grid/rdbms/lib/config.o

[grid@dbaasm ~]$ mv $ORACLE_HOME/rdbms/lib/config.o $ORACLE_HOME/rdbms/lib/config.o_BAK

[grid@dbaasm ~]$ ls -l $ORACLE_HOME/rdbms/lib/config.o*
-rw-r--r-- 1 grid oinstall 1256 Sep 18 23:03 /u01/app/grid/product/11.2.0/grid/rdbms/lib/config.o_BAK

3.2) Then relink the the Oracle Grid Infrastructure Standalone installation:

[grid@dbaasm ~]$ script /tmp/relink_gi.txt
Script started, file is /tmp/relink_gi.txt
[grid@dbaasm ~]$
[grid@dbaasm ~]$ id
uid=1100(grid) gid=1000(oinstall) groups=1000(oinstall),1100(asmadmin),1200(dba),1300(asmdba),1301(asmoper)

[grid@dbaasm ~]$ env| egrep 'ORA|PATH' | sort
LD_LIBRARY_PATH=/u01/app/grid/product/11.2.0/grid/lib
ORACLE_BASE=/u01/app/grid
ORACLE_HOME=/u01/app/grid/product/11.2.0/grid
ORACLE_SID=+ASM
PATH=/usr/lib64/qt-3.3/bin:/usr/NX/bin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/home/grid/bin:.:/u01/app/grid/product/11.2.0/grid/bin

[grid@dbaasm ~]$ $ORACLE_HOME/bin/relink all

writing relink log to: /u01/app/grid/product/11.2.0/grid/install/relink.log


[grid@dbaasm ~]$ exit
exit
Script done, file is /tmp/relink_gi.txt
[grid@dbaasm ~]$

4) Connect as root user (different session) and lock back the Oracle Grid Infrastructure Standalone installation as follows:

[grid@dbaasm ~]$ su -
Password:
[root@dbaasm ~]# . oraenv
ORACLE_SID = [root] ? +ASM
The Oracle base has been set to /u01/app/grid


[root@dbaasm ~]# $ORACLE_HOME/rdbms/install/rootadd_rdbms.sh

[grid@dbaasm ~]$ su -
Password:
[root@dbaasm ~]# . oraenv
ORACLE_SID = [root] ? +ASM
The Oracle base has been set to /u01/app/grid


[root@dbaasm ~]# $ORACLE_HOME/crs/install/roothas.pl -patch
Using configuration parameter file: /u01/app/grid/product/11.2.0/grid/crs/install/crsconfig_params
CRS-4123: Oracle High Availability Services has been started.

On 12.1/12.2/18c, to lock back the GI Home use command <Grid oracle home>/crs/install/roothas.sh -postpatch

Note: OHAS services (ASM instance, diskgroups, listeners, DB instances, etc.) will automatically start.

5) Verify that the all the OHAS services (ASM instance, diskgroups, listeners, DB instances, etc.) started:

[root@dbaasm ~]# crsctl stat res -t
--------------------------------------------------------------------------------
NAME           TARGET  STATE        SERVER                   STATE_DETAILS       
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.ACFSBIG.dg
               ONLINE  ONLINE       dbaasm                                       
ora.DATA.dg
               ONLINE  ONLINE       dbaasm                                       
ora.LISTENER.lsnr
               ONLINE  ONLINE       dbaasm                                       
ora.RECO.dg
               ONLINE  ONLINE       dbaasm                                       
ora.SPFILE.dg
               ONLINE  ONLINE       dbaasm                                       
ora.asm
               ONLINE  ONLINE       dbaasm                   Started             
ora.ons
               OFFLINE OFFLINE      dbaasm                                       
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       dbaasm                                       
ora.db1.db
      1        ONLINE  ONLINE       dbaasm                   Open                
ora.diskmon
      1        OFFLINE OFFLINE                                                   
ora.evmd
      1        ONLINE  ONLINE       dbaasm                                       
[root@dbaasm ~]#

B) How To Relink The Oracle Grid Infrastructure RAC/Cluster Installation.

In order to relink the Oracle Grid Infrastructure RAC/Cluster Installation, please follow the next steps after stopping all the services running:

1) As root OS user, please unlock the Grid Infrastructure Oracle Home (on every node) as follows:

# cd < Grid Infrastructure Oracle Home >/crs/install
# perl rootcrs.pl -unlock

Note: On 12.1/12.2/18c releases, rootcrs.sh can be used instead of rootcrs.pl. Command as "rootcrs.sh -unlock"

2) As the Oracle Grid Infrastructure owner (on every node) relink the Grid Infrastructure Oracle Home as follows:

$ export ORACLE_HOME=< Grid Infrastructure Oracle Home >
$ < Grid Infrastructure Oracle Home>/bin/relink all

3) As root OS user again, please execute the next commands (on every node):

# cd < Grid Infrastructure Oracle Home >/rdbms/install/
# ./rootadd_rdbms.sh
# cd < Grid Infrastructure Oracle Home >/crs/install
# perl rootcrs.pl -patch

On 12.1, use "rootcrs.sh -patch". On 12.2/18c, use "rootcrs.sh -lock" then "crsctl start crs"

 

Note: CRS services (CRS, CSS ASM instances, diskgroups, listeners, DB instances, etc.) will automatically start.

 
4) Please review the relink.log file located at the following directory (to confirm or discard any error):

$ < Grid Infrastructure Oracle Home>/install/relink.log

---

Community Discussions

Still have questions? Use the communities window below to search for similar discussions or start a new discussion on this subject. (Window is the live community not a screenshot)

Click here to open in main browser window

REFERENCES

NOTE:1637766.1 - How To Recompile config.c / Relink Executables Of A Grid Infrastructure Home (Cluster)
NOTE:1931142.1 - How to check and fix file permissions on Grid Infrastructure environment
https://docs.oracle.com/database/121/CWLIN/rem_orcl.htm#CWLIN495
https://docs.oracle.com/database/121/AXDBI/oraclerestart.htm#AXDBI7724
https://docs.oracle.com/database/121/CWLIN/rem_orcl.htm#CWLIN348
http://docs.oracle.com/database/122/CWLIN/relinking-oracle-grid-infrastructure-for-a-cluster-binaries.htm#CWLIN-GUID-11A2832B-A1F1-4454-888F-0CF1CF45EB16
https://docs.oracle.com/database/122/AXDBI/modifying-oracle-grid-infrastructure-for-a-standalone-server-binaries-after-installation.htm#AXDBI-GUID-3A0164E9-8814-4137-808F-CCF5DA32DD26

NOTE:1355977.1 - Steps To Shutdown(stop)/Startup(start) CRS, OHAS, ASM, RDBMS & ACFS Services on a RAC Cluster 11.2 & 12.1 Configuration
NOTE:1422517.1 - Reconfiguring & Recreating The 11gR2/12cR1 Restart/OHAS/SIHA Stack Configuration (Standalone) / How to Reconfigure Oracle Restart

How to Reconfigure Oracle Restart (Doc ID 986740.1)

In this Document

Goal

Solution

1. Remove Oracle Restart configuration

2. reconfigure Oracle Restart

3. Add ASM back to Oracle Restart configuration

4. Start up ASM instance

5. Recreate ASM server parameter file (SPFILE)

6. Restart HAS stack

7. Add components back to Oracle Restart Configuration

7.1. Add database component

7.2. Add listener component

7.3. Add other components

---

APPLIES TO:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

GOAL

This document is about reconfiguring Oracle Restart. One reason for such action might be if the server (host) was renamed. If that was the case and the server was rebooted, the ASM startup would fail with ORA-29701.

The solution is to reconfigure Oracle Restart.

SOLUTION

1. Remove Oracle Restart configuration

This step should be performed as privileged (root) user.

# $GRID_HOME/crs/install/roothas.pl -deconfig -force

The expected result is "Successfully deconfigured Oracle Restart stack".

2. reconfigure Oracle Restart

This step should also be performed as privileged (root) user.

# $GRID_HOME/crs/install/roothas.pl

The expected result is "Successfully configured Oracle Grid Infrastructure for a Standalone Server"

3. Add ASM back to Oracle Restart configuration

This step should be performed as Grid Infrastructure owner (grid user).

$ srvctl add asm

The expected result is no output, just a return to the operating system prompt.

4. Start up ASM instance

This step should be performed as Grid Infrastructure owner (grid user).

$ srvctl start asm

That should start ASM. Note that at this time there will be no ASM initialization or server  parameter file.

5. Recreate ASM server parameter file (SPFILE)

This step should be performed as Grid Infrastructure owner (grid user).

Create a temporary initialization parameter file (e.g. /tmp/init+ASM.ora) with the following content (specify your own disk group names):

asm_diskgroups='<DG_NAME>','<DG_2_NAME>'
instance_type='asm'
large_pool_size=12M
remote_login_passwordfile='EXCLUSIVE'

Mount the disk group where the new server parameter file (SPFILE) will reside (e.g. <DG_NAME>) and create SPFILE:

$ sqlplus / as sysasm

SQL> alter diskgroup <DG_NAME> mount;
Diskgroup altered.

SQL> create spfile='+<DG_NAME>' from pfile='/tmp/init+ASM.ora';
File created.

SQL> show parameter spfile
NAME TYPE VALUE
------- ------- -------------------------------------------------
spfile string +<DG_NAME>/asm/asmparameterfile/registry.253.707737977

6. Restart HAS stack

crsctl stop has
crsctl start has

7. Add components back to Oracle Restart Configuration

If you had the database, listener and other components, add them back to the Oracle Restart Configuration.

7.1. Add database component

This step should be performed as RDBMS owner (oracle user).

srvctl add database -d <db_unique_name> -o <oracle_home>

7.2. Add listener component

This step should be performed as Grid Infrastructure owner (grid user).

srvctl add listener

7.3. Add other components

For information on how to add back additional components, please review:
Oracle database Administrator's Guide 11g Release 2 (11.2)
Chapter 4 Configuring Automatic Restart of an Oracle database
Section Configuring Oracle Restart