Running DDDAUDIT
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, indexed views, materialized query tables, materialized 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, you can view the .LIS file using any text editor.
The following table lists the names of each query that DDDAUDIT performs on the PeopleSoft system. The table elaborates on the query type, if any row is returned on running the query then what does it suggest, and how to resolve the inconsistencies.
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 |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
INDEX-1 |
Indexes are defined in Application Designer and not found in the database. |
Use Application Designer to create the index. |
|
Query |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
IVIEWS-1 |
Indexed views or summary tables which are defined in Application Designer, but are not found in the database. |
Use Application Designer to Build the indexed views or summary tables. |
|
IVIEWS-2 |
Indexed views or summary tables which are defined in the database, but are not found in the Application Designer. |
Drop the indexed view or summary table if it is not valid. Otherwise, define a new indexed view or summary table in the Application Designer. |
|
IVIEWS-3 |
Indexed views or summary tables which are missing a related language record. |
Use the Application Designer to add a related language record for the indexed views or the summary tables. |
|
IVIEWS-4 |
Indexed views whose keys are not defined. |
Use the Application Designer to set the keys for the indexed views. |
|
Query |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
MQT-1 |
Materialized query table that are defined in Application Designer, but are not found in the database. |
Use the Application Designer to build the materialized query table. |
|
MQT-2 |
Materialized query table that are defined in the database, but are not found in Application Designer. |
Drop the materialized query table if it is not valid. Otherwise, define a new materialized query table in the Application Designer. |
|
MQT-3 |
Materialized query table that are missing a related language record. |
Use the Application Designer to add a related language record for the materialized query tables. |
|
MQT-4 |
Materialized query tables whose table spaces are not set. |
Use the Application Designer to set table space for the materialized query tables. |
|
Query |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
MVIEWS-1 |
Materialized views which are defined in the Application Designer, but are not found in the database. |
Use the Application Designer to build the materialized views. |
|
MVIEWS-2 |
Materialized views which are defined in the database, but are not found in the Application Designer. |
Drop the materialized view if it is not valid. Otherwise, define a new materialized view in the Application Designer. |
|
MVIEWS-3 |
Materialized views which are missing a related language record. |
Use the Application Designer to add a related language record for materialized views. |
|
Query |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
TABLE-1 |
SQL table names are defined in the Data Designer that are not blank and not the same as the record name. |
Use the 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. |
Drop the table if it is not valid. Otherwise, define a new record in the 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 the Application Designer to assign table spaces to these tables. |
|
TABLE-5 |
Table contains more than 500 fields. |
Use the Application Designer to adjust the number of fields on the table, as needed. |
|
Query |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
TRIGGER-1 |
Trigger defined in the Application Designer and not found in the database. |
Delete the definition if it is not needed. Otherwise, use the Application Designer to create the trigger in the database. |
|
Query |
The Returned Rows Indicate |
Resolution |
|---|---|---|
|
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. |
Drop the view if it is not valid. Otherwise, define a new view in the Application Designer. |