Absent Member.
Absent Member.
702 views

Error with import Catalog with Dp 5.5

Jump to solution
Hi all,
i've tryed to import a catalog for restore but there 's an error:
[Normal] From: MMA@sanman "LTO3 - sanman" Time: 30/01/2007 13:50:22
STARTING Media Agent "LTO3 - sanman"

[Normal] From: MMA@sanman "LTO3 - sanman" Time: 30/01/2007 13:50:24
By: UMA@sanman@scsi2:0:2:0
Loading medium from slot 11 to device Tape0:0:2:1C

[Normal] From: MSM@sanman "LTO3 - sanman" Time: 30/01/2007 13:50:55
Data Protector medium "Mensile_Nov06" found.

[Critical] From: MSM@sanman "LTO3 - sanman" Time: 30/01/2007 16:56:08 [65:6] Internal Database layer reports:
"Internal error: CtXXXX functions."

[Normal] From: MMA@sanman "LTO3 - sanman" Time: 30/01/2007 16:58:08
By: UMA@sanman@scsi2:0:2:0
Unloading medium to slot 11 from device Tape0:0:2:1C

[Normal] From: MMA@sanman "LTO3 - sanman" Time: 30/01/2007 16:58:21
ABORTED Media Agent "LTO3 - sanman"


============================================================================
0 media out of 1 successfully imported.
============================================================================

Thanks a lot in advance.

Regards...
Alberto
0 Likes
1 Solution

Accepted Solutions
Absent Member.
Absent Member.
Ciao Alberto,

I saw that error more times, I refer to "Internal error: CtXXXX functions.". One of these times the reason was that the medium was already in IDB. Is that medium (that you want to import catalog) in IDB already?
You can try to export/import again the entire medium and not just the catalog.

Did you try 'omnidbcheck -extended' to check the database? Does it report any errors? You have to run that in exclusive mode.

Best regards,
Fabio
WISH? IMPROVEMENT!

View solution in original post

0 Likes
12 Replies
Absent Member.
Absent Member.
Ciao Alberto,

I saw that error more times, I refer to "Internal error: CtXXXX functions.". One of these times the reason was that the medium was already in IDB. Is that medium (that you want to import catalog) in IDB already?
You can try to export/import again the entire medium and not just the catalog.

Did you try 'omnidbcheck -extended' to check the database? Does it report any errors? You have to run that in exclusive mode.

Best regards,
Fabio
WISH? IMPROVEMENT!

View solution in original post

0 Likes
Absent Member.
Absent Member.
Ciao Fabio,
I've 3 media must be imported in my IDB.
I've imported one but when i see IDB for choose my backup set for restore i dont't found this media with restore set.Why ?
I would import the another two but in a one of that this error occour.
These media aren't imported anymore in my IDB.
Alberto.
0 Likes
Absent Member.
Absent Member.
Ciao Alberto,

if you don't see data on Restore section then I suppose that was purged from IDB. So it's normal you have to import that again. Are you sure are they the correct media to import? Have you tried to export/import the media which obtains that error?

If you need soon data on that media, you can try 'List From Media' (however consider that doesn't work for integrations, so I suppose you have filesystem data on media):

Open GUI ---> clieck on Restore section
and from Actions ---> List From Media

Best regards,
Fabio
WISH? IMPROVEMENT!
0 Likes
Absent Member.
Absent Member.
hi Fabio,
today afternoon i've launched another media import catalog and it's still working.
See you tomorrow for the tests which you propose.
Thanks a lot.
Alberto....
0 Likes
Absent Member.
Absent Member.
Ok Alberto,

just try to export/import that media which obtains the error (medium "Mensile_Nov06") and I think you will solve the problem.

Anyway ok, see you tomorrow here.

Best regards,
Fabio
WISH? IMPROVEMENT!
0 Likes
Absent Member.
Absent Member.
Hi Fabio, yesterday i've started another import catalog of medium never import before it's called Mensile_Ottobre06.
I've launched the command C:\Program Files\OmniBack\bin>omnidbcheck -extended

Check Level Mode Status
==================================================
Core -core OK
Filenames -filenames OK
DCBF(presence and size) -bf OK
SIBF(readability) -sibf OK
OMNIDC(consistency) -dc Corrupted: 2 major errors detected
DONE!

This error occour.
Best regard!
Alberto
0 Likes
Absent Member.
Absent Member.
Hi Alberto,

so the IDB has corrupted entries about DC part. Please let me know the output of

omnidbcheck -dc

which should show an error on 2 media (as the error was "Corrupted: 2 major errors detected ").

I think you will need a readdb/writedb of IDB to solve your problem.

Best regards,
Fabio
WISH? IMPROVEMENT!
0 Likes
Absent Member.
Absent Member.
Hi Fabio,
i've done this procedure for remove DC corrupted:
Recovering if DC

Binary Files Are

Corrupted

If some DC binary files are corrupted, you can remove the DC binary

files and recreate them. The only effect of removing the files is that some

media positions point to the non-existent binary files, and thus an error

message is displayed when browsing the relevant filesystems. Proceed as

follows:

1. From the omnidbcheck -dc output, identify the Medium ID of the

corrupted DC binary file. Run the omnimm -media_info

command to get other attributes of the medium, such as medium

label and media pool.

2. Identify the DC binary file for the affected medium. DC binary files

are named: _.dat (in the , and

colons ":" are replaced with underscores "_").

3. Remove the corrupted DC binary files.

4. Run the omnidbutil -fixmpos command to establish consistency

between media positions (mpos) and binary files.

Now my DB works fine but is it possible for import a catalog 6-8 hours?? It's very too long time!!!!!My medium are from 800 GB but it's very longer operation!
Now Can i try to import the same catalog again?
Thanks a lot...
Alberto...
0 Likes
Absent Member.
Absent Member.
Hi Alberto,

very well, that is the procedure as manual to recover DC corrupted files, so very well that you solved the problem of DC corruptions.
However a consideration: as far as I know you can import only the catalog if the medium is already in IDB. If the medium is not in IDB already then you should import entirely the medium (by click on Import....and no Import Catalog). That is the reason I asked you if the medium is already in IDB. If you are sure that medium is not in IDB then I should suggest to import it. I don't know if you will see the same error yet. Probably you saw "Internal error: CtXXXX functions." because of DC corruptions but I'm not sure about that.
About the long import, I don't think you can do something to speed up the operation as it depends on data on medium.

Good luck...

Best regards,
Fabio
WISH? IMPROVEMENT!
0 Likes
Absent Member.
Absent Member.
Thanks a lot Fabio for your help but i ask you the ultimate question...
How can i do to know when the medium is in the DB? This medium is very older October 2006 if i see in my restore session for choice this version i don't found it.Then in this situation must do import catalog with All Log, is it correct ?
Thanks a lot.
Alberto...
0 Likes
Absent Member.
Absent Member.
Hi Alberto,

in order to know if the medium is in IDB you can run

omnimm -media_info "Mensile_Nov06"

and the same on medium about October 2006.

If you see the medium then is in IDB, if the command reports 'Medium not found' then it is not in IDB and you will need to import it entirely.

Also you ask: "if i see in my restore session for choice this version i don't found it.Then in this situation must do import catalog with All Log, is it correct ?"

Teorically it is correct but sometimes I saw that didn't work, I mean the data was not imported again. At that time I exported/imported the entire medium to import catalog correctly.

Best regards,
Fabio
WISH? IMPROVEMENT!
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.