PeopleSoft Data Mover Overview Transfer application data between PeopleSoft databases. Move PeopleSoft databases across operating systems and database platforms. Execute Structured Query Language (SQL) statements against any PeopleSoft database, regardless of the underlying operating system or database platform. Control database security and access. Create, edit, and run scripts. These scripts may include any combination of SQL commands and PeopleSoft Data Mover commands for exporting and importing data. Data Mover Modes Regular mode. Most of the time, you use regular mode. To sign in to regular mode, enter your PeopleSoft user ID and password during sign-in. In regular mode, all commands are valid. Bootstrap mode. In bootstrap mode, you use a database access ID and password when signing in. Typically, you use bootstrap mode for database loading, because no PeopleSoft security tables are established yet. You also use bootstrap mode for running some security commands, such as ENCRYPT_PASSWORD Data Mover Script Commands ENCRYPT_PASSWORD EXPORT IMPORT REM REMAR RENAME REPLACE_ALL REPLACE_DATA REPLACE_VIEW\ RUN SET SET IGNORE_ERRORS SET BASE_LANGUAGE SWAP_BASE_LANGUAGE 1 Changing Access Password Below are the methods to change the access password in a PeopleSoft Application Method 1 : Login into Data Mover and run the below command CHANGE_ACCESS_PASSWORD <Symbolic Id> <New Access Password> Symbolic id : eg. SYSADM1 in Oracle aand sa1 in oracle Method 2: Change using Application Designer Go to Application Designer > Tools > Miscellaneous Objects > Access Profile Choose the Symbolic ID Enter Old Password . ACCESSPSWD = '<New Access Password>' . where SYMBOLICID = '<Symbolic Id>'. New Password and Confirm the New Password Method 3: Changing Access Password from Database Login into Data Mover in bootstrap mode and run the below SQL Update PSACCESSPRFL set ACCESSID = '<Access Id>'. ENCRYPTED = 0. Then Run ENCRYPT_PASSWORD * 2 . dms” in your documentation. 1. It is also recommended to have regular maintenance runs of these audits to resolve integrity issues on a proactive basis. Ensure that the reports match 2. For any mismatch there has to be an explanation Note 1: UPGCOUNT might not match for all records after application of Maintenance Pack/Bundle/Upgrade. UPGCOUNT (just prior to the actual migration) The first three can be executed a few hours or days before the actual migration as long as you ensure that no changes are migrated or performed in to the target environment which might cause an impact on these reports. DDDAUDIT and ALTER AUDIT report. DDDAUDIT 3. application of bundles/ patches. However the UPGCOUNT process has to run just prior to the actual migration because this provides a row count of every record in the DB. Record PSPRCSRQST Before 10002 After 10008 Comments Bundle # 11 – Execution of SQR program in step 21. PeopleSoft provides Audit reports which includes DDDAUDIT. 29. The objective should be as noted below. 22. I’ll just highlight the other reports. You need to identify what caused the change. SYSAUDIT 2. You need to re-run the above reports after completion of the migration. ALTER AUDIT 4. It is important to understand the purpose and the usage of these reports to make correct decisions for the objects in the system.dms BENEFIT_PARTIC 103110 103212 Note 2: It is a good practice to ensure that you have a clean SYSAUDIT.PeopleSoft Audit Reports and Migration Prior to application of the bundles execute the following. 3 . There was an earlier article on the same topic with the focus on UPGCOUNT to report the counts of the tables. This exercise will ensure that you have a clean migration. 1. Bundle # 12 – Execution of data mover script upgnnnn. You can denote “Bundle 12 – Data Mover script upgnnnn. In this post. SYSAUDIT. Alter Audit to check the integrity of the PeopleSoft system especially after major changes to the system such an upgrade. major customization. length and the structure match. However. The Alter Audit helps bring synchronization between the structure of the PS record definition and the actual database table. Security Retrofit during an Upgrade can take inputs from SEC-28 section of the SYSAUDIT which reports invalid entries in PSAUTHITEM. the Database Audit report reports the inconsistencies between the PeopleSoft Record and Index objects and the Database objects. For PeopleSoft Systems which face App Server errors/ disruptions due to an invalid object load in the cache. this report runs into a number of pages in an Upgrade because of the large amount of changes between one version and another. During an Upgrade. one of the core tables for Permission lists. one can fix the object inconsistencies during the development phase when most of the retrofit activity is completed which automatically resolves many of the issues. Keeping clean audits helps you to apply major bundles or maintenance packs or even prepare for Upgrades in a controlled environment. new objects (TABLE-2 & VIEWS-1) need to be built correctly so as not to have any inconsistencies reported. It is a good practice to regularly run these reports and ensure they are clean so that potential issues due to such inconsistencies can be avoided in the system. Usually.DDDAUDIT. SYSAUDIT. the root cause might point to PSLOCK version integrity for which a version Application Engine may have to be run. It is important to review this report to filter such objects (TABLE-3 & VIEWS-2) and remove them from the database if they are dropped at the PS metadata tables. There are more than 300 integrity checks and reported on individual section on the various object types that one can find in the SYSAudit report. Likewise. For Systems where there are frequent Tree Level changes. format.51 PeopleBook: Data Management > Ensuring Data Integrity. the section on Tree Integrity queries can be referred to check and cleanup accordingly. This is to ensure that all data types. the System Audit report reports orphan PeopleSoft objects & inconsistencies within the PeopleSoft metadata. 4 . The error descriptions and their resolutions can be found in Peoplebooks at this location: Home > PeopleBooks > Enterprise PeopleTools 8. Unique Indexes (INDEX-3) reported in this report after an Upgrade usually indicates that the base table has duplicate rows which requires validation of the upgrade and conversion scripts. a significant number of objects get dropped or added newly in the latest version. 5 . 6 .