06-09-2000 01:35 PM
The first error I got was that there wasn't enough space on the OB database device.
I made a new directory on a device with 150MB of space, made a soft link to it and tried again. Same error.
I made a new logical volume with 600MB of space, copied the db there and tried
This time I got the following error when clicking on the Media&Devices button:
[12:1012} Can not access file.
The xomni Help/Troubleshooting tells me that this means one of the daemons cannot read or access one of the configuration files - of course, it doesn't tell me which file.
The following command-line command gives the same error:
I have checked and compared all the configuration files, permissions and etc.
I believe we had a problem similar to this when we upgraded to 3.00 some time ago but forget what we did about it.
06-12-2000 06:08 AM
06-12-2000 09:31 AM
06-15-2000 05:55 AM
1. I installed the patches recommended for 11.00 in the HP OpenView OmniBack II A.03.10 Software Release Notes.
2. I tried omnimm -show_pools and got the same error.
3. I tried omnidbinit (which had not worked previously) and it worked.
4. That seems to have solved the problem since I no longer get that error.
However, for those of you who have had a problem magically disappear without knowing what you have done right, it will be difficult for me to trust this system for awhile....:-)