This knowledge article explains the workaround for resuming failed refreshing projections.
Environment
OpenText Analytics Database 23.3 or later releases
Situation
In 23.3, it introduced the partition range projections to improve the refresh operation. Previously, the new and updated projections had to be refreshed with all table data to be available to the queries. Now, when refreshing the projections of the partitioned tables, the refresh operation first loads data from the partition with the highest partition key. After refreshing this partition, it begins to refresh the partition with the next highest key. The projections that have completed the refresh operation become available to the queries.
As of 25.3, restarting the refresh operation for partition range projections cannot resume if the refresh operation fails due to issues such as a lock timeout.
