Oracle database import recommendations

Oracle recommends the following when importing previously exported studies into an Oracle 12c database.

Use single-user imports for importing study data into the new Oracle database.
Before you import the study into the study database, set the Oracle database import parameters STREAMS_CONFIGURATION and STREAMS_INSTANTIATION to N.
Do not import the STRMADMIN user and STRMADMIN proxy user into the Oracle 12c database.
Set grants=N for the import.
If you are using the Data Pump export and import utilities (expdp and impdp), apply the EXCLUDE=OBJECT_GRANT parameter when importing study data into the new Oracle database.
Note: If you are importing study databases that were used in an environment that includes the InForm Adapter application, you might encounter Oracle error 31167: XML nodes over 64K in size cannot be inserted. You can ignore this error.

Note: If an export was done for a study schema that contained the Reporting and Analysis module installed in the same database as the study, messages might appear saying that the database tables contain a ROWID column, and that values might be obsolete. You can ignore these messages. The messages are related to the materialized views that are being imported. The reporting upgrade script you run later removes the materialized views that were imported.

Note: If an export was done for a study schema that contained the Reporting and Analysis module installed in a different database from the study, an error message might appear saying that the system could not create a database link. You can ignore this message. This database link is not necessary for the study. If it exists after import, it is removed by the reporting upgrade scripts that you run later.