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