Loading Client Data#

The following steps can be used to load client supplied DMP file into an internal database for testing.

1. Using the Application Access page, identify where the clients dump file is to be loaded
   * for this example, we'll assume DB05.CASTOR
2. Determine if the dump file was created by EXP or EXPDP. If a log file was not provided, you may need to call the client.
3. Log into the target database and confirm that it contains the data defined in the Application Access page.
   • SELECT DESCRIPTION FROM P2K_AM_SITES;
4. Log into the target database as the P2K user and drop the current contents of the database with the DB_DROP.sql script.
   • If the existing database has a lot of extra custom objects you may be better off dropping the user entirely
5. Move a copy of the DMP file to the database server.
   * If this is a data pump file it MUST be loaded into the data pump directory defined by the directory object DATA_PUMP_DIR
   • SELECT * FROM ALL_DIRECTORIES;
6. Open a remote session on the database server Linux = SSH, Windows = RDP
7. Set the Oracle environment variables, such as ORACLE_SID, for the target database.
   * Use the '. oraenv' command in Linux.
8. Run the import data pump command to load the data
   • eg. impdp SYSTEM/PASS@DB dumpfile=EXPDP_TEST.DMP logfile=Import.log schemas=p2k
9. From an SQL Plus session connected as SYS, run the SYS_UPGRADE.sql script.
10. From an SQL Plus session connected as P2K, run DB_RECOMPILE.SQL, DB_CREATE_CONTEXT.sql
11. From an SQL Plus session connected as P2K, run the DB_SANITIZE_DATA script
12. Reset the P2K password to a known value, IE p2k. This should match the Application Access page setting.
    • UPDATE P2K_AM_ACCESS_RULES SET VALIDATION_METHOD = 'SHA' WHERE ACCESSOR_TYPE = 'MUS';
    • UPDATE P2K_AM_ACCESSOR_DETAILS SET PASSWORD_HASH = NULL, ACCESS_STATUS = '01' where mac_id = (select ID from p2k_am_accessors where mus_id = (select ID from p2k_am_users where user_name= 'P2K'));
    • UPDATE P2K_AM_USERS SET USER_PASSWORD = 'p2k', PASSWORD_CHANGED_DATE= SYSDATE where user_name = 'P2K';
    • COMMIT;
13. Ensure the application instance that is connected to the database is running the correct version of EP.
    • The Application EAR may need to be replaced, or the database upgraded to the correct software level.
14. Once access to the database from the EP application is possible, several IMST parameters must be altered. All of the following entries will need to point to directories on our application server.
    • ATTACHMENTS FLDR
    • EXTRCT DATA FLDR
    • LOAD DATA FLDR
    • EMP IMAGE FLDR
15. Update the IMST preferences for
    • HELP_URL .. set to http://argo.highlinecorp.com/Wiki/Wiki.jsp?page=
    • REP DB ALIAS .. set to the database you have just loaded
    • REP SERVER IP .. set to wvmwlrs.highlinecorp.com
    • REP SERVER NAME .. set to rep_wls_reports_wvmwlrs_asinst_1
    • REP SERVER PORT .. set to 9001
16. Update other IMST values
    • Set MAIL HOST .. mail.exchange.telus.com
    • Set MAIL_DOMAIN .. highlinecorp.com
    • Set MAIL_AUTH_USER .. noreply@highlinecorp.com
    • Set EMAIL_ADDRESS preference .. devdb2@highlinecorp.com
    • Set the Description to indicate the database contents, what database and what app server this is (e.g. AS01.BREVIS - DB01.DIDO - NFI)
17. If appropriate set the IMST preferences for
    • LOGISERVERURL
    • ORACLE_BIPUBLISH
    • SITE_LOGO_URL .. May not be used in NextGen
18. Install and configure Symmetry Tax Engine, if needed
    • Don't forget to set the IMST preferences if using it
19. UPDATE the Application Access page with the new version and customer data
20. Delete the dump and zip files

HighLine.Standard Operating Procedures