RE: XPRAS_AIMMRG Errors EHP8

      Hi All,

      XPRAS_AIMMRG error with the following message.

      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

      XPRA ERRORS and RETURN CODE in SAPR750ZDA.TS4

      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

      A3 ESCPR 827XInstalled languages: “1234568CDEFGHIJKLMNOPQRSTUVWdì©”

      A3 ESCPR 828 Activation languages: “1234568CDEFGHIJKLMNOPQRSTUVWdì©”

      A3 ESCPR 625XBC Set “HRASR_V_T7XSSSERSAR_ENH_02”: The BC Set (last change “20070                                                                                                             419″/”222731”) was passed for activation

      A3 ESCPR 747 BC Set “HRASR_V_T7XSSSERSAR_ENH_02”: BC Set is client-specific and                                                                                                              cascading

      A3 ESCPR 746 BC Set “HRASR_V_T7XSSSERSAR_ENH_02”: BC Set is assigned to package                                                                                                              ‘”PAOC_ASR_SFWS_UI_02″‘ and switch ‘”HRASR_SFWS_UI_ENH_02″‘

      1AETR012XProgram canceled (job “RDDEXECL”, number “19543500”)

      1AEPU320 See job log”RDDEXECL””19543500″”TS4″

      1 ETP111 exit code           : “12”

      >>> PLEASE READ THE REPORT DOCUMENTATION OF THE REPORTS MENTIONED ABOVE <<<

      XPRAs are application reports that run at the end of an upgrade.

      Most XPRA reports have a report documentation that explains what

      the report does and how errors can be corrected.

      Accepting the Accept Non severe error also results in the failure of this process

      ==Alert Log shows the following==

      Sun Sep 11 19:54:52 2016

      Errors in file /oracle/SID/saptrace/diag/rdbms/SID/SID/trace/SID_ora_61398.trc  (incident=211445):

      ORA-00600: internal error code, arguments: [kdlxdup:kdlwReadCallback_pga], [294], [0], [], [], [], [], [], [], [], [], []

      Incident details in: /oracle/SID/saptrace/diag/rdbms/SID/SID/incident/incdir_211445/SID_ora_61398_i211445.trc

      Use ADRCI or Support Workbench to package the incident.

      See Note 411.1 at My Oracle Support for error and packaging details.

      Sun Sep 11 19:54:54 2016

      Root Cause: ORA-00600: internal error code, arguments: [kdlxdup:kdlwReadCallback_pga], [294], [0], [], [], [], [], [], [], [], [], [], the argument is 294. I did not find anything related with the argument 294

      Looking forward to your suggestions

      Regards,

      Sebastian

      Hi Guys,   I am sure someone might face this error in the future, i have a work around from SAP. I hope this can be useful for others who may face similar issue in the future.   Diagnoses:   1AETR012XProgram canceled (job "RDDEXECL", number "19543500") Job RDDEXECL is cancelled with the log showing runtime error DBSQL_SQL_ERROR The trace file shows that WP has reached abap/heaplimit = 40000000 bytes after which the Oracle 600 occurred. Oracle 600 occurred with the following argument         ORA-00600: internal error code, arguments: [kdlxdup:kdlwReadCallback_pga],           [294] , [0], [], [].            Some thing to notice here…

      User Rating: Be the first one !
      Ben Bolker Reviewer Asked on November 2, 2016 in enhancement packages.
      Add Comment
      1 Answers

        Hi Guys,

         

        I am sure someone might face this error in the future, i have a work around from SAP. I hope this can be useful for others who may face similar issue in the future.

         

        Diagnoses:

         

        1. 1AETR012XProgram canceled (job “RDDEXECL”, number “19543500”)
        2. Job RDDEXECL is cancelled with the log showing runtime error DBSQL_SQL_ERROR
        3. The trace file shows that WP has reached abap/heaplimit = 40000000 bytes after which the Oracle 600 occurred.
        4. Oracle 600 occurred with the following argument

                ORA-00600: internal error code, arguments: [kdlxdup:kdlwReadCallback_pga],           [294] , [0], [], [].

                   Some thing to notice here is the code kdlxdup and 294.

            5. And SM21 shows the following.

                  SM21

                  Database error 600 with FET access to table SCPRSREVERTD

                  FET – Reading one or several records of a database cursor

            

        Solution:

        SAP says the following

        The issue seems to be related to bug 17533661 currently being worked on by Oracle Development.

         

        Unfortunately there is not yet any fix available for this.
        SAP gives the below work around.
        They asked me to use the “old” LOBs (BasicFiles) for the table SCPRSREVERTD instead of the “new” SecureFile LOBs.
        They asked me to use the brspace tool for the reorganisation as described in the SAP note:    1431296 – LOB conversion and table compression with BRSPACE 7.20    Chapter 1.2:  Syntax of the options for LOB conversion”
        With Note 1
        Note 1: There is, however, a hidden option “-COL” (create old LOBs) that prevents this.            If this is set on the command line, the system converts the LONG fields into the old LOBs (BasicFiles).            In the “lob2lob” action, you can use this option to force the system to convert the new LOBs into old LOBs
        So I reorganized the table with the action lob2lob with the -COL option and continued the upgrade, then issue got resolved. While SAP is working on providing a fix for this
        Regards,
        Sebastian

         

         

         

        Add Comment

        Your Answer

        By posting your answer, you agree to the privacy policy and terms of service.