SAP_COLLECTOR_FOR_PERFMONITOR failing with dump

HI All,
SAP standard job SAP_COLLECTOR_FOR_PERFMONITOR is failing with below job log
31.05.2012 00:19:03 Job started
31.05.2012 00:19:03 Step 001 started (program RSCOLL00, variant , user ID CP1SUP)
31.05.2012 00:19:06 Clean_Plan:Cleanup of DB13 Plannings
31.05.2012 00:19:06 Clean_Plan:started by RSDBPREV on server ttahmsv2050
31.05.2012 00:19:06 Clean_Plan:Cleaning up jobs of system PRD
31.05.2012 00:19:06 You are not authorized for DB access (S_DBCON: <LOCAL SYSTEM> PRD <Windows authentication> 03)
31.05.2012 00:19:06 Function DB6_PLAN_STOP_BATCH_JOB failed with return code = Job error
31.05.2012 00:19:06 Clean_Plan:terminated with error
31.05.2012 00:19:06 REASON=Job error
31.05.2012 00:19:06 ABAP/4 processor: COMPUTE_INT_TIMES_OVERFLOW
31.05.2012 00:19:06 Job cancelled
and its also getting finished with job log
31.05.2012 01:19:03 Job started
31.05.2012 01:19:03 Step 001 started (program RSCOLL00, variant , user ID CP1SUP)
31.05.2012 01:19:06 Database system not supported
31.05.2012 01:19:06 Database system not supported
31.05.2012 01:19:11 Job finished
i.e every alternate run it gets finsihed and gets cancelled
Dump obtained is COMPUTE_INT_TIMES_OVERFLOW
I have found this note 1027512 not sure if there is any other way

Hi,
thank you all for your help. I tried the solution provided in SAP Note 199586. Although, it does not talk about my specific issue, however, I tried solution 1 and after that job is running fine.
Thanks again for all your help.
Regards,
Sudhir

Similar Messages

Delta load failing with dump TSV_TNEW_PAGE_ALLOC_FAILED

Hi,
When we are loading BW statistics delta load, the load is failing with error "Job in source system terminated --> Request is set to red." and its giving short dump with "TSV_TNEW_PAGE_ALLOC_FAILED".
I have already gone through Forum and changed package size also. But could not solve the problem.
We are using 3.5 version, Could you please post your thought ASAP.
Regards
Satya

Hi there,
Yes that dump is lack of memory...
So probably your package has too many records to be processed, especially if you have code in start routine or end routine or something like that, the process for each package might take too long and fails with out of memory.
Try in fact change the package size to a smaller size, so fewer records are processed in each package.
Diogo.

GRC 10.1 SP06 - Role sync fails with dump DBIF_RSQL_INVALID_RSQL

Hi!
We're experiencing an issue with the repository sync job for one connector. When selecting the full option, the sync for users and profiles report success but for the role sync we get the error "Error in RFC; 'Error in module RSQL of the database interface'" and a dump is generated in the back-end ( DBIF_RSQL_INVALID_RSQL) with the program /GRCPI/CL_GRIA_ROLE===========CP
The problem occurs in the sentence:
>>>>>
SELECT agr_name parent_agr FROM agr_define
"#EC CI_SGLSELECT
   84
INTO TABLE lt_derived
   85 *
WHERE agr_name IN it_incl_role
   86
WHERE agr_name IN lt_incl_role
   87
AND ( change_dat GE iv_update_date OR
   88
( create_dat GE iv_update_date AND change_dat = '00000000' ) ).
We've tried working with the parameter 1122 (Batch size for Role sync) switching it to different values like 500, 100, 50, 10 and even 1 but the error still persists.
Synch for another connector with the same GRC System works fine.
any idea?
Thanks,
Diego.

Sounds like an old foe from 10.0
http://service.sap.com/sap/support/notes/1632421
You may have to ask SAP to make a 10.1 version of this fix for you to apply to the plug-in system.
There is a specific note for this issue in both 10.0 and 10.1, but it is part of 10.1 SP01 (you are on SP06)
http://service.sap.com/sap/support/notes/1803121

SAP job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND

Dear Experts,
Background job SAP_COLLECTOR_FOR_PERFMONITOR getting failed with abap dump LOAD_PROGRAM_NOT_FOUND.
As it is hourly scheduled job and it gets finished 22 times in a day but other 2 times fails with abap dump.
Finished Job log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Clean_Plan:Cleanup of DB13 Plannings
Clean_Plan:started by RSDBPREV                       on server
Clean_Plan:Cleaning up jobs of system DEV
Clean_Plan:finished
Job finished
Failed Job Log
Job started
Step 001 started (program RSCOLL00, variant , user ID Bharath)
Internal session terminated with a runtime error (see ST22).
Kindly suggest on this..
Thanks,
Bharath.

Dear Divyanshu,
Our system in ERP 6.0 EHP5 with SP level 10. The ABAP Dump shows below error.
|Short text                                                                                        |
|    Program "RSORA811" not found.                                                                 |
|What happened?                                                                                    |
|    There are several possibilities:                                                              |
|                                                                                                  |
|    Error in the ABAP Application Program                                                         |
|                                                                                                  |
|    The current ABAP program "RSCOLL00" had to be terminated because it has                       |
|    come across a statement that unfortunately cannot be executed.                                |
|    or                                                                                            |
|    Error in the SAP kernel.                                                                      |
|                                                                                                  |
|    The current ABAP "RSCOLL00" program had to be terminated because the                          |
|    ABAP processor detected an internal system error.                                             |
|What can you do?                                                                                  |
|    Note down which actions and inputs caused the error.                                          |
|                                                                                                  |
|                                                                                                  |
|    To process the problem further, contact you SAP system                                        |
|    administrator.                                                                                |
|                                                                                                  |
|    Using Transaction ST22 for ABAP Dump Analysis, you can look                                   |
|    at and manage termination messages, and you can also                                          |
|    keep them for a long time.                                                                    |
|Error analysis                                                                                    |
|    On account of a branch in the program                                                         |
|    (CALL FUNCTION/DIALOG, external PERFORM, SUBMIT)                                              |
|    or a transaction call, another ABAP/4 program                                                 |
|    is to be loaded, namely "RSORA811".                                                           |
|                                                                                                  |
|    However, program "RSORA811" does not exist in the library.                                    |
|                                                                                                  |
|    Possible reasons:                                                                             |
|    a) Wrong program name specified in an external PERFORM or                                     |
|       SUBMIT or, when defining a new transaction, a new                                          |
|       dialog module or a new function module.                                                    |
|    b) Transport error                                                                            |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "RSCOLL00" - in                                      |
|     "LOOP_AT_SYSTEMS_AND_REPORTS".                                                               |
|    The main program was "RSCOLL00 ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 535                                 |
|    of the (Include) program "RSCOLL00".                                                          |
|    The program "RSCOLL00" was started as a background job.                                       |
|    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"                                               |
|    Job Initiator.. " bharath"                                                                       |
|    Job Number..... 18243400
Kindly check and suggest..
Thanks,
Bharath.

BDLS failing with ASSERTION_FAILED dump

Dear Experts,
We have replaced the existing quality system DF0 with RC0.These both system are quality systems and RC0 has been refreshed from production.
So in BW qulaity system we need to replace the DF0 with RC0 as source system. I have created logical system name LSRC0310 for RC0 in BW qulaity system and ran a BDLS to convert DF0 to RC0. But it is giving a dump ASSERTION_FAILED.
Earlier it failed with error that logical system LSRC0310 name alreday exists.So i deleted the logical system name and ran BDLS but it again failed with same error.I have checked the logs and it just makes an entry in table TBDLS, TBDLST. The logs in BDLSS also says that the conversion went in error with "Error in field of table . Manual correction required."
Thus the source system DF0 is not replaced in RSA1 also i can still see cubes pointing to DF0.
I have referred to Modify source system link but it is failing in the BDLS step so cannot proceed ahead.
Please can you guide and help is solving this issue.
Regards,
KUldeep.

Thanks Walter for your reply.
This note is already present in the system and still BDLS fails with this message.
I hope my approach is correct.
Currently source system is DF0 and we want to convert to RC0. So running a BDLS will convert all the logical source system names for all the transfer structure and DTPs and transformations.Then after BDLS step i can restore the source system in RSA1.
Please confim if my this is feasible.
Regards,
Kuldeep.

LANDSCAPE FETCH (RSGET_SMSY) fails with ASSERTION_FAILED dump

We are running Solution Manager 7.1 SP14 on Unix/Oracle. When we execute LANDSCAPE FETCH (or RSGET_SMSY), it fails with an ABAP dump runtime error ASSERTION_FAILED. We have searched OSS and SDN and the notes that appear to resolve the issue cannot be implemented in our system.
Has anyone seen this before in their Solution Manager system? Any help will be appreciated.
WL

Hi Wayna,
Can you share ST22 dump ?
Also, What have you recently changed in SLD/LMDB ?
Regards,
Divyanshu

Data load failing with a short-dump

Hello All,
There is a data load failing with the following short-dump:
Runtime Errors UNCAUGHT_EXCEPTION
Except. CX_FOEV_ERROR_IN_FUNCTION
Full text:
"UNCAUGHT_EXCEPTION" CX_FOEV_ERROR_IN_FUNCTIONC
"CL_RSAR_FUNCTION==============CP" or "CL_RSAR_FUNCTION==============CM004"
"DATE_WEEK"
It seems as if it is failing in a function module - please advise.
Regards,
Keith Kibuuka

Did you read OSS [Note 872193 - Error in the formula compiler|https://service.sap.com/sap/support/notes/872193] or OSS [Note 855424 - Runtime error UNCAUGHT_EXCEPTION during upload|https://service.sap.com/sap/support/notes/855424]
Regards

Export dumps failing with ORA-31623: a job is not attached to this session

Hi,
Oracle Version : 11.1.0.7.0
OS Solaris : 10
Export partition dumps failing with the Error message ORA-31623: a job is not attached to this session via the specified handle.
When i checked the table dba_datapump_jobs, i found several table is in "NOT RUNNING" status. Please help me what to do this?
OWNER_NAME JOB_NAME OPERATION JOB_MODE STATE DEGREE ATTACHED_SESSIONS DATAPUMP_SESSIONS
OAM BIN$wzWztSbKbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbZbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztScGbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSaxbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbAbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbPbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbobFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSb3bFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSanbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSb8bFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSa2bFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OWNER_NAME JOB_NAME OPERATION JOB_MODE STATE DEGREE ATTACHED_SESSIONS DATAPUMP_SESSIONS
OAM BIN$wzWztSbtbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbFbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbybFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztScLbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSasbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbUbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztScBbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSa7bFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbebFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
OAM BIN$wzWztSbjbFjgRAAUT9ZhNg==$0 EXPORT TABLE NOT RUNNING 0 0 0
21 rows selected
Regards,
Deeban

Hi,
I read this is some site to stop or kill the data pump jobs. But i wants to know anyone tried this and whether this is recommendable to do or not?
we can now stop and kill the job:
SET serveroutput on
SET lines 100
DECLARE
h1 NUMBER;
BEGIN
-- Format: DBMS_DATAPUMP.ATTACH('[job_name]','[owner_name]');
h1 := DBMS_DATAPUMP.ATTACH('SYS_IMPORT_SCHEMA_01','SCHEMA_USER');
DBMS_DATAPUMP.STOP_JOB (h1,1,0);
END;
Regards,
Deeban

Infocube data loads fail with UNCAUGHT_EXCEPTION dump after BI 7.01 upgrade

Hi folks,
We're in the middle of upgrading our BW landscape from 3.5 to to 7.01. The Support pack we have in the system is SAPKW70103.
Since the upgrade any of the data loads going to infocubes are failing with the following
ABAP dump UNCAUGHT_EXCEPTION
CX_RSR_COB_PRO_NOT_FOUND.
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_RSR_COB_PRO_NOT_FOUND', was not
     caught and
    therefore caused a runtime error.
    The reason for the exception is:
    0REQUEST is not a valid characteristic for InfoProvider
Has anyone come accross this issue and if so any resolutions you adopted to fix this. Appreciate any help in this regard.
Thanks
Mujeeb

hi experts,
i have exactly the same problem.
But I can`t find a test for infoobjects in rsrv. How can I repair the infoobject 0REQUEST`?
Thx for all answers!
kind regards
Edited by: Marian Bielefeld on Jul 7, 2009 8:04 AM
Edited by: Marian Bielefeld on Jul 7, 2009 8:04 AM

Attribute change run process type failed with short dump

Hi all,
In the process chain Attribute change run process type failed with short dump. I checked the locks in SM12 but there are no locks associated. I checked in the attribute change run screen through RSA1 -> infoobject list but there are no infoobjects there. I think the ACR was completed successfully, still the process type in the PC was in red colour. What to do and let me know what happened here.
Thanks,
Jack

1. This kind of scenario is extremely rare but it happens sometimes. It might be the case that 2 attribute change runs are running at the same time.
2. Same IO is being used in Differnet PC and getting activated.
I think if this frequently occurs you need to check at the time of locking all running jobs and see whether anywhere else or simultaneously 2 ACR are running.
Please do close the thread if that answers your questions. Please help us keep the forums clean and open useful information only.
For more information search on help.sap.com and you will get lots of material.
Regards.
Den

Transport of Transformation failed with RC= 12 and job: RDDEXECL cancelled in Target sytem

Gurus,
When i am importing the workbench request from dev to qty.
I am getting error : Program terminated (job: RDDEXECL, no.: 22321300).
Transformation contains only Endroutine.
Job log:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server xxxxxx were synchronized
The internal session was terminated with the runtime error UNCAUGHT_EXCEPTION (see ST2
Job cancelled.
When i see the dump it is througing errror at the method of following class.
CL_RSO_TLOGO_PERSISTENCY-CHECK_INITIALIZED
Could you please help. Thanks in advance.
Ashok

Hi Ashok,
In QA use program "RSTRAN_ROUT_RSFO_CHECK" to check and remove any inconsistencies for the transformations. After that again transport those transformations in new TR and import in QA.
Also you have to search "Transport of Transformation failed with RC= 12 and job: RDDEXECL canceled in Target system" by Dinesh Tiwari.
Check the reply of Fun Sébastien in http://scn.sap.com/message/13795238#13795238.

ECC 6.0 EhP6 SPS08 failed with RC12 in phase ACT_UPG

Dear gurus,
We are upgrading from ECC 6.0 EHP4 SP12 to ECC 6.0 EHP6 SP8 and phase ACT_UPG has failed with RC12. When we check the dump it shows the following error:
Runtime error: DBIF_REPO_SQL_ERROR
Shorttext: SQL error "-99999" occurred when accessing program
Database error text........: "CLI0106E Connection is closed. SQLSTATE=08003"
Triggering SQL statement...: "CX_SY_OPEN_SQL_DB=============CP "
Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
Any help would be appreciated
Thanks
Diana

After pushing the message at SAP I got the following answer:
It is the problem from note 1417505. There is no guarantee that all objects where imported with the used R3trans. A rerun of phase will be unsuccessfully because error came up in DDIC_IMPORT.
A reset of the queue is only possible if SPAM/SAINT is used for importing support packages. In case of upgrade, like here, the upgrade has got to be resetted as described in upgrade guide.
After start between phase extraction and configuration the newest R3trans has got to be copied manually in /abap/exe folder.
Regards,
Julia

Package failed with run time error: " GETWA_NOT_ASSIGNED".

Hi,
One of our custom package is failing with run time error " GETWA_NOT_ASSIGNED". We are getting this error after refresh. Infact this package is working fine both in production and Dev, but in QA system it giving runtime error.
Here with I am pasting run time error details. Please see...If any one have any idea or clue or if you have faced this kind of error.
Thanks is advance.
Error Details.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "CL_UJK_CUSTOM_LOGIC===========CP" had to be
     terminated because it has
    come across a statement that unfortunately cannot be executed.
What can you do?
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can look
    at and manage termination messages, and you can also
    keep them for a long time.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 32774).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
Regards, Trine

Hi Trine,
the error is about some field you are trying to map using field-simbols, that is diferent in the other system.
Go to the code program in the st22, there you will see when the erros occurs e what field gives the error.
Best Regards,
António

Proc Chain - Delete Overlapping Requests fails with aggregates

BW Forum,
Our weekly/daily load process chain loads several full (not delta) transaction infopackages. Those infopackages are intended to replace prior full loads and are then rolled up into aggregates on the cubes.
The problem is the process chains fail to delete the overlapping requests. I manually have to remove the aggregates, remove the infopackages, then rebuild the aggregates. It seems that the delete overlapping request fails due to the aggregates or a missing index on the aggregates, but I'm not certain. The lengthy job log contains many references to the aggregate prior to it failing with the below messages.
11/06/2004 13:47:53 SQL-END: 11/06/2004 13:47:53 00:00:00                                                 DBMAN        99
11/06/2004 13:47:53     SQL-ERROR: 1,418 ORA-01418: specified index does not exist                        DBMAN        99
11/06/2004 13:47:59 ABAP/4 processor: RAISE_EXCEPTION                                                       00        671
11/06/2004 13:47:59 Job cancelled                                                                           00        518
The raise_exception is a short dump with Exception condition "OBJECT_NOT_FOUND" raised.
The termination occurred in the ABAP program "SAPLRRBA " in
"RRBA_NUMBER_GET_BW".
The main program was "RSPROCESS ".
I've looked for OSS notes. I've tried to find a process to delete aggregates prior to loading/deletion of overlapping requests. In the end, I've had to manually intervene each time we execute the process chain, so I've got to resolve the issue.
Do others have this problem? Are the aggregates supposed to be deleted prior to loading full packages which will require deletion of overlapping requests? I presume not since there doesn't seem to be a process for this. Am I missing something?
We're using BW 3.3 SP 15 on Oracle 9.2.0.3.
Thanks for your time and consideration!
Doug Maltby

Are the aggregates compressed after the rollup? If you compress the aggregate completely, the Request you are trying to delete is no longer identifiable once it is in the compressed E fact table (since it throws away the Request ID).
So you need to change the aggregate so that it the most recent Requests remain in the uncompressed the F fact table. Then the Request deletion should work.
I thought what was supposed to happen if the aggregate was fully compressed and then you wanted to delete a Request, the system would recognize that the Request was unavailable due to compression and that it would automatically refill the aggregate - but I'm not sure where I read that. Maybe it was a Note, maybe that doesn't happen in a Process Chain, just not sure.
The better solution when you regularly backout a Request is just not the fully compress the aggregate, letting it follow the compression of the base cube, which I'm assuming you have set to compress Requests older than XX days.

Background jobs failing with ABAP/4 processor: RFC_CONVERSION_FIELD

Hi Guru's,
Below are the backgroud jobs failing with runtime Error " ABAP/4 processor: RFC_CONVERSION_FIELD" in solution manager system (solution manager 3.0,SR2). Not sure why all these jobs failing with this dump on of sudden. i haven't made any changes to the system in the recent past.
BTC_CMS_COLLECTOR
SAP_APPLICATION_STAT_COLLECTOR
SESS_Y000001806_COLL_TRANS
ABAp Dump says that
Conversion error between two character sets
What happened?
Conversion error "ab_rfccon" from character set 4103 to character set 1100.
When executing a remote function call a conversion error occurred. This
occurred when receiving or sending the data. The conversion error can
only appear, when the data is transferred from a Unicode system to a
non-Unicode system.
Could some one please share some information if any one experienced the issue. Please note that all of our ECC systems are uni-code systems.
Thanks & Regards,
Vinod.

Hi Vinod
Just try to understand the purpose of these jobs and may be these Notes will help you
Note 814707 - Troubleshooting for RFC connections Unicode/non-Unicode
Note 647495 - RFC for Unicode ./. non-Unicode Connections
Note 1361970 - Conversion problems during RFC communication

SAP_COLLECTOR_FOR_PERFMONITOR failing with dump

Similar Messages

Maybe you are looking for