Data Protector 6.2
Windows Server 2008 R2
While ejecting tapes recently, I started getting errors like the following:
"Internal error: DbaXXXXfunctions."
I've seen this before, so I ran an omnidbcheck -extended. It came back clean. I did a purge of the IDB by removing old sessions, then running a filenames and dcbf purge with -force option. I also ran a purge of the mpos, then a fixmpos, and remap_dcdir. This all took about 3 days to complete because of the size of the IDB. It was about 150 GB in size, and afterwards was about 82 GB. We back up about 190 TB of data, keep each monthly permanently, and have it set to log all, so yeah we have a very large database with a lot of media. When I went to do the writedb/readdb, I did the writedb, and then looked at the media.txt file to see if there were any 0's in the second column, as I've seen that cause that error before. No 0's, so it looked clean from that perspective. I then tried to do the readdb, but got the following error:
C:\>omnidbutil -readdb -mmdb C:\idb_tmp\mmdb -cdb C:\idb_tmp\cdb
Database import will overwrite old database. All data will be lost!
Are you sure (y/n)?y
* Add 1 extension files for tablespace pos.key.
I looked up pos.key in this forum, and came up with this thread:
It mentioned to set the following in the global options file, and stop and re-start services:
DbPosDatLimit=8
DbPosKeyLimit=8
Then it says to extend the tablespaces. So I tried putting these in the global file, restart services, then running the following:
C:\Users\appENTBAKSVC>omnidbutil -extendtblspace pos.dat C:\ProgramData\OmniBack\db40\datafiles\Cdb -maxsize 2047
DONE!
C:\Users\appENTBAKSVC>omnidbutil -extendtblspace pos.key C:\ProgramData\OmniBack\db40\datafiles\Cdb -maxsize 2047
ERROR: It is not allowed to extend the specified tablespace.
I checked the file pos.key, and it is 1.99 GB in size, so it is definitely full. In the thread above, it also mentions that there may be a patch that can be used to allow you to extend this tablespace. We don't have a current support contract for Data Protector anymore because management doesn't want to pay it, so I can't really open a ticket for it. I know that the version I have is out of date, but again, this is not under my control, it is a requirement to be on the version we are on. So my hope is twofold, either find a way to extend this tablespace, or find a way to purge data from it to open space back up in it. What would I do to do this? Do I start mass exporting tapes from the database? Do I need to start a whole new IDB? What is the best way to proceed?
Tony