Question

Skip migrating LOC table for huge Repositories

Version 9 Installation and Upgrades

Updated December 12, 2014

asked on December 11, 2014

Hello,

I need to migrate a big repository from version 7 to version 9.

We did a Proof of Concept for the migration in a test environment, and it came out that migrating the LOC table took 2 days and 4 hours (50 million records)

Is there any way to skip this step in the final Repository migration?

I need to speed up the migration as much as possible, to minimize the downtime and transition issues for users, so i prefer to re-OCR all the documents once the repository is live again, rather than making the Migration tool to handle this step.

If anyone has an idea, i will appreciate the colaboration.

Thank you and best regards,

Ignacio PdeA

BMB sal

0 0

Replies

replied on December 11, 2014

Does this database have expansion databases or is it using full SQL?

0 0

replied on December 11, 2014

If you'd really rather re-OCR everything, you could try just manually clearing the loc table data in the source SQL database before performing the migration. I haven't tried this, so definitely do so on a backup. Keep in mind that of course re-OCR'ing is a very long process and will also requiring redoing any manual text editing or annotations, including redactions.

0 0

replied on December 12, 2014

Thank you for your replies.

Definitely i will not take the risk of manually altering the LOC table, even though it would save 2 days during the migration.

Best regards,

Ignacio PdeA

BMB sal

0 0

You are not allowed to follow up in this post.

Question

Question

Skip migrating LOC table for huge Repositories

Replies

Sign in to reply to this post.