Documentum: Crypto Initialization Problem

Created: 2 May 2010  Modified:
  1. Shutdown all the repositories on the target server
  2. Backup the database
  3. Rename the AEK file or rename it and move it some where else
  4. From sql on the database, run the following statements
  5. SQL> update dm_docbase_config_s set i_crypto_key = ‘ ‘.
  6. SQL> update dm_docbase_config_s set i_ticket_crypto_key = ‘ ‘.
  7. SQL> select r_object_id from dmi_vstamp_s where i_application = ‘dm_docbase_config_crypto_key_init’;
  8. SQL> delete from dmi_object_type where r_object_id = ‘returned r_object_id from above’;
  9. SQL> commit;
  10. SQL> delete from dmi_vstamp_s where r_object_id = ‘returned r_object_id from step above’
  11. SQL> commit;
  12. SQL> select r_object_id from dmi_vstamp_s where i_application = ‘dm_docbase_config_ticket_crypto_key_init’;
  13. SQL> delete from dmi_object_type where r_object_id = ‘returned r_object_id from above’;
  14. SQL> delete from dmi_vstamp_s where r_object_id = ‘returned r_object_id from step above’
  15. SQL> commit
  16. Change to the $DM_HOME/bin directory. Run dm_crypto_create
  17. To re-encrypt the dbpasswd.txt file do the following:
  18. cd $DM_HOME/bin
  19. dm_encrypt_password -docbase -rdbms -encrypt
  20. You need to perform all steps except running cm_crypto_create for each repository. Running dm_crypto_create should only be run once.
  21. Startup the repositories.
tags: Documentum - crypto - initialization
   Less Is More