Skip to Main Content
Return to Navigation

Running DDDAUDIT

This section discusses DDDAUDIT queries.

The Database Audit Report (DDDAUDIT) finds inconsistencies between PeopleTools record and index definitions and the database objects. This audit consists of queries that check tables, views, indexes, and triggers.

DDDAUDIT.SQR. is located in PS_HOME\sqr.

When you run DDDAUDIT.SQR, its results are written to a file called DDDAUDIT.LIS in the \TEMP folder. After running DDDAUDIT, view the .LIS file by using any text editor.

DDDAUDIT Queries

The following table lists the names of each query that DDDAUDIT performs on the PeopleSoft system, what it means if rows are returned, and how to resolve the inconsistency.

Note: The query names in this table are arranged alphabetically, and are not necessarily in the order in which they appear in DDDAUDIT.LIS:

Query

If Rows are Returned?

Resolution

INDEX-1

Indexes are defined in Application Designer and not found in the database.

Use Application Designer to create the index.

INDEX-2

Indexes are defined in the database and not found in Application Designer.

If the index is valid, use Application Designer to define the index.

Otherwise, drop the index.

INDEX-3

Uniqueness or the number of keys in the Index Definition do not match between Application Designer and the database.

See INDEX-1.

TABLE-1

SQL table names are defined in the Data Designer that are not blank and not the same as the record name.

Use Application Designer to enter the record name as the Non-Standard SQL Table Name.

TABLE-2

SQL tables are defined in the Data Designer and not found in the database.

If you want to delete the record definition, use Application Designer (select File, Delete).

Otherwise, to create the SQL table, use Application Designer. This command also creates the appropriate indexes for keys, duplicate order keys, alternate keys, and list items.

TABLE-3

SQL tables are defined in the database and not found in the Data Designer.

SYSINDEXES and SYSTABLES can be ignored in these results.

For Informix: PSALTERLONG can also be ignored.

If the table is not valid, drop it.

Otherwise, define a new record in Application Designer.

TABLE-4

Tablespace is not defined for the SQL table in Application Designer.

If you're using or migrating to a relational database management system that uses table spaces, you should use Application Designer to assign table spaces to these tables.

TABLE-5

Table contains more than 500 fields.

Use Application Designer to adjust the number of fields on the table, as needed.

VIEWS-1

Views are defined in the Data Designer and not found in the database.

If you want to delete the view definition, use Application Designer (select File, Delete).

Otherwise, to create the SQL view, use Application Designer.

VIEWS-2

Views are defined in the database and not found in the Data Designer.

If the view is not valid, Drop it.

Otherwise, define a new view in Application Designer.

TRIGGER-1

Trigger defined in the Application Designer and not found in the database.

Delete the definition if it is not needed.

Otherwise, use Application Designer to create the trigger in the database.