p_manage_01 indexing job did not update everything in changed tab_type_config

• Article Type: General
• Product: Aleph
• Product Version: 19.01

Description:
The p_manage_01 indexing job (run in the abc03 parallel library) did not update everything that was changed for tab_type_config.eng. For example, a new definition of WTY=Database was added. I get only 24 hits on Prod, but 327 on Test.

Resolution:
As noted in Step 5 of the Parallel Indexing document:

"Define the setup of the indexing tables in the tab directory of the indexing library. You can choose to copy the tables that are used for indexing in the actual library into the tab directory of the indexing library, or you can use the path_convert configuration table to direct the system to the actual library’s configuration tables. This option is feasible only if you do not want to change the indexing setup.

"You may change $data_tab values in the indexing library in order to improve the indexing. If you do this, be sure to copy these changed tables to the actual library as described in Step 9."

In this case we see that the update to tab_type_config.eng was done in the $data_tab of the abc01 (actual) library,
but not in the $data_tab of the abc03 parallel library.

If the affected records are few enough (fewer than 5,000?), you could do a search (or run p_ret_01) and use the result as input to p_manage_40 which will create a z07 indexing request for each.

• Article last edited: 10/8/2013