Info:
Running Control-M 6.4 server/agent
Issue:
We just upgraded from 6.1 to 6.4 and we are running tests on all our agents. We are testing a few job types across all agents. The only one not acting normally are Dummy jobs. When we do our multi agent submit from the EM GUI they are all stuck in Wait State, and all say "Job is not in Wait State" when you "Why" them.
Holding/Freeing the Dummy job and releasing it will move them to Executing state in the EM GUI.
Looking in the DB they are all state 5 (ended). But in the EM GUI they are either wait or executing. I left them overnight yesterday, nothing changes.
Short:
Dummy jobs stuck in wait state in EM GUI,
In DB state is 5 (ended). GUI never reflects the 5 state from the DB.
- Is only effecting jobs of type Dummy jobs
- Command and Job types are acting normally
Dummy jobs stuck in Wait Status
Ok found the reason, but don't have a solution on the fix.
1208 21:37:01.29 TR: TR_JOB_handle_job_locked: checkerr(StructLogin=0x8fdc8c0) - Error, ORA-12899: value too large for column "CTLM64SCAL"."CMR_AJF"."OSCOMPMSG" (actual: 1002, maximum: 999)
1208 21:37:01.29 TR: TR_JOB_handle_job_locked: checkerr(StructLogin=0x8fdc8c0) - Error, ORA-12899: value too large for column "CTLM64SCAL"."CMR_AJF"."OSCOMPMSG" (actual: 1002, maximum: 999)
Code: Select all
1208 21:37:01.29 TR: TR_JOB_handle_job_locked: checkerr(StructLogin=0x8fdc8c0) - Error, ORA-12899: value too large for column "CTLM64SCAL"."CMR_AJF"."OSCOMPMSG" (actual: 1002, maximum: 999)
1208 21:37:01.29 TR: TR_JOB_handle_job_locked: ExecDML() - Failed in OCIStmtExecute
1208 21:37:01.29 TR: TR_JOB_handle_job_locked: update CMR_AJF set JOBNO= 137483 ,PRIORITY= 0 ,CRITICAL='N ',TASKTYPE='U ',CYCLIC='N ',CONFIRM_R='N ',CONFIRMED='N ',RETRO='N ',AUTOARCH=' ',TASKCLASS=' ',HOLDFLAG='N ',STATUS='Y ',STATE='6 ',CYCLICINT='00001M',APPLGROUP='OPS-TEST-1',NODEGRP='64AgntInst',NODEID='peck',MEMLIB=' ',MEMNAME=' ',OVERLIB=' ',ODATE='20091203',PROCID=' ',RERUN_NO= 1342767877 ,OSCOMPSTAT= -133627131 ,OSCOMPMSG='ÔTöF¢^F^HP^E^C ^A ',NEXTTIME='20091208213800',PREVDATE='20091202',NEXTDATE='20091204',STARTRUN='20091208213700',ENDRUN='20091208213700',MAXRERUN= 0 ,FROMTIME=' ',UNTIL=' ',JOBNAME='TEST-DUMMY',SCHEDTAB='OPS-TEST',OWNER='ag64scal',MAXWAIT= 0 ,APPLIC='Operational',RUNCOUNT= 2 ,DAILYNAME='FORCED',AJFSONSTR='NNNNNNNYNNNNNY',DOCMEM=' ',DOCLIB=' ',MAXDAYS= 0 ,MAXRUNS= 0 ,UNKNOWNTIM= 0,STARTENDCYCIND= ' ' ,TRIGGER_TAG= ' ' ,GROUP_ORD= 0,AUTHOR= 't819986',ADJUST_COND= ' ',MULTIAGENT= 'Y ',APPLTYPE= ' ',TIMEZONE= ' ',STATEMSK= 'N ',APPLVER= ' ',TIMEREF= ' ',CMVER= ' ',APPLFORM= ' ',ORDER_TIME= '20091204121234',RJX_AGENT_NAME= ' ',INSTREAM_IND='N ',TOLERANCE= 0 ,CURRENT_RUN= 0 ,CYCLIC_TYPE= 'C ',CPUTIME= 0,ELAPTIME= 0 where ORDERNO = 348456
From: Control-X@yahoogroups.com
I have been looking at the 6.4.01 Server release notes of Fix Pack 3 which is due to be GA in a few days, and think this issue is now resolved.
CAR00040409 In rare circumstances, dummy jobs in CONTROL-M/Server may not end (remain in color yellow).
So I think you just need to wait for the offical notification of FP3 release,and try it out.