on 02-06-2014 10:21 AM
Hi All ,
Currently in my environment i have 4 real time jobs that coneect with 2 Job server
In the Access Server Tab for Real time Job mostly i am getting "Recyling" status
Error details in Server event log of Job Server:
(14.1) 02-06-14 00:00:16 (14894:472913664) JobServer: StopJob : Job is killed. (BODI-850054)
(14.1) 02-06-14 00:00:27 (14894:3823527680) JobServer: Starting job with command line -NOracle -SS1D.WORLD -UQA_REPO -P******** -eg -BOESsapdss01 -BOEUAdministrator
-BOEAsecEnterprise
-BOEP+04000000001A0B010010000022EC584AA633F668845D4CEA222ADE69DA5B99344F25770ABB3FF45D4070285079B2AE179708052BD44CC6674F27AB6DCD
821812A80B9DA8 -sRTJob_AddressRetrieval -hsapdss01:4000#service.SP_Service_AddressRetrieval_1@NoSSL -np
-Cx000000-183887605020511410314291064000000006447618500000 -CtRTDF -Cmsapdss01 -CaAccessServer -Cjsapdss01 -Cp3500
-l"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/trace_02_06_2014_00_00_27_1939__RTJob_AddressRetrieval.txt"
-z"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/error_02_06_2014_00_00_27_1939__RTJob_AddressRetrieval.txt"
-w"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/monitor_02_06_2014_00_00_27_1939__RTJob_AddressRetrieval.txt"
-Dt02_06_2014_00_00_27_1939 (BODI-850052)
(14.1) 02-06-14 00:00:27 (14894:3823527680) JobServer: StartJob : Job '02_06_2014_00_00_27_1939__RTJob_AddressRetrieval' with pid '31898' is kicked off
(BODI-850048)
(14.1) 02-06-14 00:01:10 (14894:472913664) JobServer: StopJob : Job is killed. (BODI-850054)
(14.1) 02-06-14 00:01:20 (14894:3823527680) JobServer: Starting job with command line -NOracle -SS1D.WORLD -UQA_REPO -P******** -eg -BOESsapdss01 -BOEUAdministrator
-BOEAsecEnterprise
-BOEP+04000000001A0B0100100000BEBF867167A7DCA2258B5F88ADD5D88EBFA3472FF7F0D4A3DEC72A46F8A58BF9638FD7A1A8B06D663C2524FCF922DC918C
5696BFEEA6FA95 -sRTJob_AddressRetrieval -hsapdss01:4000#service.SP_Service_AddressRetrieval_1@NoSSL -np
-Cx000000-183887605020511410314291064000000006447618500000 -CtRTDF -Cmsapdss01 -CaAccessServer -Cjsapdss01 -Cp3500
-l"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/trace_02_06_2014_00_01_20_1941__RTJob_AddressRetrieval.txt"
-z"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/error_02_06_2014_00_01_20_1941__RTJob_AddressRetrieval.txt"
-w"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/monitor_02_06_2014_00_01_20_1941__RTJob_AddressRetrieval.txt"
-Dt02_06_2014_00_01_20_1941 (BODI-850052)
(14.1) 02-06-14 00:01:20 (14894:3823527680) JobServer: StartJob : Job '02_06_2014_00_01_20_1941__RTJob_AddressRetrieval' with pid '429' is kicked off
(BODI-850048)
(14.1) 02-06-14 00:02:04 (14894:472913664) JobServer: StopJob : Job is killed. (BODI-850054)
(14.1) 02-06-14 00:02:14 (14894:3823527680) JobServer: Starting job with command line -NOracle -SS1D.WORLD -UQA_REPO -P******** -eg -BOESsapdss01 -BOEUAdministrator
-BOEAsecEnterprise
-BOEP+04000000001A0B010010000095D29DFD28893CEB22601B45CC165AF3473C1CA2E156ADAB265871CBEE03F2F1522D21CC88287327C7791EEC912C822307
30022C8131B0C0 -sRTJob_AddressRetrieval -hsapdss01:4000#service.SP_Service_AddressRetrieval_1@NoSSL -np
-Cx000000-183887605020511410314291064000000006447618500000 -CtRTDF -Cmsapdss01 -CaAccessServer -Cjsapdss01 -Cp3500
-l"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/trace_02_06_2014_00_02_14_1943__RTJob_AddressRetrieval.txt"
-z"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/error_02_06_2014_00_02_14_1943__RTJob_AddressRetrieval.txt"
-w"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/monitor_02_06_2014_00_02_14_1943__RTJob_AddressRetrieval.txt"
-Dt02_06_2014_00_02_14_1943 (BODI-850052)
"server_eventlog_2014-02-06.txt" 8988L, 1284371C
I am using BODS 4.1 & BOIPS 4.0 would you please update me the reason for this error and pls share your past experience.
Thanks
Daya
Hi Daya,
Could you please help me what is the resolution for this issue. I am also facing the same issue.
Thanks
John
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Joseph,
In my case issue is related to JMS Adapter & Memory.
(a) JMS Adapter re-starts issue in
Solution:
For this issue SAP has provided customized jar files.
Jar Files Name:
(a) acta_adapter_sdk.jar
(b) acta_broker_cleint.jar
(b) Memory Issue:
We have arond 38 real time job & 25 batch job and for that we have only 8 GB of RAM available in Server, But after analysis with below point we come to conclusion that we have to increase the RAm then only Job Server PID will remain constant.
(1) Check the memory utilization of Web Application
(2) Check the memory utilization of CMS Application
(3) Check the memory utilization of APS Services
(4) Check the memory utilization of RFC Services
(5) Check the memory utilization of all AL_Engine (All Real Time Job & Batch Job)
(6) Check the memory utilization of all AL_AccessServer (All Access Server configured in current landscape)
(7) Check the memory utilization of all AL_JobServer (All Job Server configured in current landscape)
(8) Check the memory utilization of database (Oracle,SQLServer,DB2..)
Thanks,
Daya
HI Daya,
Firstly, how can we measure these metrics, any guideline as to how to go about capturing them?
We are also having the same kind of an issue where a Real time job is processing a record and when we receive the second record it fails to process and keeps the XML file in reject queue. As the process failed, real time service is getting assigned a new PID. Upon doing additional testing found this.
In our real time job we have a Dimension and Fact that are inserted/updated within the same data flow. To ensure the referential integrity is maintained we have added a Transaction control on target table with Dimension as 1 and Fact as 2. The same job is running fine in DS 3.2 environment from where we are upgrading to DS 4.2.
We are using IPS 4.1 with DS 4.2 on Linux Red hat.
Regards,
Islauddin
Daya, could you please let us know what is there written in the Error Log of the RT job?
"/usr/sap/S1D/BOIPS/dataservices/log/JS_SBX01/s1d.world__qa_repo/error_02_06_2014_00_02_14_1943__RTJob_AddressRetrieval.txt"
Cheers
Ganesh Sampath
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
I think you can set the recycle count max value some where in the real time configuration of management console. Also kill the access server engine if its running long.
Arun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Daya,
Your settings seems ok. There is an option of controlled restart where you can manually do it.
Admin guide page 110, 3.13.5
https://help.sap.com/businessobject/product_guides/sbods42/en/ds_42_mgmt_cons_en.pdf
Arun
Thanks for the suggestion, But here issue is only that ID of Job Server is created again and again and due to that the log size of that Job Server is in GB.
As i understand that Job Server PID should be fixed if it change then it will generate a new log.
So here issue is configuration Let me chk again this real time configuration recycle count status.
Thanks,
Daya
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.