Reltio and GBQ record counts are different after tenant data clone.

Issue : 

Reltio and GBQ record counts show different or not matching after a tenant data clone/refresh. 

Cause : 

When a tenant clone/refresh happens, Reltio streaming services are disabled. hence, the GBQ sync will stop. However, the GBQ will have the data sets. After the tenant clone/refresh is complete, the Relto and GBQ sync will be established and the new data will be appended to GBQ with the sync job. Since the GBQ had old data set the record count will show higher in GBQ compared to the Reltio tenant. 

Solution : 

To align the data between Reltio and GBQ, follow these steps:

1. Recreate GBQ Objects

   After completing the tenant clone, initiate the recreation of GBQ tables and views to ensure they reflect the current schema and data.

2. Perform a Bulk Synchronization

   Execute a bulk synchronization to transfer the current data from Reltio to GBQ. This process ensures that GBQ is updated with the latest records from Reltio.

3. Verify Synchronization

   After the bulk sync, validate that the record counts in GBQ match those in Reltio. You can do this by querying the total number of entities in both systems and comparing the results.

Related Documentation:

Our Doc Links can change over time, so please search for the Documentation based on the titles shared below. Thank you.

• Configure the Reltio Data Pipeline for GBQ
• Recreate GBQ tables and views in your BigQuery dataset