cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade from 4.6C to ERP ECC 6.0

Former Member
0 Kudos

Hi,

Help!!! I'm running the prepare the first time and encountered this problem during the Kernel extract. I received this message from '/usr/sap/put/EXTRKRN.LOG'

1 ETQ201XEntering upgrade-phase "EXTRACTKRN_PRE" ("20061016131342")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '', GwService = ''

4 ETQ399 Environment variables:

4 ETQ399 =<null>

4 ETQ399 auth_shadow_upgrade=0

1EETQ204 Upgrade phase "EXTRACTKRN_PRE" aborted with severe errors

Ramon

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

What Kernel CD/DVD are you using? I had problems loading the kernel from DVD that came with my upgrade kit. I downloaded 51031792 to solve the problem.

thanx

Mark

Former Member
0 Kudos

Hi Victor,

Here is the command when I received the error.

Error message CPF0006 running 'APYSAP TYPE(KERNEL) SID(DEV) DSTLIB(SAP700DEV) DLTSQLPKG(NO) DSTDIR

('/usr/sap/put/exe')'

SEVERE ERROR(S) OCCURRED IN EXTRACTKRN_PRE !!!

Thanks,

Former Member
0 Kudos

Hi Ramon,

If the library SAP700DEV does contain the kernel programs, likely LODSAPKRN didn't have issue with the path.

Run the APYSAP command manually and check the jog log?

The root cause may be hidden in the log or xml files in /usr/sap/put or the spool files, just hard to dig it out sometimes.

Thank you,

Victor

0 Kudos

Hi Ramon,

The major source of information should be the joblog of the job running APYSAP. During the upgrade this should be the joblog of the SAPup job.

When trying to reproduce by hand make sure you have

- SAPUP *LIB in your library list and an

- empty target directory '/usr/sap/put/exe'.

If you want you can frame your APYSAP call with STRO4TRC and ENDO4TRC from the 700 kernel library (add SAP700DEV to your libl only for the call of xxxO4TRC and remove it afterwards). Specify a trace id as a name, your job and qinter as the subsystem.

HTH,

Thomas

Former Member
0 Kudos

Hi Ramon,

In the thread "Error on LODSAPKRN during EP Install", Thomas mentioned the following:

**********

I am pretty sure that LODSAPKRN is not capable of the long paths. A workaround could be to create a link to the DVD root (or provide a copy with shorter names) and run the command manually with adapted paths.

**********

Could it be the reason for your case? More info is availabe in that thread.

Good luck,

Victor