on 09-11-2012 11:26 AM
hi experts,
we are using the tidal tool to schedule and monitor the jobs in the BI system .we are facing the momentary issues for the jobs .In the sm37 job logs are showing as the cancelled but in the rspc the chain is success..This was happening once in while.
The loads are success but why job log is showing cancelled .is there any sap notes to be implemented to avoid this error or at code level any enhancements to be performed.....please provide any valid inputs related to this issue .
hi Karthik,
Please go and check whether the process really is doing what it is supposed to do properly.. Like in your log - the log clearly says that the job terminated..
Please check the structure of your chain - the log in the beginning says something about sequencing..
I have highlighted the log lines I am referring to, check and see your process chain if it has sequencing which is wrong or if it needs restructuring. This must help resolve your issue.
Regards,
Sheen
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Karthik,
What is error message and in which step your job is failing.
Please check for dumps in ST22 and check system log using SM21 for specific date/time.
Regards,
Rajendra Dewangan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi rajendra,
Thanks for your quick reply..
i wanna to confirm that the chain is success and no failures to any of the steps.(Tcode:-rspc) but if we check the job logs in the sm37 it showing status as the cancelled .Is there any reason why the job logs status is cancelled but the chain is success.
HI rajendra,
Here iam sending the logs please find it.....thanks for your support.
Job log overview for job: 001_AP00_GLB_LD_EPMD_R3_CMSTD / 21061700
09/10/2012 21:06:17 Job started 00 516 S
09/10/2012 21:06:17 Step 001 started (program ZPROCESS, variant AP_E2_D_CMSTD, user ID HPBTCH) 00 550 S
09/10/2012 21:06:18 A type "Attribute Change Run" process has to follow process "Execute InfoPackage" var.ZPAK_47NW83SLPBL4571HJ6E16BTR1 in the chain RSMPC 016 S
09/10/2012 21:06:18 A type "Attribute Change Run" process has to follow process "Execute InfoPackage" var.ZPAK_47O0XRA1YKI9Z74547TFO6XY5 in the chain RSMPC 016 S
09/10/2012 21:06:19 A type "Attribute Change Run" process cannot precede process "Execute InfoPackage" var. ZPAK_4QH4G4OHWIQA36SXUFSZDIEZG in the chain RSMPC 013 S
09/10/2012 21:06:30 Chain AP_GLB_LD_EPMD_R3_CMSTD was removed from scheduling RSPC 026 S
09/10/2012 21:06:30 Program RSPROCESS successfully scheduled as job BI_PROCESS_AND with ID 21063005 RSM 703 S
09/10/2012 21:06:31 Program RSPROCESS successfully scheduled as job BI_PROCESS_AND with ID 21063006 RSM 703 S
09/10/2012 21:06:31 Program RSPROCESS successfully scheduled as job BI_PROCESS_ATTRIBCHAN with ID 21063103 RSM 703 S
09/10/2012 21:06:31 Program RSPROCESS successfully scheduled as job BI_PROCESS_ATTRIBCHAN with ID 21063104 RSM 703 S
09/10/2012 21:06:31 Program RSPROCESS successfully scheduled as job BI_PROCESS_ATTRIBCHAN with ID 21063105 RSM 703 S
09/10/2012 21:06:31 Program RSPROCESS successfully scheduled as job BI_PROCESS_ATTRIBCHAN with ID 21063106 RSM 703 S
09/10/2012 21:06:31 Program RSPROCESS successfully scheduled as job BI_PROCESS_CHAIN with ID 21063100 RSM 703 S
09/10/2012 21:06:32 Program RSPROCESS successfully scheduled as job BI_PROCESS_CHAIN with ID 21063101 RSM 703 S
09/10/2012 21:06:32 Program RSPROCESS successfully scheduled as job BI_PROCESS_CHAIN with ID 21063202 RSM 703 S
09/10/2012 21:06:32 Program RSPROCESS successfully scheduled as job BI_PROCESS_DROPCUBE with ID 21063200 RSM 703 S
09/10/2012 21:06:32 Program RSPROCESS successfully scheduled as job BI_PROCESS_DROPCUBE with ID 21063201 RSM 703 S
09/10/2012 21:06:32 Program RSPROCESS successfully scheduled as job BI_PROCESS_DTP_LOAD with ID 21063201 RSM 703 S
09/10/2012 21:06:32 Program RSPROCESS successfully scheduled as job BI_PROCESS_LOADING with ID 2106320K RSM 703 S
09/10/2012 21:06:33 Program RSPROCESS successfully scheduled as job BI_PROCESS_LOADING with ID 2106320L RSM 703 S
09/10/2012 21:06:33 Program RSPROCESS successfully scheduled as job BI_PROCESS_LOADING with ID 2106330M RSM 703 S
09/10/2012 21:06:33 Program RSPROCESS successfully scheduled as job BI_PROCESS_ODSACTIVAT with ID 21063302 RSM 703 S
09/10/2012 21:06:33 Program RSPROCESS successfully scheduled as job BI_PROCESS_ODSACTIVAT with ID 21063303 RSM 703 S
09/10/2012 21:06:33 Program RSPROCESS successfully scheduled as job BI_PROCESS_TRIGGER with ID 21063301 RSM 703 S
09/10/2012 21:06:33 Chain AP_GLB_LD_EPMD_R3_CMSTD Was Activated And Scheduled RSPC 025 S
09/10/2012 21:06:39 4R56Q8ZRP6BQQWC8J8PA5UYWX log id generated,process chain started ZBW 007 S
09/10/2012 21:07:00 The 4R56Q8ZRP6BQQWC8J8PA5UYWX DROPCUBE of DELETE_GMTOGECA DELC_4R58G2T6BDJRW906L7ZHUBW3L finished ZBW 004 S
09/10/2012 21:07:10 The 4R56Q8ZRP6BQQWC8J8PA5UYWX DROPCUBE of DELETE_GMTOMECA DELC_4R56QCU16H6I262BG9VF6UBSX finished ZBW 004 S
09/10/2012 21:07:20 The 4R56Q8ZRP6BQQWC8J8PA5UYWX TRIGGER of AP_GLB_LD_EPMD_R3_CMSTD 4R56Q97G84XG9IVOP2RMFWXMP finished ZBW 004 S
09/10/2012 21:07:51 The 4R56Q8ZRP6BQQWC8J8PA5UYWX LOADING of ZPAK_47O0XRA1YKI9Z74547TFO6XY5 REQU_4R5GF56WVA002YTLCB708FDC1 finished ZBW 004 S
09/10/2012 21:08:23 The 4R56Q8ZRP6BQQWC8J8PA5UYWX ODSACTIVAT of ACTIVATE_ODS_GMTOMECA2 ODSA_4R56QQHMVZRV68N1TQ192C1MP finished ZBW 004 S
09/10/2012 21:10:50 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:11:11 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:11:31 The 4R56Q8ZRP6BQQWC8J8PA5UYWX ATTRIBCHAN of APJ_ATTR_CHANGE_RUN_MM_IO STRU_4R56S6Z8GG48G9JHP615RR9S1 finished ZBW 004 S
09/10/2012 21:11:41 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:12:02 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:12:23 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:12:43 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:13:04 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:13:25 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:13:45 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:14:06 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:14:26 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:14:47 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:15:07 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:15:28 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:15:38 The 4R56Q8ZRP6BQQWC8J8PA5UYWX LOADING of ZPAK_47NW83SLPBL4571HJ6E16BTR1 REQU_4R56QJG5I9VH3KT8H5VZUJ801 finished ZBW 004 S
09/10/2012 21:15:59 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:16:20 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:16:40 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:17:01 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:17:22 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:17:42 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:18:03 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:18:24 The 4R56Q8ZRP6BQQWC8J8PA5UYWX CHAIN of AP_MM_IO 4R5FOUHBHX08SRDO9WVSSNDJQ finished ZBW 004 S
09/10/2012 21:19:35 Job cancelled after system exception ERROR_MESSAGE 00 564 A
Thanks & Regards,
karthik.M
Hi Karthik,
The job log is clearly saying there is some system exception, something wrong in system. Please use tcode ST22 for checking/analyzing it. You can take help from your ABAP/Basis team for analyzing this system exception.
As commented earlier you can also check or ask basis team to check system logs using tcode SM21.
It is very tough to recommend something based on line "Job cancelled after system exception ERROR_MESSAGE".
Hope this helps.
Regards,
Rajendra Dewangan
hi experts,
please provide any inputs regarding the issue..
Thanks & Regards,
karthik.M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
90 | |
10 | |
10 | |
10 | |
7 | |
7 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.