Standard Job SAP_CCMS_MONI_BATCH_DP is cancelling

Hello All
I am facing problem with standard job SAP_CCMS_MONI_BATCH_DP...It is scheduled on hourly basis.
But on some days at some time it is failing with only one error message as
08/04/2011 17:52:26 Job started
08/04/2011 17:52:26 Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID
08/04/2011 17:52:29 You can only work in client 320
08/04/2011 17:52:29 Job cancelled
There is no specific time that it is failing.Please suggest me how can i resolve this?
Manmohan Soni

Hi,
Looks like the client in which job is to run, is different from which client the job is called from.
Check thread: Sm37 job problem
Also check sm21 log to get more details.
Regards,
Srikishan

Similar Messages

SAP Standard Jobs are getting canceled

Hi Basis Gurus,
In our Quality BW 3.5 system the SAP Standard jobs are getting canceled.
The jobs are as follows
SAP_APPLICATION_STAT_COLLECTOR
SAP_CCMS_CPH_HRCOLL
SAP_CCMS_MONI_BATCH_DP
SAP_COLLECTOR_FOR_JOBSTATISTIC
SAP_COLLECTOR_FOR_NONE_R3_STAT
SAP_COLLECTOR_FOR_PERFMONITOR
SAPCONNECT ALL SEND
SAP_REORG_ABAPDUMPS
SAP_REORG_SPOOL
SAP_RSICFDLT
In SM37 when i click on the job log for the above mentioned jobs the system is promting a message saying as "Error reading job log"
Please let me know how can troubleshoot it and resolve this issue.
Our is qulaity BW 3.5 system
Solaris OS
Oracle Database
Please help me.
Regards,
Anil.

Hi ,
For log display reason, try the note suggested. Jobs cancel reason may be due to that the user who schedule that job are locked or not exist on that client. Or other reason will be clear only after log display.
Ankit

Standard job, sap_ccms_moni_batch_dp, creates remote gateway

I noticed that standard job, sap_ccms_moni_batch_dp, in our sandbox environment creates a remote gateway to our Production environment. I'm thinking this is not a good thing. I deleted all the standard SAP jobs and used the function in tcode SM36 to reschedule them. They still create a remote gateway that seems to point at Production. Is this an artifact of our recent system copy procedure to create our Sandbox? How can I correct it?

James,
Did you run BDLS (Logical Name Conversion) after System Copy?
Secondly you need to know if you need this job in your system.
Please check the below link for more details. Please let us know if you still have some doubt.
http://help.sap.com/saphelp_nw04/helpdata/en/be/44443c4a08ba26e10000000a114084/content.htm
Regards,
Sujit.

Standard job failing -- SAP_CCMS_MONI_BATCH_DP

Hi All,
I am running the standard job SAP_CCMS_MONI_BATCH_DP from last couple of years on my production system. I monitored from last 4 - 5 days the job is getting cancelled and providing a dump like ABAP/4 processor: CONVT_NO_NUMBER.
Sometime the job log says :
1. Logical system MSG_SSS is not configured in table /ISDFPS/ALE_SYS
    Job cancelled after system exception ERROR_MESSAGE
2. Logical system Startuptoo is not configured in table /ISDFPS/ALE_SYS
     Job cancelled after system exception ERROR_MESSAGE
Dump says :--
Runtime Errors         CONVT_NO_NUMBER
Exception              CX_SY_CONVERSION_NO_NUMBER
Date and Time          17.02.2009 13:16:59
Short text
     Unable to interpret "More than 100 " as a number.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_CONVERSION_NO_NUMBER', was n
      caught in
     procedure "RETRY_MECHANISM_SETUP" "(FORM)", nor was it propagated by a RAISIN
      clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
     The reason for the exception is:
     The program attempted to interpret the value "More than 100 " as a number, bu
     since the value contravenes the rules for correct number formats,
     this was not possible.
     There is probably an error in the program
     "SAPLSALSLD_MODEL".
Please advice ..

Hi Shashi
Yes!!!!!! definitely an ABAP Program error..
The source code may have been modified and has something as "more than 100" wrongly written in it. This could also be a case of variable settings as text is input in place of numbers or something like this.
An ABAPer could help you better in this one or the best possible solution definitely would be an OSS message to SAP.
Regards
Chen

Error in program RSAL_BATCH_TOOL_DISPATCHING (job SAP_CCMS_MONI_BATCH_DP)

Hi All,
After successfull upgrade in Support pack level 17, I am getting an error message in with a standard job SAP_CCMS_MONI_BATCH_DP. I am getting the following error messages in SM21.
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Database error -440
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Database error -440
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Database error -440
Database error -440 at OPC
> SQL0440N No authorized routine named "DB6PMCF" of type
> "FUNCTION" having compatible arguments was found.
> SQLSTATE=42884
Even after checking the error in details I found the program "RSAL_BATCH_TOOL_DISPATCHING" causing the error message. In details the error message says :
Job started
Step 001 started (program RSAL_BATCH_TOOL_DISPATCHING, variant , user ID
:Exception CX_DBA_ADBC in class CL_DB6_RDI method GET_SNAPSHOT line 431
: Kernel Error ID:
: SYSID: <SID>
: SY-SUBRC: 1208
: Message: ADBC error
: SQL statement: SELECT '20091109062730',0 as DB6PMCF_PARTITION,' ','T
: ','20091106055752','700',0.0,0.0,0.0,0.0,0 FROMSYSIBM.SYSDUMMY1, TABL
: E(SAPTOOLS.DB6PMCF('/db2/SID/log_dir/') ) AS FS_CONFIG
: Database:
:caused by
:Exception CX_SQL_EXCEPTION in class CL_SQL_STATEMENT
: Kernel Error ID:
: DB Error: Yes
: SQL Code: 440-
: SQL Message: SQL0440N No authorized routine named "DB6PMCF" of typ
: e "FUNCTION" having compatible arguments was found. SQLSTATE=42884
: DB Object Exists: No
: Duplicated Key: No
: Internal Error: 1
: Invalid Cursor: No
: Unknown Connection: No
: Connection Closed: No
Did anybody encountered with any situstion like this...Would appreciate any early response.
DID CHECK WITH KERNEL FILES, LOOKS GOOD FOR ME. ALSO CHECKED WITH note 978319 ..
Thanks in Advance

I have not yet tried to apply the note 978319.
Current DB LEVEL is as follows..
DB client lib.     DB6_81
DB releases        DB6 08.02.*, DB6 0
DBSL version       700.08
DBSL Patch Level   171

SAP_CCMS_MONI_BATCH_DP getting cancelled with error in program SAPLSPFL

Hi Experts,
The job SAP_CCMS_MONI_BATCH_DP scheduled by user DDIC is getting cancelled everyday at 20:00 CET (system time).
The reason for the job getting cancelled with the runtime error Syntax error in program SAPLSPFL and a short dump is generated.
Runtime Errors         SYNTAX_ERROR
Date and Time          07.03.2012 20:24:50
Short text
    Syntax error in program "SAPLSPFL ".
As per instructions I did syntax check for Program SAPLSPFL . It shows syntactical error as shown below.
The following syntax error occurred in program "SAPLSPFL " in include "LSPFLF07
" in
line 148:
"Bei PERFORM bzw. CALL FUNCTION "SET_DIRVALUE" ist der Aktualparameter "
""DIR_VALUES-DIR_ROLL" zum Formalparameter "DIR_VALUE" inkompatibel."
Please help me on this.

hi
check out this SAP Note
1000897 RZ10 profile import: Maximum path length is 60 characters

Standard job SLCA_LCK_SYNCHOWNERS is failing

This standard job has started to fail and I can't seem to find out the reason why.
In the spool of the job the only error (i think) is the line "No vendor specified", next line is Job cancelled after system exception ERROR_MESSAGE
I have check sm21 and ST22 and the errors aren't being reported.
I have read about you only need this job if it is a liveCache server, what is a liveCache server and how do I know if I have one.
The SAP we are using is SAP All in ONE SAP ECC 6.0
Thanks for the help

Hi,
the job is failling because the other job SAP_WP_CACHE_RELOAD_FULL is failling too, as this job is now obsolete, check the logs and dumps for detailed analysis.
Thanks,
Macherla

Job SLCA_LCK_SYNCHOWNERS getting cancelled

Hi Guyz,
We had job "SLCA_LCK_SYNCHOWNERS " getting cancelled everyday. Im not understanding what this job is doing. When i search in SAP Market Place this talks more as a job in MaxDB or some Live cache related. Could anybody tell me wht this job is doing , is it necessary in our BI system, our DB is Oracle 10g and OS in HP-UX.
Thank you

If this is not a LiveCache system, then you can just remove the job. This is scheduled by default in the SAP Standard Jobs area if you click the 'Default scheduling' button.
Hope that helps.
J. Haynes

Job is getting cancelled in CPS

Hi,
We have implemented CPS on SOLMAN, and when we were submitting a job for one of the SAP system and we are using Job chain method for submiting the job.
Job is getting cancelled with the below error,please find the below error and log.
Failed to create the job in the SAP system
BAPI exception while calling BAPI_XBP_JOB_ADD_ABAP_STEP: E XM 034 Internal problem (function BAPI_XBP_JOB_ADD_ABAP_STEP) [BAPI_XBP_JOB_ADD_ABAP_STEP, , , ]
     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.checkBapiReturnCode(ClientConnectionImpl.java:818)
     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.ClientConnectionImpl.call(ClientConnectionImpl.java:605)
     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection$4.doPerform(AbstractRfcConnection.java:289)
     at com.redwood.scheduler.connector.sap.rfc.connection.RemoteFunctionCall.perform(RemoteFunctionCall.java:130)
     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.perform(AbstractRfcConnection.java:445)
     at com.redwood.scheduler.connector.sap.rfc.connection.AbstractRfcConnection.execute(AbstractRfcConnection.java:282)
     at com.redwood.scheduler.connector.sap.rfc.jco2.connection.impl.SapFunctionModuleWrapper.execute(SapFunctionModuleWrapper.java:194)
     at com.redwood.scheduler.connector.sap.rfc.jco.AbstractSapFunctionModule.execute(AbstractSapFunctionModule.java:107)
     at com.redwood.scheduler.connector.sap.rfc.command.impl.AbapRunPrintCommand.doAddSteps(AbapRunPrintCommand.java:353)
     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpJobRunCommand.execute(AbstractXbpJobRunCommand.java:177)
     at com.redwood.scheduler.connector.sap.rfc.command.AbstractXbpCommand.doExecute(AbstractXbpCommand.java:123)
     at com.redwood.scheduler.connector.sap.rfc.command.AbstractCommand.execute(AbstractCommand.java:56)
     at com.redwood.scheduler.connector.sap.rfc.service.SapJobWork.doWork(SapJobWork.java:107)
     at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:59)
     at java.lang.Thread.run(Thread.java:770)

This message is most of the times thrown when the parameters you specify for the job to run are inconsistent. Possibly a variant name that does not exist or is missing, maybe a printer/sap user name/application server name that does not exist in the target system.

Job is getting cancelled

Hi Friends !
We have job name RSIMPCUST scheduled by the USER ID ABC. Now this ABC ID no longer exists. Hence job is getting cancelled. In the SM37, I did tried "Repeat Schedule" but thatz also getting cancelled. How I can schedule this job on my ID? Please advise.
With Regards
Rekha

Hi Rekha,
In order to be able to use the job with your Id please make setting according to this docuement ::
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00b6b739-47a6-2e10-9abf-bdac1124dde1?QuickLink=index&overridelayout=true
Regards,
Arpit

Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.

Hi All,
Background job SAP_PERIODIC_ORACLE_SNAPSHOT got cancelled.
Im SM37 the log shows that the job has been cancelled because 'No Vendor Specified'
Is that any variant needs to be specified.
Please help me on this.
Thanks & Regards,
Gopi L.

Hi,
Please check the SM21 log and the corresponding work process trace (dev_wX - X refers to the work process number used by the job, can be seen from SM21) for errors.
Best regards,
Warren

Error saving job to database for standard jobs scheduling

Hi,
In IDES server when iam goto Tr.code -- SM36 -- Standard Jobs -- Default Scheduling iam getting below error.
Error saving job to database
Message no. BT117
Diagnosis
The SAP system was unable to save the current job in the database. This failure suggests that there is a problem with the database system or with the network connections between the SAP application servers and the database system.
System Response
Job not saved and not scheduled.
Procedure
To analyze this problem, start by checking the system log for messages about network or database problems. You can also use the computing center management system to check your system for problems.
Guide me for the same.
Thanku

HI,
Sometimes this error will come.
Try to schedule jobs manually using SM36 instead of using standard job button.
Also you can check this thread
Re: Error saving job SAP_REORG_JOBS to database
Which seems to report same problem.
Its nothing to take with database conenctivity as SAP is up and running .
Try this and revert.
Regards,

Standard job scheduling problem

hi,
i am using ERP 6 ,windows 2003 , MS SQL 2005.
i am scheduling the standard job like (SAP_COLLECTOR_FOR_JOBSTATISTIC ).
in start time when i am selecting IMMEDIATE it is ok and working.
but in start time when i select particular date/time it gives error (Error saving job SAP_COLLECTOR_FOR_JOBSTATISTIC to
database)
can any one tell me why is this happing.

hi,
i am using ERP 6 ,windows 2003 , MS SQL 2005.
i am scheduling the standard job like (SAP_COLLECTOR_FOR_JOBSTATISTIC ) in sm36.
in start time when i am selecting IMMEDIATE it is ok and working.
but in start time when i select particular date/time it gives error :-
"Error saving job SAP_COLLECTOR_FOR_JOBSTATISTIC to
database"
can any one tell me why is this happing.

Standard Job Definition - What are these?

Can someone tell me what the following jobs are? Can't find any SAP documentation on these.
I see them in the BWCCMS, but can't find any information on them. Shouldn't these be documented if they are defined as standard jobs that should be run?
SAP_PROCESS_CUA_IDOCS_INB_000
SAP_REORG_SECURITY_LOG
SISM_COLL_AND_TRANS_DATA

Hello Kenneth,
all these jobs belong to SAP internal systems and should only be used by them (component XX-HST-OPR*). There's little information released for them, all for internal use of SAP only.
This is a summary of each one that can be made public:
job SAP_PROCESS_CUA_IDOCS_INB_000:
The job SAP_PROCESS_CUA_IDOCS_INB_000 executes the program RBDAPP01 (Inbound processing for Idocs ready for transfer) with an internal variant to perform the (Inbound Processing of CUA IDOC). This is a part of CUA (Central User Administration) configuration, but for Hosting Users/Systems only. The job is required to run in short periods to get the data from CUA server and must be run only in a specific SAP standard client and not in any customer client.
job SAP_REORG_SECURITY_LOG:
This job is a new job that hosting is deploying as part of security logging in a specific SAP standard client. It performs security/systems settings scans in SAP Hostings Systems for optimization and security purposes.
job SISM_COLL_AND_TRANS_DATA:
This job collects specific data for transaction SISM (SAP inhouse system manager), used to manage SAP Hosting systems.
I hope this information helps.
Best regards,
Tomas Black

Jobs are in "Cancelling" Status

Hi Team,
Some of the Jobs are in "Cancelling" from long time . More than a month. Could you please help me in deleting those jobs.
Is there any way we can do job status check (like in SM37)
Thanks,
Preethish

Hi Preetish,
You can use the System_ForceJobStatusUnknown JobDefinition to set a particular job to Unknown, after that you can delete the Unknown job.
Regards,
Anton.

Standard Job SAP_CCMS_MONI_BATCH_DP is cancelling

Similar Messages

Maybe you are looking for