Data Protector 7.0 - Catalog DataBase errors

Good afternoon.


We are having problems with backup jobs as it gives the following error:

[Critical] From: OB2BAR_SAPBACK @ hostname "PRD" Time: 01/24/15 17:01:27
Can not initialize OB2BAR Services (Interprocess communication problem.)
[Critical] From: OB2BAR_SAPBACK @ hostname "PRD" Time: 01/24/15 17:01:29
Can not initialize OB2BAR Services (Interprocess communication problem.)
Can not init OB2BAR "Catalog not loaded, message # 7595 in September 11"
sh: 4242 Memory fault


I purged the catalog as follows:
omnidbutil -purge -filenames -force
omnidbutil -purge_stop

With this I have managed to free space database catalog and no longer have errors in bakups.

My query is:
1. I have added two extensions files of 2GB each but "catalog database / filenames" but "Total Size" size remains 0Mb (The bbdd not write new files on this)
2 .- "catalog database / positions" only has a 3% free. Is it possible to remove obsoletes data in the same way we do with filenames?


attach the output of "omnidbutil -info"

Media Management database space usage:

Space used by Diskspace usage Total Records Records used
================================================== ==========================
Devices 160 June 80
Libraries 96 January 40
Cartridges 1344 142 888
Compounds 32 0 96
Pools 64 October 40
Media 96139176

Catalog database space usage:

Space used by Diskspace usage Total Records Records used
================================================== ==========================
Sessions 6752 2965 6048
Objects 352,819,960
Object versions 69920 45932 74080
Positions 116800 463773 477896
Filenames 7061696 50659777 59148342

Detail catalog binary files usage:

Size limit usage Diskspace DC Directory
================================================== ==========================
2337 4096 C: / Program Files / OmniBack / DB40 / DCBF
-------------------------------------------------- --------------------------
2337 4096

Session messages binary files usage:

Diskspace usage Num. Of files SMBFS Directory
================================================== ==========================
307 2962 C: / Program Files / OmniBack / DB40 / msg

Serverless integrations binary files usage:

Diskspace usage Num. Of files SIBFs Directory
================================================== ==========================
0 0 C: / Program Files / OmniBack / DB40 / meta

Parents Reply Children
  • You have at least formating issues with your output, could you please post a clean one again? (September instead of Set and so on)

    The IPC Errors can be contered by setting up something like this in omnirc-File on Cell- and Media-Server:

    OB2IPCKEEPALIVE=1
    OB2IPCKEEPALIVETIME=900
    OB2IPCKEEPALIVEINTERVAL=60
    OB2RECONNECT_RETRY=3600

    With properly working Network this shouldn't be required but with slow Servers or Firewalls in between it helps.

  • I don't think that thsi has anything at all to do with the Internal Database.  The error

     

    "Catalog not loaded, message # 7595 in September 11"

     

    lathough I have never seen it expressed as 'September" means to me that the error is inidenfiable, in the sense that the error is not in our standard message catalog.  Are you sure the error is not something lie

     

    "Catalog not loaded, message # 7595 in Set 11"

     

    which makes more sense to me.  I checked both a DP 7 and a DP 9 cell using the 'omnigetmsg 11 7595' command, and found nothing.

     

    YOu will probably need to create a case with the response center to have thsi analyzed

     

     

  • I don't think that thsi has anything at all to do with the Internal Database.  The error

     

    "Catalog not loaded, message # 7595 in September 11"

     

    lathough I have never seen it expressed as 'September" means to me that the error is inidenfiable, in the sense that the error is not in our standard message catalog.  Are you sure the error is not something lie

     

    "Catalog not loaded, message # 7595 in Set 11"

     

    which makes more sense to me.  I checked both a DP 7 and a DP 9 cell using the 'omnigetmsg 11 7595' command, and found nothing.

     

    YOu will probably need to create a case with the response center to have thsi analyzed

     

     

  • I don't think that thsi has anything at all to do with the Internal Database.  The error

     

    "Catalog not loaded, message # 7595 in September 11"

     

    lathough I have never seen it expressed as 'September" means to me that the error is inidenfiable, in the sense that the error is not in our standard message catalog.  Are you sure the error is not something lie

     

    "Catalog not loaded, message # 7595 in Set 11"

     

    which makes more sense to me.  I checked both a DP 7 and a DP 9 cell using the 'omnigetmsg 11 7595' command, and found nothing.

     

    YOu will probably need to create a case with the response center to have thsi analyzed