KRN updagrade error

[Former Member]

Hi,

Please help me, while doing a kernel upgrade recived following error -

=====================================================

Constraint was added.

1 constraint(s) added to file O4AFFILE.

Constraint was added.

1 constraint(s) added to file O4AFFILE.

File O4AFFILE in library PCHX42HYB restored.

8 objects restored from PCH640UOPT to PCHX42HYB.

20400 - UPDHYBLIB SRCHYBLIB(PCHX42HYB) SRCARCHIVE(O4AFFILE)

DSTHYBLIB(R3640X2OPT) DSTARCHIVE(O4AFFILE) CHKCONS(YES) CHKLCK(NO)

Checking patch library R3640X2OPT for consistency

found invalid record (PARTID=¢dir=1]ifsname=servicehttp]!)

Number of invalid records found: 1

Number of ILE objects missing: 0

Number of IFS blobs missing in archive file: 0

Number of IFSNAME duplicates found: 0

---> hybrid library PCHX42HYB is inconsistent - ERROR

Patch library PCHX42HYB is inconsistent.

25000 - RCVMSG MSGTYPE(EXCP) RMV(NO) KEYVAR(&ERRKEYVAR1)

25200 - RCVMSG MSGTYPE(PRV) MSGKEY(X'000006D4') RMV(NO)

KEYVAR(&ERRKEYVAR2) MSG(&ERRMSG) MSGDTA(&ERRMSGDTA) MSGID(&ERRMSGID)

RTNTYPE(&ERRRTNTYPE) MSGF(&ERRMSGF) SNDMSGFLIB(&ERRMSGFLIB)

25800 - RCVMSG MSGKEY(X'000006D4') MSGDTA(&ERRMSGDTA) MSGID(&ERRMSGID)

MSGF(&ERRMSGF) SNDMSGFLIB(&ERRMSGFLIB)

25900 - SNDPGMMSG MSGID(CPF0006) MSGF(QSYS/QCPFMSG) MSGDTA(' ')

MSGTYPE(*ESCAPE)

Errors occurred in command.

Library PCHX42 removed from library list.

APYR3FIX: Patch installation failed (see joblog)

Errors occurred in command.

============================================================

Please check if you could give some clue to me to proceed furthur on this

-Gopi

[Former Member]

Hi Gopi

please have a look at note 1026035. I think, it could solve your problem.

Regards

Bernd Zimmer, basycs GmbH

[Former Member]

Hi Bernd,

I've find the same note in OSS, And the error is solved now.

Any way thanks a lot for your responce and for ur quick responce.

Thank You !

gopi.

[Former Member]

Hi Gopi,

that sounds to me, that the APYR3FIX had a problem during the last apply ;-((

In order to find the root cause it might be an option to restore the old kernel again and retry. If it is OK, nobody can check, otherwise an OSS message should be opened at BC-OP-AS4 in order to find a real solution for that problem.

Regards

Volker Gueldenpfennig, consolut.gmbh

http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de