Troubleshoot observability errors - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

Learn how to tackle the following common Data Observability issues you may face while accessing Data Integrity Suite.

Profile or observer run failures

The Profile or Observer fails to save or run when your table or column contains double quotes in the name. A failed Profile or Observer does not display statistics for that dataset

Error message: In the following example, the column name is "id" and the table names are "test3" and "test_double"

Save observer Failed. tables[0].columns[].name has invalid value “id"|tables[0].name has invalid value “test3".
Save observer Failed. tables[0].name has invalid value "test_double".

Workaround: Review your data assets for tables or columns with single or double quotes in their names, such as ‘TableName’ or “ColumnName”. Quoted database objects can cause Profile or Observer runs to fail. Consider renaming affected objects without quotes.

Missing individual profile statistics

An individual profile does not display statistics after a successful run.

You can create an individual profile from the Profilers page. When you try viewing the statistics immediately after a successful profile run, having a large number of tables, it displays a message No Statistics available.

Workaround:
  1. After the profile run is complete, wait for a few minutes before you view the statistics.
  2. On the Profiling Results page, switch between selecting different tables or columns. The statistics for all assets will be displayed within 10 to 20 seconds.