Category Archives: TRAM - Page 3

DDDAUDIT Errors After Running FSCM MP5

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

(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.

(SEC-30) Role User table (ROLEXLATOPR) should be populated

Problem:

After running SYSAUDIT, the following error appears:

(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

Solution:

1. Launch the PeopleSoft instance (PIA) and log on as a user with access to the PeopleTools responsibility.
2. Navigate to PeopleTools > Security > User Profiles > User Profiles.
3. Click Search, and choose ENTMGR_PRO (Procurement Catalog Manager).
4. Make a change to the record (e.g. change Language Code from English to Finnish), and save the record.
5. Revert the change (e.g. change Language Code from Finnish to English), and save the record again.
6. Then run the SYSAUDIT report.

Uninstalling PeopleSoft PIA for WebSphere

1. In WebSphere Administration Console http://server:9060/ibm/console, log on as user admin

2. Applications > Enterprise Applications

3. Check fsdmo and then Stop

4. Check fsdmo and then Uninstall

5. Save configuration changes

6. Repeat for 9061 (PSEMHUB) and 9062 (PSOL)

7. Stop WebSphere using the command:

webserv\binstopServer.bat server1

e.g.
E:PSOFTFS900webservPIA_fsdmobinstopServer.bat server1
E:PSOFTFS900webservPSEMHUB_fsdmobinstopServer.bat server1
E:PSOFTFS900webservPSOL_fsdmobinstopServer.bat server1

8. Uninstall profiles using the commands:

manageprofiles.bat –delete -profileName

e.g.
cd /d E:PSOFTFS900webserv
PIA_fsdmobinmanageprofiles.bat -delete -profileName PIA_fsdmo
PSEMHUB_fsdmobinmanageprofiles.bat -delete -profileName PSEMHUB_fsdmo
PSOL_fsdmobinmanageprofiles.bat -delete -profileName PSOL_fsdmo

9. Delete the PIA_fsdmo, PSEMHUB_fsdmo and PSOL_fsdmo directories.

10. Reboot the server.

Reference:

Page 173-174, Enterprise PeopleTools 8.49 Installation for Microsoft SQL Server

Audit contents of PS_AELOCKMGR

Problem:

Application Engine Audits Result: Exception(s) Found
 (AE-16) Audit contents of PS_AELOCKMGR:
Message
 ----------------------------------------------------
 PS_AELOCKMGR contains 2row(s). There should be 1.
 1 Total Rows

Solution:

In SQL Server Management Console, checked the contents of the S_AELOCKMGR table.

It returns:

AE_LOCK
 -------
 N
 N

Delete the extra row using:

SET ROWCOUNT 1
 DELETE FROM [FSDMO].[dbo].[PS_AELOCKMGR]

Invalid User ID and Password Logging Into Application Designer

Problem:

When logging on to Application Designer as a new (Windows) user, the user is unable to login and the following error appears:

Invalid User ID and Password Logging Into Application Designer

Solution:

In Configuration Manager, under Profile, edit the Default program and create new entries for Database and Application Server.

[amazon asin=0071664939&template=iframe image&chan=default]     [amazon asin=1430237074&template=iframe image&chan=default]     [amazon asin=0071787925&template=iframe image&chan=default]

Build and Alter Step While Applying MP5

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.

Subquery returned more than 1 value

Problem:

File: e:pt84915b-retailpeopletoolssrcpsappengaedebug.hSQL error. Stmt #: 16
 03 Error Position: 0 Return: 8601 - [Microsoft][SQL Native Client][SQL Server]
 Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, , >= or 
when the subquery is used as an expression.
 [Microsoft][SQL Native Client][SQL Server]The statement has
 Failed SQL stmt:UPDATE PS_PTPP_OPTIONS SET PTPP_REG_PREFIX = 
( SELECT A1.EOPP_REG_PREFIX FROM PS_EOPP_OPTIONS A1)
 Message Set Number: 200
 Message Number: 0
 Message Reason: File: e:pt84915b-retailpeopletoolssrcpsappengaedebug.hSQL
 error. Stmt #: 1603 Error Position: 0 Return: 8601 - [Microsoft][SQL Native Client][SQL Server]Subquery 
returned more than 1 value. This is not permitted when the subquery follows =, !=, <, , >= or 
when the subquery is used as an expression.
 [Microsoft][SQL Native Client][SQL Server]The statement has
 Failed SQL stmt:UPDATE PS_PTPP_OPTIONS SET PTPP_REG_PREFIX = 
( SELECT A1.EOPP_REG_PREFIX FROM PS_EOPP_OPTIONS A1) (200,0)
Process 7113 ABENDED at Step UPGPT846PP.EO_TO_PT.Step51a (SQL) -- RC = 8601 (108,524)
 Message Set Number: 108
 Message Number: 524
 Message Reason: Process 7113 ABENDED at Step UPGPT846PP.EO_TO_PT.Step51a (SQL)
 -- RC = 8601 (108,524)
Process %s ABENDED at Step %s.%s.%s (Action %s) -- RC = %s

Solution:

Ran:

SELECT * FROM PS_EOPP_OPTIONS A1
Two rows returned. Ran:

SELECT DISTINCT * FROM PS_EOPP_OPTIONS A1
One row returned.

Checked PS_EOPP_OPTIONS table in FSDEMO. It has one row.

Solution: Delete duplicate row:

SET ROWCOUNT 1
DELETE FROM [FSDMO].[dbo].[PS_EOPP_OPTIONS]

Unable to Install Micro Focus Net Express

Problem:

Micro Focus Net Express not installing

Solution:

1. On GLWEBAPP, share the E:stagingCDImagesMicro Focus NetExpress CDsdisk1

2. On GLWEBAPP, map the shared disk1 directory to Z:

3. Using My Computer, navigate to Z:AUTORUNHTML and run START.HTM

4. Click Install, and then click “Click here to install or upgrade Net Express 4.0”