cancel
Showing results for 
Search instead for 
Did you mean: 

System Rename Error

former_member302241
Discoverer
0 Kudos

I tried to do system rename with following environment:

SAP ERP 6 SR3. Kernel 720. DB2 10.1 FP3 -AIX 6.1. Use latest SWPM, hostagent, kernel.

I strugled with error during creating relocate.template file

Error log dev_sapdbctrl :

[PID 5636240] *** ERROR => 'Prepare database copy' failed: Generic error [sapdbctrl.cp 2594]

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

                  BACKUP DATABASE &
      RETRIEVE TABLESPACE AND CONTAINER INFORMATION &
           CHECK REDIRECT RESTORE SCRIPT

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

* RETRIEVING OF TABLESPACE AND CONTAINER INFORMATION

* RETRIEVING  FAILED

Please help.

Regards,

Fendhy

Accepted Solutions (1)

Accepted Solutions (1)

BorisZarske
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Fendhy,

SAP Note 1657141 (DB6 - Create relocate.template for system rename) could be worth a try:

http://service.sap.com/sap/support/notes/1657141

Best regards,

Boris

former_member302241
Discoverer
0 Kudos

I've followed the sapnote but got same error.

I solve it by add database authorization to user <sid>adm.

Now i get confuse with the filesystems.

My scenario is renaming system SID in same host.

I have filesystems mounted with source SID.

/usr/sap/<SID>, /sapmnt/<SID>, /db2/<SID>, /db2/db2<sid>, /db2/<SID>/sapdata1 and so on

What should i do with the filesystems? change it to target SID ?

Regards,

Fendhy

BorisZarske
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Fendhy,

Please proceed as described in the system rename guide, section 3.51 "Performing Preparation Steps for IBM DB2 for Linux, UNIX, and Windows". The guide is available for download from http://service.sap.com/sltoolset --> Software Logistics Toolset 1.0 --> Documentation <at the end of the page> --> System Provisioning --> System Rename: Systems based on SAP NetWeaver 7.0x. It contains the following information for your database platform concerning the mount points:

Best regards,

Boris


former_member302241
Discoverer
0 Kudos

Boris,

I succesfully did this system rename scenario in my testing environment.

I renamed following mount points contain <SID> to <Target SID>

/db2/<SID> change to /db2/<Target SID>

/db2/<SID>/sapdata(1..4) to /db2<Target SID>/sapdata (1..4)

/db2/<SID>/log_dir to /db2/<Target SID>/log_dir

/db2/<SID>log_arch to /db2/<Target SID>/log_arch

/db2/<SID>/db2dump to /db2/<Target SID>/db2dump

Except mount point for db2software i keep old one /db2/db2<sid>

and created new for for Target SID /db2/db2<target sid>

I succesfully do the system rename with this setting in sandbox environment.

source sid is SP1 and target SID is DSP

But when i tried in my real environment i got following error.

DB2 Setup log file started at:  Wed Aug  6 11:37:16 2014 WIT
============================================================

Operating system information: AIX 6.1
ERROR: The DB2 installer detects that one or more DB2 instances "db2dsp" are still
active. Stop the active instances and rerun the command again.

ERROR: The "db2iupdt" command failed. Ensure the command parameters are valid,
that errors reported in the log file are fixed, then rerun the command.

Please advise.

Regards,

Fendhy

BorisZarske
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Fendhy,

Looks to me like the database can't be shut down properly (as maybe some agents are still active), but already approached the database experts and asked them for advice, will get back to you as soon as I got a reply. If this should be urgent, I would advice to open a support message in parallel.

Best regards,

Boris

BorisZarske
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hello Fendhy,

Sorry, due to vacation period, the answer form the database experts is pending. As I will be on vacation as of next week, I won't be able to provide an answer until end of this month. So, my recommendation would be that you open a support message instead, I hope this is okay for you.

Thanks for your understanding + best regards,

Boris

Answers (0)