homogenous system copy NW-7.03 and kernel 7.20-EXT

[christoph_ostrop]

how to make a homogenous system copy from a NW-7.03 ABAP-system (ECC-606 EHP6) with 7.20_EXT Kernel?

with Data restore from tape

is there an installation master for NW-7.03 available, which can handle the 7.20_EXT Kernel?

[Former Member · Accepted solution]

I'm not sure why you would need the installation master if you're using the save/restore method. It's all done at the OS level. (savlib/rstlib) I can't find the link for Volker's quick and dirty homogeneous system copy right now but maybe he will provide it.

[christoph_ostrop · Accepted solution]

Rick Githens wrote:
I'm not sure why you would need the installation master if you're using the save/restore method. It's all done at the OS level. (savlib/rstlib) I can't find the link for Volker's quick and dirty homogeneous system copy right now but maybe he will provide it.

Rick,

we try and want to use the official SAP way to proceed a homogenous system copy.

we use this installation master:

SAP EHP1 FOR SAP NETWEAVER 7.3

OS/DB dependent Components   

Number 51042225             

but we have big problems to run the RSTLIB ..... of the database (from another system)

but we dont know, why?

TRACE      2012-09-13 14:18:47.171
NWDB._getParameter() done: Property(rstcmdABAP, RSTLIB SAVLIB(R3ERPDATA) DEV(TAPMLB08) RSTLIB(R3ERYDATA) OPTION(*NEW) MBROPT(*ALL) ALWOBJDIF(*ALL) OUTPUT(*PRINT) VOL(200063) SEQNBR(135))

TRACE      2012-09-13 14:18:47.171
NWDBdb4.getRSTCMD(): RSTLIB SAVLIB(R3ERPDATA) DEV(TAPMLB08) RSTLIB(R3ERYDATA) OPTION(*NEW) MBROPT(*ALL) ALWOBJDIF(*ALL) OUTPUT(*PRINT) VOL(200063) SEQNBR(135)

TRACE      2012-09-13 14:18:47.172
Function setMessageIdOfExceptionMessage: os4mod.commandCallFailed

ERROR      2012-09-13 14:18:47.174
           CJSlibModule::writeError_impl()
MOS-02001  Call of command "RSTLIB SAVLIB(R3ERPDATA) DEV(TAPMLB08) RSTLIB(R3ERYDATA) OPTION(*NEW) MBROPT(*ALL) ALWOBJDIF(*ALL) OUTPUT(*PRINT) VOL(200063) SEQNBR(135)" failed. Exception is "65280:CPF3794: Sichern/Zur}ckspeichern ohne Erfolg beendet.".

TRACE      2012-09-13 14:18:47.175 [iaxxejsbas.hpp:503]
           EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.

TRACE      2012-09-13 14:18:47.353 [syuxctask.cpp:276]
           CChildApplicationImpl::doStart() lib=syslib module=syslib
A child process has been started. Pid = 16207

TRACE      2012-09-13 14:18:47.759 [syuxctask.cpp:886]
           CUnixProcessManager::sap_waitpid(pid_t pid, int * pStatus, int options)
           lib=syslib module=syslib
Child process 16207 returned 0

[Former Member · Accepted solution]

Christoph - I don't honestly know what the official "SAP way" is these days but the method we use was certainly supported when we started using it 15 years ago. Volker G. has refined it over the years (as have we and many others in the 400 world). I've done at least 35 "refreshes" using his method. As to CPF3794, that's a pretty generic failure message so you probably want to look in the joblog to see what preceded it. The most common cause I have seen is the job message queue fills up. Hence the command I use is:

SBMJOB CMD(RSTLIB  SAVLIB(R3PRDDATA) DEV(TAP01)  OPTION(*NEW) RSTLIB(R3<SID>DATA))  JOB(RSTPRD)  JOBMSGQFL (*WRAP)

Also, I am not sure why you want the output to go to *print; that's just one more thing that can break, although you would have a message on the operator's message queue to alert you that the printer file has overflowed.

[christoph_ostrop · Accepted solution]

Rick Githens wrote:
Christoph - I don't honestly know what the official "SAP way" is these days but the method we use was certainly supported when we started using it 15 years ago. Volker G. has refined it over the years (as have we and many others in the 400 world). I've done at least 35 "refreshes" using his method. As to CPF3794, that's a pretty generic failure message so you probably want to look in the joblog to see what preceded it. The most common cause I have seen is the job message queue fills up. Hence the command I use is:
SBMJOB CMD(RSTLIB  SAVLIB(R3PRDDATA) DEV(TAP01)  OPTION(*NEW) RSTLIB(R3<SID>DATA))  JOB(RSTPRD)  JOBMSGQFL (*WRAP)

manually executed, the prompted RSTLIB .... CMD starts to run and might be sucessfully,

but not within the SAP install program,

executing the RSTLIB .... from the SAP install program, only CPF3794 appears, but no other MSG in Joblogs

Rick Githens wrote:
Also, I am not sure why you want the output to go to *print; that's just one more thing that can break, although you would have a message on the operator's message queue to alert you that the printer file has overflowed.

that is the way how the SAP-installation program prompt the RSTLIB CMD, with ... OUTPUT(*PRINT) ...

i dont know, if this print-option is necessary for the SAP install program or not?

[christoph_ostrop · Accepted solution]

for people having the same problem ......in our OSS-ticket, we got the answer,

that the licence-program 5770SS1-Option-33 (PASE) has a problem,

CHKPRDOPT PRDID(5770SS1) OPTION(33)
-----------------------------------
Product 5770SS1 release V7R1M0 option 0033 load 2924 correctly installe
Product 5770SS1 release V7R1M0 option 0033 load 2929 correctly installe
Object not found for product 5770SS1 option 0033 release V7R1M0.
Exit program processing found error in product.
Product 5770SS1 release V7R1M0 option 0033 load 5111 not correctly installed.
Errors found by CHKPRDOPT.

i am not sure, if the status *ERROR in Option-33 is since installation of V7R1

or if some circumstances (maybe sapinstall-program) caused this problem,

all other LPARs with V7R1 do have Option-33 with status "*COMPATIBLE"

so we will re-install this 5770SS1-Option-33 and apply PTF again .....