Can use either of the below options to perform the test refresh from production database.
Option 1:
- First backup the production data base library to tape (or to a save file), then restore from the tape (or the save file) to the test data base library
- Rename or delete the test database library first so all objects within the library are replaced by restoring the copy of the production library
- AWR database library is E3Tcustid
- ASR or VMR database library is E3Scustid
Option 2:
- Copy the production data base library to the test data base library after ensuring that there are no users on the system using both data bases
- If test and production are at a different version (or Service Pack level), then E3 Data base update needs to be executed using t he E3DBUPDAT command over the refreshed test database library
- After running the E3DBUPDAT tool contact JDA Support for verification of the test environment
- If there any logical files in “U”, “C”, or “P” libraries pointing to the "S" or "T" library, these logical files will have to be recompiled over the refreshed database library
- If the customer id in the Test environment is different than the customer id for Production, then update the customer id in the Test company control settings
- After the above steps are completed either using Option 1 or Option 2, need to validate the below settings:
- Change customer ID in the Company Control factors to match new CUSTID (for example: "XYZTS")
- Change the customer name field in Company file to indicate “TEST” to identify test system for users
- Change the two libraries in the E3ICNTRL data area in the E3(S)XYZTS to be the new test library values
If needed; contact JDA Support for assistance working with data areas
Please contact JDA Support if your settings are different or for any specific instructions.
