Migration of Documentum database from Oracle to Sql

2»

Comments

  • @YuricS there is a object in dmi_vstamp table with name sqlobject which gets created when we setup cs with sql server, in oracle setup its not there ,create empty repo with sql first and then copy all entries from dmi_vstamp table from empty repo to your migrated repo.

    Hi, Were you able to resolve the issues? Can you share the steps/documentation on this approach please
  • Resolved using the same step as told "there is a object in dmi_vstamp table with name sqlobject which gets created when we setup cs with sql server, in oracle setup its not there ,create empty repo with sql first and then copy all entries from dmi_vstamp table from empty repo to your migrated repo.
  • UGSP
    edited August 4, 2020 #34
    Resolved using the same step as told "there is a object in dmi_vstamp table with name sqlobject which gets created when we setup cs with sql server, in oracle setup its not there ,create empty repo with sql first and then copy all entries from dmi_vstamp table from empty repo to your migrated repo." 

    So the r_object_id you were able to retain? Any additional steps to make sure workflow objects are not corrupted?
  • SandipDabhade
    edited August 4, 2020 #35
    If we copy all entries from dmi_vstamp table from empty repo to your migrated repo you will not face any error related to r_object id, For workflows no additional steps required, only thing is data types both in Oracle and SQL are different so make sure that your SQL schema is with proper data types, refer empty repo sql schema for data types
  • Oracle to SQL can be migrated automatically with Ispirer MnMTK - Migrate Oracle to Microsoft SQL Server - Ispirer

  • Whatever database migration tool is ok, like the free Microsoft Sql migration tool. All the migration tools are not enough, also the Ispirer one.