Troubleshooting Oracle schema creation
If you encounter problems when you run the scripts to create the Oracle database schema during a fresh installation, you can run scripts to drop a portion or all of the schema objects.
- You can drop the schema objects that were created when you ran the non-DBA script
(op-database-product-install.sh|.bat).
Use this option to remove all of the schema objects from the OpenPages® database schema user. See Dropping OpenPages schema objects in an Oracle database.
After you drop the schema objects, you can re-run the op-database-product-install.sh|.bat script. See Running the steps that do not require DBA privileges.
- You can drop the database objects created by both the
op-database-dba-install.sh|bat and
op-database-product-install.sh|.bat scripts.
Use this option to remove all of the schema objects from the OpenPages database schema user, drop the tablespaces, and keep the OpenPages schema user. For this option, run the init-db-cleanup.sql script with the
keepuserparameter. See Dropping the full schema in an Oracle database.After you complete this step, re-run the op-database-dba-install.sh|bat and op-database-product-install.sh|.bat scripts to create the OpenPages database schema objects. See OpenPages database schema creation for Oracle.
- You can drop the database objects (created by the
op-database-dba-install.sh|bat,
op-database-product-install.sh|.bat) and drop the schema owner created by
op-database-sysdba-install.sql scripts.
Use this option to remove all of the schema objects from the OpenPages database schema user, drop the tablespaces, and drop the OpenPages schema user. For this option, run the init-db-cleanup.sql script and specify
xfor thekeepuserparameter. See Dropping the full schema in an Oracle database.After you complete this step, re-run op-database-sysdba-install.sql, and then re-run the op-database-dba-install.sh|bat and op-database-product-install.sh|.bat scripts. See OpenPages database schema creation for Oracle.