DP 9.09 upgrade to DP 10.60 fails with "Database update failed. (Return code = 3)"

0 Likes
over 1 year ago

Summary

ERROR: Database update failed. (Return code = 3) For more detail please refer to /var/opt/omni/server/log/DPIDBsetup_7173.log

Problem

DP 9.09 upgrade to DP 10.60 into RHEL 7 fails with the following messages:

---InstallationMessages---
NOTE: Internal Database version A.09.00 found. Updating...
Configuring and starting up Internal Database... Done!
Configuring and starting up Internal Database Connection Pool... Done!
Configuring and starting up Application Server... Starting up Data Protector Services... Done!
Encrypting Internal Database passwords and storing encryption key into KMS... Done!
Encrypting Internal Database user passwords...
WARNING: Unable to encrypt IDB user passwords(Return code = 177)
Done!

ERROR: Database update failed. (Return code = 3)
For more detail please refer to /var/opt/omni/server/log/DPIDBsetup_7173.log
warning: %post(OB2-CS-A.10.60-1.x86_64) scriptlet failed, exit status 3

Cause

The problem was that schema of the IDB was not consistent. The schema version reported the IDB in 9.02 when it was actually in 9.09.

Here the schema output:

COPY dp_concepts_version_info (release, revision, created_on, id) FROM stdin;
8.0    $Rev: 37111 $    2016-05-18 00:00:00-04    1
8.01    $Rev: 40447 $    2016-05-18 11:24:50.842691-04    2
8.10    $Rev: 42146 $    2016-05-18 11:24:54.860711-04    3
9.0    $Rev: 40447 $    2016-05-18 11:24:54.862223-04    4
9.02    $Rev: 45303 $    2016-05-24 09:34:25.08011-04    5
9.06    $Rev: 45303 $    2016-05-24 09:34:25.162936-04    6
9.07    $Rev: 45303 $    2018-09-18 11:45:32.971186-04    7
9.08    $Rev: 45303 $    2018-09-18 11:45:35.873393-04    8
9.08_113    $Rev: 45303 $    2018-09-18 11:45:35.884971-04    9
9.09    $Rev: 45303 $    2018-09-18 11:45:35.95842-04    10
9.02    $Rev: 45303 $    2018-09-18 17:36:26.786278-04    11
9.06    $Rev: 45303 $    2018-09-18 17:57:08.43861-04    12
9.07    $Rev: 45303 $    2018-09-18 17:57:09.22994-04    13
9.08    $Rev: 45303 $    2018-09-18 17:57:09.257424-04    14
9.08_113    $Rev: 45303 $    2018-09-18 17:57:09.261552-04    15
9.02    $Rev: 45303 $    2018-09-18 18:10:09.153558-04    17
9.06    $Rev: 45303 $    2018-09-18 18:23:05.286635-04    18
9.07    $Rev: 45303 $    2018-09-18 18:23:05.92442-04    19
9.08    $Rev: 45303 $    2018-09-18 18:23:05.948838-04    20
9.08_113    $Rev: 45303 $    2018-09-18 18:23:05.953031-04    21
9.02    $Rev: 45303 $    2018-09-19 11:13:54.85772-04    23
9.02    $Rev: 45303 $    2018-09-19 12:00:04.56955-04    25

To get this output you can run a sql script with this content:

select * from hpdpidb_app.dp_concepts_version_info;

Save that sql script in a temporary place and name it like script.sql. To run it execute this command: omnidbutil -run_script script.sql -detail

Fix

To solve this problem, create another sql script with this content:

delete from hpdpidb_app.dp_concepts_version_info where id >10;

Save it like solution.sql and run the command: omnidbutil -run_script solution.sql -detail.

IMPORTANT: here the 10 in the script refers to the ID of the last correct line collected in the command run before:

9.08_113    $Rev: 45303 $    2018-09-18 11:45:35.884971-04    9
9.09    $Rev: 45303 $    2018-09-18 11:45:35.95842-04    10

The script will delete all the lines with an ID bigger than 10.

If you want, open a support ticket referring to this KB for help applying that solution.

Links for reference

Labels:

Support Tip
Comment List
Anonymous
Related Discussions
Recommended