util_a_17_01 Segmentation fault - KB solution results in merged file_lists

Last updated
Save as PDF
Share
1. Share
2. Tweet
3. Share

Article Type: General
Product: Aleph
Product Version: 19.01

Description:
[Version 19] With file_list_type and file_list_size commented out in the $data_root/prof_library, util a/17/1 from the utilities menu results in a segmentation fault. But, running $aleph_proc/util_a_17_b from the command line successfully drops and recreates a table and its indexes, whether file_list_type and file_list_size are commented out or not. The last 2 lines in $aleph_proc/util_a_17_01 are calls to $aleph_proc/util_a_17_b to build the table and index(es).

From SI #16384-103198, it was found a seg fault occurred when "check_synonym $table" (in util_a_17_01) is called. The solution was to uncomment $FILE_LIST_TYPE and $FILE_LIST_SIZE in $data_root/prof_library.

However, this results in the merge of the $data_root/file_list with the file_list templates in the a-tree. We don't use a merged file_list. Our file_lists in $data_scratch are a copy of the ones in $data_root (no TS0 and TS1 tablespaces).

I tried bypassing "check_synonym", then the "check_remote $table" call produced a seg fault but it did allow the drop and recreate of the table and index(es).

How do we use util a_17_01 as is and not merge $data_root/file_list with the file_list templates? Are merged file_lists a requirement now?

Resolution:
The only way that we know of to eliminate the Segmentation fault is by specifying a file_list_type in the prof_library.

If your $data_root/file_list contains all the tables in the $aleph_root/tab/file_list.xxx template, then the aleph_root/tab/file_list.xxx template will not be used.

If there's a particular table defined in the $aleph_root/tab/file_list.xxx template which you do not want to be defined in your xxx library, then you can include an "NA" entry for it in your $data_root/file_list. This is described in KB 8192-5095.

If you want a tablespace other than ts0/ts1 to be used for tables generated from the template, you can use the file_list_ts0/ts1 parameter. From KB 8037: "The file_list_<table/index space name> parameter can be used to change the default table/index space assigned in the template."

Article last edited: 10/8/2013