20 Replies Latest reply: May 10, 2011 12:56 PM by Lukas Hunana RSS

not start MaxDB after ugrade from 7.5 to 7.7

Mieczyslaw Kaczor
Currently Being Moderated

Hi,

when I try database switch to Admin or OnLine state, I have error:

 

-24994 Runtime environment error [DB_admin -f]; 20090, Check knldiag! Kernel exited with '1' before reaching ADMIN state

 

 

File: knldiag is empty, only in file KnMsg I found:

....

<MSGL _NO="5068" _PROCESS="417880" _THREAD="0x1" _TIME="2010-04-14 11:12:13.000">

  <MSG _NO="1" _ID="20235" _COMP="RTE" _TEXT="Dump of all kernel parameters done">

   <MSG_ARGS

     FILE="RTEConfParameterAccessKernelInterface.cpp"

     _LINE="1271"

     _TIME="2010-04-14 11:12:13.000"

    />

  </MSG>

</MSGL>

<MSGL _NO="5069" _PROCESS="417880" _THREAD="0x1" _TIME="2010-04-14 11:12:13.000">

  <MSG _NO="1" _TYPE="Error" _ID="1" _COMP="SAPDBMem" TEXT="Out of memory needed $BYTESNEEDED$ for $DESCRIPTION$">

   <MSG_ARGS

     FILE="RTEConfVolumeConfiguration.cpp"

     _LINE="992"

     _TIME="2010-04-14 11:12:13.000"

     _MESSAGEVERSION="1"

     BYTES_NEEDED="152"

     DESCRIPTION="Missing log mirror"

     ALLOCATOR="RTEMem_RteAllocator"

    />

  </MSG>

</MSGL>

<MSGL _NO="5070" _PROCESS="417880" _THREAD="0x1" _TIME="2010-04-14 11:12:13.000">

  <MSG _NO="1" _TYPE="Error" _ID="0" _COMP="RTEKERN" _TEXT="--&gt; Symbolic stack backtrace &lt;--">

   <MSG_ARGS

     FILE="MsgOutputKnlDiag.cpp"

     _LINE="709"

     _TIME="2010-04-14 11:12:13.000"

     _LABEL="DIAG"

    />

  </MSG>

</MSGL>

......

 

 

please help me

Best regards,

Mieczysław Kaczor

  • Re: not start MaxDB after ugrade from 7.5 to 7.7
    M. Dijsselbloem
    Currently Being Moderated

    Hi,

     

    Do you see any invalid components when you execute sdbregview -l

     

    Kind regards,

     

    Mark Dijsselbloem

    • Re: not start MaxDB after ugrade from 7.5 to 7.7
      Mieczyslaw Kaczor
      Currently Being Moderated

      Server Utilities    /sapdb/programs    7.7.04.28     64 bit    valid

      DB Analyzer         /sapdb/programs    7.7.04.28     64 bit    valid

      PCR 7300            /sapdb/programs    7.3.00.58               valid

      PCR 7301            /sapdb/programs    7.3.01.22               valid

      PCR 7500            /sapdb/programs    7.5.00.50     64 bit    valid

      SAP Utilities       /sapdb/programs    7.7.04.28     64 bit    valid

      Base                /sapdb/programs    7.7.04.28     64 bit    valid

      Redist Python       /sapdb/programs    7.7.04.28     32 bit    valid

      JDBC                /sapdb/programs    7.6.05.06               valid

      Messages            /sapdb/programs    MSG 0.7113              valid

      ODBC                /sapdb/programs    7.7.04.28     64 bit    valid

      Database Kernel     /sapdb/HXR/db      7.7.04.28     64 bit    valid

      SQLDBC 77           /sapdb/programs    7.7.04.28     64 bit    valid

      Loader              /sapdb/programs    7.7.04.28     64 bit    valid

      SQLDBC              /sapdb/programs    7.7.04.28     64 bit    valid

      SQLDBC 76           /sapdb/programs    7.6.05.09     64 bit    valid

      Fastload API        /sapdb/programs    7.7.04.28     64 bit    valid

      PCR 7403            /sapdb/programs    7.4.03.50     64 bit    valid

  • Re: not start MaxDB after ugrade from 7.5 to 7.7
    Markus Doehr
    Currently Being Moderated

    > <MSGL _NO="5069" _PROCESS="417880" _THREAD="0x1" _TIME="2010-04-14 11:12:13.000">

    >   <MSG _NO="1" _TYPE="Error" _ID="1" _COMP="SAPDBMem" TEXT="Out of memory needed $BYTESNEEDED$ for $DESCRIPTION$">

     

    How big is your CacheSize set?

     

    Btw: you can simply execute "protconv" in the wrk directory to create a readable output.

     

     

     

     

    Markus

    • Re: not start MaxDB after ugrade from 7.5 to 7.7
      Mieczyslaw Kaczor
      Currently Being Moderated

      CacheMemorySize: 375000

      - increase (500000, 800000) does not change anything

      • Re: not start MaxDB after ugrade from 7.5 to 7.7
        Markus Doehr
        Currently Being Moderated

        Is this 32bit?

         

         

         

        Markus

        • Re: not start MaxDB after ugrade from 7.5 to 7.7
          Mieczyslaw Kaczor
          Currently Being Moderated

          no,

          it's Unix 64-bit

          • Re: not start MaxDB after ugrade from 7.5 to 7.7
            Markus Doehr
            Currently Being Moderated

            Please try to start the database, then execute

             

            protconv > knldiag.txt

             

            and post the last lines containing the error.

             

             

             

            Markus

            • Re: not start MaxDB after ugrade from 7.5 to 7.7
              Mieczyslaw Kaczor
              Currently Being Moderated

              Thread    0x1 Task      -  2010-04-14 12:27:53     RTE        20235:  Dump of all kernel parameters done

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR SAPDBMem       1:  Out of memory needed 152 for Missing log mirror,ALLOCATOR=RTEMem_RteAllocator,_FILE=RTEConf_VolumeConfiguration.cpp,_LINE=992

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:  -


              > Symbolic stack backtrace <----

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:  Using 'PPC frame trace' for stack tracing

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    0: TraceStackSymbolic__17RTEDiag_CallStackFPC19RTEDiag_RegisterSet + 0x5c

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x00000001006ea3dc (0x00000001006ea380+0x5c) FP: 0x0fffffffffffea40

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    1: TerminateOnStartupFailure__17RTEKernel_StartupFiRC20SAPDBErr_MessageList + 0x5c

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x000000010139b388 (0x000000010139b32c+0x5c) FP: 0x0fffffffffffeb00

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    2: TerminateOnStartupFailure__17RTEKernel_StartupFRC20SAPDBErr_MessageList + 0x14

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x00000001013a04bc (0x00000001013a04a8+0x14) FP: 0x0fffffffffffebb0

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    3: ThreadMain__17RTEKernel_StartupFv + 0x9b4

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x00000001013a02bc (0x000000010139f908+0x9b4) FP: 0x0fffffffffffec20

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    4: ThreadMain__23RTEKernel_StartupThreadFv + 0x18

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x00000001013a1d58 (0x00000001013a1d40+0x18) FP: 0x0ffffffffffff4e0

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    5: CThreadMain__16RTEThread_ThreadFPv + 0xb4

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x000000010091c0b8 (0x000000010091c004+0xb4) FP: 0x0ffffffffffff550

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    6: AppointMainThreadToThreadObject__16RTEThread_ThreadFiR20SAPDBErr_MessageList + 0xcc

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x000000010091baa8 (0x000000010091b9dc+0xcc) FP: 0x0ffffffffffff650

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    7: AppointMainThreadToThreadObject__16RTEThread_ThreadFR20SAPDBErr_MessageList + 0x14

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x000000010139e6b0 (0x000000010139e69c+0x14) FP: 0x0ffffffffffff870

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    8: Main__17RTEKernel_StartupFv + 0x250

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x000000010139dcac (0x000000010139da5c+0x250) FP: 0x0ffffffffffff8e0

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:    9: main + 0x1c

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x0000000100eb8910 (0x0000000100eb88f4+0x1c) FP: 0x0ffffffffffffc60

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:       -


              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:   10: __start + 0x90

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           SFrame: IP: 0x00000001000002d4 (0x0000000100000244+0x90) FP: 0x0ffffffffffffcd0

              Thread    0x1 Task      -  2010-04-14 12:27:53 ERR DIAG           0:           Module: kernel

              • Re: not start MaxDB after ugrade from 7.5 to 7.7
                Markus Doehr
                Currently Being Moderated

                Ok - still not more information

                 

                Please post starting from the lines containing the first "ERR".

                 

                 

                 

                Markus

                • Re: not start MaxDB after ugrade from 7.5 to 7.7
                  Mieczyslaw Kaczor
                  Currently Being Moderated

                  This is it, previously is:

                  .....

                                             2010-04-14 12:27:53     RunTime       15:   UseUnicodeColumnCompression=NO

                                             2010-04-14 12:27:53     RunTime       15:   USEVARIABLEINPUT=YES

                                             2010-04-14 12:27:53     RunTime       15:   UseVectorIOSimulation=NEVER

                                             2010-04-14 12:27:53     RunTime       15:   UseVolumeLock=YES

                                             2010-04-14 12:27:53     RunTime       15:   USE_COEXISTENCE=NO

                                             2010-04-14 12:27:53     RunTime       15:   USE_COROUTINES=YES

                                             2010-04-14 12:27:53     RunTime       15:   USEIOPROCS_ONLY=NO

                                             2010-04-14 12:27:53     RunTime       15:   USE_OPEN_DIRECT=NO

                                             2010-04-14 12:27:53     RunTime       15:   USE_SYSTEM_PAGE_CACHE=YES

                                             2010-04-14 12:27:53     RunTime       15:   VolumeFormattingMode=PARALLEL

                                             2010-04-14 12:27:53     RunTime       15:   VolumeIOQueuesForHighPriority=0

                                             2010-04-14 12:27:53     RunTime       15:   VolumeIOQueuesForLowPriority=1

                                             2010-04-14 12:27:53     RunTime       15:   VolumeIOQueuesForMediumPriority=9

                                             2010-04-14 12:27:53     RunTime       15:   VOLUMENO_BIT_COUNT=8

                                             2010-04-14 12:27:53     RunTime       15:   WORKDATASIZE=8192

                                             2010-04-14 12:27:53     RunTime       15:   WORKSTACKSIZE=32768

                                             2010-04-14 12:27:53     RunTime       15:   XP_ConverterStripes=0

                                             2010-04-14 12:27:53     RunTime       15:   XP_DATA_CACHE_RGNS=0

                                             2010-04-14 12:27:53     RunTime       15:   XP_MAXPAGER=0

                  Thread    0x1 Task      -  2010-04-14 12:27:53     RTE        20235:  Dump of all kernel parameters done

                  .....

                  • Re: not start MaxDB after ugrade from 7.5 to 7.7
                    Markus Doehr
                    Currently Being Moderated

                    I meant the first line containing an error (an ERR next to the date and time).

                     

                     

                     

                    Markus

                    • Re: not start MaxDB after ugrade from 7.5 to 7.7
                      Mieczyslaw Kaczor
                      Currently Being Moderated

                      2010-04-14 12:27:53 ERR SAPDBMem       1:  Out of memory needed 152 for Missing log mirror,ALLOCATOR=RTEMem_RteAllocator,_FILE=RTEConf_VolumeConfiguration.cpp,_LINE=992

                      • Re: not start MaxDB after ugrade from 7.5 to 7.7
                        Markus Doehr
                        Currently Being Moderated

                        It's very difficult to suggest something if you post just fragments...

                         

                        I suggest:

                         

                        Check your operating system kernel parameters against

                         

                        Note 628131 - SAP DB/MaxDB operating system parameters on Unix

                         

                        and also check your shell limits (MaxDB 7.7 needs higher limits than 7.5).

                         

                        If it all does not help open an OSS call (BC-DB-SDB)

                         

                         

                         

                        Markus

                      • Re: not start MaxDB after ugrade from 7.5 to 7.7
                        Lars Breddemann
                        Currently Being Moderated

                        Hi there,

                         

                        as we handle this in a support call already, I propose to update this thread once the solution is found.

                         

                        regards,

                        Lars

                        • Re: not start MaxDB after ugrade from 7.5 to 7.7
                          Mieczyslaw Kaczor
                          Currently Being Moderated

                          OSS replied:

                          "....is a problem with the

                          log volume parameter setup.

                          Although the database does only use one (mirrored) log volume, there

                          are parameters specified for some more:

                          LogVolumeSize002=0

                          LogVolumeSize003=640000

                          ...."

                           

                          I removed these parameters. Result:

                           

                          "

                          >param_checkall

                          OK

                           

                          ---

                          >db_admin

                          OK

                           

                          ---

                          >db_online

                          ERR

                          -24988,ERR_SQL: SQL error

                          -9407,System error: unexpected error

                          3,Database state: OFFLINE

                          Internal errorcode, Error code 6433 "system_error"

                          20028,Initialization of log for 'restart' failed

                          with 'LogSizeHasDecreased'

                          "

                          • Re: not start MaxDB after ugrade from 7.5 to 7.7
                            Lars Breddemann
                            Currently Being Moderated
                            Mieczyslaw Kaczor wrote:

                            >

                            > OSS replied:

                             

                            Nope - I replied to you (I'm the processor of your message).

                            "OSS" never replies to anything, it's always the people that do

                             

                            Let's continue to work on the message tomorrow!

                             

                            regards,

                            Lars

                            • Re: not start MaxDB after ugrade from 7.5 to 7.7
                              Mieczyslaw Kaczor
                              Currently Being Moderated

                              Hello Lars

                              WOW!, is You. )

                               

                              best regards,

                              /MK

                              • Re: not start MaxDB after ugrade from 7.5 to 7.7
                                Lukas Hunana
                                Currently Being Moderated

                                Hi guys,

                                 

                                I have same issue during installation LC 7.7.04 Bld 29 on AIX 6.1, but I'm not using mirrored logfiles.

                                 

                                bash-3.00# tail XCMDOUT.LOG

                                > Subprocess starts at 20110419150429

                                 

                                Execute Command : /sapdb/programs/bin/dbmcli -n sapald -d ALD -u CONTROL,******** db_start

                                Start subprocess as user with uid: root

                                 

                                > Subprocess stops at 20110419150434

                                 

                                ERR

                                -24994,ERR_RTE: Runtime environment error

                                20090,Check knldiag! Kernel exited with '1' before reaching ADMIN state

                                 

                                 

                                bash-3.00# /sapdb/programs/bin/dbmcli -n sapald -d ALD -u CONTROL,********* db_state

                                OK

                                State

                                OFFLINE

                                bash-3.00# /sapdb/programs/bin/dbmcli -n sapald -d ALD -u CONTROL,********* show state

                                OK

                                 

                                Bad magic number in /sapdb/data/wrk/ALD/rtedump_dir/RTEMemory_Table.0: 0x0x found (expected 0x184541191x)

                                No mapping chunk entries found

                                'RTECons_MemoryDumpMapping' instance could not be created

                                Failed to map memory dump files

                                bash-3.00# ls -l /sapdb/data/wrk/ALD/

                                total 520

                                drwxrwx---    3 sdb      sdba            256 Apr 19 15:00 DIAGHISTORY

                                -rw-rw----    1 sdb      sdba         245760 Apr 19 15:00 KnlMsg

                                -rw-rw----    1 sdb      sdba           4096 Apr 19 15:00 KnlMsgArchive

                                -rw-rw----    1 sdb      sdba              0 Apr 19 15:00 dbm.cfg

                                -rw-rw----    1 sdb      sdba          16384 Apr 19 15:07 dbm.prt

                                drwxr-xr-x    2 root     system          256 Mar 15 14:18 lost+found

                                drwxr-x---    2 sdb      sdba            256 Apr 19 15:04 rtedump_dir

                                 

                                If you know what else I should check, please let me know.

                                 

                                Regards,

                                Lukas Hunana

                                • Re: not start MaxDB after ugrade from 7.5 to 7.7
                                  Markus Doehr
                                  Currently Being Moderated

                                  > If you know what else I should check, please let me know.

                                   

                                  Execute

                                   

                                  protconv > knldiag.txt

                                   

                                  And check knldiag.txt.

                                   

                                   

                                   

                                  Markus

                                  • Re: not start MaxDB after ugrade from 7.5 to 7.7
                                    Lukas Hunana
                                    Currently Being Moderated

                                    Hello,

                                     

                                    1st of all ... /sapdb was full, but after I've cleared it, was still not wokring. Than I've checked all permisions and ownership of sdb files. At the end, after few unsuccessfull tries was again /sdb full. so we cleared it and it was working OK after. SO probably ownership/permissions helped, but as we had full /sdb we had not figured out, what exactly helped.

                                     

                                    Regards,

                                    Lukas

                                    • Re: not start MaxDB after ugrade from 7.5 to 7.7
                                      Rashmi Ranjan Patra
                                      Currently Being Moderated

                                      Hi Team,

                                      I faced the same error when I was upgrading the release of livecache from build 17 to build 33 (7.7).

                                       

                                      The error I did was to restore a higher version backup (33) to lower version system (17). As a result of which

                                      Livecache did not get start. even running ./SDBUPD for 17 build or 33 bulid was not working.

                                       

                                      The steps followed by me to solve the issue is as follows:

                                       

                                      1) Restored the livecache backup of source system (which was of 17 build).

                                      2) Then I ran the ./SDBUPD for 17 build package for consistency.

                                      3) Then proceeded with ./SDBUPS for 33 build package which completed successfully.

                                      4) Finally I restored the backup of the target system (which was of 33 build).

                                       

                                      Hope, I am clear. Please let me know the outcome.

                                       

                                      Regards,

                                      Rashmi Ranjan Patra

Actions