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

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

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
14 26-Nov-2021 10:22 5 KB JAiken to previous
13 26-Nov-2021 10:22 5 KB JEscott to previous | to last
12 26-Nov-2021 10:22 5 KB JEscott to previous | to last
11 26-Nov-2021 10:22 5 KB JEscott to previous | to last
10 26-Nov-2021 10:22 5 KB JEscott to previous | to last
9 26-Nov-2021 10:22 5 KB JEscott to previous | to last
8 26-Nov-2021 10:22 5 KB JEscott to previous | to last
7 26-Nov-2021 10:22 5 KB JEscott to previous | to last
6 26-Nov-2021 10:22 5 KB JEscott to previous | to last
5 26-Nov-2021 10:22 5 KB JEscott to previous | to last
4 26-Nov-2021 10:22 5 KB JEscott to previous | to last
3 26-Nov-2021 10:22 5 KB JEscott to previous | to last
2 26-Nov-2021 10:22 5 KB JEscott to previous | to last
1 26-Nov-2021 10:22 1 KB JEscott to last

Page References

Incoming links Outgoing links
COPY PILOT DATA TO PROD DB
COPY PILOT DATA TO PROD DB

Version management

Difference between version and

At line 18 changed one line
NOTE: if you are a “Quick Start” customer, the database is located on an Oracle server in our office. We will have to export the data and provide this on the FTP server for downloading.
NOTE: if you are a “Quick Start” customer, the database is located on an Oracle server in Toronto. High Line will have to export the data and provide this on the FTP server for downloading.
At line 20 changed one line
!Step 2: Drop Personality
!Step 2: Drop [{$applicationname}]
At line 35 changed one line
The import process will generate errors during the creation of some of the Oracle objects. Generally, these errors can be ignored. The next step will clean up the data that did not get created correctly. If the clean up process does not correct all the Oracle objects the log file, list above, will need to be sent to Support to identify the problem.
The import process will generate errors during the creation of some of the Oracle objects. Generally, these errors can be ignored. The next step will clean up the data that did not get created correctly. If the clean up process does not correct all the Oracle objects the log file, list above, will need to be sent to High Line Support to identify the problem.
At line 38 changed one line
Clean up import errors generated when loading the data. The IMP command loads all the objects into the new database in a very specific order. This order does not match the order we use to create a new database from scratch. This different load order attempts to create views and functions the reference functions that do not exist yet. To resolve these reference errors in the loaded objects, an SQL script has been provided that will recompile all the stored objects that are invalid. To run this script, you must load onto SQL Plus as P2K and issue the {{@DB_RECOMPILE}} command.
Clean up import errors generated when loading the data. The IMP command loads all the objects into the new database in a very specific order. This order does not match the order High Line uses to create a new database from scratch. This different load order attempts to create views and functions the reference functions that do not exist yet. To resolve these reference errors in the loaded objects, High Line has provided an SQL script that will recompile all the stored objects that are invalid. To run this script, you must load onto SQL Plus as P2K and issue the {{@DB_RECOMPILE}} command.
At line 42 changed one line
If there are still errors at the end of this process forward a copy of the log file generated by this script to Support. A copy of the DMP file and the log generated by the export may also be needed.
If there are still errors at the end of this process forward a copy of the log file generated by this script to High Line support. A copy of the DMP file and the log generated by the export may also be needed.
At line 47 changed one line
Deleting the employee data is done in two steps. The first step is to delete the employees’ payroll information. This is done using a supplied SQL script named DB_UNPILOT.SQL. Again, this script must be run in SQL Plus as P2K. The second step is to delete the employees them self. Again an SQL script has been provided to do this called DB_PERSON_DELETE.SQL. This script is slightly different than the first, in that it will prompt for an employee to delete. Simply replying with a single percent sign [%] will delete all employees.
Deleting the employee data is done in two steps. The first step is to delete the employees’ payroll information. This is done using a High Line supplied SQL script named DB_UNPILOT.SQL. Again, this script must be run in SQL Plus as P2K. The second step is to delete the employees them self. Again High Line has supplied an SQL script to do this called DB_PERSON_DELETE.SQL. This script is slightly different than the first, in that it will prompt for an employee to delete. Simply replying with a single percent sign [%] will delete all employees.
At line 50 changed one line
Since the users in the PILOT database may not exist as users in the PROD database, or may not exist with the same privileges, we need to recreate the security settings for the users. There is an SQL script that can be used to read the users information and recreate them at the Oracle database level. Start an SQL Plus session, log on as the P2K user and run the DB_UMRS.SQL script.
Since the users in the PILOT database may not exist as users in the PROD database, or may not exist with the same privileges, we need to recreate the security settings for the users. High Line has created an SQL script that can be used to read the users information and recreate them at the Oracle database level. Start an SQL Plus session, log on as the P2K user and run the DB_UMRS.SQL script.
At line 53 changed one line
Since the information in the database has changed significantly, it is recommended that you analyze the data and compute the statistics. Again, use the supplied script DB_ANALYZE_SEL.SQL script to do this.
Since the information in the database has changed significantly, it is recommended that you analyze the data and compute the statistics. Again, use the High Line supplied script DB_ANALYZE_SEL.SQL script to do this.
At line 56 removed 5 lines
----
![Notes|Edit:Internal.COPY+PILOT+DATA+TO+PROD+DB]
[{InsertPage page='Internal.COPY+PILOT+DATA+TO+PROD+DB' default='Click to create a new notes page'}]
This page (revision-14) was last changed on 26-Nov-2021 10:22 by JAikenTop