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

AEM 6.3 to 6.5 in-place upgrade - reference/property/disabled/counter type (non-lucene) indexes?


Level 3

I'm practicing this upgrade and am working to rebuild all indexes. I've removed all checkpoints (rm-all), compacted the segmentstore, deleted the /repository/index folder, and restarted the instance. Lucene indexes get rebuilt. Oak Run reports they are valid, however it also says many non-Lucene indexes were ignored.

In the past, I believe removing all checkpoints caused more than the Lucene indexes to rebuild.

But in this case, removing all checkpoints, compacting segmentstore, deleting the /repository/index folder, and restarting, only rebuilds the Lucene indexes.

Looking at /libs/granite/operations/content/diagnosistools/indexManager.html, it reports all the non-Lucene indexes are of type reference, property, disabled, or counter? I had at one point tried to rebuild them by switching the rebuild flag to true in crxde - it seemed to start reindexing, but saving the flag change resulted in a repository error. 

Do I need to rebuild and re-enable these non-Lucene indexes? If so, how should I do it? In crxde, or some other way?

Related, when will the repository gain more checkpoints after having removed all of them? What is a checkpoint anyway? Why are there sometimes more than 1?

Ignored indexes as these are not of type lucene:
- /oak:index/cqCloudServiceConfig
- /oak:index/cqMaster
- /oak:index/jcrLanguage
- /oak:index/extensionType
- /oak:index/containeeInstanceId
- /oak:index/active
- /oak:index/cqIsCommunitySite
- /oak:index/repMembers
- /oak:index/processingProfile
- /oak:index/counter
- /oak:index/cqDefaultFormFor
- /oak:index/slingResourceSuperType
- /oak:index/cqCugEnabled
- /oak:index/cqAcUUID
- /oak:index/externalPrincipalNames
- /oak:index/campaignpath
- /oak:index/eclink
- /oak:index/subType
- /oak:index/damS7watch
- /oak:index/acPrincipalName
- /oak:index/fpContentType
- /oak:index/cqVariantFamily
- /oak:index/uuid
- /oak:index/slingVanityPath
- /oak:index/jcrLockOwner
- /oak:index/deviceIdentificationMode
- /oak:index/cqCloudServiceConfigs
- /oak:index/slingResources
- /oak:index/cqPayloadPath
- /oak:index/fpNodeType
- /oak:index/contentPath
- /oak:index/ecuuid
- /oak:index/cqOwnerCanvasPage
- /oak:index/nodetype
- /oak:index/cqTemplate
- /oak:index/verb
- /oak:index/reference
- /oak:index/lockCreated
- /oak:index/principalName
- /oak:index/guideComponentType
- /oak:index/externalId
- /oak:index/slingAlias
- /oak:index/fragmentPath
- /oak:index/authorizableId
- /oak:index/slingResourceType
- /oak:index/cqKeywords
- /oak:index/damStatus
- /content/oak:index/enablementResourceName

3 Replies


Level 3

Thanks for the info Pavalli.


I have ACS Commons 5.0.14 - the index manager is here for me: 


it is deprecated, but looks like a good interface to manage indexes. 


Why is this deprecated?
AEM 6.2+ now contains a better and more current version of Oak Index Manager located at:



The "better and more current" tool they mention above doesn't look to have the ability to rebuild indexes? Did they deprecate for something less functional? Maybe I'm not seeing how the UI works in /libs/granite/operations/content/diagnosistools/indexManager.html to re-index an index?


Back to the question, do I need to re-index the type: reference, property, disabled, or counter indexes?




Level 5

@thisthatheotter  I am also not seeing any button for re-index at the OOTB index manager - seems to me a known defect - /libs/granite/operations/content/diagnosistools/indexManager.html 


I think you can use /apps/acs-commons/content/oak-index-manager.html - it works well !!


Apart from optimized code, indexing plays a very important role in an application running smoothly. But saying so, re-indexing can be an expensive operation. Please ensure you understand the impact of the system or (do a dry run over local)  before performing a reindex, and especially a bulk re-index on higher environments.


Hope this helps.