Link to home
Start Free TrialLog in
Avatar of Prardhan N
Prardhan NFlag for India

asked on

Offline Backup is failing

Hi All

I need to take an Offline Backup as logging is not enabled on my DB.

But I am failing to take the Offline Db Backup cause Applications are not getting killed.

I have forced the Applications with force command for 10 times,  and  quiesced the DB and Instance.

But still Db Backup command failing.

Below are the Errors I have faced when I run the Backup command.

SQL2413N  Online backup is not allowed because the database is not recoverable
or a backup pending condition is in effect.
SQL2413N  Online backup is not allowed because the database is not recoverable
or a backup pending condition is in effect.
SQL1350N  The application is not in the correct state to process this request.
Reason code="1".
SQL2413N  Online backup is not allowed because the database is not recoverable
or a backup pending condition is in effect.
SQL1035N  The database is currently in use.  SQLSTATE=57019
SQL1035N  The database is currently in use.  SQLSTATE=57019

Any Inputs please with your goodness.
Avatar of Omar Soudani
Omar Soudani

Hello,

Make sure that the values for LOGARCHMETH1 and LOGRETAIN are Logretain and Recovery respectively.
Avatar of Prardhan N

ASKER

Does these parameters change affect the Killing of  Applications ?

Below are my configurations

 Log retain for recovery enabled             (LOGRETAIN) = OFF
 First log archive method                 (LOGARCHMETH1) = OFF
 Options for logarchmeth1                  (LOGARCHOPT1) =
 Second log archive method                (LOGARCHMETH2) = OFF
 Options for logarchmeth2                  (LOGARCHOPT2) =
 Log pages during index build            (LOGINDEXBUILD) = OFF

Any further inputs Please
Hi!

Most likely your database is activated which speeds up the connection process especially the first connection to a database
 Deactivate it using the command
db2 deactivate db yourdbname;

LOGARCHMETH1 is configurable online
but  LOGRETAIN is only configurable "offline" so to activate that change you need to bounce the database (db2stop/db2start).
Make sure that you configure the logfilsiz to a suiteble size. A size of >10000 pages  is recommended depending on the workload.
Also configure logprimary and logsecondary to make sure that active logs on disk can handle your biggest unit of work + all other workload.
Note that Logprimary + Logsecondary <= 256 logfiles. And if you have logfilesiz of 10000 pages then maximum diskspace for the active logfiles = 256*10000* 4K = 10 GB

Regards,
     Tomas Helgi
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.