Object locked by another process in Data Lake

Legacy Contributor

Hi Team,

I am getting below error while executing the query in Data Lake.

Data Storage ERROR 573Error Message: Object locked by another process. Try again later.

Can you please suggest that how we can see the data without error.

@mike-kalinowski Can you please suggest on this.

Find more posts tagged with

Infor Data Fabric

Accepted answers

Legacy Contributor

Hey Rajini,

The 573 error is encountered when Compass is generating the cache for new data objects that've landed in Data Lake. The caching process is an invisible background process and is typically triggered when users or clients run a query against a table in Compass but once that process is all caught up, the queries should run as expected. Any queries against the table while that caching is ongoing would receive a 573 error in the meantime.

In short, you'll need to wait for the caching process to complete from your previous query but then everything should shake out fine.

All comments

Legacy Contributor

Hey Rajini,

In short, you'll need to wait for the caching process to complete from your previous query but then everything should shake out fine.

Legacy Contributor

Hi Mike,

Thanks for your reply.

I am not able to view the query results in compass, as it is taking more time to load and throwing error because of data

Is there any possibility to overcome this issue and see the results because I need to verify the production data.

Legacy Contributor

Hey Rajini,

It's likely that you have quite a lot of data stored for that data object which means increased times in cache generation. Until that completes, you'll still get the 573 error but in the meantime, you can attempt to use Compass' skipReformatting query hint to explore the data that's already been cached.

Legacy Contributor

Thank you so much Mike.. Working with skipReformatting..

Thank you for quick reply

Copyright © 2025 Infor. All rights reserved.