ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1,

Hello,
I am installing ECC 6.0 on database Maxdb7.6. window 2003 service pack 2 processor AMD 3400 RAM 2 GB,
I am getting the following error at the ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
WARNING 2010-10-29 22:40:15
Execution of the command "C:\j2sdk1.4.2_09\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ADA -importDirs D:\Ides\exportdb\db1\EXP1;D:\Ides\exportdb\db2\EXP2;D:\Ides\exportdb\db3\EXP3;D:\Ides\exportdb\db4\EXP4;D:\Ides\exportdb\db5\EXP5;D:\Ides\exportdb\db6\EXP6;D:\Ides\exportdb\db6\EXP7;D:\Ides\exportdb\db6\EXP8;D:\Ides\exportdb\db6\EXP9;D:\Ides\exportdb\db6\EXP10;D:\Ides\exportdb\db6\EXP11 -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS" -orderBy "" -r3loadExe E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles no -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -nolog -c 0" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_09"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.Loading of 'SAPSSEXC' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
ERROR 2010-10-29 22:40:15
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-10-29 22:40:15
FCO-00011 The step runMigrationMonitor with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
import_monitor.java.log
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 17, failed 0, total 19.
Loading of 'SAPSSEXC' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 17, failed 1, total 19.
PLZ help me
Thanks&regards
Vijay kumar
Moved from ABAP, General
Edited by: kishan P on Nov 2, 2010 10:17 AM

ERROR: 2010-10-29 22:07:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2010-10-29 22:07:56
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2010-10-29 22:07:56
1 error(s) during processing of packages.
INFO: 2010-10-29 22:07:56
Import Monitor is stopped.
INFO: 2010-10-29 22:39:45
Import Monitor is started.
CONFIG: 2010-10-29 22:39:45
Application options:
dbCodepage=4103
dbType=ADA
extFiles=no
importDirs=D:\Ides\exportdb\db1\EXP1;D:\Ides\exportdb\db2\EXP2;D:\Ides\exportdb\db3\EXP3;D:\Ides\exportdb\db4\EXP4;D:\Ides\exportdb\db5\EXP5;D:\Ides\exportdb\db6\EXP6;D:\Ides\exportdb\db6\EXP7;D:\Ides\exportdb\db6\EXP8;D:\Ides\exportdb\db6\EXP9;D:\Ides\exportdb\db6\EXP10;D:\Ides\exportdb\db6\EXP11
installDir=C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS
jobNum=3
loadArgs= -nolog -c 0
monitorTimeout=30
orderBy=
r3loadExe=E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe
sapinst=
trace=all
tskFiles=yes
CONFIG: 2010-10-29 22:39:45
List of packages with table structure: 'SAP0000'.
CONFIG: 2010-10-29 22:39:45
List of packages with views: 'SAPVIEW'.
TRACE: 2010-10-29 22:39:45 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is started.
INFO: 2010-10-29 22:39:45 com.sap.inst.migmon.imp.ImportStandardTask preCreate
Parse of 'C:\Program Files\sapinst_instdir\ERP\SYSTEM\ADA\CENTRAL\AS\DDLADA.TPL' template file is successfully completed.
Primary key creation: before load.
Index creation: after load.
INFO: 2010-10-29 22:39:45
Data codepage 4103 is determined using TOC file 'D:\Ides\exportdb\db1\EXP1\DATA\SAPAPPL0.TOC' for package 'SAPAPPL0'.
TRACE: 2010-10-29 22:39:45 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is started.
TRACE: 2010-10-29 22:39:45 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAPSSEXC' import package into database:
E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 0
ERROR: 2010-10-29 22:39:46 com.sap.inst.migmon.LoadTask run
Loading of 'SAPSSEXC' import package is interrupted with R3load error.
Process 'E:\usr\sap\IOL\SYS\exe\uc\NTI386\R3load.exe -i SAPSSEXC.cmd -dbcodepage 4103 -l SAPSSEXC.log -nolog -c 0' exited with return code 2.
For mode details see 'SAPSSEXC.log' file.
Standard error output:
sapparam: sapargv( argc, argv) has not been called.
sapparam(1c): No Profile used.
sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
WARNING: 2010-10-29 22:40:15
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2010-10-29 22:40:15
1 error(s) during processing of packages.
INFO: 2010-10-29 22:40:15
Import Monitor is stopped.

Similar Messages

Hyperion IR BQY job run successful few month but recently failed to export pdf and sending email

Anyone have encountered the problem that the BQY jobs which are running more than 3 years successfully. But recently no one update the report, but the job export keep failing to send result pdf to receivers intermittently.
It shouldn't be BQY job itself problem. Because this job has running years and fine. Only recent days comes out this problem. And user manually run the report can also be successful.
After checking the server log, find out that Hyperion IR retrieved data successfully but export-excel/bqy type file all works except pdf format. And in one week, some day it works fine. Some day it failed.
Trace in workspace job schedule log, it saying:
Emailing section 'xxxxxx' as 'PDF' to:
[email protected]
[email protected]
Export failed with unknown error.
And checked the server_message_IRJobService.log it just saying:
Error in export.[[
And
TCApp::ExecuteJavaScript failed:
We stuck at this error for a period of time. Anyone can help? Oracle Support has mentioned it might be system performance issue. Will keep an eye on this issue, to see any solution can be find.

Hi RamKumar,
Thank you very much for your inputs. We haven't tried
Increase the memory for the Hyperion Framework Services
will test and see if it can solve the problem. For 'Hyperion Framework Service', do you mean 'Reporting and Analysis Framework'?
We only tried increase the parameter of "Job Service" and "Intelligence Service" which called Dynamic Service Properties set to "PROCESS_MEMORY_LIMIT=2500MB". But seems hyperion this 32bit application only can reach to 2047MB.
Our EPM version is 11.1.2.1.600.07.
a. We have increased the memory from 24G to 48G and add more memory for JobService (now it has 2 GB memory).
     For the provided solution.
     Set the filters in the query to return smaller amount of data
     We are still working on, but it seems slightly solve the "Error in export" problem.
b. We have confirmed the SMTP Server configuration is correct. So this solution not fit for our case. As the trouble job has been running more than 3 years, until recent month it starts with this error. And the job failed this error only happens intermittently e.g. Monday,Tuesday,Friday it all works fine(Proved the job it self is OK) but Wednesday some period, it failed to export. So we are thinking it might the hyperion performance issue.
For the KM reference:
Interactive Reporting (IR) Jobs do not Send Emails. Error: "Export failed. Error Sending Mail" (Doc ID 1401854.1)
We have already read and checked, we do have correct configuration.
Interactive Reporting Job Completing With Javascript Errors - Not Producing Excel Output (Doc ID 1065483.1)
Our case is customer can successful extract data and send excel/bqy result to customer with no problem. But it failed to send pdf result sometime.
Thanks and Regards,
Erica

IMPORT MONITOR JOBS ERROR IN ECC 6 INSTALLATION

WARNING 2014-12-18 23:54:18
Execution of the command "C:\Program Files\j2sdk1.4.2_13\bin\java.exe -classpath migmon.jar -showversion com.sap.inst.migmon.imp.ImportMonitor -dbType ORA -importDirs "E:\ECC EXPORT 1\EXPORT_51031897-1\EXP1;E:\EXPORT 2\51031897-2\EXP2;E:\EXPORT 3\51031897-3\EXP3;E:\EXPORT 4\51031897-4\EXP4;F:\EXPORT 5\51031897-5\EXP5;F:\EXPORT 5\51031897-5\EXP6;F:\EXPORT 5\51031897-5\EXP7;F:\EXPORT 5\51031897-5\EXP8;F:\EXPORT 5\51031897-5\EXP9;F:\EXPORT 5\51031897-5\EXP10;F:\EXPORT 5\51031897-5\EXP11" -installDir "C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS" -orderBy "" -r3loadExe F:\usr\sap\AMC\SYS\exe\uc\NTI386\R3load.exe -tskFiles yes -extFiles yes -dbCodepage 4103 -jobNum 3 -monitorTimeout 30 -loadArgs " -stop_on_error" -trace all -sapinst" finished with return code 103. Output: java version "1.4.2_13"Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)Import Monitor jobs: running 1, waiting 3, completed 68, failed 0, total 72.Import Monitor jobs: running 2, waiting 2, completed 68, failed 0, total 72.Import Monitor jobs: running 3, waiting 1, completed 68, failed 0, total 72.Loading of 'SAPAPPL1_14' import package: ERRORLoading of 'SAPAPPL2_2' import package: ERRORImport Monitor jobs: running 1, waiting 1, completed 68, failed 2, total 72.Import Monitor jobs: running 1, waiting 1, completed 68, failed 2, total 72.Loading of 'D010TAB' import package: ERRORImport Monitor jobs: running 0, waiting 1, completed 68, failed 3, total 72.
this is the error i'm getting
i started oracle instance through command prompt but in vain. only four jobs r not completing.
i checked virtual memory.
please help me out.
thanks
krish

Hi Krish,
Welcome to SDN.
The installation log files would help figure out the exact error.
In the below case, the log file SAPAPPL2_2.LOG might give more information. Let us if the logs have any errors mentioned.
Logs should be in the <OS drive>\Program Files\sapinst_instdir\.... folfer.
Regards,
Srikishan

How to reprocess failed monitor jobs in Import ABAP phase of system copy

Hi Experts,
Can you please let me know how to reprocess the failed monitor jobs during Import ABAP phase as i am performing the import of data as part of system copy of ABAP stack.
But i have not got any errors so far as the import process is running fine but there are few jobs which are showing as failed.Hence how can i reprocess these failed jobs again.
Regards,
Dheeraj

Hi Juan,
Here you go.And i have not selected the option" Start migration monitor manually "and where as on Source system the guy has used migration monitor option in order to split the tables and ftp for transferring the export data on target system.
Is this error anything to do with that?
Import Monitor.java.log
Import Monitor jobs: running 1, waiting 1, completed 223, failed 13, total 238.
Loading of 'RSERRORHEAD' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 224, failed 13, total 238.
Import.monitor.log
WARNING: 2011-04-30 02:57:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2011-04-30 02:57:31
13 error(s) during processing of packages.
INFO: 2011-04-30 02:57:31
Import Monitor is stopped.
SAPINST_dev.log
TRACE 2011-04-30 02:57:37.578 [iaxxgenimp.cpp:699]
 CGuiEngineImp::showMessageBox
<html> <head> </head> <body> An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > Central System > Based on AS ABAP > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.). You can now: <ul> <li> Choose Retry to repeat the current step. </li> <li> Choose Log Files to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> Log files are written to <code>C:\Program Files/sapinst_instdir/NW701/LM/COPY/ORA/SYSTEM/CENTRAL/AS-ABAP/</code>. </body></html>
TRACE 2011-04-30 02:57:37.578 [iaxxgenimp.cpp:1248]
 CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
Regards,
Dheeraj

Ccms monitoring - Long running job

I checked in CMMS monitoring (RZ20) version ECC 6.0, there is no option to monitor long running background job.
How to monitor long running background job using transaction RZ20?

Hi,
Check this [link|Re: How to monitor long running background job.;
Thanks
Sunny

Jobs stays in waiting state but does not ever run in target system

This usually happens when there is a network problem or the target system is down for some reason. Is there a way to ignore the waiting status so that the next scheduled job runs would be affected? If not can CPS be configured to constantly request for the actual status of the job in the target system?

Hi,
Set the below parameter on the process server of the target system for which jobs stays in waiting state.
Parameter: SAP_MaxReconnectTime value: 60
Reason: Process servers tries to connect to Target system at the time when the network issue happens and due to that It does not connect to the target SAP system and all the jobs stays in waiting status.
When you set this parameter with the value (what ever you want in Minutes), it will automatically try to reconnect to the target SAP System at every 60 min (or the value provided) when ever it loses the connection with Target system and Jobs will start processing again.
Thanks and Regards,
Vipul Kaswala

Problem with Sales Order CIF IM-job running longer

We have CIF integratiom Model generation(RIMODGEN) and activation(RIMODAC2) jobs
running everyday in sequence.
One of the jobs is for Sales Order Generation
and activation. The activation job used to take 30-40 seconds earlier(since last
1 year) but for the last month the job has been taking a lot of time to
complete. And that too intermittently. On some days the job completes in 30-40
seconds but on some it takes more than 3000 seconds(and still doesnt complete-
eventually we mark it successful manually to let successor jobs to start).
When we analysed the log for this job transfer in SLG1 we found out that
during activation of this Integration Model, not only Sales Orders pertaining to
new materials(that would have been added within the day between last IM
generation job and current IM generation job) were getting transferred. But
Sales orders pertaining to Materials(which have been active since a number of
days) were also getting transferred. Ideally, any changes/new Sales orders
pertaining to these older materials(which were already in an active integration
model) should have been transferred real time and should not have waited to be
transferred during the IM activation job.
We have also noticed that for
some Sales Olders(for which the materials were already active for long) and
there has been NO change in the Sales Orders are also getting transferred
throguh our IM activation job.
The mesage that we see in the log for
these Sales Order is shown below:
Source system:XXXXXX user: RSP100
transaction CFM2 T_SLS 0001119 function module: /SAPAPO/CIF_XXXXX (As far as I
understand CFM2 T_SLS* prefix is for Sales Order transfer happen during IM
activation job)
"Customer Requirement N BM 0001223200 00010 0001: Method
changed from N to G"
"Customer Requirement 0001223200: Requirement adopted
in APO"

Is the full name of the directory where you have your source code Documents and Settings as in Win2k or WinXP. In that case, move the source code to a different directory(you might like to create a separate directory). Note that the directory name should not have spaces in it. Try and see what you get.

SSIS job runs in designer but fails in SQL Agent - timeout error

I have several SSIS packages that have been running without issue for well over a year. These jobs were imported into SQL Server and run on a schedule with SQL Agent.
Over the weekend these jobs failed with the message:
Description: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. The statement has been terminated. Source: .Net SqlClient Data Provider Started: 8:13:01 AM
Finished: 8:13:31 AM Elapsed: 30.155 seconds. The package execution failed. The step failed.
When I look at the package history it doesn't even show that the job attempted to run over the weekend. As such I assume that the error is related to SQL Agent attempting to connect to the SSIS job.
As stated in the title, the jobs run without issue in the designer.
I did stop and restart SQL to see if that would have an effect - sadly it did not.
I attempted to reload one of the packages. More specifically I re-imported it and allowed it to overwrite the existing project, This step completed ok and moved to the next step - deploy the project. It fails to deploy the project with the following error
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&ProdVer=11.00.2218&EvtSrc=MSSQLServer&EvtID=-2&LinkId=20476
Server Name: XXXXXXX
Error Number: -2
Severity: 11
State: 0
Program Location:
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.SqlServer.IntegrationServices.Common.ObjectModel.SqlHelper.ExecuteSQLCommand(SqlStoreConnection storeConnection, CommandType cmdType, String cmdText, SqlParameter[] parameters, ExecuteType execType, Int32 commandTimeout)
   at Microsoft.SqlServer.Management.IntegrationServices.CatalogFolder.DeployProject(String projectName, Byte[] projectStream)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeployExportProjectHelper.DeployProject(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.Deploy(CatalogFolder folder, Project project)
   at Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.DeployProject()
   at Microsoft.SqlServer.IntegrationServices.Deployment.DeployProjectPage.DoWork(Object sender, DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.OnDoWork(DoWorkEventArgs e)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
===================================
The wait operation timed out
It would seem to me that there is an environmental error, though I know of nothing that has changed. I don't know where to look. If you have seen this behavior before or have an idea, I welcome your input.
Thanks
Mike

Hi Mike,
Based on the error message, we can infer that the issue is caused by connection or command timeout.
To work around this issue, we can increase the connection timeout and command timeout, buffer size and create two indexes in the SSISDB catalog to improve the performance. For more details, please see:
http://capstonebi.blogspot.com/2012/09/ssis-2012-deployment-frustrations.html
Reference:
https://connect.microsoft.com/SQLServer/feedback/details/804901/ssis-2012-deploying-new-versions-of-large-projects-runs-into-a-timeout-during-deployment-into-ssis-catalog
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Monitor job failure

Hi
after a local chain completes then monitor job is executed. We fix some time for this. If process chain takes long time than that it fails
i just want to see the time fixed for that
Thanks & Regards,
Virinchi.

Check what is the maximum time its taking to complete the process. and set it as the maximum wait time.
Sometimes as the system is busy it can not allocate the processes to complete the process.If this is the case you can avoid it by checking whether any other processchains are triggering at this time. If there are any, try to change the process chain start timings( With Client Permission).
Assign points if it helps.....

How to get spool from background job run?

Hello,
I have this situation and need help on how to resolve:
I have RFC FM which called from another system, in that FM I am submitting BDC section as a batch job by report RSBDCSUB. The problem is that this job may run for 1 or 2 hours and my RFC call will be close by that time. How can I bring the result of my batch job run back to the calling system in this case? Will appreciate any hints.
Thank you,
Glenn

Hi
After you the Job completes. Use the spool ID and fetch the Spool list using the report RSPOLST2.
You can download the spool job using the Function module RSPO_DOWNLOAD_SPOOLJOB.
Thanks
Dev

T code to check the job run status

Hi Gurus,
I am filling the setup tables for inventory, but i didn't run in background. I clicked on execute button, but suddenly i got disconnected from net and my server also.
Now i have to check the job run status whether it is running or not.
Request you to provide the suggessions.
Thanks & Regards,
Saketh

Hi,
if you ran job in background you can see at SM37.use proper time ,date and use id to get your job.
if you ran on frond end then you won't see job.if your job was completed then you can see data at SE11 by using setup table name or you can see at t code NPRT by using name of the run.
if you won't find your job then just delete your setup tables again and fill it.
No issues.
Thanks

Background Job running long time.

Hello All,
One of customer background job running for long time more than 11 hours, but usually this jobs get completed within 4 hrs.
I have checked in WP trace file, it shows "WP has reached abap/heaplimit=40000000".
This is the Value I can see in RZ11. Now it is not possible to change the value.
Frequently facing this problem, please guide me to solve this issue.
Regards
Vinay.

Hi
First of all, abap/heaplimit is the limit of memory usage by a WP.
Follwing is the documentation from help.sap.com
The value of the parameter should be between 10000000 (10 MB) and 2000000000 (2GB), the recommended default setting is 40000000 (40 MB).
The objective is to have the least number of work process restarts as possible, without a swap space bottleneck occurring. The heap memory allocated by the work processes has to be released again.
As shown in the graphic, the value of abap/heaplimit should be smaller than abap/heap_area_dia or abap/heap_area_nondia, so that the dialog step that is running can still be executed. This prevents the work process from working against the operating systemu2019s swap space limit if there is a programmed termination of the work process.
So,Do the above checks. And importantly check the memory utilizations at the time of running your job and check whether any other job was also running at the sametime.
Increasing the parametes is not a good idea.. If you continuously face this issue then only think of parametes. As u said ,this problem is not happenng too often.
Hope this is useful

Background job running for a long time - trace is not capturing.

hi guys,
My background job runs for more thatn 4 hours. some times. (normally it completes withing one hour)
i tried to trace using st12 ....and executed this program. but not got complete trace report of 4 hours.
what is the best way to trace long running programs like this.
is there any alternative for this...???
regards
girish

Giri,
There is no need to trace a program for the full 4 hours. There is usually just one piece of rogue code causing the problem, and it can be identified quite quickly.
If I were you I would just watch the job run via SM50, to see if it lingers on any database tables. Also check if the memory is filling up - this is the sign of a memory leak.
You can also try stopping the program (via SM50 debugging) at random points, to see what piece of code it is stuck in.
The issue should reveal itself fairly quickly.
Tell us what you find!
cheers
Paul

DBMS_JOB.SUBMIT works, Job runs, but no information in dictinary views.

We run a Job in a 10g (10g Enterprise Edition Release 10.2.0.4.0) DB using this code in SQL*Plus.
SQL> EDIT
Wrote file afiedt.buf
1   DECLARE
2     v_JobNum   NUMBER;
3   BEGIN
4     DBMS_JOB.SUBMIT(v_JobNum,'chs_job_test;',sysdate, NULL);
5     DBMS_OUTPUT.PUT_LINE('Job # = ' || v_jobnum);
6     commit;
7* END;
8 /
PL/SQL procedure successfully completed.
SQL> set serverout on
SQL> /
Job # = 462Job runs successfully. i.e. the procedure chs_job_test is executed OK. Problem is when we query the USER_JOBS view, we don't see any record for Job 462??
Why is this??
Where can we get information of the jobs submitted???
If an error occured when running job, from where, which DD View we can get this?

If you submit a job without specifying the NEXT_DATE and INTERVAL, Oracle treats it as a "single execution" job. It is removed from the job queue once it is completed.
Hemant K Chitale

Background job delay due to 'ARFC' jobs running continously

Dear all,
As we are facing problem that,there is job starting with the 'ARFC'(example: ARFC:AC1F0C0D386B463CA88E8D10) which runs with all the users in the system.Thus the other background jobs even the sys monitoring jobs also goes for the delay for the longer time.This is happening from past 10 days.I m unable to trace what has got change in the system due to which ,I m facing this issue.I had checked in the job logs also, in which i didnt got any help.In that it is only mentioned owner of the job.Pls check this at the high priority as it is affecting my normal background jobs.
Thanks in advance.
Regards,
Akif

Hi akif,
jobs which are stuck at ARFC mode needs to trigger other event controlled jobs. since they are updating the Database, unless those jobs trigger this job cannot run forward so try to find what kind of jobs from the user who scheduled the job and then take the action if the jobs are related to support packages and releasing of change request then try to schedule RDD* jobs under user DDIC in 000 client
this is not due to instance consistency
regards,
kanthi

ERRORImport Monitor jobs: running 0, waiting 1, completed 17, failed 1,

Similar Messages

Maybe you are looking for