Oracle

  1. In Architect, check in and release the database. This ensures that the production and authorized schemas are synchronized.
  2. Create a complete backup of the source production and authorized schemas.
  3. On the destination database server, create tablespaces for the schemas you will import and Oracle users for all the users. Also create all of the roles such as BPAdmin or BPHolder if they do not already exist.
  4. Grant the appropriate privileges and roles for all the Oracle users that will access the ported application. You can use the sample Ctrain_ModelCreate_Oracle.sql script in the ProgramData\Infor\CPM\Architect\Database Creation Scripts directory on the CPM Server computer as a starting point.
  5. Use Oracle export/import commands to move the production and authorized schemas.
  6. For both the imported production schema and the imported authorized schema, the user_ids for all users need to be synchronized with the user_ids generated internally by Oracle and stored in the system view, ALL_USERS.
  7. Grant each user the correct role.

Synchronizing user ids is a complex process, as the user_ids need to be synchronized in a number of tables. We recommend that you contact customer support for a general script to provide you with a starting point that you can customize as needed.

The following user and user security tables are involved:

  • BPR_USERS
  • BPR_USER_SECURITY
  • NOTE_DETAIL_BASE
  • UNIT_SECURITY_ACCESS
  • UNIT_SECURITY_RW
  • <SecuredDimension*>_SECURITY_ACCESS
  • <SecuredDimension*>_SECURITY_RW

* If your application has security assigned to multiple dimensions, you must synchronize the user_ids in the SECURITY_ACCESS and SECURITY_RW tables associated with each secured dimension. The Unit dimension is always a secured dimension.