Failed maxdb 7.8.02.41 patch installation due to log full

[nelis]

Hi there,

I am having an issue where the database was put online and patched without knowing there was a log full situation. What happened is it ran through the installation then switched the database offline and then online again to continue the patching process but couldn't go further. Now I have the problem in that there is a maxdb runtime environment problem and I can't backup the log because of this runtime error.

I have opened a SAP support call but 1st level are not really helpful in these situations and it is taking long to get some help so trying here.

Some information:

MaxDB 7.8.02.35 patched to 7.8.02.41 on 64 bit linux

SAP MaxDB Installation Manager - Database Upgrade 7.8.02.41
***********************************************************


Checking upgrade...
Finding instance type...
Checking mmap support...
Finding starting release...
Finding migration strategy...
Looking for running instances...
Checking paramfile modifications...
Checking volume access...
Checking data consistency for database migration...
Value of MCOD-Parameter is YES
Switching database state to OFFLINE
Preparing package "Base" ...
Preparing package "SQLDBC" ...
Preparing package "SQLDBC 77" ...
Preparing package "Fastload API" ...
Preparing package "SQLDBC 76" ...
Preparing package "SAP Utilities" ...
Preparing package "Server Utilities" ...
Preparing package "Database Kernel" ...
Preparing package "Redist Python" ...
Preparing package "Loader" ...
Preparing package "ODBC" ...
Preparing package "Messages" ...
Preparing package "JDBC" ...
Preparing package "DB Analyzer" ...
Updating package "Base" ...
Updating package "SQLDBC" ...
Updating package "SQLDBC 77" ...
Updating package "Fastload API" ...
Updating package "SQLDBC 76" ...
Updating package "SAP Utilities" ...
Updating package "Server Utilities" ...
Updating package "Database Kernel" ...
Updating package "Redist Python" ...
Updating package "Loader" ...
Updating package "ODBC" ...
Updating package "JDBC" ...
Updating package "DB Analyzer" ...
Running finalize check...
Current database state is OFFLINE
Checking parameters...
Switching database state to ADMIN
Switching database state to ONLINE
ERR: Upgrade failed
ERR: error upgrading
ERR: Finalize upgrade failed: Current database state is OFFLINE
Checking parameters...
Switching database state to ADMIN
Switching database state to ONLINE
Cannot switch database mode, error during dbm command:
db_online
ERR
-24895,ERR_SHUTDOWN: shutdown of database occured
-24994,ERR_RTE: Runtime environment error
6,connection broken server state 6
Looking for error messages in knldiag
No error messages found in knldiag

/sapdb/programs/bin/sdbverify
Checking installation "Global" (/sapdb/programs, 7.8.02.27)
Checking package Installer
Checking package SAP Utilities Compatibility
Checking package Global Listener
Checking package Installation Compatibility
Checking installation "Legacy" (/sapdb/programs, )
Checking installation "CL_SMP" (/sapdb/clients/SMP, 7.8.02.41)
Checking package Base
Checking package SQLDBC
Checking package SQLDBC 77
Checking package Fastload API
Checking package SQLDBC 76
Checking package SAP Utilities
Checking package ODBC
Checking package Messages
Checking package JDBC
Checking installation "SMP" (/sapdb/SMP/db, 7.8.02.41)
Checking package Base
Checking package SQLDBC
Checking package SQLDBC 77
Checking package Fastload API
Checking package SQLDBC 76
Checking package SAP Utilities
Checking package Server Utilities
Checking package Database Kernel
Checking package Redist Python
Checking package Loader
Checking package ODBC
Checking package Messages
Checking package JDBC
Checking package DB Analyzer
ERR:  Failed
ERR:    Checking installation "CL_SMP" failed
ERR:      Directory /sapdb/clients/SMP/data/pipe doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/ipc doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/dbspeed doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/diag doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/fifo doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/pid doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/ppid doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/wrk doesn't exist
ERR:      Directory /sapdb/clients/SMP/data/config doesn't exist

I tried putting the database online but I just see a whole lot of RTEMemory_Chunk files being created in rte_dump directory.

Bit of a mess! At this stage I would be happy just to get the maxdb runtime environment repaired even if I have to do a restore of the database. How do I proceed to fix the failed patch update ?

Any advice appreciated.

Thanks.

Regards,

Nelis

[nelis · Accepted solution]

Thanks to a bit of help from SAP Support(Balázs) I was able to get my system running again.

I couldn't do a log backup with the log full situation because of the runtime environment error but thankfully was able to do a data backup in ADMIN state. After this I cleared the log file and then finally I was able to put the database back ONLINE. I then repeated the same patch installation which completed successfully this time. All is well.