Skip to Content

Take care to correctly set log path after DB6 redirect restore

Hello community,

As you know, we need to update the following log related parameters such as OVERFLOWLOGPATH \ MIRRORLOGPATH after DB6 redirect restore. However, you may set them wrong if you do this thing the first time.

You may hold the idea that I can refer to the log settings in the source system to set them in the target system 🙂 , so you check the configurations on source system and they look like that:

source_host:db2src 50> db2 get db cfg for src | grep -i log

Path to log files                                       = /db2/SRC/log_dir/NODE0000/LOGSTREAM0000/

Overflow log path                     (OVERFLOWLOGPATH) = /db2/SRC/db2overflow/NODE0000/LOGSTREAM0000/

Mirror log path                         (MIRRORLOGPATH) = /db2/SRC/log_dir2/NODE0000/LOGSTREAM0000/

HOWEVER, you should not just update them with the value above.

The right way should be:

target_host:db2tgr 120> db2 update db cfg for tgr using MIRRORLOGPATH /db2/TGR/log_dir2

target_host:db2tgr 120> db2 update db cfg for tgr using FAILARCHPATH /db2/TGR/log_fail/

It takes me some effort to change back after facing the wrong settings.

Digressions: Update parameter NEWLOGPATH to /db2/TGR/log_dir within the generated restore script before execute it on target system.

Wish this blog can help you to avoid such kind of thing. 🙂

Best Regards,

Ning Tong

Be the first to leave a comment
You must be Logged on to comment or reply to a post.