Skip to main content
ExLibris

Knowledge Assistant

BETA
 
  • Subscribe by RSS
  • Back
    Aleph
    Ex Libris Knowledge Center
    1. Search site
      Go back to previous article
      1. Sign in
        • Sign in
        • Forgot password
    1. Home
    2. Aleph
    3. Knowledge Articles
    4. Unwanted entries being included from the $aleph_root/tab/file_list.XXX templates

    Unwanted entries being included from the $aleph_root/tab/file_list.XXX templates

    1. Last updated
    2. Save as PDF
    3. Share
      1. Share
      2. Tweet
      3. Share
    No headers
    • Article Type: General
    • Product: Aleph

    Description:
    I like to use the file_list mechanism to set up table sizes. In earlier versions of Aleph, these were located in the $data_root directory, but I seem to recall that either they moved in Aleph 18 or there was a change we could make so that they could continue to be in that location.

    I find that with Aleph 20, creating all tables is not looking at my file_list but must be looking at something else.

    KB 8192-3719 recommends commenting out the file_list_type and file_list_size, but if I do that I get the Segmentation Fault described there.

    We have tried adding file_list_TSnD / file_list_TSnX lines with dummy tablespace names, but it seems to default to ts0 / ts1 in that case.

    Resolution:
    If you find that tables which you don't want to have defined are being included from the file_list.XXX template, then you can prevent their being created by adding a line such as this in your $data_root/file_list:

    NA z13u

    This entry in the $data_root/file_list will take precedence over the entry in the template. This is described in detail in KB 8192-5095.

    Or, if you don't like that solution, you could delete all the lines in each of the $aleph_root/tab/file_list.XXX's.

    (It's possible that something could complain if they were deleted, but certainly having no lines would not be a problem....)

    You would need to check after each Service Pack to make sure that new, populated ones have not replaced your empty ones.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Unwanted ADM record created
      • Unwanted hold request on available Aleph items in Primo
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. contype:kba
      2. Prod:Aleph
      3. Type:General
    1. © Copyright 2025 Ex Libris Knowledge Center
    2. Powered by CXone Expert ®
    • Term of Use
    • Privacy Policy
    • Contact Us
    2025 Ex Libris. All rights reserved