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.

Similar Messages

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

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.

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

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

Urgent: Data Loading error(Load failed with Short Dump) caller 70 missing

Hi please go through the error occured.
<b>"Request is still running.
Diagnosis:
No error could be found. The current process has probably not finished yet.
System Response:
The ALE Inbox of the SAP BW is identical to ALE Outbox of the source System and /or the maximum wait time for this request has not yet run out and/or the batch job in the cource system has not ended.
current status
in the source sytem."</b>
Update mode: Full, processing Online.
I think we processed the infopackage in the online. if we process it in the back ground then we won't face any problem. Singal turns to Red.
Please guide us. we need to load it immidiately.
Thanks in advance.
Regards,
Nagesh.
Message was edited by: Nagesh Ganisetti
Message was edited by: Nagesh Ganisetti

Hi Friends,
   at last the load has Terminated with Short Dump. Can any one guide me how can i reslove this. we could see the data in PSA.
i'm sending the part of the short dump.
Too many parameters specified with PERFORM.
What happened?
In a subroutine call, there were more parameters than in the routinedefinition.
Error in ABAP application program.
The current ABAP program "GP3KGSUXARXPB2F9YCR4B3MFPT6 " had to be terminated because one of statements could not be executed.
This is probably due to an error in the ABAP program.
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.
is especially useful if you want to keep a particular message.
Error analysis
A PERFORM was used to call the routine "VALUE_TO_SID_CONVERT_DB" of the program
"GP3KGSUXARXPB2F9YCR4B3MFPT6 ".
This routine contains exactly 7 formal parameters, but the current
call contains 8 actual parameters.
parameters.
How to correct the error
Correct the PERFORM call. You can find out where the call occurs in the section "Active calls / events".
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:
Please guide me.
Regards,
Nagesh.
Message was edited by: Nagesh Ganisetti

Delegate Admin install fails with core dump

I have been attempting to install the iPlanet Delegated Adminstrator with the Messaging Server 5.2 release. I am using Directory Server 5.1 service pack 1 on Solaris 8.
Installation of DS 5.1 goes fine.
Installation of MS 5.2 goes fine.
Installation of the web server 6.0 wtih sp4 goes fine
Every time I attempt to install DA, I get a "Segmentation Fault - core dumped" and absolutely no other information.

Since this is not a normal thing, I only have two suggestions left:
1. Download the latest version if iDA:
http://wwws.sun.com/software/download/products/3ed69a6c.html
2. Download and apply p1 for iMS (now a year old, but the latest publically available version):
http://wwws.sun.com/software/download/products/3e3afb91.html
3. Install the latest Solaris patch cluster.
If the above fail, then:
4. Open up a tech support ticket.

Bex Report with and without BIA . . Fails with a dump EXPORT_TOO_MUCH_DATA

Hi Folks,
We have a report thats has been running well in production for more about 18 months. This month it did not complete execution.
We did implement BIA couple of 4 months back and the run times have drastically reduced after the BIA. Now this query execution results in a Dump with and without BIA. FYI the underlying cube has 195,876,020 records only.
Name of Runtime error: EXPORT_TOO_MUCH_DATA
Short text:     Too much data for export.
What happened?     Runtime error
    The current ABAP program "CL_RSR_CACHE_DO_SPID==========CP" had to be
     terminated because one     of the statements could not be executed at runtime.
Error analysis: The dataset stored under an EXPORT/IMPORT ID is restricted
by
1. The maximum possible size of 2 GB
2. The length of a data record and the capacity of the sequence counter. This error occurs only if the capacity of the
sequence counter does not go beyond 255.
Source Code Extract:
    1 METHOD if_rsr_cache_data_object~get_xstring.
    2
    3   FIELD-SYMBOLS:
    4     <l_xstring>            TYPE xstring,
    5     <l_sp>                 TYPE ANY,
    6     <l_spinfo>             TYPE ANY.
    7
    8   CREATE DATA r_r_xstring.
    9   ASSIGN r_r_xstring->* TO <l_xstring>.
   10   ASSIGN n_s_spid-r_sp->*     TO <l_sp>.
   11   ASSIGN n_s_spid-r_spinfo->* TO <l_spinfo>.
   12
   13 *... Sp has to be the first component
>>>>>   EXPORT sp = <l_sp> spinfo = <l_spinfo>
   15          TO DATA BUFFER <l_xstring> COMPRESSION ON.
   16
   17 ENDMETHOD.
Referred to the below note 0001232573
which says to have 'RSRCACHE_ITAB_COMPR' parameter using report SAP_RSADMIN_MAINTAIN
Note say the below (It might be a little tricky, to find an appropriate value for 'RSRCACHE_ITAB_COMPR' as it heavily depends on the query-specific data structures that are stored in the cache. The general recommendation would be to start with a value of about 5000. Test this with a query, that dumped previously. In case the dump persists reoccurs, reduce the value of the parameter significantly. Otherwise, if no dump occurs but you face noticeably longer runtimes, increase the parameter.)
We are trying not able to get to the right parameter value. (changed it from 5000, 4000, 3000, & 1000) without much help. Did any of you had to change this parameter. How low or High can this parameter be changed?
We would like to understand if changing any other parameters would help in RSADMIN table would help?
Any thoughts from the experts would be appreciated
Thanks,
FHF

Hi,
Are you running the report for all the selections(all the data )?
execute the report with data selection and check?
Is the data in the Ic - compressed?
Regards
KP

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

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

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.

Determination dumps with assertion_failed error

Hi gurus,
I am enhancing a TM feature and my determination dumps with assertion_failed error. I check ST22 and the dump lies in method /BOBF/IF_FRW_CONFIGURATION~GET_CONTENT_KEY_MAPPING.
Below is my determination to set the read-only flag.
CREATE OBJECT lf_control
     EXPORTING
       IS_CONTEXT = IS_CTX    " Context Information for Determinations
       IO_MODIFY = IO_MODIFY.   " Interface to Change Data
lf_control->SET_ATTRIBUTE_READ_ONLY(
         EXPORTING
           IV_ATTRIBUTE_NAME = /SCMTMS/IF_TCC_TRNSP_CHRG_C=>SC_NODE_ATTRIBUTE-ITEMCHARGEELEMENT-RATE_AMOUNT
           IV_KEY                       = ls_chrg_el-key
           IV_VALUE                   = ABAP_TRUE
Do you have any clues on this?
Thanks,
Clark

Hi Clark,
Few questions on the above code.
Is this an standard determination you tried to enhance or a Custom determination you have created?
The work around you can use is..to create a custom determination using the transaction bopf_ewb.
Enhance that particular node & create a a property determination for that node in which the field which has to be done read-only.
The above same code can be implemented to make it read-only.Instead of enhancing the standard, I would suggest you try this method to make the field read-only.
Note: Please ensure that you that the determination is written for that particular node in which the field is present.
Hope this helps you.
Regards,
Sanket.

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

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.

BDLS failing with ASSERTION_FAILED dump

Similar Messages

Maybe you are looking for