Deferred Indexing Errors

There are certain mq_indexes that must be assigned to certain queues. If you try to enter an incorrect queue assignment, Horizon may display an error message. This table lists the error messages you may see while using deferred indexing:

Error name

Error message

Explanation

Active queue error

Cannot change queue value when queue is active. Shut down QIndex before changing queue setting.

Active mq_index rows cannot be assigned to a different queue. You must first stop the queue indexer before changing the queue setting.

Awaiting processing error

Cannot change queue value from deferred (> 0) to zero when mq_index_queue entries exist for the mq_index in question.

There cannot be any pending queue entries for a deferred index when you change the queue assignment to queue 0. You must let QIndex completely empty the queue before you change the queue assignment of the index back to zero.

Note: This restriction does not apply to complex queues. (For example, you can change an index from queue 1 to 2 without emptying the queue after you stop the QIndex session that is handling queue 1.) (For more information on multiple queues, see Setting Up Complex Deferred Indexing .)

Change parent value error

Cannot change queue value of mq_indexes which depend on parent mq_indexes; change queue value of parent index instead.

In Horizon, an index_table_name (a child index) of one row in the mq_index can have the same name as a base_index_table (a parent index) for another row. If this happens, these related rows must be assigned to the same queue. (If a parent and child index were in different queues, corresponding information could not be inserted into the child index.)

You can change the queue setting of a parent row. Whenever a parent queue is changed, the trigger changes queue settings of all child rows to match the new queue of the parent.

Functional role error

When index & base table names are the same, queue value must be zero.

There are some cases where an mq_index exists to perform processing functions on the base table itself. In such cases, the processing functions must occur before the record is saved. If not, the record may be inserted into the wrong place in the table.

Match point error

Mq_indexes which are match points must be assigned to queue zero.

Any delay in fully populating the data used for matching could disrupt matching or linking during an import.

Non-MARC error

Queue value must be zero for non-MARC base tables.

Only MARC data can be indexed in a deferred fashion. Any non-MARC data, such as borrower or item information, must be indexed immediately.

 


© 1998-2017 Sirsi Corporation