DataStoreException in error log but not in consistency check | Community
Skip to main content
J
jakej40603950
Level 5
August 27, 2017
Solved

DataStoreException in error log but not in consistency check

  • August 27, 2017
  • 5 replies
  • 4359 views

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by joerghoh

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

5 replies

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
August 27, 2017

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

Jörg

J
jakej40603950Author
Level 5
August 28, 2017

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?

joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
August 28, 2017

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

J
jakej40603950Author
Level 5
August 28, 2017

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.

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
August 28, 2017

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

Terms & ConditionsAccessibility statement

Loading footer...