SAP_COLLECTOR_FOR_NONE_R3_STAT and SAP_COLLECTOR_FOR_PERFMONITOR

[Former Member]

Hi all,

We are useing SAP ECC 6.0 with Oracle 10.2.0.2. We scheduled all standard jobs in SM36.

My doubt is:

If we do not schedule only these two standard jobs SAP_COLLECTOR_FOR_NONE_R3_STAT and SAP_COLLECTOR_FOR_PERFMONITOR, what are the problems we will face in future and where these jobs update the information?

Thanks in advance!!!

Regards,

Veera

[Former Member · Accepted solution]

Hi,

If those two jobs are not scheduled, then the data related to performance of server cannot get populated.

Say for eg: ST03 data will not be there.

If performance data was missing you cannot analyze or check what transactions are consuming more time or what reports consumed more HW resources.

In future it will be hard time to analyze where to fine tune for better system performance.

On a whole if the jobs dont run you dont have performance related statistics avilable for analysis.

Reagrds.

[Former Member · Accepted solution]

Hi ,

I am able to see dialy performance data in ST03 ( without running the above 2 jobs ). Can anyone explain where these jobs update performance related data in the system

[Former Member · Accepted solution]

Please go through the note I have given earlier, which has all the details for each standard jobs.

[Former Member · Accepted solution]

Hi,

There is a MONI table where the collected data will be put and the system do the math to bring up the data in st03.

You said the job was not running but still able to see the stat data. How many instances do you have, can you see all the instance data is getting populated under st03n.

Also chk if these jobs are getting run under diff job name by putting the program name in SM37 under ABAP program name in your system, since it was not possible to get the data if the job not running at all.

Job: SAP_COLLECTOR_FOR_PERFMONITOR -- This is for ST03N data

Program: RSCOLL00

Job: SAP_COLLECTOR_FOR_NONE_R3_STAT -- Non-R3 related content even this job diont run nothing to worry. Program: RSN3_STAT_COLLECTOR

Please chk the note: 16083

Please check the below links:

http://help.sap.com/saphelp_nw04/helpdata/en/51/84e93ad578f915e10000000a11402f/content.htm?cf03388EF...

http://help.sap.com/saphelp_nw04/helpdata/en/bf/0ae73ac6e7ec28e10000000a114084/content.htm

Hope this helps you.

Edited by: Sita Rr Uppalapati on Dec 21, 2010 6:32 PM

[Former Member · Accepted solution]

Hi Sita Rr,

Thanks for your reply but in our sap ecc 6.0 system those above 2 jobs are some times running successfully and some times cancelled with below log:

21.12.2010 12:00:22 Job started

21.12.2010 12:00:30 Step 001 started (program RSCOLL00, variant , user ID BASIS)

21.12.2010 12:00:38 Clean_Plan:Cleanup of DB13 Plannings

21.12.2010 12:00:38 Clean_Plan:started by RSDBPREV on server sp545

21.12.2010 12:00:38 Clean_Plan:Cleaning up jobs of system QAS

21.12.2010 12:00:38 Clean_Plan:finished

21.12.2010 12:00:39 Internal session terminated with a runtime error (see ST22)

21.12.2010 12:00:39 Job cancelled

In ST22 is is giving dump

Runtime Errors SAPSQL_ARRAY_INSERT_DUPREC

Exception CX_SY_OPEN_SQL_DB

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", nor was it propagated

by a RAISING 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:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to

Please help if anyone faced this problem or have any idea.

Regards

Veera

[Former Member · Accepted solution]

whats your support pack levels? check Note 1041894

[Former Member · Accepted solution]

Hi Sunil,

Support package details are:

Software

Comp Release Level Highest support Component

SAP_ABA 701 0005 SAPKA70105 Cross-Application Component

SAP_BASIS 701 0005 SAPKB70105 SAP Basis Component

PI_BASIS 701 0005 SAPK-70105INPIBASIS Basis Plug-In

ST-PI 2008_1_700 0002 SAPKITLRD2 SAP Solution Tools Plug-In

But I am facing this problem from last 2 days only and also only in one system. It is running fine in all other systems

Regards

Veera

Edited by: Veerab on Dec 21, 2010 3:59 PM

[Former Member · Accepted solution]

can you please paste some part of the dump need to check what program/function causing the issue.

[Former Member · Accepted solution]

Hi Sunil,

Dump is as mentioned below:

Short text

The ABAP/4 Open SQL array insert results in duplicate database records.

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it

has

come across a statement that unfortunately cannot be executed.

Error analysis

An exception occurred that is explained in detail below.

The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught

in

procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", nor was it propagated

by a RAISING 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:

If you use an ABAP/4 Open SQL array insert to insert a record in

the database and that record already exists with the same key,

this results in a termination.

(With an ABAP/4 Open SQL single record insert in the same error

situation, processing does not terminate, but SY-SUBRC is set to 4.)

Information on where terminated

Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in

"BAL_DB_INTERNAL_NO_UPDATE_TASK".

The main program was "SWNCCOLL ".

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

of the (Include) program "LSBAL_DB_INTERNALU02".

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

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

Job Initiator.. "BASIS"

Job Number..... 08893100

The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in

procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither

handled locally nor declared

in the RAISING clause of its signature.

The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins

line

1 of the (Include program "LSBAL_DB_INTERNALU02 ".

System environment

SAP-Release 701

Application server... "appl543"

Network address...... "122.99.01.88"

Operating system..... "AIX"

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

Hardware type........ "099DER88BN90000"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 27

Shortdump setting.... "full"

Database server... "appl543"

Database type..... "ORACLE"

Database name..... "Q22"

Database user ID.. "SAPSR3"

[Former Member · Accepted solution]

Hi,

The dump triggers when same record is getting updated again.

Is this dump getting generated everytime when job runs or occurs at random time?

How many dumps getting generated per day and during what time of day.

[Former Member · Accepted solution]

Below note looks similar to your issue.

Note 196113 - SAPSQL_ARRAY_INSERT_DUPREC, BALHDR

Edited by: Sunil Bujade on Dec 22, 2010 10:31 AM

[Former Member · Accepted solution]

Hi Sita Rr,

This is a hourly job and It got cancelled 20 times per day and successfully ran only 4 times.

It is generating the dump in ST22 every time when the job cancelled. Kindly give me your valuable advice on this isssue.

Edited by: Veerab on Dec 22, 2010 11:22 AM

[Former Member · Accepted solution]

Hi,

I need some more information, can you please provide what are the log entries in SM21 during st22 dump.

Entries above to st22 dump entries in sm21.

[Former Member · Accepted solution]

Hi Sita Rr,

The SM21 details are :

10:41:45 BTC 026 150 USER AB 0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred

10:41:45 BTC 026 150 USER AB 1 > Short dump "101222 104345 s6350_EO 1_50 " generated

10:41:45 BTC 026 150 USER D0 1 Transaction Canceled 00 671 ( SAPSQL_ARRAY_INSERT_DUPREC 10:41:51 BTC 028 150 USER AB 0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred

10:41:51 BTC 028 150 USER AB 1 > Short dump "101222 104351 s6350_EO 1_50 " generated

10:41:51 BTC 028 150 USER D0 1 Transaction Canceled 00 671 ( SAPSQL_ARRAY_INSERT_DUPREC 11:41:23 BTC 028 150 USER AB 0 Run-time error "SAPSQL_ARRAY_INSERT_DUPREC" occurred

11:41:23 BTC 028 150 USER AB 1 > Short dump "101222 114323 s6350_EO 1_50 " generated

11:41:23 BTC 028 150 USER D0 1 Transaction Canceled 00 671 ( SAPSQL_ARRAY_INSERT_DUPREC

the log details :

Documentation for system log message :

The transaction has been terminated. This may be caused by a

termination message from the application (MESSAGE Axxx) or by an

error detected by the SAP System due to which it makes no sense to

proceed with the transaction. The actual reason for the termination

is indicated by the T100 message and the parameters.

Additional documentation for message 00 671

Internal session terminated with a runtime error (see ST22)

No documentation exists for message 00671

Edited by: Veerab on Dec 22, 2010 11:58 AM

Edited by: Veerab on Dec 22, 2010 12:00 PM

Edited by: Veerab on Dec 22, 2010 12:01 PM

[Former Member · Accepted solution]

Have you checked the note which I give before as the note looks same as the error you are getting.

[Former Member · Accepted solution]

Hi,

This seems to be problem with number range buffering in regards to APPL_LOG. Please check the s-note provided by sunil.

As per my understanding when the job was trying to update the Application log details of performance statistics from that instance onto BALHDR table it was getting a record number which was already present(record number picked by other instance of the server).

Please tell me if this dump was throwing only to this background job running on this instance or if there are some other jobs also getting terminated with this error.

how many instances do you have.

[Former Member · Accepted solution]

Hi Sita Rr,

Only this job generating the dumps and also we are getting this dumps only in QA . The central instance and database instance are on the same host system in QA and we are not getting this type of dump in any other SAP systems

[Former Member · Accepted solution]

Hi,

SInce this was a QAS system, does any refresh happen recently.

Check below link

http://help.sap.com/saphelp_nw04/helpdata/EN/95/3d5540b8cdcd01e10000000a155106/frameset.htm

Analyse if it was ok to perform buffer reset for appl_log, (I prefer you raise a customer message)

Steps:

start transaction SM56.

in the menu select goto-->Number range buffer -> Reset. Fill the fields in the dialog box that appears as follows:

Client <your productive client>

Object APPL_LOG

Subobject

Range

Year

Global reset X

If you still have dump, better you approach SAP by customer message.

Edited by: Sita Rr Uppalapati on Dec 22, 2010 7:48 PM

[Former Member · Accepted solution]

>>Steps:

>>start transaction SM56.

You copied the texts from note, thats what I said to him to refer note: 196113, not sure why he has not refered.

[Former Member · Accepted solution]

Hi,

We have already dealt with similar issue where it was affecting system performance due to Number range buffering. I dont get your statement "copied from" that info was available in the note(which you posted as note number) and sap help portal as well.

[Former Member · Accepted solution]

I mean that the information you have given was already in note, he should have gone through the note. Than waiting for some to give step by step soltuion. You agree?

[Former Member · Accepted solution]

.....agree, that saves time.

[Former Member]

For those who had this problem and the note 196113 did not help, I iopened a message at SAP and they refered me to note 16083 which says that almost all standard jobs should be scheduled in client 000.

My systems were built with jobs in clients other than 000.

I rescheduled the jobs under client 000 and now it does not fail.

[Former Member]

Hi VeeraB,

You can try the following:

Goto Tcode ST03 --> Ensure you are in Expert mode.

Expand Collector and performance DB --> Performance Database --> Monitoring Database

Double Click Contents.on the LHS frame.

Select the first line.

Cick on the button "Select the block"

Select the last line,

Click the button "Select the Block".

Click on Save.

Rerun your background job.

I hope this resolves your problem.

Best Regards,

Chandan.

• Caution, this will delete data from the database, Its only performance data, so you should be ok, but this is a risk you need to evaluate. ***

[Former Member]

The "Note 16083 - Standard jobs, reorganization jobs" should help to clarify your query.