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

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

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

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

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

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

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

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

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

In this Document

APPLIES TO:

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:

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

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

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

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

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

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

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

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

Example:

Or

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

11) Validate that the candidate disks are being discovered:

12) Create a new ASM instance spfile:

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

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

MOS 上有參考文件 How to change Hostname/ IP in GI standalone (SIHA) (文件 ID 1552810.1)。    
文件中對於ASM是採用新建立的PFILE來重新新增ASM例項。其實就使用以前的SPFILE，也可以，只需要記下來，重新配置SPFILE的位置引數就行了。

點選(此處)摺疊或開啟

1. // #行都使用root使用者執行, $行使用對應使用者執行
2. # $GI_HOME/bin/crsctl status resource ora.asm -f
   
3. // 記錄以下兩個引數的值
4.                         ASM_DISKSTRING=/dev/UPRR*
   
5.                         SPFILE=+UPRRDB_DATA/asm/asmparameterfile/registry.253.832110249
   
6. 
   
7. # $GI_HOME/crs/install/roothas.pl -deconfig -force
8. 
   
9. Using configuration parameter file: /u01/app/grid/product/11.2.0/grid/crs/install/crsconfig_params
   CRS resources for listeners are still configured
   PRKO-2573 : ONS 守護程式已停止。
   CRS-2673: Attempting to stop 'ora.UPRRDB_DATA.dg' on 'uprr1'
   CRS-2677: Stop of 'ora.UPRRDB_DATA.dg' on 'uprr1' succeeded
   CRS-2673: Attempting to stop 'ora.asm' on 'uprr1'
   CRS-2677: Stop of 'ora.asm' on 'uprr1' succeeded
   CRS-2673: Attempting to stop 'ora.cssd' on 'uprr1'
   CRS-2677: Stop of 'ora.cssd' on 'uprr1' succeeded
   CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'uprr1'
   CRS-2673: Attempting to stop 'ora.evmd' on 'uprr1'
   CRS-2677: Stop of 'ora.evmd' on 'uprr1' succeeded
   CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'uprr1' has completed
   CRS-4133: Oracle High Availability Services has been stopped.
   Successfully deconfigured Oracle Restart stack
10. 
    
11. //改主機名

1. # hostname uprr.phanx.com
2. # vim /etc/hosts
   
3. # vim /etc/sysconfig/network
   
4. # service network restart
   
5. 
   
6. 
   
7. //重新登入   Logout and re-login.
   
8. 
   
9. # $GI_HOME/crs/install/roothas.pl
   
10. 
    
11. Using configuration parameter file: /u01/app/grid/product/11.2.0/grid/crs/install/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 'root'..
    Operation successful.
    CRS-4664: Node uprr successfully pinned.
    Adding Clusterware entries to upstart
    
    
    uprr     2014/06/30 14:48:16     /u01/app/grid/product/11.2.0/grid/cdata/uprr/backup_20140630_144816.olr
    Successfully configured Oracle Grid Infrastructure for a Standalone Server
    
    
12. # crs_stat -t
    
13. 
    
14. Name           Type           Target    State     Host        
    ------------------------------------------------------------
    ora.cssd       ora.cssd.type  OFFLINE   OFFLINE               
    ora.diskmon    ora....on.type OFFLINE   OFFLINE               
    ora.evmd       ora.evm.type   ONLINE    ONLINE    uprr        
    ora.ons        ora.ons.type   OFFLINE   OFFLINE   
    
    
15. su - grid
16. $ vim $GI_HOME/network/admin/listener.ora
    
17. $ $GI_HOME/bin/srvctl add asm
    
18. $ $GI_HOME/bin/crsctl modify resource "ora.asm" -attr "AUTO_START=1"
    
19. $ $GI_HOME/bin/srvctl modify asm -p '+UPRRDB_DATA/asm/asmparameterfile/registry.253.832110249' -d '/dev/UPRR*'
    
20. 
    
21. //檢查監聽是否已經啟動，如果啟動了就停止。 check if listener is active, if yes kill it.
    
22. 
    
23. $  ps -ef|grep tnslsnr|grep -v grep | awk '{print $2}'|xargs -L1 kill -9
    
24. 
    
25. 
    
26. 
    
27. $ $GI_HOME/bin/srvctl add listener -l LISTENER -o $GI_HOME
    
28. $ $GI_HOME/bin/lsnrctl start
29. $ crsctl start resource ora.cssd
    
30. 
    
31. CRS-2672: Attempting to start 'ora.cssd' on 'uprr'
    CRS-2672: Attempting to start 'ora.diskmon' on 'uprr'
    CRS-2676: Start of 'ora.diskmon' on 'uprr' succeeded
    CRS-2676: Start of 'ora.cssd' on 'uprr' succeeded
    
    
32. $ sqlplus / as sysasm
    
33. SQL> startup
34. SQL> alter system set local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=uprr.phanx.com)(PORT=1521))))';
35. 
    
36. 
    
37. # su - oracle
    
38. $ srvctl add database -d UPRR -o $ORACLE_HOME
    
39. $ sqlplus / as sysdba
    
40. SQL> startup
    
41. SQL> alter system set local_listener='(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=uprr.phanx.com)(PORT=1521))))';
42. # $GI_HOME/bin/crs_stat -t
43. Name           Type           Target    State     Host        
    ------------------------------------------------------------
    ora....ER.lsnr ora....er.type ONLINE    ONLINE    uprr        
    ora....DATA.dg ora....up.type ONLINE    ONLINE    uprr        
    ora.asm        ora.asm.type   ONLINE    ONLINE    uprr        
    ora.cssd       ora.cssd.type  ONLINE    ONLINE    uprr        
    ora.diskmon    ora....on.type OFFLINE   OFFLINE               
    ora.evmd       ora.evm.type   ONLINE    ONLINE    uprr        
    ora.ons        ora.ons.type   OFFLINE   OFFLINE               
    ora.uprr.db    ora....se.type ONLINE    ONLINE    uprr
    
    

如果還有其它地方，像 tnsnames.ora, sqlnet.ora 中，如果有主機名的地方，對應修改以下。
我沒有用DB Control，如果有的話，還需要重建DB Control，參考 MOS 文件 Note 278100.1 How To Drop, Create And Recreate the Database Control (DB Control) Release 10g and 11g  278100.pdf

In this Document

APPLIES TO:

GOAL

 The present document provides the example about how to migrate an ASM Oracle Restart configuration from one host to another host on Unix/Linux.

SOLUTION

You need to follow the next steps to migrate an ASM Oracle Restart configuration from one host to another host on Unix/Linux on 11.2 or 12c releases:

1) Shutdown all the Oracle Services as follows:

2) Then shutdown the source Linux/Unix host.

3) Disconnect/unplug your Storage and connect it to the new Linux host.

4) Install the ASMLIB on the new hosts (this installation will scan the original disks).

Note: This steps is only required if ASMLIB API was present on the original source host.

5) Then Install the 11.2 Grid Infrastructure Standalone "Software Only" + any required GIPSU    on the new hosts to match the original release.

6) Then Install the 11.2 RDBMS Standalone "Software Only" + any required RDBMS PSU   on the new hosts to match the original release.

7) Then configure the CSS & OHAS services as root user:

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

Note: On 12c release you will need to add the  -unsupported parameter as follows:

9) Restart the OHAS stack as grid or oracle OS user:

10) Check the CSS & OHAS state as grid or oracle OS user:

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

11) Remove the Old listener running under the old Grid Infrastructure Oracle Home, thru the NETCA GUI (from the old Grid Infrastructure Oracle Home).

12) Recreate the default listener (LISTENER) using port 1521, thru the NETCA GUI located on the new Grid Infrastructure Oracle Home.

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

14) Add the ASM instance as grid or oracle user or the Grid Infrastructure installation owner and execute:

15) Enable ASM instance Auto Start as follow:

Note: On 12c release you will need to add the  -unsupported parameter as follows:  

16) Make sure the disks are discovered by kfod:

Example:

Or

17) If so, then startup the ASM instance as follow:

18) Validate that the original diskgroup(s) were mounted:

19) Create a new ASM instance spfile:

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

21) Finally validate the OHAS (autostart) services start as follow:

22) Check the new HAS version as well as follow:

23) If you need to add additional OHAS/Restart/SIHA resources (e.g. database instances), then please follow the steps described in the next note (I wrote it):