Oracle RAC 更改DB_UNIQUE_NAME网站首页 技术杂谈

Oracle RAC 更改DB_UNIQUE_NAME

nebofeng 2023-05-31 20:00:02

简介Oracle RAC 更改DB_UNIQUE_NAME

背景

遇到一个场景是更改 RAC 架构下的 Oracle DB_UNIQUE_NAME ,使得跟DB_NAME不一致，尝试了网上的方法，都没能成功，最后是看了官方support的solution，下面是主要操作步骤，11g203版本，已经验证是没问题的。

具体操作步骤

For example, a database that was originally created with Global Database Name “<database>” would have a db_name and db_unique_name of “<database>” and its corresponding CRS database resource would be named “ora.<database>.db”. Changing the db_unique_name requires a complete restart of the database.

Remove the database, instance and service resources from CRS, this does NOT affect database itself.
$ srvctl stop database -d <database>
$ srvctl remove database -d <database>
Start the database and change the db_unique_name at database level.
SQL> Startup;
SQL> alter system set db_unique_name=<database>_test scope=spfile sid=‘‘;
SQL> alter system set db_domain=<domain> scope=spfile sid=’’; << only required when db_domain needs to be changed.
SQL> alter database rename global_name to <database>_test.<domain>;
Now add the database resource to cluster-level.
$ srvctl add database -d <database>_test -n <node> -o <ORACLE_HOME>
$ srvctl add instance -d <database>_test -i <instance1> -n <node1>
$ srvctl add instance -d <database>_test -i <instance2> -n <node2>
Create dependency between database and ASM instance so that database starts after ASM instance starts.
$ srvctl modify instance -d <database>_test -i <instance1> -s +ASM1
$ srvctl modify instance -d <database>_test -i <instance2> -s +ASM2Please
note that, for 11.2, it is no longer required to modify at instance level, it should be done at database level:
srvctl modify database -d <db_unique_name> -a "<diskgroup_list>
"5) Create database service, the following example add service with both instances as preferred
$ srvctl add service -d <database>_test -s <service> -r “<instance1>,<instance2>”