Structure Management ─ Deployment and Administration
Structure index states
Understand different categories of index states and their meaning and implications. There are various categories of index states: Initial Indicates either new index creation or that an existing index is marked for deletion. In the state output, the create state is 0 - ReadForIndexing and the marked for deletion state is 10 - MarkedForDeletion. These states are usually set by the bomindex_admin utility, but can also be set by certain TcFTSIndexer actions. When the next sync action occurs, any product configuration in these states is propagated to other states during processing. Transitional Tracks the intermediate progress while processing a given product configuration. Transitional states should naturally propagate to final or terminal (failed) states during sync processing. Transitional states are only expected to be encountered during sync processing. If a transitional state is encountered at the start of sync processing, that indicates the given product configuration was not able to complete index processing for an unknown reason and that product configuration is promoted to the closest failure state. Final Indicates index processing for the given product configuration completed normally (8 - SolrIndexGenSuccess). Although you might expect to have a final deleted success state as well, the final step in index delete processing is to delete the product configuration data for the index, along with the state information. Terminal Track failures at particular steps in index processing. Once these states are reached, no further processing occurs for the given product configuration. Failure states are set either: Directly as a result of a processBOMIndex SOA call when the tcserver process had an issue processing the index. Examine the tcserver syslogs for details about the failure. Examine the TcFtsIndexer.log file for the ERROR message and any other information that was sent back with the error. Or the failure was detected in the TcFTSIndexer process due to a failure or an unexpected event. Examine the TcFtsIndexer.log file or the TcFtsIndexer_structure.log file for ERROR information. To recover from terminal states (failures) use the structure:recoverfailures action, which resets all failed product configurations to the appropriate initial state and the next sync action attempts to process them again. You must be careful that TcFTSIndexer is never stopped while the structure:sync action is running. If it is stopped prematurely any indexes that were still being processed are in transitional states and are set to terminal states on the next sync action.
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/administering_product_structures/ygh1737253426868/xid900585.html · retrieved 2026-07-11