This is version 1 2 3 4 5 6 7 8 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

Database Check List#

Introduction#

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 Wiki for problem resolution. The list below is written to be used either by a client or internally at Wiki.

---

Information Required#

• 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.
  

---

After Import#

• 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
  • DB_SANITIZE_DATA.sql removes or camouflages all of the above as well as zip/postal codes, business numbers, and rotates around last names to make the data unrecognizable.
• IF US Taxation is required for the environment, then configure the Vertex server.
• 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 required, change the mail server settings to appropriate values
  • Configure Oracle Reports Server parameter entries
    • REP CACHE EXPIRY
    • REP DB ALIAS
    • REP SERVER IP
    • REP SERVER NAME
    • REP SERVER PORT
  • Set the directory for attachments, load, extract parameters, and images
    • ATTACHMENTS FLDR (also used by Reports)
    • EXTRCT DATA FLDR
    • LOAD DATA FLDR
    • EMP IMAGE FLDR
  • Set the IMST Description to reflect appropriate environment. At HLC, this should be customer, Pilot/Prod, and AS/DB Environment
• Update tracking information and Index.html with current information as required
• 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