UBE kernel and sqlcode 113 (F98BLOB)

[jdeKrnl]

Hi. I was wondering if anyone has seen this issue. UBE kernel displays the following error, keeps throwing similar errors, and eventually goes to zombie:

60 Wed Feb 16 07:05:52 2005 dbdrvag.c263
OS40001078 - DoPrepare: sql code is -113

60 Wed Feb 16 07:05:52 2005 jdb_drvm.c839
JDB9900168 - Failed to initialize db request

60 Wed Feb 16 07:05:52 2005 jtp_cm.c1088
JDB9909007 - Unable to obtain driver request handle

60 Wed Feb 16 07:05:52 2005 jdb_exet.c4091
JDB3500011 - Failed to delete for F98BLOB

This is on ERP 8.0, SP22_L1, AS400, V5R2. The issue is somewhat intermittent (every other day, usually early in the morning when there is heavy volume of UBE requests). Other UBE kernels perform correctly before, during, and after failure in this particular process.

It appears that once the report is in queue (status S), the UBE kernel does a blind DELETE on F98BLOB. The SQL statement is built using the report name and job number, something like

DELETE FROM SVM7334B/F98BLOB WHERE ( KSKEYSEQ = '%SERVER%-%JOBNUMBER%-' AND KSOBNM = 'F986110' )

It seems that the UBE kernel is failing when trying to build this statement. From the IBM DB2 Message reference:

“<identifier>” contains a character that is not allowed or does not contain any characters. Explanation: An SQL-variable-name, parameter-name or condition-name “<identifier>” contains an invalid character. Only characters that are valid for an SQL ordinary identifier are allowed.

Eventually a new UBE kernel is spawned and it works fine. The strange thing is that the kernel apparently cannot recover from this error.

Any ideas will be greatly appreciated.

Thanks

jdeKrnl
ERP 8.0, SP22_L1, AS400, V5R2

 

[JDEPrincess]

“DoPrepare: sql code is -113” indicates that SQL Prepare statement has failed with “Name &1 not allowed” error message (replace ‘&1’ with invalid name UBE attempted to use).

An ordinary identifier (name) must begin with (A-Z, $, #, or @) and be followed by zero or more (A-Z, 0-9, $, #, @, or _).

Diagnostics should be focused on the process that generates the name for the UBE, as it is generating an invalid name.

 

[jdeKrnl]

The thing that puzzles me is why the UBE kernel cannot recover from this error...

 

[jean_driscoll]

I called in that issue awhile back. It was fixed in a service pack upgrade, somewhere in the SP22 range. We've been on SP22_E1 since Aug, 2003. We've had the -113 issue since we put on AS/400 V5R2 cum 4077520 in October and are getting ready to upgrade to a new service pack after 1 1/2 years on the current one. The OneWorld support tech says that there was a limit to how many jobs could be submitted to the UBE kernel and the problem was fixed in a service pack.

 

[jdeKrnl]

Hi Jean,

Thank you for the information. It is somewhat comforting to know that others have seen this issue before. I also have a case open for this issue, but it has gone nowhere so far. Since we have no plans to upgrade Service Pack any time soon, we may have to push for a custom one-off.

Cheers,

jdeKrnl
ERP 8.0, SP22_L1, AS400, V5R2