Crypto initialization problem
Created: 5 February 2010 Modified:Originally published on chrislynch.info website.
- Shutdown all the repositories on the target server
- Backup the database
- Rename the AEK file or rename it and move it some where else
-
From sql on the database, run the following statements:
SQL> update dm_docbase_config_s set i_crypto_key = ‘ ‘.
- SQL> update dm_docbase_config_s set i_ticket_crypto_key = ‘ ‘.
- SQL> select r_object_id from dmi_vstamp_s where i_application = ‘dm_docbase_config_crypto_key_init’;
- SQL> delete from dmi_object_type where r_object_id = ‘returned r_object_id from above’;
- SQL> commit;
- SQL> delete from dmi_vstamp_s where r_object_id = ‘returned r_object_id from step above’
- SQL> commit;
- SQL> select r_object_id from dmi_vstamp_s where i_application = ‘dm_docbase_config_ticket_crypto_key_init’;
- SQL> delete from dmi_object_type where r_object_id = ‘returned r_object_id from above’;
- SQL> delete from dmi_vstamp_s where r_object_id = ‘returned r_object_id from step above’
- SQL> commit
- run this file from $DM_HOME/bin: dm_crypto_create
-
- To re-encrypt the dbpasswd.txt file do the following: cd $DM_HOME/bin
- dm_encrypt_password -docbase
-rdbms -encrypt - You need to do all modification on the database for each repository except step 15. This should only be done once.
- Startup the repositories.