SAP_COLLECTOR_FOR_PERFMONITOR JOB fails

Hi experts..

In SRM system, SAP_COLLECTOR_FOR_PERFMONITOR jobs is failing at specified intervels like 9, 13, 14, 19 and 22 with RAISE_EXCEPTION error.

this job has scheduled with other user also..with that user its completing successfully in every run....

when i check st22 its shows message like this..

Exception condition "NO_AUTHORIZATION" raised.

What happened?

The current ABAP/4 program encountered an unexpected
situation.

What can you do?

Print out the error message (using the "Print" function)
and make a note of the actions and input that 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.

Could you please let me know the issue....

SAP Managed Tags:
SAP NetWeaver

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (1)

Hi Renuka,

Did you try giving SAP_ALL to the background user and checking the results ?

Regards,

Deepak Kori

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Deepak,

We are not supposed to give SAP_ALL to background user.(Given authorization to run background job)

My doubt is...its completing succesfully in all runs except 5 runs mentioned above.

Hi Renuka,

Did it happened on a single day or it is a continuous behavior since inception of the background job ?

Regards,

Deepak Kori

Hi Deepak,

It is a continuous behaviour...

Hi Renuka,

Please attach the failed job log

Regards,

Deepak Kor

Hi Deepak,

Please find the below job log

Job started

Step 001 started (program RSCOLL00, variant , user ID BASISBGD)

Failed to delete log for job COLLECTOR_FOR_PERFORMANCEMONITOR

Failed to delete log for job SAP_COLLECTOR_FOR_PERFMONITOR

Failed to delete log for job COLLECTOR_FOR_PERFORMANCEMONITOR

Failed to delete log for job SAP_COLLECTOR_FOR_PERFMONITOR

ABAP/4 processor: RAISE_EXCEPTION

Job cancelled

Hi Deepak,

In my systems 2 OS collector jobs are running..

COLLECTOR_FOR_PERFORMANCEMONITOR in 000client with DDIC user

and SAP_COLLECTOR_FOR_PERFMONITOR in 400client with BASISBGD log..

in the above mentioned log its showing like failed to delete log for 2jobs mentioned overe here...

Hi Renuka,

Can you share following details

1) How many application servers exists for the SAP environment where this job fails ?

2) Check on which application server the failed job got executed .

3) I understand that jobs are failing with DDIC user as well as BASISBGD user ?

4) Is this system a new system or a copied system ?

Regards,

Deepak Kori

Hi Deepak,

Thank you for giving instant response..

1.We have only one application server.

2.With DDIC its running fine, with user BASISBGD only its failing.

3.it is a new system.

Hi Deepak..

Pls find the log below....

Mon Aug 18 19:05:24 2014

A ABAP Program SAPLSTUB .

A Source LSTUBF02 Line 888.

A Error Code RAISE_EXCEPTION.

A Module $Id: //bas/640_REL/src/krn/runt/abfunc.c#25 $ SAP.

A Function ab_jfune Line 2386.

A ** RABAX: level LEV_RX_STDERR completed.

A ** RABAX: level LEV_RX_RFC_ERROR entered.

A ** RABAX: level LEV_RX_RFC_ERROR completed.

A ** RABAX: level LEV_RX_RFC_CLOSE entered.

A ** RABAX: level LEV_RX_RFC_CLOSE completed.

A ** RABAX: level LEV_RX_IMC_ERROR entered.

A ** RABAX: level LEV_RX_IMC_ERROR completed.

A ** RABAX: level LEV_RX_DATASET_CLOSE entered.

A ** RABAX: level LEV_RX_DATASET_CLOSE completed.

A ** RABAX: level LEV_RX_ERROR_SAVE entered.

A ** RABAX: level LEV_RX_ERROR_SAVE completed.

A ** RABAX: level LEV_RX_ERROR_TPDA entered.

A ** RABAX: level LEV_RX_ERROR_TPDA completed.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.

A ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.

A ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.

A ** RABAX: level LEV_RX_END entered.

A ** RABAX: level LEV_RX_END completed.

A ** RABAX: end no http/smtp

A ** RABAX: end RX_BTCHLOG|RX_VBLOG

A Exception condition "NO_AUTHORIZATION" raised..

Hi Renuka,

Could you ensure BASISBGD has right set of authorization . For guidelines refer SAP help

Authorizations for Background Processing (SAP Library - Background Processing)

You may also keep same authorization like DDIC ( if DDIC does not have SAP_ALL in client 000).

Regards,

Deepak Kori

Hi Deepak,

DDIC has SAP_ALL authorization...

My question is ..if it is authorization issue..why it is running fine in other turns..it couldnt be run right?

Hi Renuka,

Oh yes. I missed that information .

If I understood correctly, you have DB+CI and 1-Application server running.

From the information whatever you have shared so far it is apparently a authorization issue.

Probability here is job getting executed on application server when it fails while rest of the time it is running on CI host.

Do you see such observation ?

Regards,

Deepak Kori

Hi Deepak,

Apoligies..We dont have any application server...we have only CI..

both finished and cancelled job both are running on CI...

Hi Renuka,

Could you please attach the relevant ABAP dump.

Regards,

Deepak Kori

Hi Deepak..

Pls find the below ST22 dump

Runtime Error RAISE_EXCEPTION
Occurred on 18.08.2014 at 09:05:09

Exception condition "NO_AUTHORIZATION" raised.

What happened?

The current ABAP/4 program encountered an unexpected
situation.

What can you do?

Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.

Error analysis

A RAISE statement in the program "SAPLSTUB" raised the exception
condition "NO_AUTHORIZATION".
Since the exception was not intercepted by a superior program

in the hierarchy, processing was terminated.

Short description of exception condition:

For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
-

How to correct the error

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:

"RAISE_EXCEPTION" C
"SAPLSTUB" or "LSTUBF02"

"AUTHORITY_CHECK"

"SAPLSTUB" "NO_AUTHORIZATION"

"RSTUNE80 " "NO_AUTHORIZATION"
If you cannot solve the problem yourself, please send the
following documents to SAP:

1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
-

2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.

3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.

4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.

System environment

SAP Release.............. "610"

Application server....... "WAFSRPRD"
Network address.......... "10.163.21.216"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "4x AMD64 Level"

Database server.......... "WAFSRPRD"
Database type............ "MSSQL"
Database name............ "EP2"
Database owner........... "dbo"

Character set............ "English_United State"

SAP kernel............... "640"
Created on............... "Nov 8 2011 21:47:05"
Created in............... "NT 5.2 3790 Service Pack 2 x86 MS VC++ 14.00"
Database version......... "SQL_Server_8.00 "

Patch level.............. "390"
Patch text............... " "

Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0, Windows NT 6.1"

User, transaction...

Client.............. 400
User................ "BASISBGD"
Language key........ "E"
Transaction......... " "
Program............. "SAPLSTUB"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6

Information on where termination occurred

The termination occurred in the ABAP program "SAPLSTUB" in "AUTHORITY_CHECK".
The main program was "RSTUNE80 ".

The termination occurred in line 888 of the source code of the (Include)
program "LSTUBF02"
of the source code of program "LSTUBF02" (when calling the editor 8880).
The program "SAPLSTUB" was started as a background job.

Source code extract

008580     ENDWHILE.
008590
008600   ENDFORM.                               " NUM_SEARCH
008610   *&                                                                     *
008620   *&      Form CURSOR_CACHE
008630   *&                                                                     *
008640   *       Bestimmt die Größe des Cursor Caches                           *
008650   *                                                                      *
008660   * <    cursor_cache      Größe Cursor Cache
008670   *                                                                      *
008680   FORM CURSOR_CACHE USING CURSOR_CACHE.
008690
008700   * Ist standardmäßig 2000 und kann zur Zeit nicht verändert werden
008710     CURSOR_CACHE = 2000.

Can check the client details for the successful jobs,

I believe few of this jobs may be running in more than one client. Remove jobs which are scheduled other than client 000.

refer 16083 - Standard jobs, reorganization jobs

The job SAP_COLLECTOR_FOR_PERFMONITOR must always be scheduled in client 000 with user DDIC or with a user with the same authorization.

regards

Swami

Hi Arunachalam,

Pls find the requested details...

SAP_COLLECTOR_FOR_PERFMONITOR BASISBGD Finished 18.08.2014 00:05:06 14 6

Yes as u said..this job is running in 000 and 400 client as well...

Hi Renuka,

Do you really need these jobs in both the clients. As shared by Swami, this job can execute in 000 client as it collects system performance data only.

Regards,

Deepak Kori

You can remove this job from client 400, check for the status for remaining scheduled job in client 000.

Hope you also checked authorization level in client 000.

I prefer to leave default user as DDIC in client 000 & need to follow SAP Standard for house keeping jobs to run.

regards

Swami

Hi All,

Thank you for all your response..

according note 16083 i have scheduled OS collector job in 000 client with DDIC user...

Ask a Question

Top Q&A Solution Author

User

Count