Skip to Content

Problem in Data Mart

I tried to transfer data from one InfoCube(ZE1) to another InfoCube(ZE2).

Please find below the procedure I exercised:

INFOCUBE ZE1 SUCCESSFULLY POPULATED DATA FROM FLATFILE WITH 20 RECORDS.

INFOCUBE ZE2 CREATED BY COPYING FROM ZE1.

GENERATED EXPORT DATASOURCE IN ZE1 AND REPLICATED THIS NEW DATASOURCE 8ZE1 IN THE B3TCLNT800 - BW CLIENT 800 SOURCE SYSTEM. THEN ACTIVATED THE TRANSFER RULES. THE INFOSOURCE IS IN DATAMART FOULDER.

THE UPDATE RULES FOR ZE2 WAS CREATED USING INFOCUBE ZE1 (data mart concept) UNDER DATASOURCE TAB.

SCHEDULED A LOAD PACKAGE ON THE INFOSOURCE 8ZE1 TO LOAD TO THE NEW INFOCUBE ZE2.

Now while running the scheduling process, a short dump is created:

No request Idoc generated in BW.

Exception condition “INHERITED_ERROR” RAISED.

Could you tell me what could be the reason behind it.

Thanks in advance.

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Aug 29, 2005 at 04:57 AM

    Hi Venkat,

    Refer to OSS Note:568768.

    Bye

    Dinesh

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 29, 2005 at 06:16 AM

    Hi,

    Even if it related to the indices or aggregarion of ur Cube. try relaoding the data after deleting the previous request inthe Cube and delete the data mart symbol in the ZE1. and then repeat the load.

    Hope this helps-

    REgards-

    MM

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Ravindra,

      The Status tab in Monitor-

      Diagnosis: No request IDoc has been created in BW. A short dump has most probably been logged in BW.

      In Dump: Exception condition 'RAISE_EXCEPTION' raised. The current ABAP/4 program encountered an unexpected situation.

      The RAISE statement in the program "SAPLRSDRC" raised the exception condition "INHERITED_ERROR". Sine the exception was not intercepted by a superior program in the hierarchy, processing was terminated.

      Information on where termination occured:

      The termination occurred in the ABAP program "SAPLRSDRC" in"RAISE_EXCEPTION". The main program was "SBIE0001". The termination occurred in line 89 of the source code of (Include) program "SAPLRSDRC".

      Line 85: *INHERITED_ERROR

      Line 86: IF i_exception = rsdrc_c_exc_inherited

      Line 87: * Message handler active --> handed over to the next level.

      Line 88: IF l_handler_active = rs_c_true

      Line 89: RAISE inherited_error.

      Thanks.

  • author's profile photo Former Member
    Former Member
    Posted on Aug 30, 2005 at 04:23 AM

    Hi Venkat,

    Posting the OSS Note:568768 for your ref:

    <u><b>Symptom</b></u>

    A shortdump with an SQL Error occurs, or a message indicates, that a SQL Error occured. You need to figure out more information about the failing statement and the reasons for failing.

    A shortdump with Exception condition "INHERITED_ERROR" occured, a RAISE statement in the program "SAPLRSDRC " raised the exception condition "INHERITED_ERROR".

    <u><b>Other terms</b></u>

    Shortdump SQL Error Oracle DB6 DB2 MSSQL SAPDB Informix Database dev_w0 developer trace syslog UNCAUGHT_EXCEPTION CX_SY_SQL_ERROR DBIF_REPO_SQL_ERROR INHERITED_ERROR SAPLRSDRC RSDRC RSDRS SAPLRSDRS DBIF_RSQL_SQL_ERROR

    <u><b>Reason and Prerequisites</b></u>

    A shortdump with a SQL Error occurs, e.g. during BW Aggregate build, compression, BW queries, Datamart extraction, or a SQL Statement failed without a shortdump.

    The actions mentioned will already indicate the cause of the error.In particular, the database administrator should frequently be able to immediately recognize solutions.Nevertheless, you should create an OSS problem and you should then attach the SQL error message including additional information (such as the SQL statement that occurred or the error message text) to the problem message.

    This note combines the two OSS notes 495256 and 568768.

    <u><b>Solution</b></u>

    1. If a shortdump occured, get the work process and App Server where the dump occured, otherwise continue with the next step.

    Inside the shortdump, scroll to "System environment". Either you find the work process number here, or continue with the next step.

    1. Get the work process number from the syslog

    Go into the system log (Transaction sm21), search for the Short dump entry with the same timestamp in the syslog of the App Server where the short dump occured.

    The column "Nr" contains the work process number. Maybe there are already syslog entries before this entry containing more information about the error.

    Example: The shortdump contains

    UNCAUGHT_EXCEPTION

    CX_SY_SQL_ERROR

    04.11.2002 at 14:47:32

    The syslog contains:

    Time Ty. Nr Cl. User Tcod MNo Text

    14:47:32 BTC 14 000 NAGELK BY2 Database error -289 at EXE

    14:47:32 BTC 14 000 NAGELK BY0 > dsql_db6_exec_immediate( SQL

    14:47:32 BTC 14 000 NAGELK BY0 > Driver][DB2/LINUX] SQL0289N

    14:47:32 BTC 14 000 NAGELK BY0 > table space "PSAPTEMP". SQLS

    14:47:32 BTC 14 000 NAGELK BY2 Database error -289 at EXE

    14:47:32 BTC 14 000 NAGELK R68 Perform rollback

    14:47:32 BTC 14 000 NAGELK AB0 Run-time error "UNCAUGHT_EXCEP

    14:47:32 BTC 14 000 NAGELK AB2 > Include RSDRS_DB6_ROUTINES l

    ...

    14:47:33 BTC 14 000 NAGELK AB1 > Short dump "021104 144732

    So from the Syslog the information can be got, that the reason of the error is

    Database error -289 at EXE dsql_db6_exec_immediate( SQLExecDirect ): [IBM][CLI Driver][DB2/LINUX] SQL0289N Unable to allocate new pages in table space "PSAPTEMP". SQLSTATE=57011

    The database error code is -289, the error text is "Unable to allocate new pages in tablespace "PSAPTEMP" ", and the work process number is "14".

    1. Displaying the developers trace

    Go to transaction sm51, select the correct application server (where the shortdump occured), now you are on transaction sm50 for this app server. Check the work process with the number you got from shortdump or syslog (in our example number 14), in the menu bar select Process - Trace - Display File.

    In the developers Trace search for the timestamp. In our example we get the entry:

    C Mon Nov 4 14:47:32 2002

    C *** ERROR in ExecuteDirect[dbdb6.c, 5617]

    C &+ 0|

    dsql_db6_exec_immediate( SQLExec...

    C &+ 0

    able space "PSAPTEMP". SQLSTATE=57011

    C &+ 0

    C &+ 0|

    INSERT INTO "/BIC/E100015" ...

    C &+ 0

    | | ...

    1. For most of the important sql statements generated by BW, when an error occurs, the SQL statement is saved as a text file called, for example, SQL00000959.sql (SQL<error code>.sql). If the statement is run in a dialog process, then the file is in the current directory of your SAP GUI on the front-end PC (for example, C:\Documents and Settings\schmitt\SAPworkdir);with batch tasks, it is stored in the DIR_TEMP directory (see transaction AL11) on the application server.

    2. For SAP Internal Support:

    Using the sql error codes determined under (1) as well as the relevant database platform, you can obtain a more detailed description of the error and possible error causes at http://dbi.wdf.sap.corp:1080/DBI/cgi/dberr.html.

    Hope this helps.

    Bye

    Dinesh

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.