Ken, what are the results of the command
omnisv status
If it is something like this:
ProcName Status [PID]
===============================
crs : Active [3464]
mmd : Active [5364]
kms : Active [5440]
hpdp-idb : Down
hpdp-idb-cp : Active [5604]
hpdp-as : Active [4284]
omniinet : Active [4980]
Sending of traps disabled
check the top level of both C: and D: for the file 'Program', and if you see it, delete it
==============
Problem:
During the update to DP 8.1, the hpdp-idb service does not start.
As a consequence, the import of the IDB (core update) does not work and needs to be repeated.
Example:
The DP 7.0 installation has been done in a way that binaries and data files are located in C:\Program Files\OmniBack.
The same applies for D:\Program Files\OmniBack (or other volumes).
During the update, 2 omnimigrate logs are created.
One for the export and one for the import.
In case the IDB cannot start, the import log file C:\Program Files\OmniBack\log\omnimigrate_2014-03-21_03-06-15.log shows:
Cannot start "hpdp-idb" service, system error:
[1053] The service did not respond to the start or control request in a timely fashion.
Solution:
The solution consists of the sequence of the following steps (assuming that common path C:\Program Files\OmniBack has been used).
1) Delete the file "C:\Program".
2) Do "omnisv stop" and "omnisv start".
3) Use "omnisv status" to check that all services have been started.
4) Check the location where the IDB has been exported to (default is C:\Program Files\OmniBack\tmp\export):
You should see a mmdb and a cdb folder there.
5) Open power shell and go to C:\Program Files\OmniBack\bin
6) Run the import manually:
PS C:\Program Files\OmniBack\bin> perl omnimigrate.pl -import -shared_dir "C:\Program Files\OmniBack\tmp\export" -force