If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Reclaimed too much log space

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 10-20-03, 11:06
suakko suakko is offline
Registered User
 
Join Date: Oct 2003
Posts: 2
Reclaimed too much log space

Hi,

we are running on 4-node database (AIX 5.1, v7.2 EEE FP10 64-bit). For some reason, NODE0002 can't release logfiles it's using. Other nodes seems to work just fine.

We've altered and tried almost everything:
- different softmax values
- increased/decreased io_cleaners/io_servers
- increased logfilesize and number of primary/secondary logs
- tried different values of CHNGPGS_THRESH

Now there is 13 gigs logspace for each node, and the database load which causes this situation below is only few hundred megs.

Do you have any ideas?
Many thanks in advance.


----------------------------------------------------------------
Reclaimed too much log space. In use: 89285687 reclaimed: 133660800
Dump File:/db2/D2P/db2dump/1736704.003 DataQLP_DBCB

2003-10-18-17.00.52.463554 Instance:db2d2p Node:002
PID:1769658(db2loggr (D2P) 2) Appid:none
data_protection sqlpgspr Probe:10

Reclaimed too much log space. In use: 65867672 reclaimed: 133660800
Dump File:/db2/D2P/db2dump/1769658.002 DataQLP_DBCB

2003-10-18-17.00.52.880375 Instance:db2d2p Node:002
PID:3792944(db2agntp (D2P) 2) Appid:*N0.db2d2p.031017131745
data_protection sqlpgrsp Probe:80 Database2P

Released too much space: 0000 0000 000e e07d .......}


2003-10-18-17.14.28.096412 Instance:db2d2p Node:002
PID:1097760(db2agntp (D2P) 2) Appid:*N0.db2d2p.031017131801
data_protection sqlpgrsp Probe:20 Database2P

Warning: active log held by dirty pages.
Decrease softmax and/or increase num_iocleaners.

2003-10-18-17.14.28.112647 Instance:db2d2p Node:002
PID:1097760(db2agntp (D2P) 2) Appid:*N0.db2d2p.031017131801
data_protection sqlpgrsp Probe:50 Database2P

Log Full -- active log held by appl. handle 0
End this application by COMMIT, ROLLBACK or FORCE APPLICATION.

2003-10-18-17.14.28.118416 Instance:db2d2p Node:002
PID:1097760(db2agntp (D2P) 2) Appid:*N0.db2d2p.031017131801
data_protection sqlpWriteLR Probe:80 Database2P
DIA3609C Log file was full.

ZRC=0xFFFFD509
-----------------------------------------------------
Reply With Quote
  #2 (permalink)  
Old 10-20-03, 11:13
koganti koganti is offline
Registered User
 
Join Date: Jul 2002
Location: ATL
Posts: 170
What is the LOGRETAIN parameter set for this node ?
Reply With Quote
  #3 (permalink)  
Old 10-21-03, 03:31
suakko suakko is offline
Registered User
 
Join Date: Oct 2003
Posts: 2
Quote:
Originally posted by koganti
What is the LOGRETAIN parameter set for this node ?


Parameter is set (LOGRETAIN) = RECOVERY like in other nodes.
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On