Database locked due to log full, but no more user tasks

[christian_janson]

Hi,

I'm using MaxDB 7.9.09 on SLES 11.

During the update of a fresh solution manager 7.2 installation via SUM, the update process stopped.The are 3 batch jobs running: DBCLONE1, DBCLONE2 and DBCLONE3. The update process stopped because the log is full; when I try to do a log backup, I get the error message "No session of type 'User' available-24994,ERR_RTE: Runtime environment error2,task limit". I have already increased MAXUSERTASKS, but this seems to need a DB restart.

There are 100 entries in the task list of type "user" like this:

T97    8   7885 User      24901 LOG FULL (246)          0               (s)2389500

T98    8   7885 User      24934 Command wait         no 0        102819 (s)2389500

T99    8   7885 User      24942 LOG FULL (246)          0               (s)2389500

T100   8   7885 User      29003 Vwait          !        0               (s)2389500

T101   8   7885 User       5601 Vwait          !        0               (s)2389500

T102   8   7885 User       5179 LOG FULL (246) !        0               (s)2389500

T103   8   7885 User      11269 LOG FULL (246)          0               (s)2389500

T104   8   7885 User      11270 Command wait         no 0        121464 (s)2389500

T105   8   7885 User       5573 LOG FULL (246) !        0               (s)2389500

Is there a possibility to solve this issue?

Regards,

Christian

[JamesZ · Accepted solution]

Hi Christian,

"LOG FULL", you need to perform a maxdb log volume backup, then the problem will be solved.

Best regards,
James

[christian_janson · Accepted solution]

Hi James,

yes, that's clear, but the root cause is still that there are no user session left. Starting the log backup I get the mentioned error message "No session of type 'User' available-24994,ERR_RTE: Runtime environment error2,task limit". In fact I can't do anything; even the shutdown of the DB is not possible. Every action I try is cancelled with this error message.

Regards,

Christian

[JamesZ · Accepted solution]

hi Christian,

try following workaround:

dbmcli>db_stop
dbmcli>db_offline

dbmcli>db_admin

now perform log backup, afterwards you can bring db online and get rid of log full

Best regards,
James

[christian_janson · Accepted solution]

Hi James,

thanks a lot, that worked for me. Unfortunately the SUM update process was broken by this (the DBCLONE-batch jobs were cancelled), but I expected this. For luck it seems SUM is able to repeat the DBCLONE-step.

Regards,

Christian

[JamesZ · Accepted solution]

Hi Christian,

Great,sorry, I forgot to let you suspend sum before stopping db.
However SUM should be able to handle unexpected situation by himself.

In case any db issue occrus, let me know.

Best regards,
James