*** IMPORTANT ***
The following information is UNSUPPORTED.
There is no delivered documentation on how to clone an existing system into a new environment. The GCS and Development consider this to be out of scope and as such it is unsupported. However, we have compiled the following information which could render assistance.
*** IMPORTANT ***
1) Copy the database
2) If your database platform has the table PS.PSDBOWNER, please don't forget to update it for the name of the database and ownerid, both in caps, ie:
INSERT INTO PS.PSDBOWNER VALUES ('H512O732','SYSADM');
3) If there is to be a different access ID and/or password you must update PSACCESSPRFL. To change just the access password use the
CHANGE_ACCESS_PASSWORD
command in Data Mover in bootstrap mode.
4) Edit, if necessary, and run the CONNECT.SQL and GRANT.SQL scripts
5) For PeopleTools 8.44 and higher, blank out the GUID in the PSOPTIONS table
6) Create new Application Server Domain (delete old one)
7) Create new PIA (delete old one)
8) For PeopleTools 8.44 and higher, update the Long name, Short name, and System Type in PeopleTools -> Utilities -> Administration -> PeopleTools Options
9) Update the Report Node definitions
10) Clear out the Process tables with PRCSCLR.DMS
Note: Still required to be run if the cloned database has the same name
11) Clear out the content tables with RPTCLR.DMS
11) Clear out the content tables with RPTCLR.DMS
Note: Still required to be run if the cloned database has the same name
12) Create new Process Scheduler domain (delete old one)
13) Make sure old URL information has been updated.
14) What we generally tell customers is that the things to look for include any node URI values (PSNODEURITXT) and of course we recommend a file system search on the PS_HOME for old values. We would also recommend looking over the webprofiles for any old values.
The following tables are a solid place to start:
SELECT * FROM PSPRDMDEFN
SELECT * FROM PSPRDMCNTPRV
SELECT * FROM PSMSGNODEDEFN
SELECT * FROM PSNODEURITEXT
SELECT * FROM PSTRUSTNODES
Make sure that the Local Default Node is correct and that it's URI values are correct. It also has to be in the trusted nodes list (it normally is automatically....). Also make sure that your Portal Registry is hosted by the correct node.
Generally this may require tweaking information manually in SQL until you get all the old data changed over. Focus on the Default Local Nodes as well as the portal definitions (as they may point to defunct nodes now).
15) For PeopleTools 844 and higher, also check the web profiles table called: PSWEBPROFNVP
Please run the following SQL to check the webprofile Virtual Addressing settings:
select * from PSWEBPROFNVP WHERE PROPERTYNAME='DEFAULTSCHEME' OR PROPERTYNAME='PSWEBSERVERNAME' OR PROPERTYNAME='DEFAULTPORT' OR PROPERTYNAME='AUTHTOKENDOMAIN'
Please ensure that these values are NOT pointing to your old environment.
12) Create new Process Scheduler domain (delete old one)
13) Make sure old URL information has been updated.
14) What we generally tell customers is that the things to look for include any node URI values (PSNODEURITXT) and of course we recommend a file system search on the PS_HOME for old values. We would also recommend looking over the webprofiles for any old values.
The following tables are a solid place to start:
SELECT * FROM PSPRDMDEFN
SELECT * FROM PSPRDMCNTPRV
SELECT * FROM PSMSGNODEDEFN
SELECT * FROM PSNODEURITEXT
SELECT * FROM PSTRUSTNODES
Make sure that the Local Default Node is correct and that it's URI values are correct. It also has to be in the trusted nodes list (it normally is automatically....). Also make sure that your Portal Registry is hosted by the correct node.
Generally this may require tweaking information manually in SQL until you get all the old data changed over. Focus on the Default Local Nodes as well as the portal definitions (as they may point to defunct nodes now).
15) For PeopleTools 844 and higher, also check the web profiles table called: PSWEBPROFNVP
Please run the following SQL to check the webprofile Virtual Addressing settings:
select * from PSWEBPROFNVP WHERE PROPERTYNAME='DEFAULTSCHEME' OR PROPERTYNAME='PSWEBSERVERNAME' OR PROPERTYNAME='DEFAULTPORT' OR PROPERTYNAME='AUTHTOKENDOMAIN'
Please ensure that these values are NOT pointing to your old environment.
16) Generate a new, unique GUID for PSOPTIONS table.
Please also refer to the solution references below which are related to cloning databases.
*** IMPORTANT ***
This is meant to be a guideline resolution because we get many requests and problems from cloned systems. Although we don't support it, we will continue to add information to this resolution so customers can guide themselves. We tell customers to do a full DB search for the old server address as well as searching the file structure. If you have successfully created a plan and detailed what you look for we would certainly add customer feedback to this resolution.
NOTE:
The GCS can't assist with problems caused by cloned databases.
*** IMPORTANT ***
KEYWORDS:
Refresh, Migrate, Clone, Copy, Duplicate, Restore, Backup, Unsupported Resolution
