Highlighted
Absent Member.
Absent Member.
3537 views

Database problem.

Hi,

Two erreor har begin to frequently appear when backups ir running.


The first error:


From DP session

[Major] From: BSM@aldpce02.lfnet.se "PRM_e75h0002" Time: 31/10/2009 10:17:36
[61:4039] Following error occurred while storing detail catalog
information for device "VLS02"
with loaded medium "0ab415ea:4ac8e37b:21e0:0008" [[LF406] LF406]
to Data Protector Internal Database:
Database internal error - see debug.log for details.
From this point on, all objects on this medium
will have logging switched to "No Log".

From debug.log


10/31/09 10:17:36 BSM.15405.0 ["db/dc/dcfb/dcfb.c /main/dp55/dp55_fix/2":133] A.05.50 bPHSS_35168
VELOCIS DB ERROR [6] internal error [-22] illegal attempt to access unlocked record/set (S_NOTLOCKED)





The second error:


From DP session

Major] From: CSM@aldpce02.lfnet.se "Copy_DP13" Time: 03/11/2009 12:24:09
[61:4039] Following error occurred while storing detail catalog
information for device "MH-ESL-E_02_tape3"
with loaded medium "0ab415ea:4a574054:5392:0001" [[MH1593L3] MH1593L3]
to Data Protector Internal Database:
Database internal error - see debug.log for details.
From this point on, all objects on this medium
will have logging switched to "No Log".



From debug.log

11/03/09 12:24:09 CSM.3340.0 ["db/dbutil.c /main/dp55/dp55_patch/1":962] A.05.50 bPHSS_35168
VELOCIS DB ERROR [18] internal error [-14] member already owned (S_ISOWNED)

Seems to be some kind of database problem. I have found some threats with this problem but, no solution. DB check, importing media etc. do not semms to help.

Anyone who has seen this problem and, has found a solution.

/leif




0 Likes
11 Replies
Highlighted
Absent Member.
Absent Member.

Is there space on the IDB?

The times I had this message: From this point on, all objects on this medium
will have logging switched to "No Log"

no matter the secondary messages, or the debug.log messages, it is always the same, at least on my cases, by extending the IDB I solved my issues.
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi,

Post the output for:
opt/omni/lbin>./omnidbutil -info
opt/omni/lbin>./omnidbutil -extendinfo

Regards
Please assign a kudo to this post, if you find it useful.
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi,

The database of this Cell Server is actually very large but, as I can see this is not a space problem.

Attached is the output from the omnidbutil command.
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi,

You need to add:
one fn3.ext
one fn4.ext
also add one more fnames.dat , next is fnames.dat9.

Try this and let me know if the problem gone.


Regards.
Please assign a kudo to this post, if you find it useful.
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi,

I have added extension for ext4 and fnames but ext3 had already reached the limits. Will see if this makes any sense or, next step is to purge the database.

I man still doubtful if this is a space problem but, it can be worth a try.

/leif
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Hi,

You can modify the number of fnx.ext in the global file.
Just modify to 6 or 7 and stop and start services.

and is good idea thinks in purge your idb.

finally , what vercion of DP do you have?
do you patches on you system?

Thanks.
Please assign a kudo to this post, if you find it useful.
0 Likes
Highlighted
Absent Member.
Absent Member.

Hi,

DP version is 5.5.

Can't find any parameter for changing the number of extension files in the global options.

0 Likes
Highlighted
Absent Member.
Absent Member.

DbFn.ExtLimit
0 Likes
Highlighted
Absent Member.
Absent Member.

You need to writedb the database out, omnidbinit and recreate the extensions, and then readdb the database back in to find out just exactly how much of that 4GB of the database tables is in play.

You can see the records used / records created for filenames is down around 75%, so it's possible fn3.ext1 might come back afterwards at only about 3GB used.

The errors seem to imply some kind of out of space errors with the database. But the CS patch on that system is really, really old. Might just be operational defects we've already fixed.

That your space usage has run up to the max means you definitely have corruption with the object and session data that was active at the time the space was maxed out. That can carry over to later activities with broken chains. Back to the writedb/readdb and don't let tables max out.

Base file plus 3 extensions (8GB) is the hard limit in 6.0 for the auxillary cdb tables. Not sure for 5.5. 32GB for 6.1x. And it's a lot easier to add extension files in 6.x 🙂

Thanks,
Scott
0 Likes
Highlighted
Absent Member.. Absent Member..
Absent Member..

I had exact issue..all my ext maxed out..no way to add new ones and we lived with it..now, time to restore...only way is to export and import the catalogue in order to be able to browse for files and folders but getting
[65:6] Internal Database layer reports:
"Database internal error - see debug.log for details."

and in debug.log
VELOCIS DB ERROR [6] internal error [-22] illegal attempt to access unlocked record/set S_NOTLOCKED)

System Info
1) A.06.00 bDPWIN_00407
2)Windows 2003 AS SP2

Any tips how to get restore work? TIA...
0 Likes
Highlighted
New Member.

was the problem ever solved??
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.