This discussion is archived
9 Replies Latest reply: Dec 12, 2012 8:18 PM by Srinath Menon RSS

Indexer never running after checkin or delete on UCM 10g

947250 Newbie
Currently Being Moderated
Hey Everyone,

My current cms is not updating when new items are checked in. The check in works successfully; however, everything that is submit is stuck in the 'Done' state. I run the auto update cycle, and things are released, but I still cannot search for them by content id.

Does anyone have any ideas?

Also isnt the indexer suppose to run shortly after check in's and alike?

Thanks for the help!
  • 1. Re: Indexer never running after checkin or delete on UCM 10g
    ryan sullivan Pro
    Currently Being Moderated
    Are you sure that the auto indexer is enabled?

    -ryan
  • 2. Re: Indexer never running after checkin or delete on UCM 10g
    947250 Newbie
    Currently Being Moderated
    Yeah I checked the configuration in the admin applets. Is this not the right place?
  • 3. Re: Indexer never running after checkin or delete on UCM 10g
    Bunty Journeyer
    Currently Being Moderated
    your index might be corrupted. Do a completely Collection Rebuild and perform search.

    Edited by: Bunty on Dec 11, 2012 11:44 AM
  • 4. Re: Indexer never running after checkin or delete on UCM 10g
    947250 Newbie
    Currently Being Moderated
    The collection rebuild is started, but it is going to take a while to run. I'll post the results :)

    Thanks for all your help either way :)
  • 5. Re: Indexer never running after checkin or delete on UCM 10g
    Srinath Menon Guru
    Currently Being Moderated
    Hi ,

    As a first step with indexer related issues , server output should be monitored with the following trace sections set :

    indexer*,systemdatabase (with full verbose tracing)

    Once the core error / issue is identified then that would need to be fixed .

    If you are seeing that collection rebuild is taking a long time then more often than not it would be a case of high percentage of index fragmentation on DB (only for DB FT or OTS case) . In that scenario you should be following Note : 1087777.1 from MoS or check the same details from the following post :

    Re: Unable to Index Content in UCM 11gR1-11.1.1.5.0 with Oracle Text Search

    This is with the assumption that the search engine is DB FT or OTS .

    Hope this helps .

    Thanks
    Srinath
  • 6. Re: Indexer never running after checkin or delete on UCM 10g
    947250 Newbie
    Currently Being Moderated
    So I ran this automatic update cycle and this was the output of indexer* with full verbose tracing

    indexermonitor     12.12 09:52:06.778     IdcServerThread-7843531     touching lock file /VisApp/stellent/install/search/lock/update_lock.dat
    indexermonitor     12.12 09:52:06.779     index update work     Starting indexing update (action=0).
    indexer     12.12 09:52:06.780     index update work     /VisApp/stellent/install/search/search.cfg doesn't exist.
    indexermonitor     12.12 09:52:06.780     index update notify     touching lock file /VisApp/stellent/install/search/lock/update_lock.dat
    indexer     12.12 09:52:06.792     index update work     isRebuild?false; IndexerStep:Init; Class:intradoc.indexer.Indexer
    indexer     12.12 09:52:06.796     index update work     isRebuild?false; IndexerStep:BuildChanges; Class:intradoc.indexer.IndexerBuildChanges
    indexer     12.12 09:52:06.925     index update work     Saving 5 update changes
    indexer     12.12 09:52:06.928     index update work     isRebuild?false; IndexerStep:PreIndexingStep; Action:preIndexingStep
    indexer     12.12 09:52:06.930     index update work     isRebuild?false; IndexerStep:CheckForWork; Class:intradoc.indexer.Indexer
    indexer     12.12 09:52:06.933     index update work     isRebuild?false; IndexerStep:IndexDeletions; Class:intradoc.indexer.CommonIndexerBulkLoader
    indexer     12.12 09:52:06.935     index update work     IndexerBulkLoader doing 'IndexDeletions' with m_change '-'
    indexer     12.12 09:52:06.948     index update work     indexWebFile: false m_retryIndexing: false m_isFirstRetry: true
    indexer     12.12 09:52:06.954     index update work     indexWebFile: false m_retryIndexing: false m_isFirstRetry: true
    indexer     12.12 09:52:06.959     index update work     indexWebFile: false m_retryIndexing: false m_isFirstRetry: true
    indexer     12.12 09:52:06.965     index update work     indexWebFile: false m_retryIndexing: false m_isFirstRetry: true
    indexer     12.12 09:52:06.973     index update work     indexWebFile: false m_retryIndexing: false m_isFirstRetry: true
    indexer     12.12 09:52:06.974     index update work     Conversion handler is not defined
    indexer     12.12 09:52:06.974     index update work     Conversion handler is not defined
    indexer     12.12 09:52:06.974     index update work     Conversion handler is not defined
    indexer     12.12 09:52:06.974     index update work     Conversion handler is not defined
    indexer     12.12 09:52:06.974     index update work     Conversion handler is not defined
    indexer     12.12 09:52:06.974     index update work     setting change on '1077417' to 'D'
    indexer     12.12 09:52:06.974     index update work     setting change on '1077416' to 'D'
    indexer     12.12 09:52:06.974     index update work     setting change on '1077401' to 'D'
    indexer     12.12 09:52:06.974     index update work     setting change on '1077394' to 'D'
    indexer     12.12 09:52:06.974     index update work     setting change on '1077393' to 'D'
    indexer     12.12 09:52:06.975     index update work     after handling indexing results: hasError: false m_retryIndexing: false m_isFirstRetry: true metaOnlyCount: 0 aSize: 5
    indexer     12.12 09:52:06.983     index update work     isRebuild?false; IndexerStep:CheckForWork; Class:intradoc.indexer.Indexer
    indexer     12.12 09:52:06.985     index update work     isRebuild?false; IndexerStep:DetermineSubscription; Class:intradoc.indexer.DetermineSubscription
    indexer     12.12 09:52:06.990     index update work     isRebuild?false; IndexerStep:Replication; Class:intradoc.server.IndexerReplication
    indexer     12.12 09:52:06.993     index update work     isRebuild?false; IndexerStep:PostIndexingStep; Action:postIndexingStep
    indexer     12.12 09:52:06.996     index update work     isRebuild?false; IndexerStep:Cleanup; Class:intradoc.indexer.Indexer
    indexer     12.12 09:52:06.996     index update work     cleanup for dID 1077393 change is D origChange is -
    indexer     12.12 09:52:06.999     index update work     cleanup for dID 1077394 change is D origChange is -
    indexer     12.12 09:52:06.999     index update work     cleanup for dID 1077401 change is D origChange is -
    indexer     12.12 09:52:06.999     index update work     cleanup for dID 1077416 change is D origChange is -
    indexer     12.12 09:52:06.999     index update work     cleanup for dID 1077417 change is D origChange is -
    indexer     12.12 09:52:07.112     index update work     isRebuild?false; IndexerStep:Init; Class:intradoc.indexer.Indexer
    indexer     12.12 09:52:07.114     index update work     isRebuild?false; IndexerStep:BuildChanges; Class:intradoc.indexer.IndexerBuildChanges
    indexermonitor     12.12 09:52:10.124     index update work     deleting lock file /VisApp/stellent/install/search/lock/update_lock.dat.
    indexermonitor     12.12 09:52:10.126     index update work     Ending indexing update.

    I dont see anything really wrong here. Then again I don't really know what I am looking at. Any ides?
  • 7. Re: Indexer never running after checkin or delete on UCM 10g
    Bunty Journeyer
    Currently Being Moderated
    Can you please try accessing
    <your cs url>/idcplg?IdcService=DOC_INFO_BY_NAME&dDocName=<contentid>
    This may not be helpful but I am really curious
  • 8. Re: Indexer never running after checkin or delete on UCM 10g
    947250 Newbie
    Currently Being Moderated
    Yup that worked just fine. Also I should mention that I have just ran a full collection rebuild cycle, but the automatic update cycle is still not kicking off or actually updating.
  • 9. Re: Indexer never running after checkin or delete on UCM 10g
    Srinath Menon Guru
    Currently Being Moderated
    Hi ,

    Follow this action plan :

    Navigate to <domain_home>/ucm/cs/search/ and there 3 sub-folders would be available :

    /rebuild
    /lock
    /update

    Clear out the contents that are present (files) in these 3 sub-folders , restart UCM , then navigate to Repo Manager - Indexer - Auto Cycle and start it.

    Once it completes , then check to see if the contents are getting auto-indexed or not .

    Thanks,
    Srinath

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points