According to note 2768127:
Work before migration:
- Make sure all <SOURCE DATABASE> local repositories have same/latest version of code/objects prior to migration.
- Please create blank databases/schemas on <TARGET DATABASE> server where local and central repositories will be moved/migrated. Appropriate permissions set, database user should be schema/DB owner.
Step to migrate central repositories:
A central repository cannot be migrated like a local repository can be migrated. That's why it is ensured in step 1 (Work before migration), so that <SOURCE DATABASE> central repository can be discontinued.
In case source and target databases of central repositories are the same (both have to be <SOURCE DATABASE> or both <TARGET DATABASE>), central repository can be preserved by copying database directly. In this case, it is moving from <SOURCE DATABASE> to <TARGET DATABASE>, the only way to move using all existing objects is using some external tools to move data from <SOURCE DATABASE> to <TARGET DATABASE>. Otherwise, starting with a fresh/blank central repository should be considered.
- From DS Repository Manager create a new secured central <TARGET DATABASE> repository (in the blank schema created in Step 2 (Work before migration))
- Configure the <TARGET DATABASE> central repository in the CMC (Created in Step 2 above)
- From Data Services Management Console activate the central repository
- From DS designer connect to central repository and start using normally. The Central repository will be empty, and objects can be checked in and subsequently checked ou from it.
NOTE: Do not copy and restore local or central repositories between different server machines.
Bluesky
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.