We are getting warning from OPS that DBID 5 IXX is reaching 95% full. In the MUF joblog, I see VIRTUAL 005,150M is defined, which tells me this is an accounting IXX and it is temporary.
In the past we had a similar issue against the TTM, and it was determined there was a high water mark of which OPS triggered the message. I recall we talked about a VIRTUAL_DYNAMIC_EXTEND, but we ended up recycling the MUF in a couple of days, and life was good.
Also, somehow, a user was identified with a bad query, and this was addressed by the DBA. I don't know if the current issue is similar to the previous issue, but I do need to know, since this is temporary space, do I need to worry about this, and if so, what is the fix?
This is a production MUF, so we can't recycle this anytime soon. Also, under SYSVIEW, I see no signs of stress from the MUF or the DB Server.
Accounting table A02 reached 100% full.
Note that DBID 05 is defined Virtual 05,150M
Customer was getting the following errors:
- Description: Customer is getting the following error in Accounting
DB01102E - UNEXPECTED 07(035) RETURN CODE ON A02 TABLE FOR ADDIT REQUEST
DB01103I - ACCOUNTING FOR A02 TABLE DISABLED
DB01107W - 01052 ACCOUNTING ENTRIES LOST FOR TABLE A02 DUE TO FAILURE
z/os, CA Datacom DB 15.1
VIRTUAL_DYNAMIC_EXTEND can be used to grow the virtual area.
This console command can be via MVS MODIFY or DBUTLTY CONSOLE API or SQL CONSOLE INSERT
This command prepares the characteristics you want to use for the virtual dynamic extend to be consumed when the data area or index area becomes full.
Unlike DASD you can have more than 16 extents when you do this MRDF data areas that are virtual. you can have up to 65535 extents when using this command.
Example of this command
COMM OPTION=CONSOLE, OPTION2='VIRTUAL_DYNAMIC_EXTEND 005,A02,1000000000,10'
This will allow DBID 5 area A02 to grow by 1B bytes each time up to 10 times. Each time the additional 1Billion bytes is consumed MUF will do a dynamic extend to get another 1 billion bytes up to 10 times or until you change any of these values by a new execution of the VIRTUAL_DYNAMIC_EXTEND console command
This storage comes from 64 bit storage
Note1- that the OPTION2 command is effective when the MUF is UP.
It will have to be re-executed after recycling MUF unless you change/increase the MUF Startup parameter (VIRTUAL 05,150 in this case).
Note2- You will need to execute the same OPTION2 against other Accounting Table/Area if some gets the same rc 7 symptom.
Note3- The command is available with CA Datacom/DB 15.1