SAP_COLLECTOR_FOR_PERFMONITOR background job cancelled in SM37

[Former Member]

Dear all ,

One of the scheduled background job has been cancelled .

Kindly check the below loga and Background job details .

Job name SAP_COLLECTOR_FOR_PERFMONITOR

Job class C

Status Canceled

(ABAP Program

Name RSCOLL00

Variant

Language EN)

Job Log :

30.05.2010 06:20:32 Job started

30.05.2010 06:20:32 Step 001 started (program RSCOLL00, variant , user ID DDIC)

30.05.2010 06:20:37 Clean_Plan:Cleanup of DB13 Plannings

30.05.2010 06:20:37 Clean_Plan:started by RSDBPREV on server PRDCIXI

30.05.2010 06:20:38 Clean_Plan:Cleaning up jobs of system IRP

30.05.2010 06:20:39 Clean_Plan:finished

30.05.2010 06:20:43 ABAP/4 processor: DBIF_RTAB_SQL_ERROR

30.05.2010 06:20:43 Job cancelled

Kindly suggest

[Former Member · Accepted solution]

ORA-00060: deadlock detected while waiting for resource

Is there any other program or standard job running in your system?

Or

Did you run this job mroe than once in your system?

Just check the lock entries from SM12 with the job owner and delete (only if any job is not there in active mode)

And check all standard jobs from SM37 and rerun this job........

*Deadlock is a normal situation in DB access, Google/Search SDN for DEADLOCK in Oracle for more info.

Regards,

Nick Loy

[former_member204746]

RSCOLL00 is probably running twice at the same time.

refer to SAP note 16083.

[Former Member]

Dear all ,

I have checked from SM37 , The same job (SAP_COLLECTOR_FOR_PERFMONITOR) has been scheduled by 2 users (DDIC and BASIS).

Kindly advise The above mentioned standard background job should be run by only one user ?

Regards

[former_member204746]

it should only run with 1 user. delete one or the other duplciate and close this mesasge.

[Former Member]

HI ,

let me know the standard job SAP_COLLECTOR_FOR_PERFMONITOR should be run DDIC user or any User .

Regards

[Former Member]

Hey Satheesh,

SAP_COLLECTOR_FOR_PERFMONITOR job is not a client specific job you may run in any client of a system and the user which it should run must be DDIC. However there are few more housekeeping jobs wherein they can run under any user like...

SAP_REORG_ABAPDUMPS

SAP_REORG_JOBSTATISTIC

SAP_REORG_UPDATERECORDS

SAP_COLLECTOR_FOR_JOBSTATISTIC

Also pls note this: If your R/3 System runs with an Arabian, Russian (Cyrillic), or Asian character set, then you may need to change the language specified in the standard background jobs listed above. Languages are assigned to jobs based on job steps. Be sure that the language specified in the job step definition in each of these jobs is set to EN, for English.

This change is required because not all languages are available with all code pages. If the language specified in the job is not available, then the background job will not run

[Former Member]

Hi Satheesh

As you can see you have got the dump as due to Oracle deadlocks... Pls check your table entries in SM12 for the table TCOLL and Program Name RSCOLL00. Check DB01 for any existence of any deadlock in your system... You can get more information about the same from OS level at

/oracle/<SID>/saptrace/background/alert<SID>.log

/oracle/<SID>/saptrace/usertrace

Also, please check the imp. note : Note 84348 - Oracle deadlocks, ORA-00060

Hope it will resolve your issue....

[Former Member]

Any dump you found in ST22 with the description DBIF_RTAB_SQL_ERROR ?

If yes paste the dump here...

Regards,

Nick Loy

[Former Member]

Dear all ,

Kindly check the ST22 error logs .

Short text SQL error occurred in the database when accessing a table. What happened? The database system detected a deadlock and avoided it by rolling back your transaction. What can you do? If possible (and necessary), repeat the last database transaction in the hope that locking the object will not result in another deadlock. Note which actions and input led to the error. For further help in handling the problem, contact your SAP administrator . You can use the ABAP dump analysis transaction ST22 to view and manage termination messages, in particular for long term reference. Error analysis The database system recognized that your last operation on the database would have led to a deadlock. Therefore, your transaction was rolled back to avoid this. ORACLE always terminates any transaction that would result in deadlock. The other transactions involved in this potential deadlock are not affected by the termination. Last error logged in SAP kernel Component............ "SAP-Gateway" Place................ "SAP-Gateway on host PRDCIXI / sapgw01" Version.............. 2 Error code........... 679 Error text........... "program prodoradb.sapccmsr.99 not registered" Description.......... "TP prodoradb.sapccmsr.99 not registered" How to correct the error Database error text........: "ORA-00060: deadlock detected while waiting for resource" Internal call code.........: "[RTAB/UPD /MONI ]" Please check the entries in the system log (Transaction SM21). 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: "DBIF_RTAB_SQL_ERROR" " " "RSHOST3M" or "RSHOST3M" "PUT_LOGBOOK" 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 System call.......... " " Module............... "gwr3cpic.c" Line................. 1835 The error reported by the operating system is: Error number..... " " Error text....... " "

for detail log.

System environment

SAP-Release 700

Application server... "PRDCIXI"

Network address...... "10.54.145.32"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "000184CAD400"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 8

Shortdump setting.... "full"

Database server... "PRODORADB"

Database type..... "ORACLE"

Database name..... "IRP"

Database user ID.. "SAPSR3"

Terminal................. " "

Char.set.... "C"

SAP kernel....... 700

created (date)... "Mar 7 2010 21:00:49"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 246

Patch text.. " "

Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 1217248

EM...... 0

Heap.... 0

Page.... 32768

MM Used. 1050520

MM Free. 146024

and Transaction

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Transactions ID..... "4BFF227871E00187E10080000A369120"

In the source code you have the termination point in line 521

of the (Include) program "RSHOST3M".

The program "RSHOST3M" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "DDIC"

Job Number..... 02033500

In the source code you have the termination point in line 521

of the (Include) program "RSHOST3M".

The program "RSHOST3M" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "DDIC"

Job Number..... 02033500

Program............. "RSHOST3M"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

rmation on where terminated

Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".

The main program was "RSHOST3M ".

[Former Member]

Dear all ,

for detail log.

System environment

SAP-Release 700

Application server... "PRDCIXI"

Network address...... "10.54.145.32"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "000184CAD400"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 8

Shortdump setting.... "full"

Database server... "PRODORADB"

Database type..... "ORACLE"

Database name..... "IRP"

Database user ID.. "SAPSR3"

Terminal................. " "

Char.set.... "C"

SAP kernel....... 700

created (date)... "Mar 7 2010 21:00:49"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_102 (10.2.0.2.0) "

Patch level. 246

Patch text.. " "

Database............. "ORACLE 10.1.0.., ORACLE 10.2.0.., ORACLE 11.2...*"

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6"

Memory consumption

Roll.... 1217248

EM...... 0

Heap.... 0

Page.... 32768

MM Used. 1050520

MM Free. 146024

and Transaction

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... " "

Transactions ID..... "4BFF227871E00187E10080000A369120"

In the source code you have the termination point in line 521

of the (Include) program "RSHOST3M".

The program "RSHOST3M" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "DDIC"

Job Number..... 02033500

In the source code you have the termination point in line 521

of the (Include) program "RSHOST3M".

The program "RSHOST3M" was started as a background job.

Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"

Job Initiator.. "DDIC"

Job Number..... 02033500

Program............. "RSHOST3M"

Screen.............. "SAPMSSY0 1000"

Screen line......... 6

rmation on where terminated

Termination occurred in the ABAP program "RSHOST3M" - in "PUT_LOGBOOK".

The main program was "RSHOST3M ".