SM37 - JOBs was CANCELED

Hello all,
Can someone explain why Job was Canceled...
tx = SM37 - JOBs were CANCELED
Some JOBS were finished ans some were canceled:
name: DELIVERY_APR / user: JHERNANS/ stts: COMPLETED/ date: 06.06.2007/start: 01:00:32/ finished: 07:26:17
name: DELIVERY_JUN / user: JHERNANS/ stts: CANCELED/ date: 06.06.2007/start: 01:00:36 /finished: 01:03:56/
name: DELIVERY_MAR / user: JHERNANS/ status: CANCELED/ date: 06.06.2007/ start: 01:00:32
name: TS MAY NAT/ user: JHERNANS/ status: CANCELED/ date: 06.06.2007/ start: 01:00:36
All JOBS above has just 1 STEP which is:
ABAP program: AQIWGM==========TS============
However each JOB has a different VARIANT(PARAMETER):
job: DELIVERY_APR / parameter: &0000000004820
job: DELIVERY_JUN / parameter: &0000000004885
job: DELIVERY_MAR / parameter: &0000000004801
job: TS MAY NAT / parameter: &0000000004856
ALL CANCELEDS JOBS were canceled because :
ABAP/4 processor: DBIF_RSQL_SQL_ERROR
All CANCELED JOBS has the same at Job Log:
- ABAP/4 processor: DBIF_RSQL_SQL_ERROR/ message class: 00/ message nº: 671/ message type: A
- Job cancelled/ message class: 00/ message nº: 518/ message type: A
Question: What has happened?
Is a time overlapping problem
Or
Can it be a program problem?
In Source Code Extract from the dump message there is:
002400 START-OF-SELECTION.
002410 perform init_texthandling(rsaqexce) using 'CL_TEXT_IDENTIFIER' ' ' 'ZSTE
002420 data: %ret type i.
002430 if sy-batch is initial and %excel is not initial.
002440 perform check_wingui(rsaqsyst) using %ret.
002450 if %ret <> 0.002460 message e842(aq).
002470 endif.
002480 endif.
002490 perform authority_begin(rsaqexce).
002500 perform authority(rsaqexce) using 'LIPS'.
002510 perform authority(rsaqexce) using 'VBUP'.
002520 perform authority(rsaqexce) using 'VBAP'.
002530 perform authority(rsaqexce) using 'LIKP'.
002540 perform authority(rsaqexce) using 'VBAK'.
002550 perform authority(rsaqexce) using 'KNA1'.
002560 perform authority_end(rsaqexce).
+002570 perform %comp_ldesc.
select LIPSLFIMG LIPSLGORT LIPSPOSNR LIPSVBELN LIPSVGBEL LIPSVGPOS
002590 VBUP~WBSTA
002600 into (LIPS-LFIMG , LIPS-LGORT , LIPS-POSNR , LIPS-VBELN , LIPS-VGBEL , L
002610 , VBUP-POSNR , VBUP-VBELN , VBUP-WBSTA )
002620 from ( LIPS
002630 inner join VBUP
002640 on VBUPPOSNR = LIPSPOSNR
002650 and VBUPVBELN = LIPSVBELN )
002660 where LIPS~LFIMG in SP$00020
002670 and LIPS~LGORT in SP$00005
002680 and LIPS~VBELN in SP$00018
002690 and LIPS~VGBEL in SP$00022
002700 and LIPS~WERKS in SP$00017
002710 and VBUP~KOSTA in SP$00014.
002720 and VBUP~WBSTA in SP$00012.
002730 %dbacc = %dbacc 1.+002740 if %dbacc = 0.
002750 stop.
002760 endif.
002770 check SP$00020.
LOOKING MORE the DUMP SCREEN:
Runtime errors DBIF_RSQL_SQL_ERROR
Exception CX_SY_OPEN_SQL_DB
Occurred on 06.06.2007 at 01:03:56
An SQL error occurred when accessing a table.
What happened?
What can you do?
Make a note of the actions and input which caused the error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer termination messages, especially those beyond their normal deletion date.
Error analysis
An exception occurred. This exception will be dealt with in more detail below. The exception, assigned to the class 'CX_SY_OPEN_SQL_DB', was not caught, which led to a runtime error. The reason for this exception is:
How to correct the error
Database error text........: "ORA-01114: IO error writing block to file %s (block # %s)" Internal call code "[RSQL/FTCH/LIPS ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem in the SAP note system. If you have access to the note system yourself, use the following search criteria:
"DBIF_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"AQIWGM==========TS============" or "AQIWGM==========TS============"
"START-OF-SELECTION"
Thanks a lot,
Barbara

From the dump:
> select LIPSLFIMG LIPSLGORT LIPSPOSNR LIPSVBELN LIPSVGBEL LIPSVGPOS
002590 VBUP~WBSTA
002600 into (LIPS-LFIMG , LIPS-LGORT , LIPS-POSNR , LIPS-VBELN , LIPS-VGBEL , L
002610 , VBUP-POSNR , VBUP-VBELN , VBUP-WBSTA )
The listing seems to be cut off, so I don't know if this is the error or not, but it's something you can check.
Rob

Similar Messages

Report Job was cancelled upon user request???

Hi,
My reports take more than 10 minutes to complete, most times I get
"Report Job was cancelled upon user request".
error, how to fix this problem? Is there any time limit inside the report I can set.
Thanks

hi ,
There is no limit on the report run time. The most probable reason why you are getting the 'Report cancelled upon user request' message is the users might have hit the "cancel Report" button which is displayed when it is running in 'SYNCHRONOUS MODE'. do not hit that button as it will terminate the report. to increase the speed of returning the results by the report, try improving the sql that you use in the report, or if you have DBA rights try adding in INDEXES on the columns of the tables used by the report.
Hope this helps
Manoj

Oracle Reports Server CGI - Report Job was cancelled upon user request.

I am running reports on the web through Forms using Run_Report_Object built in. I am using Oracle 9iAS Enterprise Edition Release 1(1.2.2.2.2), Forms 6i Patch 9 (6.0.8.18.3) and Reports 6i Patch 9 (6.0.8.18) using CGI implementation. Most reports are running fine, but I have one that produces 125 pages and we are getting the following messages in the browser:
Error: The requested URL was not found, or cannot be served at this time.
Oracle Reports Server CGI - Report Job was cancelled upon user request.
However if you look at the Reports Server Queue Status thru the browser it shows that the report did finish, but it took 16 minutes. But the user gets the above message in their browser window.
Is there a way to get the first page of the report to display, while the rest of the report finishes, so the browser window doesn't timeout and display the above error?
Any help would be greatly appreciated.

hi ,
There is no limit on the report run time. The most probable reason why you are getting the 'Report cancelled upon user request' message is the users might have hit the "cancel Report" button which is displayed when it is running in 'SYNCHRONOUS MODE'. do not hit that button as it will terminate the report. to increase the speed of returning the results by the report, try improving the sql that you use in the report, or if you have DBA rights try adding in INDEXES on the columns of the tables used by the report.
Hope this helps
Manoj

Job was cancelled in source sytem.

Hi,
One job was in cancelled state in source system itself.How can i correct the error?how can i get the data from source sytem.could please anybody help me out on this issue please.In RSMO,in that statu tab its stating as JOB OVERVIEW,by clicking onto this its leads to,r/3.by executing this one it shows as job cancelle.update method is delta.
Thanks & Regards,
Praveena.

Hi anil,
one ODS is getting nearly 500000 of records,it is loading master data,here the problem is that in details tab processing process is well all the datapackets are getting fine data,but at transfer tab after processing of infoidocs,dataidocs should be filled,but there it self problem is getting.in status tab its is in yellow status i cant forcibly make it into green.how can i solve this issue.And please give me reply more detaily about RSODSACT tbale details,what are changes can be done by using this table.
Thanks & Regards,
Mano.

User had just run a payment run when it was cancelled

Hi
We ran a payment run on F110, but the job cancelled because the user was set to locked by accident. No payments have processed, but the payment run icon shows the payment run is complete The log in F110 shows the payment run job was cancelled. When we tried to create a new proposal the payments in the canceled payment run did not appear. Please advise, can we use reorganise the payment run to delete the run and then create a new proposal and payment run, or is there any other option to process the run that has been cancelled. Is there a programme that will rerun the cancelled job or rerun the payment run.
thanks
Kylie

Take a look at note 86587.
The note states the followingu2026
Payment Posting and Update Terminations.
To check for, analyze and determine how to correct terminations, use the following menu path from F110:
'Edit>Payments>Termination of Posting'
You may drill down on the "ERR" (error) notifications to get details. Once corrections are made, processing can be restarted and followed to completion.
The menu path 'Edit>Payments>After Termination>Draw up again' may be used to restart the entire payment run from the point where processing has stopped, if permitted according to the run status.

Hai i am facing problem in solving the job which cancelled.

In monitoring the porocess chain the non loading process failed (AND PROCESS) when i went diplay messages the job was cancelled.how to correct the cancelled and where i have to correct.

Ashok,
Looks like you have raised a duplicate post for finding cancelled jobs in BI:
How to find the cancelled job
am locking the post mentioned since it appears to be a duplicate...

In LO Cockpit, Job contol job is cancelled in SM37

Dear All
   I am facing one problem. Pl help me to resolve that issue.
When ever I am scheduling the delta job for 03 (Application Component), that is cancelled in SM37. Hence, I couldn't retrive those data from queued delta MCEX03 (smq1 or lbwq) to RSA7 because of job is cancelled. When I have seen that job log I got below Runtime Errors. Please hep me to resolve this issue
Runtime Errors         MESSAGE_TYPE_X
Date and Time          04.10.2007 23:46:22
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
Short text of error message:
Structures have changed (sy-subrc=2)
Long text of error message:
Technical information about the message:
Message class....... "MCEX"
Number.............. 194
Variable 1.......... 2
Variable 2.......... " "
Variable 3.......... " "
Variable 4.......... " "
How to correct the error
Probably the only way to eliminate the error is to correct the program.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"MESSAGE_TYPE_X" " "
"SAPLMCEX" or "LMCEXU02"
"MCEX_UPDATE_03"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Thanks in advance
Raja

LO EXTRACTION:
First Activate the Data Source from the Business Content using LBWE
For Customizing the Extract Structure LBWE
Maintaining the Extract Structure
Generating the Data Source
Once the Data Source is generated do necessary setting for
Selection
Hide
Inversion
Field Only Know in Exit
And the save the Data Source
Activate the Data Source
Using RSA6 transport the Data Source
Replicate the Data Source in SAP BW and Assign it to Info source and Activate
Running the Statistical setup to fill
the data into Set Up Tables
Go to SBIW and follow the path
We can cross check using RSA3
Go Back to SAP BW and Create the Info package and run the Initial Load
Once the Initial delta is successful before running delta load we need to set up V3 Job in SAP R/3 using LBWE.
Once the Delta is activated in SAP R/3 we can start running Delta loads in SAP BW.
Direct Delta:- In case of Direct delta LUWs are directly posted to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUWs are directly posted to Delta Queue (RSA7) the application is kept waiting until all the enhancement code is executed.
Queued Delta: - In case of Queued Delta LUWs are posted to Extractor queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue (LBWQ) to Delta Queue (RSA7) and we extract the LUWs from Delta Queue to SAP BW by running Delta Loads. Queued Delta is recommended by SAP it maintain the Extractor Log which us to handle the LUWs, which are missed.
V3 -> Asynchronous Background Update Method Here by seeing name itself we can understand this. I.e. it is Asynchronous Update Method with background job.
Update Methods,
a.1: (Serialized) V3 Update
b. Direct Delta
c. Queued Delta
d. Un-serialized V3 Update
Note: Before PI Release 2002.1 the only update method available was V3 Update. As of PI 2002.1 three new update methods are available because the V3 update could lead to inconsistencies under certain circumstances. As of PI 2003.1 the old V3 update will not be supported anymore.
a. Update methods: (serialized) V3
Transaction data is collected in the R/3 update tables
Data in the update tables is transferred through a periodic update process to BW Delta queue
Delta loads from BW retrieve the data from this BW Delta queue
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Issues:
Even though it says serialized , Correct sequence of extraction data cannot be guaranteed
V2 Update errors can lead to V3 updates never to be processed
Update methods: direct delta
Each document posting is directly transferred into the BW delta queue
Each document posting with delta extraction leads to exactly one LUW in the respective BW delta queues
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Less monitoring overhead of update data or extraction queue
Cons:
Not suitable for environments with high number of document changes
Setup and delta initialization have to be executed successfully before document postings are resumed
V1 is more heavily burdened
Update methods: queued delta
Extraction data is collected for the affected application in an extraction queue
Collective run as usual for transferring data into the BW delta queue
Transaction postings lead to:
1. Records in transaction tables and in extraction queue
2. A periodically scheduled job transfers these postings into the BW delta queue
3. This BW Delta queue is read when a delta load is executed.
Pros:
Extraction is independent of V2 update
Suitable for environments with high number of document changes
Writing to extraction queue is within V1-update: this ensures correct serialization
Downtime is reduced to running the setup
Cons:
V1 is more heavily burdened compared to V3
Administrative overhead of extraction queue
Update methods: Un-serialized V3
Extraction data for written as before into the update tables with a V3 update module
V3 collective run transfers the data to BW Delta queue
In contrast to serialized V3, the data in the updating collective run is without regard to sequence from the update tables
Transaction postings lead to:
1. Records in transaction tables and in update tables
2. A periodically scheduled job transfers these postings into the BW delta queue
3.This BW Delta queue is read when a delta load is executed.
Issues:
Only suitable for data target design for which correct sequence of changes is not important e.g. Material Movements
V2 update has to be successful
Direct Delta: With this update mode, the extraction data is transferred with each document posting directly into the BW delta queue. In doing so, each document posting with delta extraction is posted for exactly one LUW in the respective BW delta queues.
Queued Delta: With this update mode, the extraction data is collected for the affected application instead of being collected in an extraction queue, and can be transferred as usual with the V3 update by means of an updating collective run into the BW delta queue. In doing so, up to 10000 delta extractions of documents for an LUW are compressed for each Data Source into the BW delta queue, depending on the application.
Non-serialized V3 Update: With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
V1 - Synchronous update
V2 - Asynchronous update
V3 - Batch asynchronous update
These are different work processes on the application server that takes the update LUW (which may have various DB manipulation SQLs) from the running program and execute it. These are separated to optimize transaction processing capabilities.
Taking an example -
If you create/change a purchase order (me21n/me22n), when you press 'SAVE' and see a success message (PO.... changed...), the update to underlying tables EKKO/EKPO has happened (before you saw the message). This update was executed in the V1 work process.
There are some statistics collecting tables in the system which can capture data for reporting. For example, LIS table S012 stores purchasing data (it is the same data as EKKO/EKPO stored redundantly, but in a different structure to optimize reporting). Now, these tables are updated with the txn you just posted, in a V2 process. Depending on system load, this may happen a few seconds later (after you saw the success message). You can see V1/V2/V3 queues in SM12 or SM13.
V3 is specifically for BW extraction. The update LUW for these is sent to V3 but is not executed immediately. You have to schedule a job (e.g. in LBWE definitions) to process these. This is again to optimize performance.
V2 and V3 are separated from V1 as these are not as real time critical (updating statistical data). If all these updates were put together in one LUW, system performance (concurrency, locking etc) would be impacted.
Serialized V3 update is called after V2 has happened (this is how the code running these updates is written) so if you have both V2 and V3 updates from a txn, if V2 fails or is waiting, V3 will not happen yet.
hope it will helps you.....

Delta Upload porblem : Job getting Cancelled in R/3 ...

Hello BW Experts ,
I did successful INIT upload from data source 2LIS_02_SGR.
But while running delta I am getting an error as mention below ,
the Job is getting cancled in R/3 .
But at the same time we are able to do delta for 2LIS_02_ITM,SCL,HDR etc successfully.
We have not made any enhancement to this data source 2LIS_02_SGR .
also we have not change any ABAP code in R/3 .
R/3 side SM37 job Log message as below ,----
Job started
Step 001 started (program SBIE0001, variant &0000000000336, user ID BWALEUSER
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 2LIS_02_SGR
 Current Values for Selected Profile Parameters *
abap/heap_area_nondia......... 2000683008 *
abap/heap_area_total.......... 2000683008 *
abap/heaplimit................ 40894464 *
zcsa/installed_languages...... ED *
zcsa/system_language.......... E *
ztta/max_memreq_MB............ 250 *
ztta/roll_area................ 2000896 *
ztta/roll_extension........... 2000683008 *
ABAP/4 processor: SYNTAX_ERROR
Job cancelled

Hi Amol,
The function module /BI0/QI2LIS_02_SGR0001 gets generated the first time you run the DELTA load after a successful Initialization.
As I can see from the short dump, I can see that the Delta load is not able to Generate the FM /BI0/QI2LIS_02_SGR0001 successfully as it recognizes that the FM already exists. I guess it would be worth to try another Initialization, and then try the Delta again.
You could also check if the INIT was successful in table ROOSPRMSC giving the datasource name 2LIS_02_SGR, and check if the field INITSTATE is marked X and whether it has the timestamp registered successfully, also check if the Request in BW is existing in targets and is GREEN in monitor. If all this is fine, then I guess it would be worth trying another INitialization and then try the delta .
Hope this resolves your issue.
Cheers,
Praveen.

Background job got cancelled for the user ----- Isolation and resolution

Hi Experts,
One background job got cancelled for the user I have the Jobname and User...
Able to view the log information in SM37.
I am not sure what is the next step to do and how to resolve this issue.
Could any one please provide me the step by step Isolating the issue and resolving it.
That would be really greatfull.
Thank you in advance.
Regards,
Prem.

Hi,
What the error it was stating in that SM37 job log?
Pls post that error log, not completely just mention the error here we'll try to help you.
rgds,

SM37 Job is not visible in SM50

Hello Gurus,
I am seeing a peculiar situation- We ran a job and after a while I am seeing it has dissappeared from SM50 but has "Active" status in SM37.
*We have only one application server.
Does anybody have any idea how it could be cancelled.
Cheers,
Ankur

Hi Subhash,
The issue was that Job was active in SM37 but was not present in SM50. I found the answer and this is due to termination of work process without making a call to "BtcCleanUp" kernel function .
Anyway thanks for replying.
Cheers,
Ankur

Transport of Transformation failed with RC= 12 and job: RDDEXECL cancelled in Target sytem

Gurus,
When i am importing the workbench request from dev to qty.
I am getting error : Program terminated (job: RDDEXECL, no.: 22321300).
Transformation contains only Endroutine.
Job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxxxxx were synchronized
The internal session was terminated with the runtime error UNCAUGHT_EXCEPTION (see ST2
Job cancelled.
When i see the dump it is througing errror at the method of following class.
CL_RSO_TLOGO_PERSISTENCY-CHECK_INITIALIZED
Could you please help. Thanks in advance.
Ashok

Hi Ashok,
In QA use program "RSTRAN_ROUT_RSFO_CHECK" to check and remove any inconsistencies for the transformations. After that again transport those transformations in new TR and import in QA.
Also you have to search "Transport of Transformation failed with RC= 12 and job: RDDEXECL canceled in Target system" by Dinesh Tiwari.
Check the reply of Fun Sébastien in http://scn.sap.com/message/13795238#13795238.

LANDSCAPE FETCH job gets cancelled

Hello Guru's,
The LANDSCAPE FETCH job gets cancelled on solution manager system due to the below mentioned error and in order to fix it
we have already applied the SAP note 1335225 but, the issue still persists.
Right now, we have come across the SAP note 1108071 which says the job will get cancelled "if you made adaptive computing
settings in SMSY and the SLD is not accessible".
can any one help me with how to check the adaptive computing settings in the header data of the system.
Also, the SLD check from system via tcode:sldcheck is sucessfull and we could access the SLD via browser. Please find the
details below.
Properties of RFC destination SAPSLDAPI
RFC host:
%%RFCSERVER%%
program id:      SAPSLDAPI_MP0
gateway host:
gateway service:
Testing the RFC connection to the SLD java client...
RFC ping was successful
SLD server access settings:
host name:   ashb01wa06pr.global.aes.com
port number: 59000
user       : SLDAPIUSER
Use transaction SLDAPICUST if you wish to maintain the SLD server access d
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code     3
=> Check whether the SLD is running!
Immediate reponse is highly appreciated
Best Regards,
S.Viswanathan

Hello,
Could you include the Landscape_fetch error you mentioned in your message?
I think the issue is still your SLD. At the bottom of SLDCHECK it tries to retreive business systems in SLD.
If it is successfull you will see something like:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call terminated sucessfully
List of business systems maintained in the SLD:
   yoursystem1
   yoursystem2
   yoursystem3
(more...)
Your SLD check shows that it cannot retrieve systems from the SLD:
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Please make sure that you have configured your SLD according to the post-installSLD setup and configuration guide. If you still have problems, follow this toubleshooting process...
http://help.sap.com/saphelp_nw70/helpdata/EN/78/20244134a56532e10000000a1550b0/frameset.htm
Best Regards.
Edited by: Phil May on Sep 2, 2009 10:31 AM

"The query was cancelled" error after upgrade from 10.1.3.3.3 to 10.1.3.4.2

Hi,
I was using OBIEE 10.1.3.3.3 /. After upgrading to 10.1.3.4.2 , the queries are not running ( long running queries alone) as expected. and so all the campaigns iwh tlong running queries are cancelled and the error message is seen in the xml log in Marketing jobs management.
We have upgraded the OBIEE version from 10.1.3.3.3 to 10.1.3.4.2 yesterday after which the connectivites have been checked with SQLPLUS and they are working fine. But when the campaign has been loaded, the Analytics have received the request for the segment query and after longer run, the task has been cancelled with the error message "The Query was cancelled as mentioned below in the Job Stats
<jobStats>
<jobID>2</jobID>
<jobType>WriteListFiles</jobType>
<jobUser>userid</jobUser>
<jobState>Error</jobState>
<jobTotalMilliSec>1h 41m 21s 160ms</jobTotalMilliSec>
<jobStartedTime>2012-03-22T08:06:13Z</jobStartedTime>
<jobFinishedTime>2012-03-22T09:47:34Z</jobFinishedTime>
<jobIsCancelling>N</jobIsCancelling>
- <exception>
<message>Job request of type "WriteListFiles" failed.</message>
- <exception>
<message>Error executing the list generation SQL.</message>
- <exception>
<message>Error in executing cursor for WorkNode (Id:0)</message>
- <exception>
<message>The query was cancelled.</message>
</exception>
</exception>
</exception>
</exception>
</jobStats>
Please let us know the suggestions
So far, the unaccessedtimingrunoutminutes tag has been tried to set 50 under ODBC tag in instanceconfig.xml. and the defaulttimeoutminutes has been tried to set to 150 in the same instanceconfig.xml.
along with that the rpd changes are done. For all the users apart from the Administrator, the timeout has been changedfrom 10 minutes to 150 minutes. But still that way is not working.
The segments was fired with the Administrator login. So , if the timeout for admin login can be set, i assume that the problem might be solved. Please let us know ur suggestions here too.
If that is the case, when we open rpd , only for Administrator user and group, the Permissions button is disabled. So i want to know how to change for Admin user settings in rpd..
Please advice us on the same.
Regards,
Madasamy M.
Edited by: Madasamy Murugaboobathi on Mar 26, 2012 1:40 PM

The issue has been resolved by setting the following parameters
<UnaccessedRunningTimeoutMinutes>120</UnaccessedRunningTimeoutMinutes>
<DefaultTimeoutMinutes>120</DefaultTimeoutMinutes>
<ClientSessionExpireMinutes>120</ClientSessionExpireMinutes>
<ConnectionExpireMinutes>120</ConnectionExpireMinutes>
<UIDefaultTimeoutMinutes>1440</UIDefaultTimeoutMinutes>

Background Job get Cancelled when executing the report. Reason?

Hi All,
I have scheduled a Back ground Job and executed Immediately.
when checking transacion SM37 the job get canceled.
How to find out the problem for the Job Cancellation.
Regards,
Viji

hi
After scheduling back ground job ( give a time laps of 2 min )
then go to sm37 ( at this moment , the job is not yet started) .
select ur job in sm 37 and when job starts processing , type JDBG as the command and press enter.
Now it will go to the debugging screen, where u will find system program . Now set a break point at the stements used in ur program from the debugging screen itself.( menu - breakpoint- breakpoint at - statement ) and press F8 .
Now you can start debug ur code.
Revrt back if any issues.
Regards,
Naveen

All Background Jobs Are cancelled

Hi all,
I make a new server by restoreing backup of our production server and SAP is running well.But when I schedule any back ground jobs all jobs are cancelled.Due to this I am not able to run SGEN.Even when I manually schedule any back ground jobs it also cancelled and I am not getting any job log in SM37.I am not able to understand why this happens as I am not found any cancelled job log.Please suggest what shall I do to overcome this problem.
Advance Thanks
Nirmal

Hi,
check the file system /SAPMNT/<SID> space in your System.I think ur memory is fully utilized sapmnt folder.
if u not need old logs delete the log file in the following location.
sapmnt/D01/global//<Clientno>JBLOG.
Regards
Senthil Kumar.S

SM37 - JOBs was CANCELED

Similar Messages

Maybe you are looking for