Errors the Catalog Doctor can detect

With the Catalog Doctor you can diagnose and validate data objects in a catalog. Since the data objects in a catalog are constructed independently from each other, the Catalog Doctor diagnoses each type of data object independently. For example, when it checks formulas, it only looks into the definition of parameters and DBFields in the current catalog. The system does not check whether the DBFields exist in the connected database. When the system checks the queries, it will only look for the mapping fields which are currently in the catalog, and does not confirm whether the formulas are valid.

For your convenience, in the following statements database refers to a raw database connected via JDBC or ODBC, mapped table/view refers to a table/view in a catalog, raw table/view refers to a table/view in a raw database, and raw column refers to the columns in a raw database.

Mapped table/view and DBField

• Checks whether the raw table/view of a mapped table/view exists in the database.
• Checks whether the raw column of a DBField exists in the database. If it exists, then it checks to see whether the stored information such as SQL Date type matches the raw column in the database.

Formulas and summaries

• Checks to see whether the formulas and summaries have correct syntax. It checks whether the remapped parameters and DBFields need to be remapped again.

Queries

• Checks whether the mapped tables/views referenced by the query exist in the catalog.
• Checks whether or not the mapping fields are valid.
  • Whether the DBFields of the table/view match those saved in the query.
  • Whether or not the formulas and parameters can be found in the catalog.