No FAs are being completed by FACOMPL - Batch Control FACOMPL - SQL Error Code 999999992 Occurred In Module CIPOFOCB:GC200 SELEC
(Doc ID 2215982.1)
Last updated on AUGUST 05, 2022
Applies to:
Oracle Utilities Customer Care and Billing - Version 2.5.0.1.0 and laterInformation in this document applies to any platform.
Symptoms
**Disclaimer:** This KM article may include the following abbreviations:
CCB/CC&B - Oracle Utilities Customer Care and Billing
FA - Field Activities
No FAs are being completed by FACOMPL. if you review the debug output of the thread pool worker (*.THD1.stdout), the error SQL Error code 999999992 can be seen. This is not to be confused with <bug 21793722>, which was addressed in <patch 21793722> and involves a different module. Even if this patch is installed, the following error can still occur:
08:56:17,858 [DEFAULTWorker:1] INFO
(com.splwg.base.api.program.Displayer_Impl) SQL error in CIPOFOCB
.
08:56:17,911 [DEFAULTWorker:1] DEBUG
(org.hibernate.type.descriptor.sql.BasicExtractor) Found [SQL Error code %1
occurred in module %2] as column [MESSAGE5_165_0_]
.
08:56:17,912 [DEFAULTWorker:1] INFO
(com.splwg.base.support.context.FrameworkSession) (Server Message)
Category: 9
Number: 3
Call Sequence: ;CIPZCTJN
Program Name: CIPZCTJN
Text: SQL Error code 999999992 occurred in module CIPOFOCB:GC200 SELECT
Description: Please contact your system administrator.
Table:
Field:
08:56:17,983 [DEFAULTWorker:1] WARN
(com.splwg.base.support.batch.BatchWorkInSessionExecutable) Exception trapped
while executing batch work
com.splwg.base.api.batch.ThreadAbortedException:
com.splwg.base.support.program.NonZeroReturnCodeException(returnCd=2)
at
com.splwg.base.api.program.standard.SubprogramCICZEXTB.perform_ZZ999_EXIT_PROG
RAM(SubprogramCICZEXTB.java:53)
at
com.splwg.base.api.program.standard.SubprogramCICZEXTB.perform_ZZ999_EXIT_PROG
RAM(SubprogramCICZEXTB.java:23)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.perform_ZZ999_EXIT_PROGR
AM(ProgramCIPOFOCB.java:2501)
at
com.splwg.base.api.program.standard.SubprogramCICZSQLE.perform_ZZ000_SQL_ERROR
(SubprogramCICZSQLE.java:497)
at
com.splwg.base.api.program.standard.SubprogramCICZSQLE.perform_ZZ000_SQL_ERROR
(SubprogramCICZSQLE.java:27)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.perform_ZZ000_SQL_ERROR(
ProgramCIPOFOCB.java:2491)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.perform_GC200_GET_SPVER(
ProgramCIPOFOCB.java:1605)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.perform_GC100_LOCK_SP(Pr
ogramCIPOFOCB.java:1398)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.perform_GA000_MAIN_PROC(
ProgramCIPOFOCB.java:1082)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.perform_AA000_MAIN(Progr
amCIPOFOCB.java:732)
at
com.splwg.ccb.domain.fieldorder.batch.ProgramCIPOFOCB.invoke(ProgramCIPOFOCB.j
ava:702)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.j
ava:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at
com.splwg.base.api.program.ProgramInvokeFactory.invoke(ProgramInvokeFactory.ja
va:31)
at
com.splwg.base.support.batch.TranslatedBatchProgramDispatcher.executeBatchProg
ram(TranslatedBatchProgramDispatcher.java:29)
at
com.splwg.base.support.batch.GenericCobolBatchProgram.callProgram(GenericCobol
BatchProgram.java:123)
at
com.splwg.base.support.cobol.AbstractCobolProgram.callCobol(AbstractCobolProgr
am.java:64)
at
com.splwg.base.support.batch.GenericCobolBatchProgram.callCobolInCobolThread(G
enericCobolBatchProgram.java:70)
at
com.splwg.base.support.batch.GenericCobolBatchProgram.execute(GenericCobolBatc
hProgram.java:36)
at
com.splwg.base.support.batch.CobolBatchWork$DoExecuteWorkInSession.doBatchWork
InSession(CobolBatchWork.java:77)
at
com.splwg.base.support.batch.BatchWorkInSessionExecutable.run(BatchWorkInSessi
onExecutable.java:62)
at
com.splwg.base.support.batch.CobolBatchWork.doExecuteWork(CobolBatchWork.java:
54)
at
com.splwg.base.support.grid.AbstractGridWork.executeWork(AbstractGridWork.java
:72)
at
com.splwg.base.support.cluster.ThreadWork.processBatchWork(ThreadWork.java:54)
.
at
com.splwg.base.support.cluster.BatchWorkManager.processWork(BatchWorkManager.j
ava:78)
at
com.tangosol.coherence.commonj.WorkManager$ScheduleWork.run(WorkManager.java:2
266)
at
com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.Invoc
ationService.onInvocationRequest(InvocationService.CDB:12)
at
com.tangosol.coherence.component.util.daemon.queueProcessor.service.grid.Invoc
ationService$InvocationRequest.run(InvocationService.CDB:1)
at
com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CD
B:1)
at
com.tangosol.coherence.component.util.DaemonPool$WrapperTask.run(DaemonPool.CD
B:32)
at
com.tangosol.coherence.component.util.DaemonPool$Daemon.onNotify(DaemonPool.CD
B:65)
at com.tangosol.coherence.component.util.Daemon.run(Daemon.CDB:51)
at java.lang.Thread.run(Thread.java:745)
Caused by:
com.splwg.base.support.program.NonZeroReturnCodeException(returnCd=2)
... 35 more
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |