Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

DataStoreException in error log but not in consistency check

jakej40603950
Level 5
Level 5

Hello, we are getting org.apache.jackrabbit.core.data.DataStoreException: Record not found: ... exceptions when starting up AEM.

But when I run datastore consistency check as given here (Datastore inconsistency record not found ) it shows no errors found?

Is there any reason for this discrepancy? Or is the consistency check to be used for a different purpose?

We get a new record not found exception every time we start AEM up - so thought of using the jmx check to get a list of all such errors in one go but no luck with that.

Please share inputs if you have come across something like this. Thanks!

1 Accepted Solution
Jörg_Hoh
Correct answer by
Employee
Employee

Hi,

If you encounter this exception, you should raise a Daycare ticket including all relevant information (like Oak version, setup etc); because this means that you might have a situation of data loss, which should not occur. Moving ahead can be a possibility, but it might also destroy any chance to fix the issue. Please get in touch with support as soon as such a situation occurs.

Jörg

View solution in original post

5 Replies
Jörg_Hoh
Employee
Employee

What version of AEM are you using? If you run on AEM 6.x, which Oak version are you using?

Jörg

jakej40603950
Level 5
Level 5

Please ignore this. It worked when tried later.

One question here : At JCR level, where are these record ids stored? (the id for datastore binary from the Record not found exception).

Where do you find the mapping between a dam asset and the corresponding data store binary represented by the id?

Jörg_Hoh
Employee
Employee

Hi,

it's stored as part of the Oak repo tree, but it's not visible via JCR. And it shouldn't be visible, as it is an implementation detail and revealing it would leak abstraction.

Jörg

jakej40603950
Level 5
Level 5

Thanks. Does that mean only way to know the dam assets affected by this error is to try to load them? - This may be a strange ask but it can sometimes help decide whether to move ahead in spite of such errors especially if you are in a crunch if the affected assets aren't that important.

Jörg_Hoh
Correct answer by
Employee
Employee

Hi,

If you encounter this exception, you should raise a Daycare ticket including all relevant information (like Oak version, setup etc); because this means that you might have a situation of data loss, which should not occur. Moving ahead can be a possibility, but it might also destroy any chance to fix the issue. Please get in touch with support as soon as such a situation occurs.

Jörg

View solution in original post