Tag Archives: Maintenance Pack

PeopleSoft HR 8.9 Installation Checklist

Posted by on August 28, 2009 No comments

1. Install SQL Server

2. Install SQL Server Native Client

3. Stage PeopleTools 8.49 CDs on F:stagingpt-849

4. Install PeopleTools 8.49 on peoplesoft4hr (E:PSOFTHR900)

5. Install Application (Human Resources) on peoplesoft4hr

6. Install Database Manually

7. Task B-1: Running Server Configuration Scripts

8. Task B-2: Creating a Database

9. Task B-3: Configuring ODBC Data Source

10. Task B-4: Running ADDOBJ.SQL

11. Task B-5: Setting Up Connect ID

12. Task B-6: Creating Data Mover Import Scripts

13. Task B-7: Running Data Mover Import Scripts

14. Task B-8: Updating Database to Latest PeopleTools Release

15. Task B-8-2: Updating PeopleTools System Tables

16. Task B-8-3: Updating PeopleTools Database Objects

17. Task B-8-5: Deleting Obsolete PeopleTools Database Objects

18. Task B-8-6: Altering PeopleTools Tables

19. Task B-8-7: Updating PeopleTools System Data

20. Task B-8-8: Running PeopleTools Conversions

21. Task B-9: Running Additional Data Mover Scripts

22. Task B-11: Running VERSION Application Engine Program

23. Task B-12: Changing the Base Language

24. Task B-13: Running SQR Reports

25. Task B-14: Checking the Database

26. Task B-15: Cleaning and Backing Up the Database

27. Shutdown, Backup Database After Creating

28. Install Tuxedo (Application Server)

29. Install BEA WebLogic 9.2 Web Server

30. Install PIA

31. Create Application Domain

32. Install PeopleTools PeopleBooks

33. Install Application PeopleBooks

34. Create Process Scheduler

35. Install COBOL compiler (and license)

36. Execute PTPATCH.DMS using Data Mover (8.49.15)

37. Apply project PATCH849 using Application Designer

38. Run DDDAUDIT, SYSAUDIT to verify system ok, troubleshoot if necessary

39. Shutdown all servers and backup PS_HOME

PIA Installation on IBM WebSphere Hangs on 20%

Posted by on February 4, 2009 Comments Off on PIA Installation on IBM WebSphere Hangs on 20%

PIA Installation on IBM WebSphere Hangs on 20%

Problem:

When installing new PIA on IBM WebSphere, the installation hangs for several minutes at 20%

Solution:

Installation takes a long time to complete. If the timeout is not long enough, the installation may fail. (Applying MP5 appears to have resolved this). Else, manually increase the timeout.

ZFSCM900_DROP5_PRE_DMS Errors

Posted by on January 28, 2009 No comments

Problem:

When running the ZFSCM900_DROP5_PRE_DMS step to drop unneeded views, many steps complete in error:

SQL Error. Error Position: 0 Return: 601 - [Microsoft][SQL Native Client][SQL Server]
Cannot drop the view 'PS_XXXX_XX_XXXX_VW', because it does not exist or you do not have permission.

The end of the log file states ‘Successful Completion’.

Solution:

This is expected behaviour. The MP5 documentation states:

Dropping Views
In this step, if you encounter an error, due to some tables and views previously dropped or already do not exist in the database, please ignore the error, mark this step as Complete and continue with the Maintenance Pack installation. Note that the script log would still mark as Successful completion.

DDDAUDIT Errors After Running FSCM MP5

Posted by on January 24, 2009 No comments

DDDAUDIT Errors After Running FSCM MP5

Problem:

After completing FSCM MP5, the DDDAUDIT report is run. The following errors appear:

(TABLE-2) SQL Table defined in the Application Designer and not found in the Database:
 Record Name Ownerid
 --------------- -------
 BP_ACT2_TAO FGL
 BP_APA_S_TAO FAP
 BP_APN_S_TAO FAP
 BP_APV_S_TAO FAP
 BP_ARM_S_TAO FAR
 BP_ARR_S_TAO FAR
 BP_BDHDR_TAO FGL
 BP_BDLN_TAO FGL
 BP_BI_S_TAO DBI
 BP_BKOUT_TAO FGL
 BP_CF_TAO FGL
 BP_CM_S_TAO DCM
 BP_EX_S_TAO FEX
 BP_FSRC_TAO FGL
 BP_GEN_S_TAO FGL
 BP_GLB_S_TAO FGL
 BP_GL_S_TAO FGL
 BP_GM_S_TAO FGM
 BP_HR_S_TAO FGL
 BP_LQDFS_TAO FGL
 BP_LQD_TAO FGL
 BP_PC1_S_TAO FPC
 BP_PC_S_TAO FPC
 BP_PFS1_TAO FGL
 BP_PFS2_TAO FGL
 BP_POA_S_TAO DPO
 BP_POC_S_TAO DPO
 BP_PO_S_TAO DPO
 BP_PRNT_TAO FGL
 BP_PST1_TAO FGL
 BP_PST2_TAO FGL
 BP_REFDBK_TAO FGL
 BP_REFD_TAO FGL
 BP_RQN_S_TAO DPO
 BP_RQ_S_TAO DPO
 BP_TA_S_TAO FEX
 BP_XCF2_TAO FGL
 BP_XCF_TAO FGL
 BP_XLBP_TAO FGL
 EX_ADVLN_TAO FEX
 EX_ADVLSS_TAO FEX
 EX_STGSHT_TMP FEX
 FS_CE_CFV_TAO FGL
 VUN_DOC_TAO FAP
 VUN_RVS_TAO FAP
 VUN_UNP_TAO FAP
 46 Total Rows
(TABLE-3) SQL Table defined in the Database
 and not found in the Application Designer:
 SQL Table Name
 ------------------
 PS_VNDR_ORDER_TMP
 PS_VNDR_REMIT_TMP
 PS_WEBLIB_EX_TV
 3 Total Rows
(TABLE-4)INFORMATIONAL ONLY - Tablespace not
 defined for SQL Table in the Application
 Designer: No rows found.
(TABLE-5) Table Contains More Than 500
 Fields : No rows found.
(VIEWS-1) Views defined in the Application
 Designer and not found in the Database: No rows found.
(VIEWS-2) Views defined in the Database and
 not found in the Application Designer: No rows found.
(INDEX-1) Index defined in the Application
 Designer and not found in the Database:
 Record Name Index ID Ownerid
 --------------- -------- -------
 BP_ACT2_TAO A FGL
 BP_ACT2_TAO B FGL
 BP_ACT2_TAO _ FGL
 BP_APA_S_TAO A FAP
 BP_APA_S_TAO B FAP
 BP_APA_S_TAO _ FAP
 BP_APN_S_TAO A FAP
 BP_APN_S_TAO B FAP
 BP_APN_S_TAO _ FAP
 BP_APV_S_TAO A FAP
 BP_APV_S_TAO B FAP
 BP_APV_S_TAO _ FAP
 BP_ARM_S_TAO A FAR
 BP_ARM_S_TAO _ FAR
 BP_ARR_S_TAO A FAR
 BP_ARR_S_TAO _ FAR
 BP_BDHDR_TAO 0 FGL
 BP_BDHDR_TAO _ FGL
 BP_BI_S_TAO A DBI
 BP_BI_S_TAO B DBI
 BP_BKOUT_TAO A FGL
 BP_CF_TAO A FGL
 BP_CF_TAO B FGL
 BP_CM_S_TAO A DCM
 BP_CM_S_TAO B DCM
 BP_CM_S_TAO _ DCM
 BP_EX_S_TAO A FEX
 BP_EX_S_TAO B FEX
 BP_EX_S_TAO _ FEX
(INDEX-1) Index defined in the Application
 Designer and not found in the Database:(continued)
 Record Name Index ID Ownerid
 --------------- -------- -------
 BP_FSRC_TAO A FGL
 BP_GEN_S_TAO A FGL
 BP_GEN_S_TAO _ FGL
 BP_GLB_S_TAO A FGL
 BP_GLB_S_TAO _ FGL
 BP_GL_S_TAO A FGL
 BP_GL_S_TAO _ FGL
 BP_GM_S_TAO A FGM
 BP_GM_S_TAO B FGM
 BP_HR_S_TAO A FGL
 BP_HR_S_TAO B FGL
 BP_LQDFS_TAO A FGL
 BP_LQD_TAO A FGL
 BP_PC1_S_TAO A FPC
 BP_PC1_S_TAO B FPC
 BP_PC_S_TAO A FPC
 BP_PC_S_TAO B FPC
 BP_POA_S_TAO A DPO
 BP_POA_S_TAO B DPO
 BP_POC_S_TAO A DPO
 BP_POC_S_TAO _ DPO
 BP_PO_S_TAO A DPO
 BP_PO_S_TAO B DPO
 BP_PO_S_TAO _ DPO
 BP_PST1_TAO A FGL
 BP_REFDBK_TAO A FGL
 BP_REFD_TAO A FGL
 BP_RQN_S_TAO A DPO
 BP_RQN_S_TAO _ DPO
 BP_RQ_S_TAO A DPO
 BP_RQ_S_TAO _ DPO
 BP_TA_S_TAO A FEX
 BP_TA_S_TAO _ FEX
 BP_XCF_TAO A FGL
 BP_XCF_TAO B FGL
 BP_XCF_TAO C FGL
 EX_ADVLN_TAO A FEX
 EX_ADVLN_TAO _ FEX
 EX_ADVLSS_TAO _ FEX
 EX_STGSHT_TMP A FEX
 EX_STGSHT_TMP B FEX
 EX_STGSHT_TMP _ FEX
 FS_CE_CFV_TAO A FGL
 VUN_DOC_TAO _ FAP
 VUN_RVS_TAO _ FAP
 VUN_UNP_TAO _ FAP
 75 Total Rows

Solution:

See the Acceptable Audit Errors section on page 53 for tips to resolving these errors, including deleting the tables under section TABLE-3

To rebuild the tables under the TABLE-2 section of the DDDAUDIT report, the RBL_MP5ERRORS_VS project was created in Application Designer and the SQL script was built to create the missing tables.

(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist in PSXLATITEM Table

Posted by on January 21, 2009 No comments

(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist in PSXLATITEM Table

Problem:

After running SYSAUDIT on FSDEV, the following error appears:

(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist In PSXLATITEM Table:
Query Name Field Name
 ---------- ----------------------
 ARDISH01 DRAFT_TYPE
 1 Total Rows

Solution:

1. Determine if scriptsPTPATCH.DMS was run. Log onto SQL Server Management Studio and running the following command:

select * from PS_MAINTENANCE_LOG where UPDATE_ID = '768890';

2. Next, load Application Designer and copy the PATCH849 project from file.

It was already copied.

3. Check PS_QRYFIELD_VW to see the fields used in the ARDISH01 query:

select * from dbo.PS_QRYFIELD_VW where QRYNAME = 'ARDISH01'

4. Get list of ‘DRAFT_’ field names from the PSXLATITEM table:

select distinct FIELDNAME from PSXLATITEM where FIELDNAME like 'DRAFT_%'

There is no DRAFT_TYPE field in this table.

5. Get list of ‘DRAFT_’ field names from the PSXLATITEM table:

Checked SYSAUDIT for FSDMO. This error is not present. Apply MP5 to FSDEV to resolve issue.

Build and Alter Step While Applying MP5

Posted by on January 16, 2009 No comments

The Build and Alter step (or ‘chapter’) consists of two tasks:

1. Build and Alter Task_1
2. Build and Alter Task

Under the first task (Build and Alter Task_1), there are two steps:
a. Build Step
b. Run Recreate Tables Script

No action is required for the Build and Alter Task_1 steps. Read the documentation in the right pane, and then mark the steps as Complete.

Under the second task (Build and Alter Task), there are seven steps:
a. Build and Alter Step
b. Run Create Tables Script
c. Run Alter Tables Script
d. Run Create Triggers Script
e. Run Create Views Script
f. Additional Step 02
g. Run Create Indexes Script

The first step (Build and Alter Step) can be run automatically. The step completes with warnings, as there are some records have over 16 keys or some record definitions do not exist. The log file is:
E:/temp/softwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5}/BuildAndAlter.log

The output scripts generated by the Build and Alter Step are located in E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5}

The second step, Run Create Tables Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateTables.sql script in SQL Server Management Studio. The CreateTables.sql script executed successfully in 59 seconds.

The third step, Run Alter Tables Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} AlterTables.sql script in SQL Server Management Studio. The AlterTables.sql script executed successfully in 1 minute 30 seconds.

The fourth step, Run Create Triggers Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateTriggers.sql script in SQL Server Management Studio. The CreateTriggers.sql script executed successfully in less than 1 second.

The fifth step, Run Create Views Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateViews.sql script in SQL Server Management Studio. The CreateViews.sql script executed successfully in 26 seconds.

The sixth step, Additional Step 02 is done by logging into PIA and populating the KEYLIST field.

The seventh step, Run Create Indexes Script is done by running the E:tempsoftwareupdateFSCM900_MP5{3d899576-cc86-11dd-930f-9c077f4a98a5} CreateIndexes.sql script in SQL Server Management Studio. The CreateIndexes.sql script executed successfully in 10 seconds.

Note: When these steps were first run against the FSDMO instance, the Create Views step failed because the PTPATCH.DMS script and PATCH849 project were not run against the database.

Errors on SYSAUDIT Report

Posted by on January 5, 2009 No comments

Problem:

After completing installing FSDEMO, SYSAUDIT is run. The following errors appear on the report:

Application Engine Audits Result: OK
Clear List Audits Result: OK
Electronic Commerce Audit Result: OK
Field Definition Audit Result: OK
Menu Definition Audit Result: OK
Security Audits Result: Exception(s) Found
(SEC-30) Role User table (ROLEXLATOPR) should be populated when new User Profiles (entries in PSOPRDEFN) are created
 using User Profile component through PIA. The following User Profiles need to be fixed by simply opening and saving
 them through PIA:
Oper ID Description
 - ----------------------------- ------------------------------
 ENTMGR_PRO Procurement Catalog Manager
 1 Total Rows
Page Definition Audit Result: OK
PeopleCode Definition Audit Result: OK
Process Scheduler Audit Result: OK
Query Definition Audit Result: Exception(s) Found
(QUERY-27) Following Queries Use XLAT Fields Whose Values Do not Exist In PSXLATITEM Table:
Query Name Field Name
 - ---------------------------------------------------------------------
 ARDISH01 DRAFT_TYPE
 1 Total Rows
Record Definition Audit Result: OK
Language Definition Audit Result: OK
SQL Audits Result: OK
Tree Definition Audit Result: OK
Version Check Audits Result: OK
XLATT Definition Audit Result: OK
Analytic Audit Result: OK
XML Publisher Audit Result: OK
Integration Broker Audits Result: Exception(s) Found
(IBRK-08) : IB Routing referencing invalid service operation:
Routing Operation Version
 - ------ --------- -------
 ~GEN~UPG~24567 IB_INST_VER_ASYNC_MSG VERSION_1
 ~GEN~UPG~17626 IB_INST_VER_RESP_MSG VERSION_1
 2 Total Rows
(IBRK-21) : Operations with duplicate routings:
Operation Version Routing
 - -------- ------- -------
 QAS_CRASH_MSG VERSION_1 ~GEN_UPG~18727
 QAS_CRASH_MSG VERSION_1 ~GEN~UPG~19278
 2 Total Rows

Solution:

Apply the latest Financials/SCM Maintenance Pack to resolve some of these errors.

Build and Alter Step (MP5) returns errors

Posted by on December 29, 2008 No comments

Problem:

When running the Build and Alter Task > Build and Alter Step, the follow appear in the log file:

SQL Build process began on 12/29/2008 at 3:43:44 PM for database FSDEV.
 Warning: SAC_SRCNODE_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: The record SPL_PEGGING_INF has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_SENT_DTL has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_SNT_D_HST has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TO_SND_DTL has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TO_SND_TMP has more than 16 keys. Table will be altered to support functional index.
 Warning: The record WTHD_TRXN_TMP3 has more than 16 keys. Table will be altered to support functional index.
 Warning: GM_CONT_CERT_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: GM_CONT_JHDR_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: GM_CONT_PROF_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: PL_SOHOLD3_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: RE_OPEXADT_PADD - Record definition does not exist. Record not processed. (76,73)
 Warning: RE_OPEXADT_RADD - Record definition does not exist. Record not processed. (76,73)
 Warning: SAC_TGTNODE_VW - Record definition does not exist. Record not processed. (76,73)
 Warning: SHIPTO_ADDR_VW1 - Record definition does not exist. Record not processed. (76,73)
 Warning: SHIPTO_ADDR_VW2 - Record definition does not exist. Record not processed. (76,73)
 Warning: SPA_SP_RC_PD_V2 - Record definition does not exist. Record not processed. (76,73)
 Warning: VNDR_ORDER_TMP - Record definition does not exist. Record not processed. (76,73)
 Warning: VNDR_REMIT_TMP - Record definition does not exist. Record not processed. (76,73)
**** Begin Build Settings for this Run
 Create Tables = Yes
 Create Indexes = Yes
 Create Views = Yes
 Create Triggers = Yes
 Alter Tables = Yes
 Log to File = Yes
 Log to Window = No
 Write comments to script = Yes
 Always overwrite files = Yes
 Execute SQL Now = No
 Write SQL to script file = Yes
 Logging level = Log fatal errors and warnings only
 Table creation option = Skip table if it exists
 View creation option = Drop and recreate view if it exists
 IndexCreationOption = Recreate index only if modified
 Alter Adds = Yes
 Alter Changes = Yes
 Alter Renames = Yes
 Alter Deletes = Yes
 Alter even if no changes = No
 Alter Table Option = Alter in Place
 Write script output to: Separate files
 Log filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log
 Table creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql
 Index creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql
 View creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql
 Trigger creation script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql
 Alter table script filename = E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql
 Alter drop column option = drop column if data present
 Alter truncate column option = truncate column if data present
 Target database platform = MICROSFT
 Target sizing set = 0
SQL Build process ended on 12/29/2008 at 3:45:28 PM.
 1641 records processed, 0 errors, 19 warnings.
 SQL Build script for Create Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTables.sql.
 SQL Build script for Create Indexes written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateIndexes.sql.
 SQL Build script for Create Views written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateView.sql.
 SQL Build script for Create Triggers written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/CreateTriggers.sql.
 SQL Build script for Alter Tables written to file E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/AlterTables.sql.
 SQL Build log file written to E:/temp/softwareupdateFSCM900_MP5{823d7dbc-c7c8-11dd-9439-e147c04c274d}/BuildAndAlter.log.

Solution:

This is acceptable according to the documentation for the step:

Important!
If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the Record being deleted by the Project. Please ignore the warning: Record definition does not exist. Record not processed. (76,73). If you receive the following warning message during the Build and Alter Step of the Build and Alter task, it is due to the field being deleted by the Project. Please ignore the warning: Field to be deleted has data present. Record processed. (76,23).DB2 Customers may need to recreate All Views manually by running createvw.dms using Datamover. This is because some views might become inoperable due to dependencies.If Run Create Triggers Script step fails because a trigger does not exist in the database then go to the CREATETRIGGERS.sql script in the Output directory, remove the offending statement and rerun the script.

Cannot locate any Change Packages in the apply directory

Posted by on December 27, 2008 No comments

Problem:

In Change Assistant (on glwebapp), navigated to Tools > Apply Change Packages. Went through wizard and reached Select apply directory. Chose directory E:staging, but the following error appeared:

Cannot locate any Change Packages in the apply directory

Solution:

Choose directory that contains the zip file of the downloaded patch (e.g. the directory that contains upd745700.zip, E:stagingCDImagescd849-FinMP5Cumulative).

Application Designer Crashes

Posted by on December 22, 2008 No comments

Problem:

When recreating database (on page 420-421 of Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server), Application Designer crashes on record 2746/4009 while copying project PPLTL84CUR.

Solution:

1. Run Application Designer on glwebapp, not gldbase

2. Copy the PTPATCH project using Application Designer

Others suggestions:

FSCM MP5 partially applied to node. Inconsistent libraries for Application Designer. Reapply MP5.

Allocate more memory to the Java runtime.