Remap schema and table space names (Oracle)

If the schema names or table space names are different in the source and target environments, you must remap them during the import.

Remap schema names

If the schema names are different in the source and target, you must remap the schema names. You must also run the import command as a DBA user.

Note: All references to the Fujitsu workflow schema apply only if you are migrating from 7.1.x, 7.2.x, or 7.3.x.

OpenPages® schema name is different

If the OpenPages schema name is different, remap it when you import the OpenPages schema. If you are migrating from 7.1.x, 7.2.x, or 7.3.x, also remap the OpenPages schema name when you import the Fujitsu workflow schema.

Add the following clause to the import command for the OpenPages schema:
```
remap_schema=<op_source>:<op_target>
```
Add the following clause to the import command for the Fujitsu workflow schema:
```
remap_schema=<op_source>:<op_target>
```

Note: If you use a different name for the OpenPages schema in the target environment, the change might impact your reports. You might need to do some remediation steps. If your reports contain references to the schema, update the reports to use the new schema name. Out-of-the-box reports are not impacted by this issue because they do not reference the schema name.

Workflow schema name is different

If the Fujitsu workflow schema name is different but the OpenPages schema name is the same, remap the workflow schema when you import the workflow schema. Add the following clause to the import command for the workflow schema:

remap_schema=<workflow_source>:<workflow_target>

OpenPages and workflow schema names are different

If both the OpenPages and Fujitsu workflow schema names are different, do the following steps:

Remap the OpenPages schema when you import the OpenPages schema. Add the following clause:
```
remap_schema=<op_source>:<op_target>
```
Remap both the OpenPages schema and the Fujitsu workflow schema when you import the workflow schema. Add the following clauses:
```
remap_schema=<workflow_source>:<workflow_target> 
remap_schema=<op_source>:<op_target>
```

Example : In this example, the OpenPages schema name is different and the Fujitsu workflow schema name is the same in the source and target.

impdp <dba_user>/\"<dba_password>\"@OP 
   DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=openpages_backup_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=openpages_import.log remap_schema=opuser:openpages 
   exclude=statistics

impdp <dba_user>/\"<dba_password>\"@OP 
   DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=opworkflow_backup_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=opworkflow_import.log remap_schema=opuser:openpages 
   exclude=statistics

Example : In this example, both the OpenPages and workflow schema names are different.

impdp <dba_user>/\"<dba_password>\"@OP 
   DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=openpages_backup_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=openpages_import.log remap_schema=opuser:openpages 
   exclude=statistics

impdp <dba_user>/\"<dba_password>\"@OP 
   DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=opworkflow_backup_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=opworkflow_import.log remap_schema=myworkflow:opworkflow
   remap_schema=opuser:openpages exclude=statistics

Example : In this example, the Cognos® schema name is different.

impdp <dba_user>/\"<dba_password>\"@OPCC 
   DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=openpage_cc_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=opcognos_import.log fromuser=cognos touser=cognos 
   TABLE_EXISTS_ACTION=REPLACE remap_schema=mycc:opcc

Remap table space names

If the source and target databases are using different table space names, include the following clause in the import command:

remap_tablespace=<source_tablespace_name>:<target_tablespace_name>

Example : In this example, the MYCRN table space is remapped to the CRN table space in the target environment.

impdp system/\"password\"@OPCC 
   DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=openpage_cc_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=opcognos_import.log fromuser=cognos touser=cognos 
   TABLE_EXISTS_ACTION=REPLACE remap_tablespace=MYCRN:CRN

To determine the table space names that are used, do the following steps:

In the source environment, log in to SQL*Plus as the cognos user.
Run the following command to get a list of table spaces:
```
select tablespace_name from user_tablespaces;
```
Run the following command to get a list of table spaces that contain objects:
```
select distinct tablespace_name from user_segments;
```
Repeat these steps in the target environment and compare the table space names.

If you need to remap the schema and the table spaces, place the remap_schema parameter before the remap_tablespace parameter. Run the command as a DBA user.

Example : In this example, the Cognos schema name is remapped and the MYCRN table space is also remapped.

impdp <dba_user>/\"<dba_password>\"@OPCC DIRECTORY=OP_DATAPUMP_DIRECTORY 
   DUMPFILE=openpage_cc_YYYY_MM_DD_HH_MI_SS.dmp 
   LOGFILE=opcognos_import.log fromuser=cognos touser=cognos 
   TABLE_EXISTS_ACTION=REPLACE remap_schema=mycc:opcc 
   remap_tablespace=MYCRN:CRN