Dear Friend,


I already configure my DB2 database to be online backup using logretain on with option LOGARCHMETH1 = VENDOR:/usr/openv/netbackup/bin/nbdb2.sl64


Backup is runing smothly weekly "Full Online Backup", but i get a concern from Netbackup so many archived logs send from db2 to NBUbecause of Log archiving "LOGARCHMETH1".

Is there any way to avoid this frequent archiving which is consuming NBU resourses and create so many queues (300 daily).


Catalog cache size (4KB) (CATALOGCACHE_SZ) = 260
Log buffer size (4KB) (LOGBUFSZ) = 100
Log file size (4KB) (LOGFILSIZ) = 1024
Number of primary log files (LOGPRIMARY) = 13
Number of secondary log files (LOGSECOND) = 4
Changed path to log files (NEWLOGPATH) =
Path to log files = /var/mqsi/wmbprd/wmbprd/NODE0000/SQL00001/SQLOGDIR/
Overflow log path (OVERFLOWLOGPATH) =
Mirror log path (MIRRORLOGPATH) =
First active log file = S0000012.LOG
Block log on disk full (BLK_LOG_DSK_FUL) = NO
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
Log retain for recovery enabled (LOGRETAIN) = OFF
First log archive method (LOGARCHMETH1) = VENDOR:/usr/openv/netbackup/bin/nbdb2.sl64
Options for logarchmeth1 (LOGARCHOPT1) =
Second log archive method (LOGARCHMETH2) = OFF
Options for logarchmeth2 (LOGARCHOPT2) =
Log pages during index build (LOGINDEXBUILD) = OFF

Note :
For my Database I don't need any logs to be backed up, I just configured like above to be able to take online backup because our application is 24/7 with no downtime which means no offline backup.




Regards,
Nasser

Log is archived when it's full. So, you can try increasing LOGFILSIZ.

Log is also closed and archived at the end of an online backup. Check DB2_DISABLE_FLUSH_LOG if you want to disable this behaviour (I'm not sure if this is supported in newer versions).

You need archived logs in case of restore.

An alternative is not to use Netbackup to archive the logs.

Andy

This is easy to solve. Revoke Insert, Update, and Delete grants made to the users, and then DB2 will not have to log these activities anymore.

Dears

Thanks for your reply , also i want to show some documents by IBM

This suggests that the database was inactive and then activated , this will trigger a log to be truncated as per documention :

DB2 Database for Linux, UNIX, and Windows

"If a database has not been activated (by way of the ACTIVATE DATABASE command), DB2 truncates the current log file when all applications have disconnected from the database. The next time an application connects to the database, DB2 starts logging to a new log file. If many small log files are being produced on your system, you might want to consider using the ACTIVATE DATABASE command. This not only saves the overhead of having to initialize the database when applications connect, it also saves the overhead of having to allocate a large log file, truncate it, and then allocate a new large log file."

Do you think this will make difference?

Regards,
nasser

What do you think?