When you use the DataPump tool in the RAC environment, Alert Log prompts you to modify the service_names parameter.
For example:
Sat Sep 13:33:20 2012
Alter system setservice_names = 'pmos ', 'sys $ sys. kupc $ c_1_20901133317.pmos' scope = memory SID = 'pmos1 ';
Sat Sep 13:33:20 2012
Alter system setservice_names = 'sys $ sys. kupc $ c_1_20901133317.pmos ', 'pmos', 'sys $ sys. kupc $ s_1_20901133317.pmos 'scope = memory SID = 'pmos1 ';
Kupprdp: Master process dm00 started withpid = 46, OS id = 1171590
To execute-SYS. KUPM $ MCP. Main ('sys _ export_table_03 ', 'pmos', 'kupc $ c_1_20120901133317 ', 'kupc $ s_1_20120901133317', 0 );
Kupprdp: Worker Process dw01 started withworker id = 1, pid = 48, OS id = 1830944
To execute-SYS. KUPW $ worker. Main ('sys _ export_table_03 ', 'pmos ');
Sat Sep 13:34:45 2012
Alter system setservice_names = 'sys $ sys. kupc $ s_1_20120901133317.pmos ', 'pmos' scope = memorysid = 'pmos1 ';
......
Sat Sep 14:21:43 2012
Alter system setservice_names = 'sys $ sys. kupc $ s_1_20120901142120.pmos ', 'pmos' scope = memorysid = 'pmos1 ';
Sat Sep 14:21:43 2012
Alter system setservice_names = 'pmos 'scope = memory SID = 'pmos1 ';
Sat Sep 14:21:58 2012
RFS [1]: Archived log: '/arch1/2_14256_654056896.dbf'
DataPump does not modify the existing servicename, but adds a new to the operation queue. For example, pmos1 and pmos2 are used before, a service name will be added to the operation queue at the beginning of DataPump, and changed to the original value after the operation is completed.
In the above Alert Log, you can verify that the operation starts with execution:
Alter system setservice_names = 'pmos ', 'sys $ sys. kupc $ c_1_20901133317.pmos' scope = memorysid = 'pmos1 ';
Run the following command after the operation is completed:
Alter system set service_names = 'pmos 'scope = memory SID = 'pmos1 ';
We do not need to care about the value of SERVICE_NAME modified by DataPump. If the instance uses the default database name as the service name, when a new service name is added to the operation queue, the alert warning does not display SERVICE_NAME (default value: Database Name). After the operation is completed, the service name is set to null.
Setting null does not affect the service because the default value of the service is always databaename. If the listener is restarted after the data pump operation is completed, pmon automatically registers the service to the listener.
Refer:
On RAC, expdp removes the service name [id1269319.1]
DataPump export: RAC instancestartup/shutdown alters service_names [ID 363396.1]
Bytes -------------------------------------------------------------------------------------------------------
All rights reserved. reprinted articles are allowed, but source addresses must be indicated by links. Otherwise, the documents will be held legally responsible!
Skype: tianlesoftware
QQ: tianlesoftware@gmail.com
Email: tianlesoftware@gmail.com
Blog: http://www.tianlesoftware.com
WEAVER: http://weibo.com/tianlesoftware
Twitter: http://twitter.com/tianlesoftware
Facebook: http://www.facebook.com/tianlesoftware
LinkedIn: http://cn.linkedin.com/in/tianlesoftware
------- Add a group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, reject the application ----
Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)
Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823
Dba6 group: 158654907 dba7 group: 172855474 DBA group: 104207940