This page (revision-8) was last changed on 26-Nov-2021 10:22 by kparrott

This page was created on 26-Nov-2021 10:22 by JMyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
8 26-Nov-2021 10:22 3 KB kparrott to previous
7 26-Nov-2021 10:22 3 KB jaiken to previous | to last
6 26-Nov-2021 10:22 3 KB JMyers to previous | to last
5 26-Nov-2021 10:22 3 KB JMyers to previous | to last
4 26-Nov-2021 10:22 3 KB JMyers to previous | to last
3 26-Nov-2021 10:22 3 KB JMyers to previous | to last
2 26-Nov-2021 10:22 3 KB JMyers to previous | to last
1 26-Nov-2021 10:22 3 KB JMyers to last

Page References

Incoming links Outgoing links
DATABASE LOAD CHECKLIST
DATABASE LOAD CHECKLIST

Version management

Difference between version and

At line 6 changed one line
When copying a database environment there are several points to be considered or done whether it is taking a copy of a production data to a test environment or to [{$applicationname}] for problem resolution. The list below is written to be used either by a client or internally at [{$applicationname}].\\
When copying a database environment there are several points to be considered or done whether it is taking a copy of a production data to a test environment or to Support for problem resolution. The list below is written to be used either by a client or internally at Support.\\
At line 9 changed 2 lines
*EXP/IMP & Database Versions\\The database version as well as the EXP tool used need to be noted to ensure the environment it is to be loaded to is at least at that level.
*Table Space Sizes\\The size of the table spaces as well as the amount used of those table spaces needs to be noted and the receiving environment made large enough to hold more than the used amount.\\
*EXP/IMP & Database Versions\\The database version, as well as the EXP tool used, needs to be noted to ensure the environment it is to be loaded to is at least at that level.
*Table Space Sizes\\The size of the table spaces, as well as the amount of table spaces used, needs to be noted and the receiving environment made large enough to hold more than the used amount.\\
At line 13 changed 2 lines
*Does the personal information contained within the database need to be hidden/camouflaged?\\If yes, there are 2 scripts available BUT before running either of these scripts the DB_DROP_WF_TRIGGERS.sql script should be run. In addition, you you are NOT upgrading the data with a full seed then the SEED_CREATE_BIUD.pls script will need to be run after.
**DB_IMPORT_DATA_CLEAR.sql removes or camouflages email addresses, phone numbers, government codes, bank accounts, street addresses
*Does the personal information contained within the database need to be hidden/camouflaged?\\If yes, there are two scripts available BUT before running either of these scripts the DB_DROP_WF_TRIGGERS.sql script should be run. In addition, if you are NOT upgrading the data with a full seed, then the SEED_CREATE_BIUD.pls script will need to be run after.
**DB_IMPORT_DATA_CLEAR.sql removes or camouflages email addresses, phone numbers, government codes, bank accounts, street addresses.
At line 17 changed 8 lines
*If necessary, change the P2k user password to be different than the former one. Contact Tech support for further instructions if required.
*Execute the DB_UMRS.sql script to populate the database level with the security as defined in the Personality tables.
*It is advisable to set any uncompleted WF logs to ‘Cancelled’ using SQL to prevent them from firing.
*Determine current the ePersonality level installed and if an upgrade is required to what level.
If upgrading, follow the instructions for that upgrade level.
*Check Windward Libraries currently in place for compatibility with software level being installed
*Ensure the appropriate Windward Templates are in place for the ePersonality version being installed
*IMST settings
*If necessary, change the P2k user password to be different than the former one. Contact Tech Support for further instructions if required.
*Execute the DB_UMRS.sql script to populate the database level with the security as defined in the [{$applicationname}] tables.
*It is advisable to set any uncompleted [WF|WORKFLOW] logs to ‘Cancelled’ using SQL to prevent them from firing.
*Determine current the [{$applicationname}] level installed and if an upgrade is required, to what level.\\If upgrading, follow the instructions for that upgrade level.
*Check the Windward Libraries currently in place for compatibility with software level being installed
*Ensure the appropriate Windward Templates are in place for the [{$applicationname}] version being installed
*[IMST] settings
At line 37 changed one line
**Set the IMST Description to reflect appropriate environment. At HLC, this should be customer, Pilot/Prod, and AS/DB Environment
**Set the [IMST] Description to reflect appropriate environment. At [{$applicationname}], this should be customer, Pilot/Prod, and AS/DB Environment
At line 39 changed 4 lines
*Test system components setup above
**Oracle Reports – Run a report like RMFN in Oracle to ensure all works properly
**Windward – Run a report like RAAC in Windward to ensure all works properly
**Vertex – Use IMSM to Ping the Vertex Server to ensure it is responding
*Test the system components setup above
**Oracle Reports – Run a report like [RMFN] in Oracle to ensure all works properly
**Windward – Run a report like [RAAC] in Windward to ensure all works properly
**Vertex – Use [IMSM] to ping the Vertex Server to ensure it is responding
This page (revision-8) was last changed on 26-Nov-2021 10:22 by kparrottTop