topic 12:1118 cannot open database/files in Operating System - HP-UX

12:1118 cannot open database/files

paulchen — Sun, 19 Oct 2003 22:04:44 GMT

I'm using Omniback 3.5. I keep on recieve this when i try to configure my device and when i type the command omnidbcheck. And i suspect my internal database was corrupted. But i had backup my internal database. How can i restore if i cannot configure the drive?
And my OS platform is Hpux 11i and my /var space balance is only about 80MB. I had also running the command omnidbutil -purge. But the size is still same.

Re: 12:1118 cannot open database/files

RAC_1 — Sun, 19 Oct 2003 22:15:57 GMT

First check with omnidbcheck. Check all(not just core check)

How you have taken the backup? Through omni?

If through omniback you can restore as follows.

omnidbrestore -autorecover.

The /var file system is dynamic. Check as follows.

cd /var
du -sk *|sort -nr

check what files/dirs are required and not required delete it.

Re: 12:1118 cannot open database/files

Michael Tully — Sun, 19 Oct 2003 22:35:50 GMT

Check this information from the help files. Perhaps your database is not corrupted. The size will only actually reduce, if you do an actual writeascii/readascii procedure. Run a omnidbcheck to see if there are any errors reported.

[12:1118] Cannot open database/file.

DESCRIPTION:

OmniBack II was unable to open the OmniBack II database. The database files are
either not available or the Unix file permissions to access the database files
are incorrect.

ACTION:

On an UNIX Cell Manager:
Check the database files ( *.dat, *.ext, *.key) in the
/var/opt/omni/db/cdb and /var/opt/omni/db/mmdb directories on
the Cell Manager. The permissions of these files should be 600 and user root.
If there are no files, database has not been initialized yet. In this case, use the
omnidbinit command to initialize the database.
Also check for /var/opt/omni/db/catalog/extfiles.txt for extension files and check they are
in place - they might be missing.

Re: 12:1118 cannot open database/files

Jakes Louw — Tue, 21 Oct 2003 00:46:40 GMT

Also run an "omnidbutil -extendinfo" to see if you need to extend your db.
We also ran into the /var limitation problem, and we then created a seperate filesystem (/omni_db) of 8 GB, moved everything from under /var/opt/omni to this filesystem (shut Omni first and kill all hanging Omni processes). We then re-created /var/opt/omni as a symbolic link (ln -s) to /omni_db.
Has been working like a charm for many years.....