1

DDDaudit, SYSaudit, and You

• DDDAUDIT finds inconsistencies between PeopleTools record & index definitions and database objects – “Data Designer/Database audit”

• SYSAUDIT identifies orphaned PeopleSoft objects and other inconsistencies within the system

2

Why audit?

• Eliminate potential sources of error• Verify validity and integrity of the code and

db objects in your system• GSC may want to know that your system

is “clean” on the audits in a given area, when troubleshooting

Who, when, where…

• CCAIM runs audits before & after patches– Did patches introduce new discrepancies?– Run cleanups for some report items

• Audits are run multiple times during upgrades– Important to start (and end) as “clean” as

possible• On-demand, or as diagnostic tool

3

Read all about it…

• Enterprise PeopleTools 8.48 [or 8.49] PeopleBook: Data Management – > Ensuring Data Integrity

• Search Customer Connection for newer audits

How to run the reports

• PeopleTools / Process Scheduler / System Process Requests– Select DDDAUDIT and/or SYSAUDIT from

the list of reports available to run• PeopleTools / Utilities / Audit / Perform

System Audit• Or ask CCAIM to run

4

An example

• Recent PAPD DDDAUDIT

DDDAUDIT sections

• (TABLE-2) SQL Table defined in the Application Designer and not found in the Database– Create db table or delete record defn from

Tools– Oversight? Or an obsolete object?

5

DDDAUDIT sections, cont.• (TABLE-3) SQL Table defined in the

Database and not found in the Application Designer– Drop the db table or recreate / remigrate the

rec defn in Tools– Is there some legit reason why table exists in

db but not in Tools– If obsolete Tools rec defn is deleted, the db

table must also be dropped

DDDAUDIT sections, cont.

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

6

DDDAUDIT sections, cont.

• (INDEX-1) Index defined in the Application Designer and not found in the Database– Could explain your performance issues!!

DDDAUDIT sections, cont.

• (TABLE-1) SQL Table Names defined in the Application Designer that are not blank and not the same as the Record Name

7

DDDAUDIT sections, cont.

• (TABLE-4) Tablespace not defined for SQL Table in the Application Designer

• (TABLE-5) Table Contains More Than 500 Fields

• (TRIGGER-1) Trigger defined in the Application Designer and not found in the Database

8

SYSAUDIT sections

• Application Engine Audits• Clear List Audits• Electronic Commerce Audit• Field Definition Audit• Menu Definition Audit• Security Audits• Page Definition Audit

SYSAUDIT sections, cont.

• PeopleCode Definition Audit• Process Scheduler Audit• Query Definition Audit• Record Definition Audit• Language Definition Audit• SQL Audits

9

SYSAUDIT sections, cont.

• Tree Definition Audits • Version Check Audits• XLATT Definition Audit• Analytic Audit• XML Publisher Audit• Integration Broker Audits

SYSAUDIT highlights

• Most broad categories have several reports, for example:– AE-01 = AE programs without any sections– AE-02 = AE sections without AE programs

• See PeopleBooks for actions to resolve the reported items.

10

SYSAUDIT, cont.

• Corrective actions are sometimes things you as a developer can take care of, for ex. Migrate the missing AE sections

• Sometimes corrections involve direct SQL updates of Tools tables – CCAIM

• Research involved – why the discrepancy occurred, where are missing pieces, is object obsolete, etc.

SYSAUDIT, cont.

• Open a case with GSC if delivered, un-customized objects are involved– Also check DM / TRUL

• Search Customer Connection (or open a case) for report items not covered in PeopleBooks

• Enlist CCAIM to help

11

What causes these things??

• Incomplete migrations• Obsolete items deleted but not all related

items deleted• PS sometimes delivers things with missing

pieces• Major upgrades may introduce

inconsistencies that need attention• Routine migrations cause some report

items to appear (VERSION, SEC-28)

An example

• Recent PAPD SYSAUDIT

12

“ALTER AUDIT”

• Verify that the table definition in database matches the record definition in PeopleTools (App Designer)

• If not, generate the DDL that will synch up the database object with the Tools object

• CCAIM runs for all records before/after patches; in upgrades

Recommendations

• DDDaudit as clean as possible• SYSaudit clean for bolt-on objects• Cleanup before/after major upgrades• Periodic audit/cleanup efforts for each

xxPD environment – CCAIM + designated housekeeper from application team