Scribd
Upload
246 views3 pages

Consistency Check On cq5

The document outlines the steps to perform a consistency check in Adobe Experience Manager (AEM): 1) Make backups and downloads before disabling LDAP and starting the check 2) Run the consistency check by adding parameters to repository and persistence manager elements and starting AEM 3) Fix any errors found like orphaned nodes manually using the CRXDE console tool

Uploaded by

Praveen Nigam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
246 views3 pages

Consistency Check On cq5

The document outlines the steps to perform a consistency check in Adobe Experience Manager (AEM): 1) Make backups and downloads before disabling LDAP and starting the check 2) Run the consistency check by adding parameters to repository and persistence manager elements and starting AEM 3) Fix any errors found like orphaned nodes manually using the CRXDE console tool

Uploaded by

Praveen Nigam
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Consistency Check

The Following are the steps to perform the consistency check.


1. Make all the necessary backups and package downloads to preserve your applications
and content.
2. If in use, disable LDAP by removing the configuration from the crx-quickstart/server/start
script.
3. Perform the consistency checks on the workspace:
a) Stop CQ.
b) Edit the following files:
o
o

crx-quickstart/repository/repository.xml
crx-quickstart/workspaces/*/workspace.xml

c) Add the following parameters to all <SearchIndex...> elements:


o
o
o

<param name="enableConsistencyCheck" value="true"/>


<param name="forceConsistencyCheck" value="true"/>
<param name="autoRepair" value="true"/>

d) Add the following parameters to all <PersistenceManager...> elements


o
o

<param name="consistencyCheck" value="true" />


<param name="consistencyFix" value="true" />

e) Start CQ.
f)

Watch the log files for any error and repair messages.

4. Fix errors/Inconsistencies (that are not automatically repaired) with the CRX Console
Tool. There can be different types of inconsistencies in the CRX/workspace but in our
case we encountered following type of inconsistency:
o

ConsistencyCheck: Not repairable: Node ab4f7781-714d-4706-95cb-76d68922479c


has unknown parent: 112111b9-bfd9-4c25-a5c2-de63b09124ea
(ConsistencyCheck.java, line 116)

NodeState 'ab4f7781-714d-4706-95cb-76d68922479c' references inexistent parent id


'112111b9-bfd9-4c25-a5c2-de63b09124ea' (may be orphaned)
(PersistenceManagerUtils.java, line 381)

5. To remove this type of inconsistency follow the following steps:


a) Stop your CRX instance (CRX Console does not work while CRX is running)
b) You may need to correct the startup script for the Console. To do that, edit
server/console.sh, and replace the variable
REPOSITORY_HOME="$CONTEXT/crx" with
REPOSITORY_HOME="$CONTEXT/../repository". (Please note you can't just add
the line to the top of the script, because the CONTEXT may not be set before that
which would cause the console use a different repository).
c) For CQ 5.3/CRX 2.x : copy server/lib/common/cq-shared-libs-5.3.4.jar to
server/lib/container.
d) To start the CRX Console, in a terminal window, type: crxquickstart/server./console.sh
e) After the console prompt is displayed then type the following command to login as
admin: login crx.default admin <pwd>

6. Once you are logged in into the CRX using this command line, tool follow the steps
below.
a) For example, For the error: NodeState 'ab4f7781-714d-4706-95cb76d68922479c' references inexistent parent id '112111b9-bfd9-4c25-a5c2de63b09124ea' (may be orphaned) (PersistenceManagerUtils.java, line 381)
b) Run these commands to remove the orphan child node save and exit:
o
o
o

rm [ab4f7781-714d-4706-95cb-76d68922479c]
save
exit

Note: If you have many errors to fix then you can prepare multiple rm commands.

7. Create a file named redo_X.log under: crxquickstart/repository/workspaces/<workspace>/index/ where the X in the file name
matches what is in the end of the filename for the crxquickstart/repository/workspaces/<workspace>/index/indexes_X file. And enter the
following in the file:
o

1 DEL ab4f7781-714d-4706-95cb-76d68922479c

1 COM

8. Start CRX and check for the error.log at ~/crx-quickstart/logs/crx/error.log.


9. If everything was done properly then you should see log messages like these in your
logs/crx/error.log upon startup of CRX:
o
o

*INFO * Recovery: Found uncommitted redo log. Applying changes now...


(Recovery.java, line 82)
*INFO * Recovery: Redo changes applied. (Recovery.java, line 85)

You might also like