How to check the status of items that have been sent (to the indexing engine) but not been indexed

Article:HOWTO59169  |  Created: 2011-09-05  |  Updated: 2014-12-09  |  Article URL http://www.symantec.com/docs/HOWTO59169
Article Type
How To



You can see the number of items that have been marked as failed using the Index Volumes Browser.
However it can take a long time for failing items to be marked as failed (or indexed) so to see the current status of any items being indexed you need to check the entries in the following SQL tables in the relevant Vault Store database:

1)    ItemAdditionStatusLog
This contains the status of new items that have been submitted to the indexing engine. Entries for successfully indexed items are removed from this table regularly.

2)    ItemUpdateStatusLog
This contains the status of updates for already indexed items that have been submitted to the indexing engine. Entries for successful updates are removed from this table regularly.

3)    ItemDeletionStatusLog
This contains the status of deletions of indexed items that have been submitted to the indexing engine. Entries for successfully deleted items are removed from this table regularly.


Note: The SQL queries below assume that the Vault Store database and Enterprise Vault Directory database are located on the same SQL server. An alternative approach would be needed if this was not the case.

1)    ItemAdditionStatusLog
select ArchiveName, ItemSeqNum, Status, ErrorNumber, PoisonPilled, RetryCount, RawError
from
(select ArchivePoint.Archivepointid, itemseqnum, status, errornumber, poisonpilled, retrycount, rawerror
from itemadditionstatuslog
inner join ArchivePoint on ArchivePoint.ArchivePointIdentity = ItemAdditionStatusLog.ArchivePointIdentity
where status > 0) SQ
INNER JOIN EnterpriseVaultDirectory.dbo.ArchiveView ON ArchiveView.VaultEntryId = SQ.ArchivePointId
order by status desc, archivepointid, itemseqnum


This lists all the items that have been submitted to the indexing engine but not confirmed as being indexed (yet). The list is ordered by ‘status’ to ensure any failed items are listed as the top.
The columns are described below:

Archivename – The name of the archive affected
ItemSeqNum – An identifying number for the archived item. This number can be used to identify the archived item itself.
Status – 3 possible values:
    0 – Successfully indexed (not returned by this SQL query)
    1 – Pending. Waiting for confirmation from indexing engine that item was indexed (or not)
    2 – Failed to be indexed

ErrorNumber – Values indicate the reason for a failure to index as detailed below:
    100 – Error retrieving data from storage
    101 – Item was corrupt (according to the indexing engine)
    102 – Indexing engine rejected item with an error (see RawError value for more information)
    103 – Indexing engine accepted item but later returned an error (see RawError value for more information)
    104 – Not Applicable (used internally)
    105 – This means that the Verify tool identified this item as failing to be indexed but could not find a reason
    106 – This means that an item has been in the ‘Pending’ state (having a Status of 1) for too long

PoisonPilled – This indicates that an item has failed to be indexed too many times and will not be tried again.
To force such items to be tried again you need to run a Synchronise (or Rebuild) task against the index volume (or archive)
RetryCount – This indicates the number of attempts that have been made to index the item.
By default 3 attempts are made before the item is poison pilled.
RawError – This contains the error received from the indexing engine


2)    ItemUpdateStatusLog
select ArchiveName, ItemSeqNum, Status, PoisonPilled, RetryCount, ModifiedDataFlags
from
(select ArchivePoint.Archivepointid, itemseqnum, status, poisonpilled, retrycount, ModifiedDataFlags
from itemupdatestatuslog
inner join ArchivePoint on ArchivePoint.ArchivePointIdentity = ItemUpdateStatusLog.ArchivePointIdentity) SQ
INNER JOIN EnterpriseVaultDirectory.dbo.ArchiveView ON ArchiveView.VaultEntryId = SQ.ArchivePointId
order by status desc, archivepointid, itemseqnum


This lists all the updates for indexed items that have been submitted to the indexing engine but not confirmed as being applied (yet). The list is ordered by ‘status’ to ensure any failed items are listed as the top.
The columns are described below:

Archivename – The name of the archive affected
ItemSeqNum – An identifying number for the indexed item. This number can be used to identify the archived item itself.
Status – 3 possible values:
    0 – Successfully indexed (not returned by this SQL query)
    1 – Pending. Waiting for confirmation from indexing engine that item was indexed (or not)
    2 – Failed to be indexed

PoisonPilled – This indicates that an indexed item has failed to be updated too many times and will not be tried again.
The Synchronise task does not retry failed updates. The Rebuild task does apply the updates though.
RetryCount – This indicates the number of attempts that have been made to update the indexed entry for the item.
By default 3 attempts are made before the item is poison pilled.
ModifiedDataFlags – Value detailed which property was changed:
    1 – Retention Category was changed
    2 – Shortcut Location was changed
    3 – Both Retention Category and Shortcut Location was changed


3)    ItemDeletionStatusLog
select ArchiveName, SavesetID, ItemSeqNum, Status, PoisonPilled, RetryCount
from
(select ArchivePoint.Archivepointid, savesetid, itemseqnum, status, poisonpilled, retrycount
from itemdeletionstatuslog
inner join ArchivePoint on ArchivePoint.ArchivePointIdentity = ItemDeletionStatusLog.ArchivePointIdentity) SQ
INNER JOIN EnterpriseVaultDirectory.dbo.ArchiveView ON ArchiveView.VaultEntryId = SQ.ArchivePointId
order by status desc, archivepointid, itemseqnum


This lists all the deletions of indexed items that have been submitted to the indexing engine but not confirmed as being applied (yet). The list is ordered by ‘status’ to ensure any failed deletions (from the index volume) are listed as the top.
The columns are described below:

Archivename – The name of the archive affected
SavesetID – A unique identifier for the corresponding deleted item
ItemSeqNum – An identifying number for the indexed item. This number can also be used to identify the archived item itself.
Status – 3 possible values:
    0 – Successfully indexed (not returned by this SQL query)
    1 – Pending. Waiting for confirmation from indexing engine that item was indexed (or not)
    2 – Failed to be indexed

PoisonPilled – This indicates that an item has failed to be deleted from the index too many times and will not be tried again.
To force such items to be tried again you need to run a Synchronise (or Rebuild) task against the index volume (or archive)
RetryCount – This indicates the number of attempts that have been made to delete the indexed item.
By default 3 attempts are made before the item is poison pilled.




Article URL http://www.symantec.com/docs/HOWTO59169


Terms of use for this information are found in Legal Notices