'migrate_content' method queries for all the objects irrespective of number specified for max_migrat

Hello,

I have used migrate_content method and created a custom method and a job to provide the functionality to migrate documents from one encrypted filestore to another. When the job is run, it consumes more time in addition to the time taken to migrate specified number of documents. When I looked at the log, I found that it initially takes 20 minutes to execute the following query against 11 million records and then continues with the migration.

select r_object_id from rmd_report (ALL) where r_lock_owner=' ' and a_storage_type='encryptfilestore_01' ORDER by r_object_id ASC

So, every time I run this job, an additional 20 minutes will be used to fetch the results of the query and also we were suspecting, it might have an impact on the database and any other Documentum usage. It would be hard to manage the migration process if I insert more conditions related to r_creation_date in the WHERE clause. Also, I tried by creating an index for a_storage_type, but that didn't help much.

Can you please provide any other suggestions?

Find more posts tagged with

Comments

DCTM_Guru

If you want to limit the query execution, then add the number you specified in max_migrate_content to the query:

select r_object_id from rmd_report (ALL) where r_lock_owner=' ' and a_storage_type='encryptfilestore_01' ORDER by r_object_id ASC ENABLE (RETURN_TOP X)

mazharali

Thanks for replying. I have tried using ENABLE (RETURN_TOP X) before, but when migrate_content method is used in the code, there's an option to enter only the WHERE clause.

String dql = "EXECUTE migrate_content WITH target_store='"

+ targetstoreName + "', " + "query='r_lock_owner =" + "'' "

+ "'' and a_storage_type=" + "''" + sourcestoreName + "'' ENABLE (RETURN_TOP 100))'" + ", " + "sysobject_query=TRUE, " + "type_to_query='"

+ strType + "', max_migrate_count=" + strMaxMigCnt

+ ", batch_size=" + strBatchSize + ", remove_original="

+ deleteOriginal + ", log_file='" + strMigLogPath + "'"

+ ", renditions='" + renditionsStatus + "'";

Just for trial purposes when I ran the query given above by adding ENABLE keyword at the end, the final query was as given below.

Final query in the log file:

select r_object_id from rmd_report(ALL) where r_lock_owner=' ' and a_storage_type='encryptfilestore_01' ENABLE (RETURN_TOP 100) ORDER BY r_object_id ASC

Though this query didn't error out it still continued to take 20 + minutes to get the results. I think it would make a difference if ENABLE was after ORDER BY.