UBE Kernel Issue (Broken Pipe)

RonWeasley

Active Member
Hi All,
We have an weird problem in one of our Enterprise Servers (AS400). The UBE kernel reports 'broken pipe' error and no new jobs could be submitted until we kill the kernel and new kernel is spawned. Have anyone heard of this; or could you provide some insight on what might be the possible cause. The log file excerpt is below:


3452/106MAIN_THREAD Tue Apr 22 01:43:09.116088dbdrv_log.c196
OS400QL012 - GetSQLStmtNameFromSQLPkg: QCPFMSG *LIBL - CPE3455 - Broken pipe
3452/106MAIN_THREAD Tue Apr 22 01:43:09.123400dbdrv_log.c196
OS400QL017 - PrepareAndOrDescribe:prepare failed. QCPFMSG *LIBL - CPE3455 - Broken pipe
3452/106MAIN_THREAD Tue Apr 22 01:43:09.123488dbdrv_log.c196
OS400AG005 - DoPrepare:Statement is not prepared.
3452/106MAIN_THREAD Tue Apr 22 01:43:09.123568jdb_drvm.c1053
JDB9900168 - Failed to initialize db request
3452/106MAIN_THREAD Tue Apr 22 01:43:09.123608jtp_cm.c1015
JDB9909007 - Unable to obtain driver request handle
3452/106MAIN_THREAD Tue Apr 22 01:43:09.123664envapi.c561
MSC0000051 - The specified Library List, "JPY900", was not found in F00941
3452/106MAIN_THREAD Tue Apr 22 01:43:09.144728jdeknube.c775
KNT0000549 - Unable to determine path code for the environment, JPY900

Thanks,
 
Ron,

I think you lost your connection to the QSQSRVR job. This can be caused by backups (I don't know why), or the job dying, or someone cancelling the job. The only recovery I know of is killing the UBE kernel itself. Thankfully this is normally a non-event.

Hope this helps.

Tom Davidson
 
Looks like related to corrupt SQL package. I would try to clean up and recreate SQL package.

Chan
 
Tom,
Thanks. We are doing the same as well. Killing the UBE kernel for the past one year. It spreads to workflow kernel and xml publisher kernel if left unattended. We kill that as well.

I still hope that there is a permanent solution.

Regards,Ron
 
Back
Top