Mumbai, India
ecmnotes.com parag@ecmnotes.com

Cloning / Copying a Docbase

Pre-requisites:

The following points need to be strictly adhered to, for Cloning/Copying a Docbase:

a. The clone of the Docbase should be created on a machine other than the source Content

Server machine.

b. The cloned Docbase should be made on a Content server installation version same as

that of the source Docbase.

c. The cloned Docbase name should be the same as that of the source Docbase

d. The cloned Docbase ID should be the same as that of the source Docbase

e. The cloned Docbase owner should be the same as that of the source Docbase

f. The Database instance used by the cloned Docbase should be different from the

Database instance used by source Docbase.

g. The cloned Docbase should project to a Docbroker different from the Docbroker used by

the source Docbase.

h. The Database owner name/password for all the existing Docbases on the target Content

server machine must be known.

To Clone/Copy a Docbase:

1. Stop/shut down the source Docbase.

2. Stop the newly created target Docbase (This Docbase is created on a different machine,

with Docbase owner, Docbase ID and Docbase name same as that of the source

Docbase).

3. Take a DB back-up of the entire source Docbase Database.

4. On the source Docbase host’s file system, create a back-up of the entire

$DOCUMENTUM\data\<Docbase name> directory.

This is the directory containing the Docbase’s content files.

5. Connect as the database system administrator to the database instance serving the

target Docbase.

6. Destroy the existing tablespaces/database using the following script in the target Content

server machine :

$DOCUMENTUM\dba\config\<Docbase name>\dm_DeleteTableSpace.sql – For SQL

Server

$DOCUMENTUM\dba\config\<Docbase_name>\destroy_tablespace.oracle – For Oracle.

7. Create new tablespaces/database for the Target Docbase using the following script in the

target Content server machine :

$DOCUMENTUM\dba\config\<Docbase name>\dm_CreateTableSpace.sql – For SQL

Server

$DOCUMENTUM\dba\config\<Docbase_name>\create_tablespace.oracle – For Oracle.

8. Import the database export taken from the production Docbase (in Step 3) into the newly-
created tablespaces or database.

9. Connect to the database serving the Docbase copy as the Docbase owner and verify that

the target database tables have the correct value for the target system host by checking

the following :

select r_host_name from dm_server_config_s

select host_name from dm_mount_point_s

select target_server from dm_job_s

select projection_targets from dm_server_config_r

select web_server_loc from dm_server_config_s

Run update queries to update the incorrect values:

update dm_mount_point_s set host_name = new_host_name’ where host_name

= ‘old_host_name’

update dm_server_config_s set r_host_name =’new_host_name’ where r_host_name

= ‘old_host_name’

update dm_server_config_r set projection_targets =’new_host_name’ where

projection_targets = ‘old_host_name’

update dm_job_s set target_server = ‘docbasename.docbasename@new_host_name’

where target_server = ‘docbasename.docbasename@old_host_name’

10. Run the following SQL on the target DB to rebuild the Documentum views :

update dm_type_s set views_valid=0

11. Copy the content file backup from the source Docbase (taken in point 4 above) to the file

system of the target Docbase.

$DOCUMENTUM\data\<Docbase name>

12. Verify that server.ini file on target Content server machine has the following key set to

true under SERVER_STARTUP section:

preserve_existing_types=T

server.ini file is located at $DOCUMENTUM\dba\config\<Docbase name>

13. If the file path is not the same as that of the target. Update the following tables with the

current path:

update dm_location

set file_system_path =’newpath’ where file_system_path=’old path’

update dm_mount_point objects

set file_system_path=’newpath’ where file_system_path=’old path’

14. Shutdown all the Docbases on the target Content server (i.e. stop the cloned Docbase as

well as the other existing Docbases on the target Content server)

15. Take a back-up of the Databases for each of these Docbases on the target Content

Server.

16. Rename the aek.key file or move it some other location on the target Content Server :

Path: $DOCUMENTUM\dba\secure\aek.key

17. Execute the following SQL queries for each of these Docbase Databases on target:

a. update dm_docbase_config_s set i_crypto_key = ‘ ‘ (Note: There should be single

space)

b. select r_object_id from dmi_vstamp_s where i_application

= ‘dm_docbase_config_crypto_key_init’;

c. delete from dmi_object_type where r_object_id = ‘<r_object_id from step b>’

d. delete from dmi_vstamp_s where r_object_id = ‘<r_object_id from step b>’

18. Create the new aek.key file for the target Content server as follows:

Run dm_crypto_create.exe (for Windows) or dm_crypto_create (for Solaris) from the

location $DM_HOME\bin on target Content Server machine:

Choose the default passphrase (say ‘Y’ ) when prompted

19. Take a back-up of the dbpasswd.txt file for each of the Docbases on the target Content

Server.

Location: $DOCUMENTUM\dba\config\<Docbase name>

20. Re-encrypt the dbpasswd.txt file for each of the Docbases on target as follows:

Execute the following command from the following location on target Content Server

machine:

$DM_HOME\bin

dm_encrypt_password -docbase <docbase name> -rdbms -encrypt <databasepassword>

Refer Next Post (PRE-CLONING QUERIES) for more queries to take care when performing cloning process.

Leave a Reply