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