SAP Note

Header Data

Symptom

********************************************************************************

System Rename for SAP NetWeaver - Based Systems

********************************************************************************

This SAP Note applies to the following SAP NetWeaver releases and SAP systems based on them:                                                                                              Using 70SWPM*.SAR:

l SAP NetWeaver 7.0 including Enhancement Package 3 l SAP Business Suite 7i 2011 ABAP on SAP NetWeaver 7.0 including Enhancement Package 3 ABAP l SAP NetWeaver 7.0 including Enhancement Package 2 l SAP Business Suite 7i 2010 on SAP NetWeaver 7.0 including Enhancement Package 2 l SAP NetWeaver 7.0 including Enhancement Package 1 l SAP Business Suite 7 on SAP NetWeaver 7.0 including Enhancement Package 1 l SAP NetWeaver 7.0 Support Release 3 l SAP Business Suite 2005 on SAP NetWeaver 7.0 Support Release 3 l SAP CRM 2007 on SAP NetWeaver 7.0 SR3 l SAP SCM 5.1 on SAP NetWeaver 7.0 SR3 l SAP Solution Manager 7.1 Support Release 1 l SAP Solution Manager 7.0 EHP1 Support Release 1

Using SWPM*.SAR:

l SAP NetWeaver 7.4 l SAP Business Suite 2013 on SAP NetWeaver 7.4 l SAP Solution Manager 7.1 powered by SAP HANA on SAP NetWeaver 7.4 l SAP NetWeaver Application Server ABAP 7.4 l SAP Business Suite, version for SAP HANA on SAP NetWeaver Application Server ABAP 7.4 l SAP NetWeaver 7.3 including Enhancement Package 1 l SAP NetWeaver 7.3 l SAP Business Suite 7i 2013 l SAP Business Suite 7i 2011 Java on SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / 7.4 l SAP Business Suite 7i 2010 Java on SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / 7.4 l SAP Business Suite 7 Java on SAP NetWeaver 7.3 / 7.3 including Enhancement Package 1 / 7.4 l SAP NetWeaver Composition Environment 7.2 l SAP NetWeaver Composition Environment 7.1 including Enhancement Package 1 l SAP NetWeaver Process Integration 7.1 including Enhancement Package 1 l SAP NetWeaver Mobile 7.1 including Enhancement Package 1 l SAP NetWeaver 7.1 including Enhancement Package 1 for banking services from SAP l SAP NetWeaver Composition Environment 7.1 Support Release 5 l SAP NetWeaver Process Integration 7.1 l SAP NetWeaver Mobile 7.1 including Support Release 1 l SAP NetWeaver 7.1 for banking services from SAP

 

Other Terms

System Rename

Reason and Prerequisites

Remarks, annotations, and corrections discovered after publication of the documentation "System Rename for SAP Systems Based on SAP NetWeaver" available on SAP Service Marketplace at:

http://service.sap.com/sltoolset  -> Software Logistics Toolset 1.0 -> Documentation -> System Provisioning -> System Rename: Systems Based on SAP NetWeaver 7.0 / 7.0 EHPs

    1619720 - System Rename for SAP Systems based on SAP NetWeaver  

Version   136     Validity: 28.09.2015 -   Language   English (Master)

Released On 28.09.2015 04:07:41

Release Status Released for Customer

Component BC-INS-SRN System Rename Utility

Priority Correction with high priority

Category Installation information

http://service.sap.com/sltoolset  -> Software Logistics Toolset 1.0 -> Documentation -> System Provisioning -> System Rename: Systems Based on SAP NetWeaver 7.1 and Higher

RESTRICTIONS: Currently, the following restrictions apply:

l Rename of a high availability system is not supported. l Rename of MCOD Systems is not supported. l Rename of SAP Systems with TREX is not supported. l Valid for Linux and Unix operating systems: Rename of SAP systems with IBM DB2 for Linux, UNIX, and Windows database version

10.1 requires FP2 or higher. l Valid for Solaris_X86_64 operating system: Rename of SAP systems with IBM DB2 for Linux, UNIX, and Windows database version

9.7 is supported as of FP7 or higher. l IBM DB2 for Linux, UNIX, and Windows database: Database setups with multiple servers are not supported.

This includes:

¡ Partitioned databases using the DB2 Database Partitioning Feature (DPF).

¡ DB2 databases using the DB2 pureScale Feature

¡ DB2 High availability disaster recovery (HADR) setups

l Oracle: ¡ System Rename is not supported for ASM database installations

n System Rename does not work for an Automatic Storage Management (ASM) installation of the Oracle database. It also does not work when you only use System Rename for changing the host name, the instance name, or the instance number. This is because there is a different ORACLE_HOME and the ora<sid> user is missing in the ASM environment. 

Solution

This SAP Note contains the following sections:

1. General Information 2. MaxDB-Specific Information 3. MS SQL Server-Specific Information 4. Oracle-Specific Information 5. IBM DB2 for Linux, UNIX, and Windows-Specific Information 6. IBM DB2 for i 7. SAP ASE

 

 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1  General Information ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

------------------------< D023322, 28/SEP/15 >-------------------------

Release of Oracle Replicate System Rename

Oracle replicate system rename (file copy) is now officially released.

 

-----------------------<I069416, 11/MAR/14>---------------------------

Date Section Description

 28/SEP/15 1 Release of Oracle replicate system rename

11/MAR/14 1 Windows: Rename of SAP system instances or database directories fails

4/MAR/14 2 Activities during system rename with MaxDB/liveCache

12/NOV/13 4 Parameter local_listener in initSID.ora or spfileSID.ora not supported for database rename

25/OCT/13 5SQL0973N Not enough storage is available in the "MON_HEAP_SZ" heap or stack to process the statement. SQLSTATE=57011>

27/APR/13 5 Windows only: Problem with DBM Configuration Parameters after a System Rename with DB2

28/MAR/13 5 Windows only: System Rename hangs

06/FEB/13 5 Windows Only: Problem with AUTOMATIC Configuration Parameters after a System Rename with DB2

30/JAN/13  1 IGS: Changing the IGS Destination

16/JAN/13 5 DB6: SAP Host agent - sapdbctrl

15/JUN/12 6 Introducing a new section for IBM DB2 for i

Windows:  Rename of SAP system instances or database directories fails.

Symptom:

System Rename on Windows is not able to rename SAP system instances or database directories.

For example, you get error messages like the following: Error moving 'D:\oracle\W24' to 'D:\oracle\W25' Error moving 'D:/usr/sap/U41' to 'D:/usr/sap/M48'

Solution:

Proceed as follows:

1. Check if service WmiPrvSe.exe is running. 2. If service WmiPrvSe.exe is running,  apply SAP Note 1459119.

-----------------------<C5017590, 30/JAN/13>---------------------------

IGS: Changing the IGS Destination

Symptom:

When you call transaction SM59, an error occurs during the retieval of logon data stored in secure storage. The password has invalid status. Solution:

Update the password.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 2  MaxDB / liveCache -Specific Information ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

----------------------<d058380, 4/MAR/14>--------------------------

Activities during system rename with MaxDB/liveCache

Symptom:

After the rename of a distributed system the system doesn't start up. This is due to the fact that the value of the profile parameter dbs/ada/schema has not been adapted to the new schema name.

Solution:

Change the value of the profile parameter dbs/ada/schema to the new schema name in all relevant profiles manually. Afterwards the system should start up successfully.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 3  MS SQL Server-Specific Information ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

<at the moment there are no entries required>

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 4  Oracle-Specific Information ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 --------------------------<d023322, 12/NOV/13>-------------------------

Parameter local_listener in initSID.ora or spfileSID.ora not supported for database rename

Symptom:

During the adaption of initSID.ora the parameter local_listener will not adapted so the startup of the database fails: ORA-00119: invalid specification for system parameter LOCAL_LISTENER ORA-00130: invalid listener address

Solution:

Before your start the rename procedure remove this parameter from your initSID.ora or spfileSID.ora.

When the error already occurred, remove this parameter from init<NEWSID>.ora.mount and init<NEWSID>.ora and retry the failing step.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 5  IBM DB2 for Linux, UNIX, and Windows-Specific Information ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

-------------------------<C5010742, 25/OCT/13>-------------------------

SQL0973N  Not enough storage is available in the "MON_HEAP_SZ" heap or stack to process the statement.  SQLSTATE=57011>

Symptom:

During system rename, you receive an error with the following message: SQL0973N  Not enough storage is available in the "MON_HEAP_SZ" heap or stack to process the statement.  SQLSTATE=57011> Solution:

In order to continue your system rename procedure, run the following command as user db2<dbsid>: db2 update dbm cfg using mon_heap_sz 66 automatic -------------------------<C5012251, 28/MAR/13>-------------------------

Windows only:  Problem with DBM Configuration Parameters after a System Rename with DB2

Symptom:

After performing system rename successfully, you may lose some DBM settings in your instance configuration.

Solution:

This problem is fixed with versions V9.5 FP8, V9.7 FP8, 10.1 FP3, 10.5 FP1 and higher.

If you have versions lower than the versions mentioned above, then you have to manually update the necessary configuration parameters, such as: NODETYPE, RELEASE, SYSADM_GROUP, DFT_MON_UOW, DFT_MON_STMT, DFT_MON_TABLE, DFT_MON_BUFPOOL, DFT_MON_LOCK, DFT_MON_SORT, DFT_MON_TIMESTAMP, TRUST_ALLCLNTS, TRUST_CLNTAUTH, HEALTH_MON, FCM_NUM_BUFFERS Before performing the system rename, execute the following:     db2 get dbm cfg Save this configuration/output. After performing the system rename, you have to check the mentioned parameters and update them manually if necessary, using the following:     db2 update dbm cfg using <parameter name> <old value> For example, to set the DFT_MON_BUFPOOL and DFT_MON_LOCK parameters back to ON, you have to run the following command as db2<sid> user:     db2 update dbm cfg using DFT_MON_BUFPOOL ON DFT_MON_LOCK ON Note: Do not use db2cfimp for this purpose. -------------------------<C5012251, 06/FEB/13>-------------------------

Windows Only: Problem with AUTOMATIC Configuration Parameters after a System Rename with DB2

Symptom:

After performing system rename successfully, you may lose the AUTOMATIC settings in your instance configuration.

Solution:

This problem is fixed with versions 9.7 FP7 and 10.1 FP2 and higher. If you have versions lower than 9.7 FP7 and 10.1 FP2, then you have to manually update the necessary configuration parameters to AUTOMATIC. Before performing the system rename, execute the following:     db2 get dbm cfg Note down which parameters are set to AUTOMATIC. After performing the system rename, you have to update each of these parameters manually, using the following:     db2 update dbm cfg using <parameter name> AUTOMATIC For example,to set the MON_HEAP_SZ parameter back to AUTOMATIC, you have to run the following command:     db2 update dbm cfg using MON_HEAP_SZ AUTOMATIC Note: Do not use db2cfexp for this purpose. -------------------------<C5010742 16/JAN/13>--------------------------

DB6: SAP Host agent - sapdbctrl

Symptom:

If the patch level of the SAP Host agent is lower than patch level 131, the following error might occur: sapdbctrl - prepareCopy parsing SAPSYSTEM name fails.

Solution:

To solve this problem, proceed as described in SAP Note 1787404.

If your operating system is HP-UX make sure patch level of the SAP Host agent is not lower than patch level 157. For more information see SAP Note 1888385.

 

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 6  IBM DB2 for i ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

<at the moment there is no entry required>

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 7  SAP ASE ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ <at the moment there are no entries required>

Validity

Support Packages & Patches

References

This document refers to:

SAP Notes

This document is referenced by:

SAP Notes (7)

Software Component From Rel. To Rel. And Subsequent

SOFTWARE_PROVISIONING_MANAGER 1.0 1.0  

Support Package Patches

Software Component Support Package Patch Level

SOFTWARE PROVISIONING MGR 1.0 SP004 000005

SP005 000010

SP006 000003

SP007 000006

SP008 000005

SP009 000001

1709155   System Provisioning with SAP Landscape Virtualization Management

1527538   SAP Landscape Virtualization Management 1.0

1492467   Supplementary information about SAP MaxDB version change to 7.9

1459119   Locked files in kernel staging directory

1353266   Supplementary information about SAP MaxDB version change to 7.8

2031385   SAP Release Note for SL Toolset 1.0 SPS 13

1680045   Release Note for Software Provisioning Manager 1.0 SP 09

1922474   SAP Release Note for SL Toolset 1.0 SPS11

2079036   SAP Release Note for SL Toolset 1.0 SPS 14

1871178   SAP Release Note for SL Toolset 1.0 SPS10

1527538   SAP Landscape Virtualization Management 1.0

1709155   System Provisioning with SAP Landscape Virtualization Management