This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process, and therefore has not been subject to an independent technical review.
Applies to: Oracle Server - Enterprise Edition - Version: 10.2.0.1 This problem can occur on any platform.
Symptoms The alert log shows that using data pump utility in RAC env alters service_names parameter at the start, ie:
Wed Mar 15 13:35:47 2006 ALTER SYSTEM SET service_names='SYS$SYS.KUPC$C_1_20060315133546.xxx.yyyy.COM' SCOPE=MEMORY SID='zzz';
Then change to '' at the end of operation.
Wed Mar 15 13:50:39 2006ALTER SYSTEM SET service_names='' SCOPE=MEMORY SID='zzz';
Changes Upgrade to 10.2.
Cause Data pump doesn't change existing service name but add news one for its own queue operation.
Assuming you started instance with service name with test1 and test 2, it will add another one at the start of operation and put the original value back at the end of operation.
------------------------------------------- Tue Mar 28 16:41:43 2006 ALTER SYSTEM SET service_names='TEST02','TEST01','SYS$SYS.KUPC$C_1_20060328164142.R2D1C.REGRESS.RDBMS.DEV.US.ORACLE.C OM' SCOPE=MEMORY SID='R2D1C1'; Tue Mar 28 16:41:43 2006 ALTER SYSTEM SET service_names='SYS$SYS.KUPC$C_1_20060328164142.R2D1C.REGRESS.RDBMS.DEV.US.ORACLE.COM','TEST02','TEST 01','SYS$SYS.KUPC$S_1_20060328164142.R2D1C.REGRESS.RDBMS.DEV.US.ORACLE.COM' SCOPE=MEMORY SID='R2D1C1'; kupprdp: master process DM00 started with pid=39, OS id=6096 to execute - SYS.KUPM$MCP.MAIN('SYS_EXPORT_SCHEMA_01', 'SCOTT02', 'KUPC$C_1_20060328164142', 'KUPC$S_1_20060328164142', 0); Tue Mar 28 16:43:20 2006 ALTER SYSTEM SET service_names='SYS$SYS.KUPC$S_1_20060328164142.R2D1C.REGRESS.RDBMS.DEV.US.ORACLE.COM','TEST02','TEST 01' SCOPE=MEMORY SID='R2D1C1';
At the end of data pump operation : Tue Mar 28 16:43:22 2006 ALTER SYSTEM SET service_names='TEST02','TEST01' SCOPE=MEMORY SID='R2D1C1'; ----------------------------------------------
But if the instance was started without sevice_name specificed (default value as database name), it could be seen that it has new service name only for data pump and it sets the value to ''(null) at the end of operation.
Solution There is no need to be concerned of data pump alerting service_name.
It adds new services on top of existing ones and removes the added one at the end of operation.
If instance was started with default value(database name) as service_name, the alert statement doens't show default value(database name) at adding service name and put the value to null at the end of operation.
But no impact to exisiting service with default (database name) even though alert says it changes servcie_name to ''(null). The service (default value as database name) is not being removed but exists always. If the listener is restarted after data pump operation, the pmon will register its default service to listener automatically.