Steps for ContentServer migration

1. back up and restore the database. Sometimes you can use the command line such as restore database QA1 from disk = 'd: \ qa1 'with replace when UI operations fail. after the data block is restored, You have to modify two tables, dm_acs_config (?) Dm_server_config (?), I do not remember the specific table name, but it is easy to find it when you open the Database Manager. After opening the two tables, modify the url and uri fields, mainly the machine name or ip address.

2. Copy C: \ Documentum \ data \ qa1

3. If an error is reported when Repository is started, for example, Docbase QA1 was not successfully opened. Docbase id: (10001 )"

This is generally caused by inconsistent Encryption Files (aek. key) on two machines. There are two solutions:

If you only have one repository, simply change the C: \ Documentum \ dba \ secure \ aek of the original machine. key and C: \ Documentum \ dba \ config \ QA1 \ dbpasswd.txt are copied to the new machine.

Just run the following command:
Cd C: \ Documentum \ product \ 6.5 \ bin

Dm_encrypt_password.exe-docbase QA1-rdbms-encrypt after execution, you will be prompted to enter a new password. At this time, enter the Database Password to be O.

 

Today, contentserver6.5sp2 was successfully executed again,

Shutdown all the docbase on the target server

Rename or moveAek. keyFile (located at $ DOCUMENTUM \ dba \ secure)

 

UPDATE dm_docbase_config_s SET I _crypto_key = '';
UPDATE dm_docbase_config_s SET I _ticket_crypto_key = '';
Delete from dmi_object_type WHERE r_object_id = (SELECT r_object_id FROM dmi_vstamp_s WHERE I _application = 'dm _ docbase_config_crypto_key_init ');
Delete from dmi_vstamp_s WHERE r_object_id = (SELECT r_object_id FROM dmi_vstamp_s WHERE I _application = 'dm _ docbase_config_crypto_key_init ');
Delete from dmi_object_type WHERE r_object_id = (SELECT r_object_id FROM dmi_vstamp_s WHERE I _application = 'dm _ docbase_config_ticket_crypto_key_init ') delete from dmi_vstamp_s WHERE r_object_id = (SELECT r_object_id FROM dmi_vstamp_s WHERE I _application = 'dm _ docbase_config_ticket_crypto_key_init ');
Delete from dmi_vstamp_s WHERE r_object_id = (SELECT r_object_id FROM dmi_vstamp_s WHERE I _application = 'dm _ docbase_config_ticket_crypto_key_init ');
Delete from dm_sysobject_s WHERE r_object_id = (SELECT r_object_id FROM dm_public_key_certificate_s WHERE key_type = 1 );
Delete from dm_sysobject_s WHERE r_object_id = (SELECT r_object_id FROM dm_cryptographic_key_s WHERE key_type = 1 );
Delete dm_public_key_certificate_s;
Delete dm_cryptographic_key_s;

Run $ DM_HOME/bin/dm_crypto_create
Run $ DM_HOME/bin/dm_encrypt_password-docbase-rdbms-encrypt-docbase
Try to start your docbases.

 

For other information, see the following:

1. Stop the docbase.

2. Backup the database
3. Rename the AEK file or move it some where else

4. From SQL on the database,
SQL> update dm_docbase_config_s set I _crypto_key = ''.
SQL> update dm_docbase_config_s set I _ticket_crypto_key =''

5. Retrieve entry from dmi_vstamp_s for 'dm _ docbase_config_crypto_key_init '.
SQL> select r_object_id from dmi_vstamp_s where I _application =
'Dm _ docbase_config_crypto_key_init ';

6. Delete entry from dmi_object_type
SQL> delete dmi_object_type where r_object_id = 'returned r_object_id from above ';

7. Delete entry from dmi_vstamp_s itself
SQL> delete from dmi_vstamp_s where r_object_id = 'returned r_object_id from step abve'

8. Retrieve entry from dmi_vstamp_s for 'dm _ docbase_config_ticket_crypto_key_init '.
SQL> select r_object_id from dmi_vstamp_s where I _application = 'dm _ docbase_config_ticket_crypto_key_init ';

9. Delete entry from dmi_object_type
SQL> delete dmi_object_type where r_object_id = 'returned r_object_id from above ';

10. Delete entry from dmi_vstamp_s itself
SQL> delete from dmi_vstamp_s where r_object_id = 'returned r_object_id from step abve ';

11. Truncate the tables dm_public_key_certificate_s
SQL> delete dm_public_key_certificate_s;

12. Truncate the tables dm_cryptographic_key_s
SQL> delete dm_cryptographic_key_s;

13. Run dm_crypto_create utility under $ DM_HOME/bin, in order to create a new aek. key file. Even though you have multiple docbases in a machine, you shoshould run this only one time.

14. Run dm_encrypt_password utility to encrypt the database access password.
Prompt> dm_encrypt_password-docbase <docbase name>-rdbms-encrypt <database password>

15. Check if views_valid is set to 0,
SQL> select views_valid from dm_type_s;

If its 1, then run the following command
SQL> UPDATE dm_type_s SET views_valid = 0;

16. Startup the docbases. The attributes deleted abve are repopulated inside database, when Docbase starts.

In addition, if after/before/during the process you got this error also:

[DM_CONTENT_E_GDCDS_NO_ACS_CRYPTO_KEY] error: "Cannot get the ACS Cryptographic key for Distributed Content. this is expected during docbase creation and the ACS Cryptographic system will be initialized by each session as needed. this error is unexpected once docbase creation is complete. status = 524"

Just clean these tables: dm_public_key_certificate_s and dm_cryptographic_key_s

Probally you will receive the following error also "Unable to open file for input" (when you try to start the docbase with Server Manager)

 

II. Another backup restoration method uses IApi

Http://www.bluefishgroup.com/library/2003/dump-and-load-a-docbase/