Status of UBEs set to E

Hi,

some of my UBEs are going sometimes to an E status code (SVM7333.F986110.JCJOBSTS). Enabled debugging on the UBE Server and the log shows the update statement to status D. The PDF is fine, no error within any log files.

Thanks for all replies.

Hi List

I am still struggeling with that F986110 updates. One/Two of 2000 UBE per day seems to have an issue with updating F986110. Unfortunately I cannot see the real values of the update statement. The job# in jde.log is unique exactly for the UBE in error.
Also OracleNet tracing or UBE tracing would produce to much data.

Here is my config:

-JDE Xe U7, SP22_I1
-Oracle RAC 9.2.0.6 on W2K3
-2 UBE server, sharing the same server map (SVM7333)

I would really appreciate any ideas what to check.
--------------------------------------------------------------

jde.log for a UBE in error:

3452/4168 Tue Jul 26 22:11:27 2005 RUNBATCH.C383
INITIALIZING RUNBATCH job: 1743066
3452/4168 Tue Jul 26 22:11:27 2005 IPCPUB.C3135
process 3452 <Program Name> registered in entry 23
3452/4168 Tue Jul 26 22:11:27 2005 RUNBATCH.C633
Startup for User=JOBS_G, Env=PD7333, Job#=1743066
3452/4168 Tue Jul 26 22:11:27 2005 RUNBATCH.C650
bAPListening=0
3452/4168 Tue Jul 26 22:11:28 2005 IPCPUB.C3515
API ipcSawUnregisterProcV1 : process 3452 unregistered in entry 23
3452/4168 Tue Jul 26 22:11:28 2005 RUNBATCH.C1422
Job of type failed with rcode = 0
3452/4168 Tue Jul 26 22:11:28 2005 DBPERFRQ.C386
OCI0000178 - Unable to execute - UPDATE SVM7333.F986110 SET JCJOBQUE=:BND1,JCJOBPTY=:BND2,JCJOBSTS=:BND3,JCENHV=:BND4,JCUSER=:BND5,JCPSWD=:BND6,JCJOBTYPE=:BND7,JCSBMDATE=:BND8,JCSBMTIME=:BND9,JCJOBNBR=:BND10,JCEXEHOST=:BND11,JCORGHOST=:BND12,JCPROCESSID=:BND13,JCACTDATE=:BND14,JCACTTIME=:BND15,JCSRVBLOBA=:BND16,JCFUNO=:BND17,JCPRTQ=:BND18,JCFNDFUF1=:BND19,JCFNDFUF2=:BND20 WHERE ( JCEXEHOST = :KEY1 AND JCJOBNBR = :KEY2 )

3452/4168 Tue Jul 26 22:11:28 2005 DBPERFRQ.C393
OCI0000179 - Error - ORA-00001: Verstoß gegen Eindeutigkeit, Regel (SVM7333.F986110_PK)
3452/4168 Tue Jul 26 22:11:28 2005 JDB_DRVM.C938
JDB9900401 - Failed to execute db request
3452/4168 Tue Jul 26 22:11:28 2005 JDB_EXET.C2594
JDB3600011 - Failed to perform Update for F986110
3452/4168 Tue Jul 26 22:11:28 2005 RUNBATCH.C1435
Unable to update F986110 with ERROR status

Michel,
The UBE that that you get an error lauch another synchronous UBE?
Because when you have for example R55X0001 that lanunches R55X0002 synchronous and you have an error on R55X0002, the result is that R55X0001 is with error. You dont see any record of R55X0002 into the submitted jobs, until is finalized successfully

Hope this help...

Re: Status of UBEs set to E but only sometimes

Hi,

no, just 'normal' reports.

1-UBEs are running fine, the runbatch process is ending with updating the job table (F986110) to Done. After that the jdequeue process that has started the runbatch process set the status to Error.
I've got this error within the jdequeue process:

--
6188/7364 Wed Jul 27 10:23:47 2005 IPCPUB.C3135
process 6188 <jdequeue.exe> registered in entry 8

6188/7364 Thu Jul 28 08:35:09 2005 JDEQUEUE.C1041
Job of type UBE failed with rcode = 1

6188/7364 Thu Jul 28 08:47:47 2005 JDEQUEUE.C1041
Job of type UBE failed with rcode = 1
--

Re: Status of UBEs set to E but only sometimes

michel,
Other possibility is that the user submitting the Job have an invalid address number.
The workcenter message fails..

Hope this help

Re: Status of UBEs set to E but only sometimes

checked this but every user and my scheduler users have AB#.