Short dump OBJECTS_OBJREF_NOT_ASSIGNED when activating infoobjects

Hi Experts,
We are getting a short dump when activating bussiness content infoobject which contain attributes, for e.g. 0COSTCENTER.
We are not getting the same dump when activating infoobjects whith out attributes.
We found a note 1019055 that recomends install sp13 or install six or seven notes for an emergency issue.
The problem is that if we install sp13 we will get out of stack.
What is your recomendation in this case? we are afraid that the problems will continue until we don't implement the sp13.
Thanks!

use t-code SNOTE to implement the OSS note you mentioned ,if it doesnt work you can always revert back to old status by doing Reset.
Hope it Helps
Chetan
@CP..

Similar Messages

Short dump error when using count(*)

Hi Experts
I am getting a short dump error when selecting the records >= current date - 30 see the coding and comment please correct the coding I want to know the ztable records it is important for command interface.
I have 1402345 records available after deleting the records but as the memory is not enough it is giving short dump error
select count(*) from ZINT_TABLE
select count(*) from ZINT_MSGS
 select * from zint_data
 nto table izint_d2 . "PACKAGE SIZE 20000
 where STATUS = 'OK' AND CREATED_ON >= w_date1. " VALUE
endselect.**
report z_eslp_command_records.
data: cnt type i.
data: cnt2 type i.
data: cnt3 type i.
data: cnt4 type i.
DATA:
 w_date1 like sy-datum .
DATA:
 w_date2 like sy-datum.
data: izint_msgs type table of zint_msgs.
data: izint_data type table of zint_data.
data: izint_m2 type table of zint_msgs.
data: izint_d2 type table of zint_data.
INITIALIZATION.
w_date1 = sy-datum - 30.
w_date2 = sy-datum - 30.
select * from zint_data
 into table izint_data PACKAGE SIZE 3000
 where STATUS = 'OK' AND CREATED_ON <= w_date1. " ZERO
endselect.
select * from zint_msgs
 into table izint_msgs PACKAGE SIZE 3000
 where CREATED_ON <= w_date2. " ZERO
endselect.
select * from zint_data
 into table izint_d2 PACKAGE SIZE 20000
 where STATUS = 'OK' AND CREATED_ON >= w_date1. " VALUE
endselect.
select * from zint_msgs
 into table izint_m2 PACKAGE SIZE 20000
where CREATED_ON >= w_date2. " VALUE
endselect.
select * from zint_data
 into table izint_data2
where STATUS = 'OK' AND CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
select * from zint_msgs
 into table izint_msgs2
where CREATED_ON >= CONVERT(CHAR(8), GETDATE() - 30, 112)).
ENDSELECT.
sort izint_data by created_on ascending.
sort izint_msgs by created_on ascending.
sort izint_d2 by created_on ascending.
sort izint_m2 by created_on ascending.
describe table izint_data lines cnt.
describe table izint_msgs lines cnt2.
describe table izint_d2 lines cnt3.
describe table izint_m2 lines cnt4.
write:/ ' Note: THE RECORDS COUNTED SHOULD SHOW ZERO ELSE THE SCRIPT FAILED TO RUN' color 3.
skip.
write:/ '1. Records counted in ZINT_DATA <=current date - 30 :' color 2, cnt color 4.
write:/ '2. Records available in ZINT_DATA >=current date - 30 'color 4, cnt3 color 4 .
skip.
write:/ '2. Records counted in ZINT_MSGS <=current date - 30 :' color 2 , cnt2 color 4.
write:/ '4. Records available in ZINT_MSGS >=current date - 30 'color 4 , cnt4 color 4 .
TOP-OF-PAGE.
WRITE:/55(60) ' WAGNERS INVESTMENT LIMITED '.
WRITE:/50(40) ' Command Interface Data' CENTERED .
WRITE:/50(40) '----
' CENTERED .
FORMAT INTENSIFIED ON.
SKIP.
"FORMAT COLOR COL_HEADING.
ULINE.
FORMAT COLOR 1.
END-OF-PAGE.

Answer

Short dump error when extracting delta records from R/3

I am working on BW 3.5 and I am facing some short dump error when extracting delta records from the r/3 to BW.
Below is the error message
Kindly do the needful ASAP.
Job started
Step 001 started (program SBIE0001, variant &0000000024277, user ID BWREMOTE)
Asynchronous transmission of info IDoc 2 in task 0001 (0 parallel tasks)
DATASOURCE = 0ISCM_PAYMENT_01
         Current Values for Selected Profile Parameters               *
abap/heap_area_nondia......... 2000000000                              *
abap/heap_area_total.......... 2000000000                              *
abap/heaplimit................ 40000000                                *
zcsa/installed_languages...... DE                                      *
zcsa/system_language.......... E                                       *
ztta/max_memreq_MB............ 2047                                    *
ztta/roll_area................ 6500000                                 *
ztta/roll_extension........... 2000000000                              *
2,454 LUWs confirmed and 2,454 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DAT
ABAP/4 processor: MESSAGE_TYPE_X
Job cancelled

Hi,
I look at the transaction ST22 to see which type of error has given you. Take a look at the notes to correct the error.
Another option is to look at OSS notes, because the error is giving you a standard extractor.
Greetings,

Short dump (DBIF_RSQL_INVALID_RSQL) during activating ODS

Hello Experts,
I found short dump during activating ODS.
The error message in short dump:
Runtime Error: DBIF_RSQL_INVALID_RSQL
Except.: CX_SY_OPEN_SQL_DB
The termination occurred in the ABAP program "GP7WIVS2MDWGSTMN3ICFDKNAH65" in "ACTIVATE_SIDS".
The main program was "RSODSACT1 ".
I add one InfoObject in the ODS. After activating related objects, I loaded data into the data target.
Data seemed to be loaded correctly, but couldn't be activated.
Any suggestion on this?
-WJ-

Hi,
Please chekc the following SAP Notes you will find solution
Note 908599 - Runtime error SAPSQL_INVALID_FIELDNAME during activation
Note 612995 - P13:ODS:Data activation in bckgrnd always ends 'successfully
Note 1175860 - P19: DSO: SDL: Automatic update after activation
Note 1113603 - P17:DSO:Postprocessing ODS - activating and updating
Note 378447 - Correction: hierarchies do not become green
Note 1272738 - P21:DSO: Activation and automatic updating
Note 794584 - P26:Timestamp field empty in RS2NDPROCPROT after ODSACTIVATE
Note 800086 - P26: ODS activation: Status field in table RS2NDPROCPROT
Note 856292 - P28: Automatic functions: No lock obtained for ERSICENQ
Thanks
Reddy

Short dump error when extracting from one of the datasource in R/3 to BW

When extracting from one of the datasource I am getting the short dump. below is the source code of the same.
Source code extract
Get boundaries of next TID block
L_FROM_INDEX = L_TO_INDEX + 1.
IF L_FROM_INDEX GT NFILL. EXIT. ENDIF.
L_TO_INDEX   = L_TO_INDEX + L_BLOCK_SIZE.
IF L_TO_INDEX GT NFILL.
L_TO_INDEX = NFILL.
L_BLOCK_SIZE = L_TO_INDEX - L_FROM_INDEX + 1.
ENDIF.
Create hashed index on TID of TID table
CLEAR L_TH_TID_IDX.
LOOP AT TIDTAB FROM L_FROM_INDEX TO L_TO_INDEX.
L_S_TID_IDX-TIDIX = SY-TABIX.
L_S_TID_IDX-TID   = TIDTAB-TID.
COLLECT L_S_TID_IDX INTO L_TH_TID_IDX.
ENDLOOP.
Select TID block from STATE table
SELECT * INTO TABLE L_T_STATE
       FROM ARFCSSTATE FOR ALL ENTRIES IN L_TH_TID_IDX
       WHERE ARFCIPID   EQ L_TH_TID_IDX-TID-ARFCIPID
         AND ARFCPID    EQ L_TH_TID_IDX-TID-ARFCPID
         AND ARFCTIME   EQ L_TH_TID_IDX-TID-ARFCTIME
         AND ARFCTIDCNT EQ L_TH_TID_IDX-TID-ARFCTIDCNT
       ORDER BY PRIMARY KEY.
Consistence check
DESCRIBE TABLE L_T_STATE LINES L_LINES.
IF L_LINES NE L_BLOCK_SIZE OR
   L_LINES EQ 0.
MESSAGE X097(SY).
ENDIF.
PERFORM DELETE_BATCH_JOB
        USING    L_T_STATE
        CHANGING L_S_TID1.
Update LUW-Status und Zeit
CLEAR L_T_STATE_IDX.
CLEAR L_TH_TID2_IDX.
CLEAR L_T_TID.
LOOP AT L_T_STATE INTO L_S_STATE.
L_S_STATE_IDX-TABIX = SY-TABIX.

Hi Pavan,
                 This is a table space error.
Regards,
rahul

Short Dump Error when we check the Data Source in RSA3

Hi. Experts.
                   We are using Data Source 2Lis_13_VDITM and when we try to check in RSA3
for recorts it is going short dump. I am just providing the error information.
              An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
not caught in procedure "MCEX_BW_LO_API" "(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:
When importing the object "MC13VD0ITM_TAB", the component no. 96 in the dataset has a different type from the corresponding component of the target object in the program "SAPLMCEX".
                    The data type is "N" in the dataset, but "X" in the program.
        Since I don't have much knowledge in ABAP, Please help me out regarding this issue. Suggest me possible solution and let me know if you need any further information.

Hi,
Try adding a TRY CATCH block in the extractor function module to catch the exception.
For the type mismatch you will have to make sure the variables are of same type or they can be type converted.
Use the debug mode of RSA3 to find what data is being exchanged.
You will need to change your extractor to avoid the dump.. or ensure that the value being passed to that object is correctly being passed(correct format)
Cheers
Kiran

Short dump (CALL_FUNCTION_FORMAT_NOT_SUP) when testing RFC connection

Hello!
I'm trying to test a RFC connection through SM59, but I'm getting the following short dump: CALL_FUNCTION_FORMAT_NOT_SUP (RFC data format not supported).
This RFC will connect to Biztalk, and this dump started occurring when Biztalk changed their codepage from 1100 to 4102.
On my SAP system the codepage is set to 1100.
There is no option to set the system as Unicode or non-Unicode on SM59, since I don't have the "Special Options" tab (My release is 4.6C).
How can I make this connection even with the different codepages?
Thanks in advance!

Hello Pedro
This is the PI forum, which is for PI technical issues. This post is not related to PI.
P.S. Please also familiarise yourself with the forum Rules of Engagement - https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement. Please do not Cross post.
Regards
Mark Smyth
XI/PI Moderator

Short dump OBJECTS_OBJREF_NOT_ASSIGNED

Hi All,
I have a BSP application where the Application class has several attributes TYPE REF TO other classes. In production we are getting hundreds of OBJECTS_OBJREF_NOT_ASSIGNED short dumps a day. The references to these TYPE REF TO attributes on the application class are being lost.
Initially we were not able to reproduce the problem in development, however I have found that if you stay on a page for 10-15 minutes then navigate to another page the references are lost and the short dump occurs. I can see in the short dump that the reference to the Application object still exists but not to the TYPE REF TO attributes which are now all ???. If you navigate without waiting everything is fine.
I thought it might be the garbage collector cleaning them up, however at the time the page is displayed all the references are valid. Why do they disappear? Is there a time-out parameter somewhere?
Thanks in advance.
Sandra Lawrence

Thanks for all your replies. I realise now that I am getting a session time-out. As I still had some data remaining I originally didn't think this was my problem.
I am now in the process of implementing Thomas Jung's timeout solution from his blog BSP Developer's Journal: Part XV - Stateful BSP and Timeouts.
Thanks again for pointing me in the right direction.

Error when generating master data routines when activating infoobject

Hello Gurus,
I had an issue with one of my info object.
I Created the one Custom InfoObject with Just 5 Char without any masterdata and used that in many cubes. we promoted the objects and cube to test and production systems. just couple of days back we can see the InfoObject went to inactive status even though the version is active(not sure how it happend). This is only happens in our test system and production is working fine. when i try to activate the InfoObject again the test system it gives me an error
Characteristic XXXXX: Error when generating master data routines. Tried to correct in RSD5 etc. Checked in RSRV everything is fine. Tried to re-promote the object from Development system. The transport also failed with the same error even though it is in unconditional mode.
Can you please suggest me what are the options.
i cannot delete the object as it is used in many cubes which is having data.
Appreciate your quick response.
Thanks,
Bhaskara Rao.

If your Prod is working fine, it should work in test too.
Did it ever worked in test after transport?
Is it possible some one tried to change something in test? If yes, you will get error when you will try to re-transport it as new transport can't find the previous structure.
You may try to activate the IO using FM RSDG_IOBJ_ACTIVATE
Edited by: ashok saha on Mar 6, 2008 8:05 PM

Error when activating infoobject 0MAT_PLANT

Dear experts,
I switched off the flag for time dependency of a navigational attribute of 0MAT_PLANT. When trying to active 0MAT_PLANT again I am receiving the error R7286 (Error in activating the InfoObjects). When running RSRV I am only getting red traffic lights but when trying to repair the system is only telling me to activate the infoobject first. The infoobject was locked for conversion, I removed the lock and flagged the time dependency again, hoping that the object could be reactivated again but unfortunately this is not the case. Can someone help me with some tips on how to approach this?
Many thanks in advance. Best regards, Jeroen

Thanks Dinesh. Not sure if it is our 30B version but I don't get very useful information when checking the long text. I also checked the complete log but it is only mentioning to analyze /BI0/QMAT_UNIT with SE11. When doing this I get an error: /BI0/QMAT_PLANT: Inconsistency DD <-> DB (check table with analysis tool)
Any other tips?

Short dump TSV_TNEW_PAGE_ALLOC_FAILED when import SAPKB70016

Hi all,
I´m trying to import the support package SAPKB70016 im my QAS system and I got an error. The import stop on phase XPRA_EXECUTION and I saw at the tcode sm37 that there is a job running with the name RDDEXECL. This job is canceled with the dump TSV_TNEW_PAGE_ALLOC_FAILED. I already changed some parameters and also I applied some notes but I can´t solve this issue.
Parameter changed                Before                 After
ztta/roll_area                        30000000          100000000
ztta/roll_extension               4000317440        8000000000
abap/heap_area_dia        2000683008        4000683008
abap/heap_area_nondia      2000683008        4000683008
abap/heap_area_total       2000683008        4000683008
em/initial_size_MB                             392                    1024
abap/shared_objects_size_MB      20                     150
es/implementation                           map                     std
JOB LOG:
Job started
Step 001 started (program RDDEXECL, variant , user ID DDIC)
All DB buffers of application server FQAS were synchronized
ABAP/4 processor: TSV_TNEW_PAGE_ALLOC_FAILED
Job cancelled
ST22 LOG:
Memory location: "Session memory"
Row width: 510
Number of rows: 0
Allocated rows: 21
Newly requested rows: 288 (in 9 blocks)
Last error logged in SAP kernel
Component............ "EM"
Place................ "SAP-Server FQAS_QAS_01 o
Version.............. 37
Error code........... 7
Error text........... "Warning: EM-Memory exhau
Description.......... " "
System call.......... " "
Module............... "emxx.c"
Line................. 1897
The error reported by the operating system is:
Error number..... " "
Error text....... " "
The amount of storage space (in bytes) filled at termination time was:
Roll area...................... 99661936
Extended memory (EM)........... 8287273056
Assigned memory (HEAP)......... 1376776176
Short area..................... " "
Paging area.................... 49152
Maximum address space.......... 18446743890583112895
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:
"TSV_TNEW_PAGE_ALLOC_FAILED" " "
"CL_ENH_UTILITIES_XSTRING======CP" or "CL_ENH_UTILITIES_XSTRING======CM008"
"GET_DATA"
Now, I don´t know what I can do to solve this problem.
Can you help me?
Thanks

Hi all,
Gagan, I already changed my parameters according to the above post. I increased this parameters until maximum allowed but the dump still persists.
Bhuban
In this server I have 16GB RAM and 600GB HD.
             total       used       free     shared    buffers     cached
Mem:      16414340    4973040   11441300          0     454436    3572592
-/+ buffers/cache:     946012   15468328
Swap:     20479968          0   20479968
Size Used     Avail Use% Mounted on
441G 201G   218G 48% /oracle
20G     6.5G    12G   36% /sapmnt
25G     21G    2.7G   89% /usr/sap/trans
25G    8.8G   15G    39% /usr
20G    14G    5.1G    73% /
Anil, I already stop my appl and my db, I rebooted my OS too and after i tried again, no success.
What else can i do?
Thanks for all.

Getting Short Dump while DSO Activation

Hi,
I am getting Error while DSO Activation, I checked in ST22 Error is (SYSTEM_CORE_DUMPED), Please suggest.
The kernel is latest version.
Also we had implemented a couple of SAP Notes while we searched on the SDN and service market place. But still no luck.
Category Internal Kernel Error
Runtime Errors SYSTEM_CORE_DUMPED
Date and Time 09.04.2014 16:14:13
Short Text
Process terminated by signal 10.
What happened?
Error in the SAP kernel
The current ABAP program
"CL_RSODSO_DATASTORE=====
terminated because the ABAP
processor detected a system error.
Thanks,
Sameer

Hi,
Yes this happens for a particular DSO only - 0FIAR_O03(DSO)
Also the kernel is the latest one.
I am from Basis. I have checked all the possibilities and have raised OSS message as well.
Thanks,
Sameer

A short dump occurs when accessing SAP BI 7.0 using GUI 620

hi,
i'm getting this error while executing..DTP.
solve this .....

Hi,
BI 7.0 will not work with SAP GUI 6.20.
Take a look at this SAP note.
Maintenance strategy / deadlines 'SAP GUI'
SAP Note Number: [147519|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes/sdn_oss_bc_fes/~form/handler%7b5f4150503d3030323030363832353030303030303031393732265f4556454e543d444953504c4159265f4e4e554d3d313437353139%7d]
Compatibility - 6.20
SAP GUI for Windows 6.20 is compatible with products based on SAP Web Application Server 6.40/7.00/7.01/7.02 and all earlier releases of SAP Software which are still supported by SAP (this includes extended maintenance).
Exceptions to this rule are
BI 7.0: Requires new frontend components shipped only together with SAP GUI for Windows 6.40 as of compilation 4. For BI 7.0 you definitely need at least this compilation CD. For further information on this please check the master guide for SAP NetWeaver 2004s components and documentation center at
http://service.sap.com/~sapidb/011000358700004970342005E/051024Instguides.htm
http://help.sap.com/saphelp_nw04s/helpdata/en/b2/e50138fede083de10000009b38f8cf/frameset.htm
SCM 5.0: Requires a new frontend component which is integrated into SAP GUI for Windows 6.40 (also see note 889989).
SAP GUI for Windows 6.20 is not compatible with SAP Systems based on SAP Web Application Server 7.10 and higher.
Additional:
Troubleshoot the SAP NetWeaver 2004s BI Frontend Installation
and
Frontend requirements - page 11
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10564d5c-cf00-2a10-7b87-c94e38267742
and
Re: GUI 640
Regards
Andreas

DBIF_REPO_SQL_ERROR short dumps while activating data in ODS

Hi All,
We are using BW3.5 with Oracle 9.2 on AIX 5.3 box, from the past few days we are getting DBIF_REPO_SQL_ERROR short dumps frequently while activating data in ODS.
Runtime Error          DBIF_REPO_SQL_ERROR
Date and Time          08.01.2008 13:01:08
     1. A printout of the problem description (short dump)
        To obtain this, select in the current display "System->List->
        Save->Local File (unconverted)".
     2. A suitable printout of the system log
        To obtain this, call the system log through transaction SM21.
        Limit the time interval to 10 minutes before and 5 minutes
        after the short dump. In the display, then select the function
        "System->List->Save->Local File (unconverted)".
     3. If the programs are your own programs or modified SAP programs,
        supply the source code.
        To do this, select the Editor function "Further Utilities->
        Upload/Download->Download".
     4. Details regarding the conditions under which the error occurred
        or which actions and input led to the error.
     Internal call code.........: "[REPO/*/43/LOAD/CX_SY_OPEN_SQL_DB=============CP
     Please check the entries in the system log (Transaction SM21).
     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:
     "DBIF_REPO_SQL_ERROR" C
     "SAPLRSSM_PROCESS" or "LRSSM_PROCESSF04"
     "CHECK_IF_ANALYZE_IS_NESSESSARY"
System environment
    SAP Release.............. "640"
    Application server....... "psapdb"
    Network address.......... "158.58.65.11"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00CD615C4C00"
    Character length......... 16 Bits
    Pointer length........... 64 Bits
    Work process number...... 22
    Short dump setting....... "full"
    Database server.......... "psapdb"
    Database type............ "ORACLE"
    Database name............ "BWP"
    Database owner........... "SAPBWP"
    Character set............ "C"
    SAP kernel............... "640"
    Created on............... "Oct 29 2006 20:49:57"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
    Patch level.............. "155"
    Patch text............... " "
    Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
    SAP database version..... "640"
Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
Roll..................... 16192
EM....................... 16759424
Heap..................... 0
Page..................... 24576
MM Used.................. 6604384
MM Free.................. 1772536
SAP Release.............. "640"
User and Transaction
    Client.............. 200
    User................ "R3REMOTE"
    Language key........ "E"
    Transaction......... " "
    Program............. "SAPLRSSM_PROCESS"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLRSSM_PROCESS" in
     "CHECK_IF_ANALYZE_IS_NESSESSARY".
    The main program was "RSPROCESS ".
    The termination occurred in line 1143 of the source code of the (Include)
     program "LRSSM_PROCESSF04"
    of the source code of program "LRSSM_PROCESSF04" (when calling the editor
     11430).
    The program "SAPLRSSM_PROCESS" was started as a background job.
    Job name........ "BI_PROCESS_ODSACTIVAT"
    Job initiator... "RPRIYANKA"
    Job number...... 02010102
Also we have a failed job here. Here is the job log.
Job log overview for job:    BI_PROCESS_ODSACTIVAT / 02010102
Date       Time     Message text
08.01.2008 13:01:00 Job started
08.01.2008 13:01:00 Step 001 started (program RSPROCESS, variant &0000000000188, user ID R3REMOTE)
08.01.2008 13:01:02 Activation is running: Data target HBCS_O25, from 1,758 to 1,767
08.01.2008 13:01:02 Data to be activated successfully checked against archiving objects
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 ANALYZE TABLE "/BIC/AHBCS_O2540" DELETE
08.01.2008 13:01:02 STATISTICS
08.01.2008 13:01:02 SQL-END: 01/08/2008 13:01:02 00:00:00
08.01.2008 13:01:02 SQL: 01/08/2008 13:01:02 R3REMOTE
08.01.2008 13:01:02 BEGIN DBMS_STATS.GATHER_TABLE_STATS ( OWNNAME =>
08.01.2008 13:01:02 'SAPBWP', TABNAME => '"/BIC/AHBCS_O2540"',
08.01.2008 13:01:02 ESTIMATE_PERCENT => 1 , METHOD_OPT => 'FOR ALL
08.01.2008 13:01:02 INDEXED COLUMNS SIZE 75', DEGREE => 1 ,
08.01.2008 13:01:02 GRANULARITY => 'ALL', CASCADE => TRUE ); END;
08.01.2008 13:01:05 SQL-END: 01/08/2008 13:01:05 00:00:03
08.01.2008 13:01:05     SQL-ERROR: 603 ORA-00603: ORACLE server session terminated by fat al error
08.01.2008 13:01:05 System error: RSDU_ANALYZE_TABLE_ORA/ ORACLE
08.01.2008 13:01:08 ABAP/4 processor: DBIF_REPO_SQL_ERROR
08.01.2008 13:01:08 Job cancelled
Listener is working fine, Checked the RFC connections, Tried restarting the system, tried adding space to the TEMP tablespace as well as PSAPBWP, but they didn't work.
Please help.

The problem got solved as there were DB errors like ORA-01114: IO error writing block to file 256 (block # 126218).
Here the point to be notes is file 256. The number greater than 255 indicates a temp datafile. This indicates an issue with PSAPTEMP tablespace. When checked on PSAPTEMP tablespace, one of the filesystems where one temp data file sitting was full. The filesystem was 100% full. This will prevent the temp datafile to grow and shrink as and when required.
So, adding more space to the filesystem solved the problem.
Thanks to everyone who have shown interest in solving my problem.

RBDAP001 causing a short dump when submitted in a FM for IDOC processing

Hi All Gurus,
I have a situation wherein I need to automate the processing of failed INBOUND IDOCS.
So the status of failed IDOCS could be 51 or 64 or anything like that.
I tried using statement 'SUBMIT RBDAP001 with......'. in a custom FM , however I got a short dump.
When I debugged I realised that RBDAP001 pops up a screen with the final IDOC processing result which probably may be the cause of dump. Dump message is 'CNTL_ERROR'.
So is there a way how I can suppress this screen OR use any other function module to process these inbound Idocs.
Appreciate your advise on same.
Thanks and Regards
RK

Hi Rajiv,
Please use program RBDMANI2 to reprocess IDoc with status 51.
Also check program RBDINPUT for reprocessing IDoc with other statuses.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Short dump OBJECTS_OBJREF_NOT_ASSIGNED when activating infoobjects

Similar Messages

Maybe you are looking for