Skip to Content
avatar image
Former Member

db2 archiving struck

Hello All,

I have limited knowledge on db2 database

PRD system 22TB database size

Linux OS

In our Production system ,  /db2/PRD/log_dir/NODE0000/LOGSTREAM0000/

has 700 files accumalated.

/db2/PRD/log_dir  is used by 99% ,

The number of Primary log files configured is 256 files.

since 12 hours the number of files  /db2/PRD/log_dir/NODE0000/LOGSTREAM0000/  remain 700

the rate of archiving is 60 to 80mb/second


1. is it a db2 issue ? as claimed by Back up and Recover team

2. we suspect archiving is not happening , TSM is not moving the file   - we ERP Team claim this

TSM has to archive these files , is this understanding correct ?

The rate of Generation of log files by db2 is more , compared to archiving , hence we see 700 files since 12 hours.

Please suggest how to come our of this situation , if we leave system like this for next 4hours,

system will go'es  down  it will be huge impact

Thanks in advance

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Oct 26, 2015 at 04:47 AM

    Hi Sidhart

    Could you please give the db2diag.log file details,  file location is /db2/SID/db2dump

    mean while check the below note may help you,

    495297 - DB6: Monitoring transaction log

    2141933 - DB6: How to initially trouble shoot transaction log full issue



    Add comment
    10|10000 characters needed characters exceeded

    • Hi

      This is the general behaviour of the db2  for log full,

      you need to do the full analysis of log generation and accordantly you need to add the space,

      yes if log is moving very slow then TSM team need to check it,

      but for the log full we as SAP BASIS and DB2 has be check,

      to handle the log full my note will help you, and you can kill the job which is causing the log full, before system get down,