How to test the Capital installation upgrade steps before migrating to a new version running with Oracle based production environment?

To test the upgrade steps before migrating to a new version of Capital, an equivalent test/development environment must be set up with the same Oracle version and Capital version used in production.

Steps for DBA to create a copy of the Capital Oracle database for the migration test:

1. Perform an Oracle export of the production database.  This could be a .dmp file or a datapump file depending on the Oracle version.
2. Create an empty Oracle database with the parameters and options listed below:
   • It is recommended that CAPITAL is used for the Global Database Name and also CAPITAL for the SID.
   • Deselect any Database Features and Additional database configurations.
   • Set a Block Size of at least 8 K Bytes in the settings for DB Sizing.
   • Set the deferred_segment_creation parameter to FALSE in the All Initialization Parameters.
   • Set an open_cursors parameter of at least 3000 in the All Initialization Parameters.
   • On the Memory tab of the Database Configuration Assistant, ensure SGA and Aggregate PGA Targets are tuned for the volume of data and concurrent users. 
   • On the Character Sets tab of the Database Configuration Assistant, select Use Unicode (AL32UTF8) and a National Character Set of UTF8. 
   • Set the REDO LOG File Sizes and LOG_BUFFER Sizes as appropriate for your volume of transactional data and concurrent users. 
   • For more information on creating a database for Capital see the "Install Guide for Capital on Oracle". Look for the section titled "Oracle Installation and Creation of Empty Database". Use the guide for the current version getting replicated.
3.  Run the configure_database.sql script on the new database. This will create the tablespaces, role, and Capital Oracle user (schema owner). 
   • The script is located in the folder <Capital Install Folder>\data\sql\oracle of the installed Capital version in production.
   • To run the script, the DBA must be connected to the database as the Oracle user SYSTEM
   • The DBA may need to edit the script for location path of database files. 
   •  Read the notes at the beginning of the script for more details about creating the schema. By default, a new database user CAPITAL is created with a default tablespace named CHS.
   • Caution: By default, the CHS and ANALYSIS tablespaces' space management are set to MANUAL. If the SecureFiles Oracle feature has been used to create the Capital database in step 2, edit the script and change the space management from MANUAL to AUTO. 
4. Import the file created in step 1 into the new Capital database.  Please consult the KB Articles on using the imp command for a dmp file, or the impDP for a datapump file, according to the Oracle export command used.

Once the database has been copied, install the same Capital version as in production, following the "Install Guide for Capital on Oracle" using the new test environment Oracle Connection Details.  Caution: Do NOT select to Configure database for the first time as the database already exists.

Now you have a replica of the production environment and can proceed to follow the "Upgrade Guide for Capital on Oracle" for the new version.