Update aek.key

1. Shutdown the docbase being moved on the target server
2. Create a copy of the AEK file (aek.key) in \Documentum\dba\secure directory on the target server and rename it (e.g., aek.bak). This is just in case something happens to the file and we need to rollback.
3. From sql on the database:
update dm_docbase_config_s set i_crypto_key = ' ';
4. From sql:
SQL> select r_object_id from dmi_vstamp_s where i_application = 'dm_docbase_config_crypto_key_init';
5. delete from dmi_object_type where r_object_id = 'returned r_object_id from above';
6. SQL> commit;
7. SQL> delete from dmi_vstamp_s where r_object_id = 'returned r_object_id from step above'
8. SQL> commit;
9. From sql on the database
update dm_docbase_config_s set i_ticket_crypto_key = ' ';
10. from sql:
SQL> select r_object_id from dmi_vstamp_s where i_application = 'dm_docbase_ticket_config_crypto_key_init';
11. delete from dmi_object_type where r_object_id = 'returned r_object_id from above';
12. SQL> commit;
13. SQL> delete from dmi_vstamp_s where r_object_id = 'returned r_object_id from step above'
14. SQL> commit;
15. To re-encrypt the dbpasswd.txt file for the moved docbase, navigate to the :\documentum\product\5.3 \bin directory in a command window.
16. From a command prompt, enter the following:
dm_encrypt_password -docbase -rdbms -encrypt
17. You will need to reboot the entire system - Content Server, PDF Aqua, Queue Manager, and Application and remove all caches once you have moved it..
18. Startup the docbase service
19. You might have to repeat some of the steps from this process. especially the i_ticket_crypto_key. I was unable to find it the first time, but the second time I ran through the instructions after trying to
start the docbase once, I found this key and was able to delete it.