000030017 - CT_OWNER.PASSWORD table causing DB Conflict in the DPM appliance.

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000030017
Applies ToRSA Product Set: Data Protection Manager
RSA Product/Service Type: Data Manager Appliance
RSA Version/Condition: 3.2, 3.5.1, 3.5.2.2
 
IssueDB conflict on ct_owner.password occurs even when doing DPM upgrades. 
WorkaroundAs root login as Oracle:
1.  su - oracle
2.  sqlplus / as sysdba
3.  delete from ct_owner.password where id = <id_number_of_ct_owner_password_conflict>;
<id_number_of_ct_owner_password_conflict> = would be the ID of ct_owner.password that has the conflict. 
4.  commit;
5.  exit out of sqlplus and oracle
exit
exit
6.  Have the latest cs status pages installed and run:
/opt/rsa/setup/sh/cs_sync_table.sh -insert
enter the table: ct_owner.password
enter the node you would like to sync the table from: ONE
ONE = The name of another node in the cluster that you have not deleted the conflict from ct_owner.password and you are syncing this table from.
7.  Check to make sure the table does not have any more conflicts on ct_owner.password:
/opt/rsa/setup/sh/cs_sync_table.sh -select
enter the table: ct_owner.password
enter the node you would like to compare: ONE
If there are no rows the table should not have any more conflicts
8.  Clean up apply errors by running (note: only if the only conflicts shown are on ct_owner.password):
/opt/rsa/setup/sh/cs_delete_apply_errors.sh
 

Attachments

    Outcomes