MESSAGE_TYPE_X IN BI_CONT 7.03 INSTALLATION

Question

Hi,
i am installing bi_cont 7.03, installation stuck at xpra_excution IN SAPKIBIII4 WITH  LOG BELOW
Runtime Errors         MESSAGE_TYPE_X
Date and Time          13.06.2009 14:15:25
     Short text
          The current application triggered a termination with a short dump.
     What happened?
          The current application program detected a situation which really
          should not occur. Therefore, a termination with a short dump was
          triggered on purpose by the key word MESSAGE (type X).
     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
          Short text of error message:
          System error in program LRSDG_IOBJ_DB_READF40 and form REGULAR_IOBJ_GET_
          FOR_META (see long text)
          Long text of error message:
           Diagnosis
               This internal error is an intended termination resulting from a
               program state that is not permitted.
           Procedure
               Analyze the situation and inform SAP.
               If the termination occurred when you executed a query or Web
               template, or during interaction in the planning modeler, and if you
               can reproduce this termination, record a trace (transaction RSTT).
               For more information about recording a trace, see the documentation
               for the trace tool environment as well as SAP Note 899572.
          Technical information about the message:
          Message class....... "BRAIN"
          Number.............. 299
          Variable 1.......... "LRSDG_IOBJ_DB_READF40"
          Variable 2.......... "REGULAR_IOBJ_GET_FOR_META"
          Variable 3.......... " "
          Variable 4.......... " "
     How to correct the error
          Probably the only way to eliminate the error is to correct the program.
          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:
          "MESSAGE_TYPE_X" " "
          "SAPLRSDG_IOBJ_DB_READ" or "LRSDG_IOBJ_DB_READF40"
          "REGULAR_IOBJ_GET_FOR_META"
          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.
     System environment
          SAP-Release 700
          Application server... "test"
          Network address...... "192.168.10.248"
          Operating system..... "Windows NT"
          Release.............. "5.2"
          Hardware type........ "4x AMD64 Level"
          Character length.... 8 Bits
          Pointer length....... 64 Bits
          Work process number.. 11
          Shortdump setting.... "full"
          Database server... "TEST"
          Database type..... "ORACLE"
          Database name..... "KIL"
          Database user ID.. "SAPKIL"
          Char.set.... "English_United State"
          SAP kernel....... 700
          created (date)... "May 31 2009 20:44:02"
          create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
          Database version. "OCI_10201_SHARE (10.2.0.1.0) "
          Patch level. 210
          Patch text.. " "
          Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
          SAP database version. 700
          Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
           NT 6.0"
          Memory consumption
          Roll.... 16128
          EM...... 62848560
          Heap.... 0
          Page.... 40960
          MM Used. 37341136
          MM Free. 12932688
     User and Transaction
          Client.............. 000
          User................ "DDIC"
          Language key........ "E"
          Transaction......... " "
          Transactions ID..... "85F657DE8ED8F1739C680015170F3C4D"
          Program............. "SAPLRSDG_IOBJ_DB_READ"
          Screen.............. "SAPMSSY0 1000"
          Screen line......... 6
     Information on where terminated
          Termination occurred in the ABAP program "SAPLRSDG_IOBJ_DB_READ" - in
           "REGULAR_IOBJ_GET_FOR_META".
          The main program was "RDDEXECU ".
          In the source code you have the termination point in line 31
          of the (Include) program "LRSDG_IOBJ_DB_READF40".
          The program "SAPLRSDG_IOBJ_DB_READ" was started as a background job.
          Job Name....... "RDDEXECL"
          Job Initiator.. "DDIC"
          Job Number..... 14151900
     Source Code Extract
     Line     SourceCde
         1     ----
         2     *   INCLUDE LRSDG_IOBJ_DB_READF40                                      *
         3     ----
         4     
         5     
         6     ----
         7     *      Form  REGULAR_IOBJ_GET_FOR_META
         8     ----
         9     *    read a regular InfoObject as Meta InfoObject
        10     ----
        11     *   --> I_INFOCUBE   InfoCube
        12     *   --> I_IOBJNM     InfoObject
        13     *   <-> C_T_COB_PRO  InfoCube specific InfoObject properties
        14     ----
        15     FORM regular_iobj_get_for_meta USING    i_infocube   TYPE rsinfocube
        16                                             i_iobjnm     TYPE rsiobjnm
        17                                    CHANGING c_t_cob_pro  TYPE rsd_t_cob_pro.
        18     
        19       DATA: l_s_cob_pro  TYPE rsdcobpro.
        20     
        21       CALL FUNCTION 'RSD_IOBJ_INCL_ATR_NAV_GET'
        22         EXPORTING
        23           i_iobjnm       = i_iobjnm
        24           i_objvers      = rs_c_objvers-active
        25         IMPORTING
        26           e_s_cob_pro    = l_s_cob_pro
        27         EXCEPTIONS
        28           iobj_not_found = 1
        29           illegal_input  = 2.
        30       IF sy-subrc <> 0.
     >>>>>         MESSAGE x299(brain) WITH 'LRSDG_IOBJ_DB_READF40'
        32                                  'REGULAR_IOBJ_GET_FOR_META'.
        33       ENDIF.
        34     
        35     * time charact --> time dimension / In BEX not visible
        36       IF i_iobjnm = rsd_c_chanm-date OR
        37          i_iobjnm = rsd_c_timnm-calday.
        38         l_s_cob_pro-chasel     = rsd_c_chasl-not_allowed.
        39         l_s_cob_pro-chanav     = rsd_c_chanv-not_allowed.
        40     
        41     **   from 3.0 these InfoObjects are marked as META objects
        42     *    l_s_cob_pro-iobjtp     = rsd_c_objtp-meta.
        43     *    the olap processor uses 0DATE / 0CALDAY as default for exceptional aggregation -
        44     *    therefore it has to be in the cobpro
        45     *    but it must not be of type META, since then day of validity logic
        46     *    does not work
        47     *    solution for 3.0: OLAP processor uses the flags CHASEL and CHANAV to determine
        48     *    if 0DATE / 0CALDAY is part of the infocube
        49     
        50     *   leave dimension empty
     Contents of system fields
     Name     Val.
     SY-SUBRC     1
     SY-INDEX     0
     SY-TABIX     0
     SY-DBCNT     0
     SY-FDPOS     0
     SY-LSIND     0
     SY-PAGNO     0
     SY-LINNO     1
     SY-COLNO     1
     SY-PFKEY     
     SY-UCOMM     
     SY-TITLE     Execute Post-Import Methods and XPRAs for Transport Request
     SY-MSGTY     X
     SY-MSGID     BRAIN
     SY-MSGNO     299
     SY-MSGV1     LRSDG_IOBJ_DB_READF40
     SY-MSGV2     REGULAR_IOBJ_GET_FOR_META
     SY-MSGV3     
     SY-MSGV4     
     SY-MODNO     0
     SY-DATUM     20090613
     SY-UZEIT     141519
     SY-XPROG     SAPLSYST
     SY-XFORM     SYSTEM_HOOK_OPEN_DATASET
     Active Calls/Events
     No.   Ty.          Program                             Include                             Line
           Name
        16 FORM         SAPLRSDG_IOBJ_DB_READ               LRSDG_IOBJ_DB_READF40                  31
           REGULAR_IOBJ_GET_FOR_META
        15 FUNCTION     SAPLRSDG_IOBJ_DB_READ               LRSDG_IOBJ_DB_READU32                 101
           RSD_ALL_META_IOBJ_GET
        14 METHOD       CL_RSD_DTA====================CP    CL_RSD_DTA====================CM021   658
           CL_RSD_DTA=>BUILD_SNG_DTA_PRO
        13 METHOD       CL_RSD_DTA====================CP    CL_RSD_DTA====================CM00H    90
           CL_RSD_DTA=>BUILD_DTA_PRO
        12 METHOD       CL_RSD_DTA====================CP    CL_RSD_DTA====================CM00I   110
           CL_RSD_DTA=>UPDATE_DTA_BUF
        11 METHOD       CL_RSD_CUBE===================CP    CL_RSD_CUBE===================CM006   197
           CL_RSD_CUBE=>IF_RSD_DTA~DTA_GET_INFO
        10 METHOD       CL_RSD_DTA====================CP    CL_RSD_DTA====================CM001   157
           CL_RSD_DTA=>IF_RSD_DTA~DTA_GET_INFO
         9 FORM         SAPLRSDI                            LRSDIF20                               63
           COB_GET_FROM_BUFFER
         8 FUNCTION     SAPLRSDI                            LRSDIU05                               42
           RSD_COB_PRO_GET
         7 FORM         SAPLRSDDK6                          LRSDDK6F01                            342
           CONVERT_A_TO_M_VERSION
         6 FUNCTION     SAPLRSDDK6                          LRSDDK6U06                             89
           RS_DAGR_AFTER_IMPORT
         5 FUNCTION     SAPLRSVERS                          LRSVERSU07                            102
           RS_AFTER_IMPORT_D
         4 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                      351
           CALL_IMP_METHODS_IN_CLIENT
         3 FORM         SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPF02                       87
           CALL_IMP_METHODS
         2 FUNCTION     SAPLSCTS_EXE_EXP                    LSCTS_EXE_EXPU02                      103
           TRINT_CALL_AFTER_IMP_METHOD
         1 EVENT        RDDEXECU                            RDDEXECU                              168
           START-OF-SELECTION
PLEASE HELP ME OUT TO SOLVE IT  I HAVE GONE THROUGH SIMILAR POST and the notes there is corrction but how to implement the correction i dont know
sunil

Answer 1

hi,
i would request yiu all to pay attention on this and help me out
CALL FUNCTION 'RSD_IOBJ_INCL_ATR_NAV_GET'
    EXPORTING
      i_iobjnm       = i_iobjnm
      i_objvers      = rs_c_objvers-active
    IMPORTING
      e_s_cob_pro    = l_s_cob_pro
    EXCEPTIONS
      iobj_not_found = 1
      illegal_input  = 2.
  IF sy-subrc <> 0.
    MESSAGE x299(brain) WITH 'LRSDG_IOBJ_DB_READF40'
                             'REGULAR_IOBJ_GET_FOR_META'.
  ENDIF.
+ time charact --> time dimension / In BEX not visible+*
  IF i_iobjnm = rsd_c_chanm-date OR
     i_iobjnm = rsd_c_timnm-calday.
    l_s_cob_pro-chasel     = rsd_c_chasl-not_allowed.
    l_s_cob_pro-chanav     = rsd_c_chanv-not_allowed.
+*   from 3.0 these InfoObjects are marked as META objects+*
+    l_s_cob_pro-iobjtp     = rsd_c_objtp-meta.+*
+    the olap processor uses 0DATE / 0CALDAY as default for exceptional aggregation -+*
+    therefore it has to be in the cobpro+*
+    but it must not be of type META, since then day of validity logic+*
+    does not work+*
+    solution for 3.0: OLAP processor uses the flags CHASEL and CHANAV to determine+*
+    if 0DATE / 0CALDAY is part of the infocube+**
PLEASE HELP WITH SOME WORK AROUND
sanjeev