Hi,
Today I was adding extents in one of the DB's when I found the error:
I saw that billingDB_13.d5 has been created in the disk but it was not added to the database .st file. I deleted billingDB_13.d5 and tried again but no luck. We have approx 100 GB space left for variable extents of this DB so i started the DB and services. Later i saw the following error in the DB log file:
billingDB_13.d4 is a variable extent. Please see the relevent part of DB .st file:
I searched for the calculation of block usage and found that this extent can take upto 137GB of data. Where as currently the data written in .d4 variable extent is approx 19GB. I couldn't add fixed extent in time due to some other activities in line and absence of DR/failover setup.
The block size details are:
Progress DB details:
Version: 9.1E
Storage: NetApp
OS: Solaris 10
QUESTION: This DB is written at approx 2GB per day. How many days do I have before the block usage reaches 100%?
What impact will I see if it reaches 100%?
Can't upgrade Progress Version. No DR/failover setup and very tough to get a downtime, is thee any other way to evade this than doing dump&load or Index rebuild (DB size is approx 600GB)?
Today I was adding extents in one of the DB's when I found the error:
Code:
Prod01:PROGRESS:/live/db/billingDB:> prostrct add billingDB add_06102014.st
Formatting extents:
size area name path name
524288 AlphaData /live/db/billingDB/data01/billingDB_7.d3 00:00:10
16 AlphaData /live/db/billingDB/data01/billingDB_7.d4 00:00:00
12800000 billData /live/db/billingDB/data01/billingDB_9.d5 00:04:08
16 billData /live/db/billingDB/data01/billingDB_9.d6 00:00:00
3780000 billIndex /live/db/billingDB/index01/billingDB_10.d5 00:01:16
16 billIndex /live/db/billingDB/index01/billingDB_10.d6 00:00:00
3780000 NewChargeData /live/db/billingDB/data01/billingDB_13.d5 SYSTEM ERROR: Attempt to read block 256 which does not exist. (210)
** Save file named core for analysis by Progress Software Corporation. (439)
Quit (core dumped)
I saw that billingDB_13.d5 has been created in the disk but it was not added to the database .st file. I deleted billingDB_13.d5 and tried again but no luck. We have approx 100 GB space left for variable extents of this DB so i started the DB and services. Later i saw the following error in the DB log file:
Code:
05:04:27 Usr 48: bkxtn: WARNING: Area: 13 extent /live/db/billingDB/data01/billingDB_13.d4 has reached the 80% threshold for block usage - current block hiwater 14640364
billingDB_13.d4 is a variable extent. Please see the relevent part of DB .st file:
Code:
#
d "NewChargeData":13,128 /live/db/billingDB/data01/billingDB_13.d1 f 57671680
d "NewChargeData":13,128 /live/db/billingDB/data01/billingDB_13.d2 f 29014656
d "NewChargeData":13,128 /live/db/billingDB/data01/billingDB_13.d3 f 10240000
d "NewChargeData":13,128 /live/db/billingDB/data01/billingDB_13.d4
#
I searched for the calculation of block usage and found that this extent can take upto 137GB of data. Where as currently the data written in .d4 variable extent is approx 19GB. I couldn't add fixed extent in time due to some other activities in line and absence of DR/failover setup.
The block size details are:
Code:
Database Status:
Database version number: 8283
Database state: Open (1)
Database damaged flags: None (0)
Integrity flags: None (0)
Database block size (bytes): 8192
Total number of database blocks: 104678799
Database blocks high water mark: 81463973
Free blocks below highwater mark: 296
Record blocks with free space: 264
Before image block size (bytes): 8192
Progress DB details:
Version: 9.1E
Storage: NetApp
OS: Solaris 10
QUESTION: This DB is written at approx 2GB per day. How many days do I have before the block usage reaches 100%?
What impact will I see if it reaches 100%?
Can't upgrade Progress Version. No DR/failover setup and very tough to get a downtime, is thee any other way to evade this than doing dump&load or Index rebuild (DB size is approx 600GB)?