|
|
|
|
Database and file customizations
- Database schema objects created or customized outside of the standard InForm application are not supported for upgrade and can cause errors during the migration process.
Note: Oracle does not support migrating tables created outside of the standard InForm application schema or by Enterprise Adoption customers. These tables might cause errors when you import the study DMP files.
- Any schema customization must have an upgrade path that results in a valid InForm 6.3.1.1 schema at the point in the migration where you create the review schema. For more information, see Import the InForm study DMP file.
You can record the customizations, and reintroduce them after you complete the standard migration procedures. Such customizations might include changes to:
- Views
- Functions
- Procedures
- Packages
- Triggers
Note: The command pfadmin RECREATEREVIEWSCHEMA runs automatically as part of the study import process. If any schema objects such as views, functions, procedures, packages, or triggers are invalid, pfadmin RECREATEREVIEWSCHEMA fails, and as a result the migration fails. You must repair any invalid schema objects before you can perform a migration.
- Any study resources that have been customized for deployment must be addressed separately before migration.
The customized changes must be modified to comply with the InForm 6.3.1.1 software and InForm 6.3.1.1 MedML schema and reinstalled so that the customized changes are not lost due to the upgrade.
