DDDAUDIT & SYSAUDIT REPORTS

DDDAUDIT - The Database Audit Report (DDDAUDIT.SQR) finds inconsistencies between PeopleTools record and index definitions and the database objects. This SQR consists of nine queries: four on tables, two on views, and three on indexes.
------------------------------------------------------------------------------------
This is the DDDAUDIT report ran from process monitor
Report Name : DDDAUDIT APPLICATION DESIGNER/DATABASE AUDIT
Database Name: TEST
Platform : UNIX DBType: Oracle
-----------------------------------------------------------------------------------

(TABLE-1) SQL Table Names defined in the Application Designer that are not blank and not the same as the Record Name:
(TABLE-2) SQL Table defined in the Application Designer and not found in the Database:
(TABLE-3) SQL Table defined in the Database and not found in the Application Designer:
(TABLE-4) Tablespace not defined for SQL Table in the Application Designer:
(TABLE-5) Table Contains More Than 500 Fields :
(VIEWS-1) Views defined in the Application Designer and not found in the Database:
(VIEWS-2) Views defined in the Database and not found in the Application Designer:
(INDEX-1) Index defined in the Application Designer and not found in the Database:
(TRIGGER-1) Trigger defined in the Application Designer and not found in the Database:

===========================================================
SYSAUDIT - The purpose of PeopleSoft’s System Audit (SYSAUDIT.SQR) is to identify “orphaned” PeopleSoft objects and other inconsistencies within your system. An example of an orphaned object would be a module of People Code that exists, but which does not relate to any other objects in the system.
--------------------------------------------------------------------------------------
This is the SYSAUDIT report ran from process monitor
Report Name : SYSAUDIT
Database Name: TEST
Platform : UNIX DBType: Oracle
---------------------------------------------------------------------------------
Application Engine Audits Result: Exception(s) Found
(AE-01) AE programs without any sections:

Clear List Audits Result: OK
Electronic Commerce Audit Result: OK
Field Definition Audit Result: OK
Menu Definition Audit Result: Exception(s) Found
(MENU-03) The Menu Item table contains Component that does not exist in the Component Definition table:

Security Audits Result: Exception(s) Found
(SEC-07) Role references a Permission List that does not exist:
(SEC-08) PSROLEUSER references a User that does not exist in PSOPRDEFN
(SEC-18) User named in a User-Role relationship does not exist in the User Definition table:
(SEC-21) Permission List named in a Role-Permission List relationship does not exist in the Permission List Definition table:

Page Definition Audit Result: Exception(s) Found
(PAGE-06) PageField table Record/Field does not exist in the RecordField table:
(PAGE-08) A Page Group contains a Page Name that does not exist in Page Definition table:
(PAGE-10) Page Group Definition contains Search Record Name that does not exist in Record Definition table:
(PAGE-11) Page Group Definition contains an Add Search Record Name that does not exist in the Record Definition table:

PeopleCode Definition Audit Result: OK

Process Scheduler Audit Result: OK

Query Definition Audit Result: Exception(s) Found
(QUERY-04) Query Definition Record name does not exist in the Record Definition table:
(QUERY-07) Query Field Record name does not exist in the Record Definition table:
(QUERY-08) Query Definition Field name does not exist in the Field Definition table:
(QUERY-22) Following Queries Were Created Without PUBLIC Access
(QUERY-26) Following Queries Have Unions But They Select Unequal Number of Fields

Record Definition Audit Result: Exception(s) Found
(RECORD-11)INFORMATIONAL ONLY-RECORDS WITH MORE THAN 2 LONGS DEFINED

Language Definition Audit Result: Exception(s) Found
(SYSLANG-08) The Following Rel Lang Records are effective dated but do not have an EFFDT field defined
(SYSLANG-13) The Following Related Language Record(s) Have More Than One Base Record Defined

SQL Audits Result: Exception(s) Found
(SQL-05) AE SQL without SQL definitions:
(SQL-06) AE SQL that's not referenced:
(SQL-07) Record Views/Dynamic Views without SQL definitions:

Tree Definition Audit Result: Exception(s) Found
(TREE-17) Tree Definition Node count does not match record count in Tree Node table:

Version Check Audits Result: OK

XLATT Definition Audit Result: Exception(s) Found
(XLATT-3) Translate field(s) do not have associated translate values defined:

Analytic Audit Result: OK

XML Publisher Audit Result: Exception(s) Found
(XMLP-01) Query Data Source does not exist in Query Definition table:

Integration Broker Audits Result: OK

Style Sheet Definition Audit Result: OK

Connected Query Audit Result: OK

Feed Audits Result: OK
=========================================================================
Alter Audit is a process that identifies any records that require SQL Alter process. i.e. if the Data Designer definition doesn’t match Database definition. All records that are flagged should be Altered.

SQL Alter - The primary purpose of the Application Designer’s “SQL Alter” function is to bring SQL tables into accordance with PeopleTools record definitions. You can run SQL Alter in an “audit-only” mode that alerts you to discrepancies between your record definitions and SQL tables, but that doesn’t actually perform an alter.

APPLYING PATCH BY RAJU

Applying PATCH

1)    Before Applying we have to shut down all servers I,e App,prcs,Webserver and PSEMAGENT server and take the backup  of  PT8.49 Folder.

(a)  The below page shows before applying patch I,e it displays: PeopleTools 8.49

2)   Shut down Application Server:

(a)  Select Option 1 to shutdown Application server

(b)  Select Option 1 

 ©  Selct option 2 to shutdown Application server

(d)  Select option 1 to shut down Application normally

 

(e)  Select option q to quit

 

 (f)   Select option 2 to shut down process scheduler.

 

 (g)  Select option 2

 

(h)  Select option q to quit

 

 3)    Shut down Webserver from Services.msc

 

 (a)   Selcet Webserver service and right click on that and select stop .

4)    Go to PT8.49\PSEMAgent\StopAgent.bat  à this is to stop PSEMAgent Server.

5)    Take the backup of PT8.49 folder and paste it any folder:

Copy all files and folders

                                                                 

         

6)        Download the Patch

6.1.     Create an Empty folder named pt84924 on your system. 

6.2.     Download the patch file from the FTP site into the pt84924 folder, and extract the contents of the self-extracting archive file into this same folder.

3.2.1.  ftp://ftp.oracle.com/peoplesoft/outgoing/ptools/84924/84924.exe

3.2.2.  The password to extract 84924.exe:

RichieRich

7)       Install Patch Files

7.1.     For Windows:

(a)   .  Run \pt84924\cd84924\Disk1\setup.exe

This is patch software from oracle support:

(b)   Select setup.bat file shown in the below:

© Select Existing folder of PT8.49

(c)   End of installation of patch 8.49.24 and click on finish button.

(8) After installing patch the below window shows version as: People Tools 8.49.24

9.       Update Your Database with Patch Version Information 

(a).     Using PeopleTools 8.49.24 launch Data Mover and logon to your database as a PeopleSoft User.

(b).     Run the script <PS_HOME>\scripts\PTPATCH.DMS (Note: This script can only be run once per database per patch.  If you reapply this patch to the same database, do not run this script again.)

Loin into DataMover: As Peoplesoft User I,e VP1

© Select ptpatch.dms Script

(d)   Run the ptpatch.dms Script from DataMover. Click on Run Button

(e) End of script ptpatch.dms

10.       Install Database Changes Included in this Patch

(a).     Using PeopleTools 8.49.24, launch Application Designer, and sign on to the database as a PeopleSoft User.

(b).     Select <Tools>, <Copy Project>, <From File>

©.     Enter <PS_HOME>\projects and select PATCH849 from the list of projects.

(d).     Select <Options> and highlight the languages <Common> and <English> ONLY.

(d).     Select <Copy> to begin copying updated PeopleTools objects to your database.

(a)

(b)   Select <Tools>, <Copy Project>, <From File>

© Enter <PS_HOME>\projects and select PATCH849 from the list of projects

(c)   Select (.) File and  press OK button.

(d)   After that the below window will be displayed: Select Copy button

(e)   Select Compare Options Tab and Select Compare Languages as : Common and English

(f)    Select Copy Options Tab and select Copy Languages: Common and English

(g)   Select All in Defination Type and select Copy Button:

(h)   This is the end of the Copying of the PATCH8.49 Project:

 In Output window it displays the start and end time and date of Project.

11.       Load PeopleTools Messages and Data Project

(a).     Logon to Data Mover in bootstrap mode as the database owner using PT 8.49.24

(b).     Run <PS_HOME>\scripts\MSGTLSUPG.DMS to load the updated messages into your database.

7.2.1.  Note: If message catalog changes have not been made in PT 8.49 by the time this patch is released, the MSGTLSUPG.DMS script may not exist in the <PS_HOME>\scripts folder and this entire step can be skipped.

       ©.     Close Data Mover

Logon to DataMover

(a)    Logon to Data Mover in bootstrap mode as the database owner using PT 8.49.24

(b)     Run <PS_HOME>\scripts\MSGTLSUPG.DMS to load the updated messages into your database.

( c ) Select Run button

( d) End of the script and script ran successfully as shown in the below:

12.       Completing Installation and configuring this PeopleTools Patch

                (a) .     Reinstall any products in use from the following folders:

( b) .  Change Assistant:  <PS_HOME>\setup\PsCA

To install change Assistant we goto  PT8.49\setup\PsCA\Setup.exe à Double click on setup.exe

Note: Change Assistant is optional if we want to install we can or otherwise leave it.

( c) Click Next

( d ) Click Next

(e)   Click Next

(f)    Select yes and select next button.

(g)Select oracle and select next button because the database we are using is : Oracle

(g)   Install path will take default no need to change:I,e C:\PeopleSoft\Change Impact Analyser

(h)   End of PS Change Impact Analyser click on finish button.

13.  PeopleSoft Internet Architecture (PIA): <PS_HOME>\setup\ PsMpPIAInstall

(a).  Websphere customers: Choose 'Redeploy PeopleSoft Internet Architecture' when prompted

(b).  WebLogic customers: Choose 'Re-create WebLogic domain and redeploy PeopleSoft Internet Architecture' when prompted.

(c).  Warning: The entire WebLogic and PIA configuration in the specified WebLogic domain is deleted when you select this option.  It is highly recommended that you make a copy of the PIA Domain directory to preserve any existing configuration settings and customizations.  You can then refer to the configuration files in the copied directory when reconfiguring the newly recreated domain.  Please refer to the patch notes at the bottom of this document for further information (ref: 1786758000).

(A)   We have to recreate PeopleSoft Internet Architecture.

(1)   For this we can recreate domain and redeploy PeopleSoft internet Architecture.

(2)   OR We delete the Webserver folder and install PIA.

(3)   In this I am redeploying PIA. Goto: PT8.49\setup\PsMpPIAInstall and select setup.exe

(B)   Select Next

© Select PSHOME Folder and click Next.

(E) Select BEAWeblogic server and click Next.

(F) Give bea path previously where we installed Weblogic and click Next.

(G) Give        Login ID        : system

                   Password        : password1

          Re-type password    : password1--------------------àIn this it will ask atleast one number.

(H) Select Existing Weblogic Domain and select Recreate Weblogic domain and redeploy PIA and select Next.

(I)             Select Single Server Domain and Select Next.

(J) Give existing website name: Previously it has fsprdsb and we have to give the same website name.

(K) Give Appserver name  : Machine name

              JSL Port               : 9000-------------Check in psappsrv.cfg file

             HTTP Port             : 8055

             HTTPS Port          : 443--------------It is a default port and click Next

(L) Give default web profile name like:DEV,KIOSK,TEST,PROD, userid and password should be same and click Next

(M) Select Install button

(N) End of Installation click on Finish button

13.     Purge all App Server and Web Server cache.  (Knowledge Management document ID <Document:753215.1> has more details on purging if needed.)

14.     Re-start your Application server(s), Batch server(s), Web Server(s), and EM Agents.

15    Finally Login to PIA and check some default reports.

16.   We can  know the patch version in different ways:

(A)    IN TOAD GIVE QUERY: SELECT * FROM PS_MAINTENANCE_LOG;

(B)    Top of  the Application Designer we can able to see patch version.

(C)    Top of the Data Mover window we can able to see patch version.

(D)    After login to Application Designer Goto:Help->About PeopleTools-àhere we can find patch version

(E)    In PIA page press CTRL+J    here also we can find patch version.