Runtime error in DB02 IMPORT_OBJECT_DESTROYED

Hi Guys,
When i call up Tx : DB02 and choose Space Statistics under Tablepace Tab, runtime error is occurring " IMPORT_OBJECT_DESTROYED".
The short dump mentions as :
Error analysis
Unable to import the dataset because it has an unexpected
format. It was
destroyed as a result of direct manipulation of the
IMPORT/EXPORT data by other means (for instance, explicit deletion of parts of the dataset using SQL instead of DELETE FROM DATABASE).
In this case, the records in the dataset do not appear in the
expected order, which is 0,1,2,3...
(sequence counter in field SRTF2).
The next record expected here is number 0,
but number 1 appears.
Information where termination occurred:
The termination occurred in the ABAP/4 program "RSORAT2M " in
"IMPORT_FROM_MONI_SAFE".
The main program was "RSORAT2M ".
The termination occurred in line 908
of the source code of program "RSORAT2M " (when calling the editor 9080).
The program "RSORAT2M " was started as a background job.
Any help is appreciated.
Naren

Hi,
Check the note [393658|https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=393658]
For me it seems that the historical data is not gathered. If so, please schedule the job SAP_COLLECTOR_FOR_PERFMONITOR for each hour .
Regards,
Srihari

Similar Messages

Runtime Error in SM36 IMPORT_OBJECT_DESTROYED

Hello,
When i call up Tx : SM36 and choose Standard Jobs a runtime error is occurring " IMPORT_OBJECT_DESTROYED".
The short dump mentions as :
Short text
    The IMPORT dataset has been destroyed.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSEU_COMPONENT" had to be terminated because it
    has
    come across a statement that unfortunately cannot be executed.
Error analysis
    Unable to import the dataset because it has an unexpected
    format. It was
    destroyed as a result of direct manipulation of the
    IMPORT/EXPORT data by other means (for instance, explicit deletion
    of parts of the dataset using SQL instead of DELETE FROM DATABASE).
    In this case, the records in the dataset do not appear in the
    expected order, which is 0,1,2,3...
    (sequence counter in field SRTF2).
    The next record expected here is number 1,
    but number 0 appears.
Trigger Location of Runtime Error
    Program                                 SAPLSEU_COMPONENT
    Include                                 LSEU_COMPONENTU01
    Row                                     41
    Module type                             (FUNCTION)
    Module Name                             RS_COMPONENT_VIEW
Source Code Extract
Line
SourceCde
   11
*" TABLES
   12
*"      NODETAB STRUCTURE SNODETEXT
   13
   14
   15
DATA: subrc LIKE sy-subrc.
   16
DATA: l_delete TYPE i.
   17
DATA: date LIKE sy-datum.
   18
   19
CLEAR sy-subrc.
   20
date = sy-datum.
   21
REFRESH nodetab. CLEAR nodetab.
   22
G_IGNORE_SFW_SWITCHES = IGNORE_SFW_SWITCHES.
   23
   24
if REFRESH ne SPACE.
   25
    G_REFRESH_ALL = REFRESH_ALL.
   26
endif.
   27
   28
IF object_type = 'FUNC'.
   29
    object_type = 'FUGR'.
   30
ENDIF.
   31
IF object_type = space.
   32
    object_type = 'APPL'.
   33
ENDIF.
   34
apid-langu = language.
   35
apid-type = object_type.
   36
   37
IF refresh IS INITIAL.
   38
*   get table "nodetab" of all object lists
   39
*   of the desired type "object_type":
   40
    CATCH SYSTEM-EXCEPTIONS conne_import_wrong_comp_leng = 1. "note 1553389
>>>>>
      IMPORT date nodetab FROM DATABASE dwtree(ap) ID apid
   42
        ACCEPTING PADDING.
   43
    ENDCATCH.
   44
    subrc = sy-subrc.
   45
ENDIF.
   46
   47
IF subrc NE 0 OR refresh = 'X'.
   48
    IF object_type = 'APPL' OR
   49
       object_type = 'DEVC'.
   50
      CASE object_type.
   51
        WHEN 'APPL'.
   52
          PERFORM get_components TABLES nodetab.
   53
        WHEN 'DEVC'.
   54
          PERFORM get_devc_view TABLES nodetab.
   55
      ENDCASE.
   56
      IF without_tree_setting IS INITIAL.
   57
        CALL FUNCTION 'RS_TREE_CONSTRUCT'
   58
          TABLES
   59
            nodetab = nodetab
   60
          EXCEPTIONS
I would appreciatte any help from you guys!
Thanks in advance.
Thales.

wrong forum. this is not a bw/bi issue. ask your basis team to take a look.
BR,
M

Refresh Runtime Error in TCODE DB02

Hello Experts!
Was just trying to refresh the statistics that I have for my DB Spaces in DB02, but I suddenly come up with this error. Can anyone tell me what this means and why this is suddenly happening (As I had no problems using this functionality just last week). Thanks!
ST22 Error Log:
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Exception              CX_SY_NATIVE_SQL_ERROR
       Occurred on     03/30/2009 at 11:11:51
SQL error "-727" occurred when executing EXEC SQL.
What happened?
The error occurred in the current database connection "DEFAULT".
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
An exception occurred. This exception will be dealt with in more detail
below. The exception, assigned to the class 'CX_SY_NATIVE_SQL_ERROR', was not
caught, which
led to a runtime error. The reason for this exception is:
                                                                                How to correct the error
Database error text........: "INF-727: Invalid or NULL TBLspace number given to
dbinfo(dbspace)."
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
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_DSQL2_SQL_ERROR" CX_SY_NATIVE_SQL_ERRORC
"RSINFTD1 " or "RSINFTD1 "
"START-OF-SELECTION"
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.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
SM21 Error Log:
BY2 Database error -727 at FET
BY0 > INF-727: Invalid or NULL TBLspace number given to
BY0 > dbinfo(dbspace).
R68 Perform rollback
AB0 Run-time error "DBIF_DSQL2_SQL_ERROR" occurred
AB1 > Short dump "090330 111151 gtbwspd 10002568 " generated

Hi.
I already had this issue and I solved by this way:
My issue happened in the following SQL statement:
94 EXEC SQL.
SELECT MAX(A.NEXTSIZE)
96 FROM SYSTABLES A, SYSFRAGMENTS B
97 WHERE DBINFO('DBSPACE',B.PARTN) = :TS_CHECK-DBSNAME
98 AND A.PARTNUM = 0
99 AND A.TABID = B.TABID
100 INTO :MAXEXT
101 ENDEXEC.
1) Please run the following sql query:
select fragtype, tabid, partn from sysfragments where partn = 0
2) Figure out which table it is:
select tabname from systables where tabid =<tabid>
3) Check the indexes of that table with oncheck -cI.
4) If you found indexes DISABLED, then you should enable them again.
5) To solve the problem you can:
-enable dropped indexes:
set indexes,constraints for <table> enabled;
-rebuild the indexes
Afterwards this operation should be corrected.
I hope I could be helpful.
Thanks,
Walter Oliveira.

Regarding runtime error DBIF_RSQL_SQL_ERROR and exception CX_SY_OPEN_SQL_DB

Hi All,
I am loading a COPA cube from a DSO.
There are about 15million records to be loaded. every time i try loading the data, 1 or 2 Data packages gets stuck and finally it leads to a runtime error DBIF_RSQL_SQL_ERROR with exception CX_SY_OPEN_SQL_DB.
When i checked in SM21 transaction code, i got the following message
10:41:52 BTC 018 500 AMRUKV                     BY O Deadlock occurred
10:41:53 BTC 018 500 AMRUKV                     BY 4 Database error 60 at INS access to table /BIC/FCSDV
10:41:53 BTC 018 500 AMRUKV                     BY 0 > ORA-00060: deadlock detected while waiting for resource
10:41:54 BTC 018 500 AMRUKV                     AB 0 Run-time error "DBIF_RSQL_SQL_ERROR" occurred
10:41:58 BTC 018 500 AMRUKV                     AB 1 > Short dump "080818 104154 s0173bel PB100 " generated
10:41:58 BTC 018 500 AMRUKV                     D0 1 Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20080818104154s0173bel_PB1_00 AMRUKV 500 )
In transaction code ST22 i got the following message:
Runtime Errors         DBIF_RSQL_SQL_ERROR
Exception              CX_SY_OPEN_SQL_DB
Date and Time          18.08.2008 10:41:54
Short text
     SQL error in the database when accessing a table.
What happened?
     The database system detected a deadlock and avoided it by rolling back
     your transaction.
What can you do?
     If possible (and necessary), repeat the last database transaction in the
      hope that locking the object will not result in another deadlock.
     Note which actions and input led to the error.
     For further help in handling the problem, contact your SAP administrator
     You can use the ABAP dump analysis transaction ST22 to view and manage
     termination messages, in particular for long term reference.
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 "WRITE_ICFACT" "(FORM)", 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:
     The database system recognized that your last operation on the database
     would have led to a deadlock.
     Therefore, your transaction was rolled back
     to avoid this.
     ORACLE always terminates any transaction that would result in deadlock.
     The other transactions involved in this potential deadlock
     are not affected by the termination.
How to correct the error
    Database error text........: "ORA-00060: deadlock detected while waiting for
     resource"
    Internal call code.........: "[RSQL/INSR//BIC/FCSDVD_C02 ]"
    Please check the entries in the system log (Transaction SM21).
    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:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "GPD3UMZD6V4YAKZAIWAOCYLV07Y" or "GPD3UMZD6V4YAKZAIWAOCYLV07Y"
    "WRITE_ICFACT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "WRITE_ICFACT" "(FORM)", or its possible occurrence must be declared in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
Can anybody suggest on what can be done?
Thanks in Advance,
Regards
A.T

Hi ,
This is a table space issue....
u will be getting a Dump...as DBIF_RSQL_SQL_ERROR check in ST22. in this DUMP if u scroll down u will find the table for which this is failing. Actually this is like some of the table related to the DSO is not having sufficient space to cary out the transaction. hence it is failing.
U can also see in DB02--> Deadlock....u will see that there is a deadlock for this table. So find the table from ST22 and ask ur basis team to increase the space for this table....
This can be solved only by increasing the space of the table...no other solution....ask help from ur basis team.
Thanks
Sandeep

Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB

Hi,
i need some guides to solve this problem.
The program works fine in client DEV. However, when it's in QAS, we encounter short dump: Runtime Error DBIF_RSQL_SQL_ERROR exception CX_SY_OPEN_SQL_DB
info from short dump:
An SQL error occurred when accessing a table.
Error analysis
An exception occurred. This exception is dealt with in more detail below
. The exception, which is assigned to the class 'CX_SY_OPEN_SQL_DB', was
neither
caught nor passed along using a RAISING clause, in the procedure
"FILL_T_DATA_TABLE" "(FORM)"
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
How to correct the error
The exception must either be prevented, caught within the procedure
"FILL_T_DATA_TABLE"
"(FORM)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Database error text........: "ORA-24371: data would not fit in current prefe
buffer"
Internal call code.........: "[RSQL/FTCH/VBUK ]"
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_RSQL_SQL_ERROR" CX_SY_OPEN_SQL_DBC
"ZSDR_SHIPPING_REPORT" or "ZSDR_SHIPPING_REPORT"
"FILL_T_DATA_TABLE"
If you cannot solve the problem yourself, please send the...
Information on where terminated
The termination occurred in the ABAP program "ZSDR_SHIPPING_REPORT" in
"FILL_T_DATA_TABLE".
The main program was "ZSDR_SHIPPING_REPORT ".
The termination occurred in line 3561 of the source code of the (Include)
program "ZSDR_SHIPPING_REPORT"
of the source code of program "ZSDR_SHIPPING_REPORT" (when calling the editor
35610).
Processing was terminated because the exception "CX_SY_OPEN_SQL_DB" occurred in
the
procedure "FILL_T_DATA_TABLE" "(FORM)" but was not handled locally, not
declared in the
RAISING clause of the procedure.
The procedure is in the program "ZSDR_SHIPPING_REPORT ". Its source code starts
in line 3468
of the (Include) program "ZSDR_SHIPPING_REPORT ".
source code:
035490
035500   *get all open sales orders (those that are deemed open at the Sales
035510   *Order "Header" level)
035520     clear open_orders.
035530     refresh open_orders.
035540     select * into corresponding fields of table open_orders
035550       from vbuk
035560       where ( vbtyp = 'C' or vbtyp = 'I' )
035570         and ( gbstk = 'A' or gbstk = 'B' ).
035580
035590   *get all open deliveries(some sales orders may be closed yet the
035600   *associated Delivery is not yet PGI'd)
     >     clear open_deliveries.
035620     refresh open_deliveries.
035630     select * into corresponding fields of table open_deliveries
035640       from vbuk
035650       where vbtyp = 'J'
035660         and ( wbstk = 'A' or wbstk = 'B' ).
035670
035680   *get sales orders associated with the Open deliveries
Please advice.
Thanks.

Thanks for the response.
Hi Renga,
The error happens in second selection.
this is the souce code:
data: begin of open_orders occurs 0,
        vbeln like vbuk-vbeln,
        gbstk like vbuk-gbstk,
        vbtyp like vbuk-vbtyp,
      end of open_orders.
data: begin of open_deliveries occurs 0,
        vbeln like vbuk-vbeln,
        wbstk like vbuk-wbstk,
        vbtyp like vbuk-vbtyp,
      end of open_deliveries.
*get all open sales orders (those that are deemed open at the Sales
*Order "Header" level)
clear open_orders.
refresh open_orders.
select * into corresponding fields of table open_orders
    from vbuk
    where ( vbtyp = 'C' or vbtyp = 'I' )
      and ( gbstk = 'A' or gbstk = 'B' ).
*get all open deliveries(some sales orders may be closed yet the
*associated Delivery is not yet PGI'd)
clear open_deliveries.
refresh open_deliveries.
select * into corresponding fields of table open_deliveries
    from vbuk
    where vbtyp = 'J'
      and ( wbstk = 'A' or wbstk = 'B' ).
Hi Prabhu,
how to identify the problem in DB02?
Please advice.
Thanks.
regards.

BAPI Runtime Error DBIF_RSQL_INVALID_REQUEST with module "KONV_BEARBEITEN"

Hi Experts
I am trying to create a sales order using BAPI FM BAPI_SALESORDER_CREATEFROMDAT1. After executing the program it shows in output screen that the sales order created and also displays the newly created sales order number. But when I want to check the order from VA03 it shows Express document "Update was terminated" received by author AAA, where AAA is login name.
I also analysis the sort dump for which the update process was terminated. I give the error details
Runtime Errors         DBIF_RSQL_INVALID_REQUES
Error analysis
    An invalid request was made to the SAP database interface in a statement
     in which the table "KONV " was accessed.
Below are the module name and report from where the error is coming.
Function Module name RV_SALES_DOCUMENT_ADD
Program Name SAPLV45U
Include LV45UF0K
Row 26
Source code from Rruntime Error
Line SourceCde
1 *****************************************************************
    2 * Unterroutinen RV-Auftragsabwicklung alphabetisch sortiert:
    3 * ----------------------------------------------------------
    4 * Buchstabe K:
    5 *
    6 *****************************************************************
    7
    8 *----------------------------------------------------------------
    9 *       FORM KONV_BEARBEITEN
   10 *----------------------------------------------------------------
   11 FORM KONV_BEARBEITEN.
   12
   13   CHECK: FKONV_GEAENDERT NE SPACE OR
   14          VORGANG = CHARH.
   15
   16   IF VORGANG NE 'H'.
   17     DELETE FROM KONV WHERE KNUMV = VBAK-KNUMV.
   18 ENHANCEMENT-POINT KONV_BEARBEITEN_10 SPOTS ES_SAPLV45U.
   19   ENDIF.
   20
   21   LOOP AT FXKOMV.
   22     FXKOMV-MANDT = VBAK-MANDT.
   23     FXKOMV-KNUMV = VBAK-KNUMV.
   24     MODIFY FXKOMV.
   25   ENDLOOP.
>>>>>   INSERT KONV FROM TABLE FXKOMV.
   27   IF SY-SUBRC NE 0.
   28     MESSAGE A100 WITH
   29   ENDIF.
   30
   31 ENHANCEMENT-POINT KONV
   32 ENDFORM.
   33 *eject
Below is my source code.
*& Report Z_BAPI_SALESORDER
REPORT z_bapi_salesorder.
* Sales document type
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
PARAMETERS: p_auart TYPE auart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Sales organization
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Distribution channel
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Division.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
PARAMETERS: p_spart TYPE spart OBLIGATORY.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Sold-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
PARAMETERS: p_sold TYPE kunnr OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Ship-to
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
PARAMETERS: p_ship TYPE kunnr.
SELECTION-SCREEN END OF LINE.
SKIP 1.
* Material
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Quantity.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
PARAMETERS: p_menge TYPE dzmengc OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Plant
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
PARAMETERS: p_plant TYPE werks_d OBLIGATORY.
SELECTION-SCREEN END OF LINE.
* Data declarations.
DATA: v_vbeln            LIKE vbak-vbeln.
DATA: header             LIKE bapisdhead.
DATA: headerx            LIKE bapisdhead1x.
DATA: item               LIKE bapiitemin OCCURS 0 WITH HEADER LINE.
DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
DATA: partner            LIKE bapipartnr OCCURS 0 WITH HEADER LINE.
DATA: return             LIKE bapireturn1    OCCURS 0 WITH HEADER LINE.
DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                         WITH HEADER LINE.
DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapisdhedu
                         WITH HEADER LINE.
* Initialization.
INITIALIZATION.
v_text   = 'Order type'.
v_text1 = 'Sales Org'.
v_text2 = 'Distribution channel'.
v_text3 = 'Division'.
v_text4 = 'Sold-to'.
v_text5 = 'Ship-to'.
v_text6 = 'Material'.
v_text7 = 'Quantity'.
v_text9 = 'Plant'.
* Start-of-selection.
START-OF-SELECTION.
* Header data
* Sales document type
header-doc_type = p_auart.
headerx-doc_type = 'X'.
* Sales organization
header-sales_org = p_vkorg.
headerx-sales_org = 'X'.
* Distribution channel
header-distr_chan = p_vtweg.
headerx-distr_chan = 'X'.
* Division
header-division = p_spart.
headerx-division = 'X'.
headerx-updateflag = 'I'.
* Partner data
* Sold to
partner-partn_role = 'AG'.
partner-partn_numb = p_sold.
APPEND partner.
* Ship to
partner-partn_role = 'WB'.
partner-partn_numb = p_ship.
APPEND partner.
* ITEM DATA
itemx-updateflag = 'I'.
* Line item number.
item-itm_number = '000010'.
itemx-itm_number = 'X'.
* Material
item-material = p_matnr.
itemx-material = 'X'.
* Plant
item-plant    = p_plant.
itemx-plant   = 'X'.
* Quantity
item-target_qty = p_menge.
itemx-target_qty = 'X'.
APPEND item.
APPEND itemx.
*   Fill schedule lines
lt_schedules_in-itm_number = '000010'.
lt_schedules_in-sched_line = '0001'.
lt_schedules_in-req_qty    = p_menge.
APPEND lt_schedules_in.
*   Fill schedule line flags
lt_schedules_inx-itm_number = '000010'.
lt_schedules_inx-sched_line = '0001'.
lt_schedules_inx-updateflag = 'X'.
lt_schedules_inx-req_qty     = 'X'.
APPEND lt_schedules_inx.
CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT1'
    EXPORTING
      order_header_in           = header
*     WITHOUT_COMMIT            = ' '
*     CONVERT_PARVW_AUART       = ' '
   IMPORTING
     salesdocument              = v_vbeln
*     SOLD_TO_PARTY             =
*     SHIP_TO_PARTY             =
*     BILLING_PARTY             =
*     RETURN                    =
    TABLES
      order_items_in            = item
      order_partners            = partner
*     ORDER_ITEMS_OUT           =
*     ORDER_CFGS_REF            =
*     ORDER_CFGS_INST           =
*     ORDER_CFGS_PART_OF        =
*     ORDER_CFGS_VALUE          =
*     ORDER_CCARD               =
*     ORDER_CFGS_BLOB           =
     order_schedule_ex          = lt_schedules_in
* Check the return table.
IF v_vbeln <> space.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
    WRITE: / 'Document ', v_vbeln, ' created'.
ELSE.
    WRITE: / 'Error in creating document'.
ENDIF.
I am unable to trace the exact reason. Please help and thanks in advance.
Edited by: Joy Banerjee on Oct 12, 2009 7:47 AM

Hi Prashant,
Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
If it doesn't work, see in transaction db02 if there is sufficient tablespace.
Let me knoe the status of tablespaces.
Regards,
Sabita

Dump error in db02 CONNE_IMPORT_WRONG_COMP_TYPE

Dear All,
When use the t-code db02 and press refresh button for database + history check it give abap runtine error dump.
it gives this error as runtime error:
CONNE_IMPORT_WRONG_COMP_TYPE.
please guide me, it is happening both in Devlopment and well as in production server.
Thanks
Bhaskar

Hi,
check Note 657981 - CONNE_IMPORT_WRONG_COMP_TYPE in DB02 for RSORAUD1
also check Note 997535 - DB02: Problems with History Data.
regards
kaushal

ABAP runtime errors SNAP_NO_NEW_ENTRY

The following errors occured just after login, can anyone tell me how to handle it?
ABAP runtime errors SNAP_NO_NEW_ENTRY
Occurred on 0000.00.00 at 13:47:44
Runtime error: Unable to write short dump.
What happened?
The current ABAP/4 program " " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
Unfortunately, the original cause of the error cannot be determined
because there is no suitable short dump in the table SNAP (which
records information about the point of termination).
termination).
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
Error analysis
Unfortunately, the original cause of the error cannot be
determined, since there is no suitable short dump in table SNAP.
The table SNAP probably already contains a number of short dumps
and cannot accept any more. Please check the situation using the
system log.
The table SNAP contains all the short dumps for the last 7 days.
How to correct the error
Check the system log for each cause of error.
More space probably needs to be provided for table SNAP
using database means.
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:

补充两句：
1. SNAP表的Reorganization应该在后台通过定期的（每天）job执行，参看Note 16083。
2. 如果登录系统即发生Dump，怀疑是否SNAP的table space是导致这个Dump的原因，考虑可能有其它致命错误。如果登录后还可以执行transaction，尝试执行SM21，DB02检查。

Runtime Error DBIF_RSQL_INVALID_REQUEST

Hi,
I have installed SAPNW trail version, and I get this error when i log on.
I have installed it on a Windows XP Professional.
Here is the log on error.
<b>Runtime Errors         DBIF_RSQL_INVALID_REQUEST
Date and Time          24.08.2006 15:25:28
Short text
Invalid request.
What happened?
The current ABAP/4 program had to be terminated because the
     ABAP/4 processor detected an internal system error.
Error analysis
An invalid request was made to the database interface
     when accessing table "DOKTL ".
     Last error logged in SAP kernel
Component............ "NI (network interface)"
     Place................ "SAP-Server hema_NSP_00 on host hema (wp 0)"
     Version.............. 38
Error code........... "-16"
     Error text........... "verify own hostname '172.16.0.101:0' failed"
     Description.......... "NiIBindSocket"
     System call.......... "bind"
     Module............... "nixxi.cpp"
     Line................. 3144
The error reported by the operating system is:
     Error number..... 10049
Error text....... "WSAEADDRNOTAVAIL: Can't assign requested address"
Trigger Location of Runtime Error
     Program                                 SAPMSYST
     Include                                 SAPMSYST
     Row                                     2.555
     Module type                             (FORM)
     Module Name                             FILL_INFO_TAB </b>
can anyone help me with this please. How to solve this problem.I referred to the forum but not helpful I checkeed the host file etc, but still not helpful.
Thanks,
Prashant.
Message was edited by: Prashant Kumar

Hi Prashant,
Set the profile parameter abap/buffersize value to maximum.Get the virtual memory increased.
If it doesn't work, see in transaction db02 if there is sufficient tablespace.
Let me knoe the status of tablespaces.
Regards,
Sabita

SNAP_NO_NEW_ENTRY runtime error

hi all,
while i am running sgen i got runtime error(dump)SNAP_ NO_NEW_ENTRY. when i try to maintain that table SNAP through DB02 again throwing dump so no transaction is working .so please how can i modify at OS(windows 2003) level .Which is SQL database

Hi
Check the space at database level,I guess your database has no free space or check if the log directory is not full(these dumps can come due to these issues)
Also while running SGEN,change the database mode from full to simple
If this doesn't help,refer to Note 17537,it might help
Rohit

Runtime error in starting Lightroom

I receive the following message when I try to start Lightroom:
Microsoft Visual C++ Runtime Library
Runtime Error!
Program:...Files\Adobe\Adobe Photoshop Lightroom 1.2\lightroom.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
Lightroom ran well for several days and then failed to open with the above message.
I have tried everything I know to do (uninstalled and reinstalled the application, restored the computer to a restore point before Lightroom was originally installed, etc.) and do not know were to go from here. Suggestions would be appreciated.
I am using Windows XP sp2 and have 4 GB of ram and 250 GB of hard disk space.
Thanks,
Cliff Culp

Aha! A fix! Please look at this...
http://www.adobeforums.com/cgi-bin
bob frost, "Help! Runtime error after Lightroom 1.1 install!" #10, 27 Jun 2007 6:54 am

Runtime error while executing rule

Hello All,
While executing the DTP for a cube, im facing the error as Runtime error while executing rule -> see long text .
For this source is another Cube, where im loading the data from Cube to Cube.
Error Description are as follows:-
Error Location: Object Type    TRFN
Error Location: Object Name    0T9SCR6Q4VWS1SOPNRRBOY1YD51XJ7PX
Error Location: Operation Type ROUTINE
Error Location: Operation Name
Error Location: Operation ID   00034 0000
Error Severity                 100
Original Record: Segment       0001
Original Record: Number        557
and Also descripton is :-
Diagnosis
    An error occurred while executing a transformation rule:
    The exact error message is:
    Division by zero
    The error was triggered at the following point in the program
    GP4H0CW3MLPOTR3E8Y93QZT2YHA 4476
System Response
    Processing the data record has been terminated.
Procedure
The following additional information is included in the higher-level
node of the monitor:
   Transformation ID
   Data record number of the source record
   Number and name of the rule which produced the error
Let me know ur valuable suggestions on these error...
thanks.

Hello,
I have checked all the transformation and End Routines.All are working fine.Yesterday i have loaded some data into it, but today its gettting errored out.
Checked completely in the forum for threads related to this, but couldnt find proper thread which had solutions....
thanks,
srinivas.

Could someone help me with a Runtime Error while saving a PDF file?

While saving a 28 page PDF file in Illustrator today, I got a window saying, "This application has requested the "Runtime" to terminate it in a unusual way." It said to contact the applications support team for more information. I keep getting the same thing each time I try it. Does anyone know how to fix this issue or how I contact the applications support team ?
Thank you for any insight.
Pam

It is a 13.5x11 inch calendar. There are 14 pages with images on them and
some text. The other pages have text, a grid and a colored background with a
gaussian blur. I saved each page as an "outline".
The printer I am using requested I save all pages in a pdf file. I was
successful in saving all but about six pages, now I can't even open the
file.
What happens is... I open Illustrator
                               I open the pdf file
                               A window appears that says... Runtime Error,
This application has requested the Runtime to terminate it in an unusual
way. Please contact the application's support team for more information.
                               I select ok
                               then a window appears that says... Adobe
Illustrator CS5 has stopped working. A problem caused the program to stop
working correctly. Windows will close the program and notify you if a
solution is available.
                               Then the program closes.
So far I have not been notified of anything.
Please let me know if you need more details.
Thank you so much for helping me with this.
Pam

RunTime Error while saving a Sales Order

Hi All,
When i am saving a Sales Order, the system is throwing a Runtime Error.
The ABAP Code in the Runtime Error screen as follows.
          select * from (t681-kotab) appending table <cond_tab>
                 up to 1 rows
                 where kappl = se_kappl
                 and   kschl = se_kschl
                 and   datbi >= se_date
                 and   datab <= se_date
                 and   (coding_tab).
Till these days, there was no such error while saving a Sales Order.
How to resolve this issue?
Regards
Pavan

Hi,
The below piece of code is trying to get the contents of the table mentioned in T681-KOTAB.
select * from (t681-kotab) appending table <cond_tab>
up to 1 rows
where kappl = se_kappl
and kschl = se_kschl
and datbi >= se_date
and datab <= se_date
and (coding_tab).
The reason could be is someone has screwed up the entries in T681 table. Check that out.
Try to put a break point on this SELECT query and see what the value of T681-KOTAB holds before the SELECT query. Check whether such a table entry exists in DB.
Let me know if you are still stuck up.
If you can send me the ST22 dump of the run time error, i might be able to help you more on this.
Hope this helps.
Thanks,
Balaji

WHILE DELETING A SALE ORDER GETTING A RUNTIME ERROR

hi to all experts,
whenever i try to delete a particular sale order im getting a runtime error
stating that
Short text
    Screen: Illegal message
What happened?
    The current screen processing action was terminated since a situat
    occurred where the application could not continue.
    This is probably due to an error in the ABAP program or in the cur
    screen.
Error analysis
    The program attempted to issue a " " message during "Exit Command" processing.
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
Trigger Location of Runtime Error
    Program                                 SAPMV45A
    Include                                 MV45AFZZ
    Row                                     370
    Module type                             (FORM)
    Module Name                             USEREXIT_SAVE_DOCUMENT
SourceCde
              message e001(zm) WITH text-335 ltab-kunnr text-334.
            else.
              if ktab-jkunnr <> ltab-kunnr.
                ktab-jkunnr = ltab-kunnr.
                jobsitecode = ltab-kunnr.
                CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
                EXPORTING
                  input = jobsitecode
                  IMPORTING
                  output = jobsitecode.
                SELECT SINGLE * FROM kna1 WHERE kunnr = jobsitecode.
                IF sy-subrc = 0.
                  ktab-jname1 = kna1-name1.
                  ktab-jstras = kna1-stras.
                ENDIF.
                chg_flg = 'X'.
              endif.
            endif.
          else.
            message e001(zm) WITH text-336.
* Validation for relationship between Sold-to Party and Ship-to Party
*          if ktab-ckunnr+0(4) NE ktab-jkunnr+0(4).
*            message e001(zm) WITH text-335 ktab-jkunnr text-337 ktab-ckunnr.
*          endif.
          custcode1 = ktab-ckunnr.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = custcode1
            IMPORTING
              output = custcode1.
          jobsitecode1 = ktab-jkunnr.
          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input = jobsitecode1
            IMPORTING
              output = jobsitecode1.
          SELECT SINGLE * FROM knvp
          WHERE kunnr = custcode1
            AND vkorg = vbak-vkorg
            AND vtweg = vbak-vtweg
            AND spart = vbak-spart
            AND parvw = 'WE'
Error analysis
    The program attempted to issue a " " message during "Exit Command"
    This is an illegal operation.
    The program was terminated.
    Screen name.............. "SAPMV45A"
    Screen number............ 4001
Trigger Location of Runtime Error
    Program                                 SAPMV45A
    Include                                 MV45AFZZ
    Row                                     370
    Module type                             (FORM)
    Module Name                             USEREXIT_SAVE_DOCUMENT

Hi,
Seems there is some problem with the user exit USEREXIT_SAVE_DOCUMENT..
Put a breakpoint and see.
Regards,
Nagaraj

Runtime error in DB02 IMPORT_OBJECT_DESTROYED

Similar Messages

Maybe you are looking for