BI exceeded

greeshma

Member
Hi All,

My client db went down this weekend due to issue "there is no space to exceed bi".
2GB is the size given for bi.We have sheduled a back up of server in every hour.

At that situvation i tried to truncate bi (without forcefully) , but that returned a error.(Sorry i dont remember error number). Then we truncated forcefully and restarted db.

Some information from db log is given below,please help me to confirm my doubts given below
1.Why normal trucate gives an error, Is that need free space in the allowed file structure
2.Is backup failure caused bi increase?

A successfull back up is given in green color.
The staements with problem is given in different color

[2013/06/15@19:15:01.879+0200] P-19269 T-0 I BACKUP 15: (-----) Login by root.
[2013/06/15@19:15:04.643+0200] P-19269 T-0 I BACKUP 15: (12850) Backup blocks will be written to /scratch/LastBackup.probk.
[2013/06/15@19:15:04.650+0200] P-19269 T-0 I BACKUP 15: (1362) Full backup started.
[2013/06/15@19:15:04.655+0200] P-19269 T-0 I BACKUP 15: (6686) 246589 active blocks out of 246599 blocks in /db/celdb/dsSHP will be dumped.
[2013/06/15@19:15:04.655+0200] P-19269 T-0 I BACKUP 15: (6688) 76288 BI blocks will be dumped.
[2013/06/15@19:15:04.657+0200] P-19269 T-0 I BACKUP 15: (9285) Backup requires an estimated 2.5 GBytes of media.
[2013/06/15@19:15:04.657+0200] P-19269 T-0 I BACKUP 15: (9286) Restore would require an estimated 323208 db blocks using 315.3K of media.
[2013/06/15@19:15:04.664+0200] P-19269 T-0 I BACKUP 15: (5459) Begin backup of Before Image file(s).
[2013/06/15@19:15:07.851+0200] P-19269 T-0 I BACKUP 15: (5460) End backup of Before Image file(s).
[2013/06/15@19:15:07.858+0200] P-19269 T-0 I BACKUP 15: (5461) Begin backup of Data file(s).
[2013/06/15@19:15:35.276+0200] P-19269 T-0 I BACKUP 15: (5462) End backup of Data file(s).
[2013/06/15@19:15:35.283+0200] P-19269 T-0 I BACKUP 15: (13625) Wrote a total of 9507 backup blocks using 2.5 GBytes of media.
[2013/06/15@19:15:35.308+0200] P-19269 T-0 I BACKUP 15: (1364) Full backup successfully completed.
[2013/06/15@19:15:35.330+0200] P-19269 T-0 I : (453) Logout by root on batch.
[2013/06/15@20:15:01.898+0200] P-31306 T-0 I BACKUP 15: (-----) Login by root.
[2013/06/15@20:15:05.300+0200] P-31306 T-0 I BACKUP 15: (12850) Backup blocks will be written to /scratch/LastBackup.probk.
[2013/06/15@20:15:05.305+0200] P-31306 T-0 I BACKUP 15: (1362) Full backup started.
[2013/06/15@20:15:05.310+0200] P-31306 T-0 I BACKUP 15: (6686) 253558 active blocks out of 253575 blocks in /db/celdb/dsSHP will be dumped.
[2013/06/15@20:15:05.310+0200] P-31306 T-0 I BACKUP 15: (6688) 168384 BI blocks will be dumped.
[2013/06/15@20:15:05.316+0200] P-31306 T-0 I BACKUP 15: (9285) Backup requires an estimated 3.2 GBytes of media.
[2013/06/15@20:15:05.316+0200] P-31306 T-0 I BACKUP 15: (9286) Restore would require an estimated 422374 db blocks using 412.1K of media.
[2013/06/15@20:15:05.326+0200] P-31306 T-0 I BACKUP 15: (5459) Begin backup of Before Image file(s).
[2013/06/15@20:15:21.164+0200] P-31306 T-0 I BACKUP 15: (5460) End backup of Before Image file(s).
[2013/06/15@20:15:21.171+0200] P-31306 T-0 I BACKUP 15: (5461) Begin backup of Data file(s).
[2013/06/15@20:15:49.749+0200] P-31306 T-0 I BACKUP 15: (5057) Backup failed due to EOF during next output device request.
[2013/06/15@20:15:49.757+0200] P-31306 T-0 I BACKUP 15: (5462) End backup of Data file(s).
[2013/06/15@20:15:49.810+0200] P-31306 T-0 I BACKUP 15: (1617) Backup terminated due to errors.
[2013/06/15@20:15:49.832+0200] P-31306 T-0 I : (453) Logout by root on batch.
[2013/06/15@20:21:10.318+0200] P-26561 T-0 I SRV 2: (739) Logout usernum 85, userid 112, on QSGRD111.
[2013/06/15@20:24:24.661+0200] P-26561 T-0 I SRV 2: (742) Login usernum 85, userid root, on qsdts.quest.sh.rccl.com batch using TCP/IP IPV4 address 172.29.2.20.
[2013/06/15@20:24:24.916+0200] P-26561 T-0 I SRV 2: (739) Logout usernum 85, userid root, on qsdts.quest.sh.rccl.com batch.
[2013/06/15@20:24:24.924+0200] P-26561 T-0 I SRV 2: (742) Login usernum 85, userid root, on qsdts.quest.sh.rccl.com batch using TCP/IP IPV4 address 172.29.2.20.
[2013/06/15@20:25:27.999+0200] P-26561 T-0 I SRV 2: (739) Logout usernum 85, userid root, on qsdts.quest.sh.rccl.com batch.
[2013/06/15@20:34:01.754+0200] P-26561 T-0 I SRV 2: (742) Login usernum 85, userid root, on qsdts.quest.sh.rccl.com batch using TCP/IP IPV4 address 172.29.2.20.
[2013/06/15@20:34:01.000+0200] P-26561 T-0 I SRV 2: (739) Logout usernum 85, userid root, on qsdts.quest.sh.rccl.com batch.
[2013/06/15@20:34:02.015+0200] P-26561 T-0 I SRV 2: (742) Login usernum 85, userid root, on qsdts.quest.sh.rccl.com batch using TCP/IP IPV4 address 172.29.2.20.
[2013/06/15@20:34:31.889+0200] P-28617 T-1115856 I ABL 13: (10601) SYSTEM ERROR: Attempted to exceed maximum size on file /bi/celbi/dsSHP.b1.
[2013/06/15@20:34:31.894+0200] P-28617 T-1115856 F ABL 13: (854) ** Insufficient disk space to extend the before-image file.
[2013/06/15@20:34:31.915+0200] P-13184 T-0 I SRV 7: (2520) Stopped.
[2013/06/15@20:34:31.915+0200] P-23150 T-0 I BIW 11: (2520) Stopped.
[2013/06/15@20:34:31.946+0200] P-23140 T-0 I APW 9: (453) Logout by root on batch.
 

TomBascom

Curmudgeon
By forcing the bi truncate you have corrupted your client's db.

The right thing to have done would have been either:

1) add disk space and allow normal crash recovery to complete

Or

2) restore from backup and roll forward your after-image files

In the future you should use the -bithold parameter to prevent the bi file from growing to more than 25% of the available space on the file system holding the bi file. Also enable large files and make sure that there is a variable bi extent.

I don't understand why you are backing up every hour but your backups are failing because you do not have enough disk space.
 
Top