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. Parallel indexing, p_manage_32, "such column list already indexed "

    Parallel indexing, p_manage_32, "such column list already indexed "

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

    Description:
    Following the Parallel Indexing document, I created LS's for z00, z103 and z0102 in the indexing library ABC02 to the actual library ABC01 in our Test region. I was able to successfully run the indexing jobs for keywords and headings but when I tried to run p-manage-32 in the ABC02 indexing library the job finished in seconds without processing any records. I used this in the ABC02 library:

    csh -f $aleph_proc/p_manage_32 ABC02,1,ALL,5, > & $alephe_scratch/abc02_p_manage_32.log &

    The $alephe_scratch/abc02_p_manage_32.log seems to indicate that it found no records to index. The actual create index logs in the $data_scratch, like create_ora_tables_z0102_id1.log, show this error:

    ORA-01408: such column list already indexed

    which seems to indicate that it used the synonym correctly since it found the indexes already present. Is there some other table I should have created a logical synonym for other than z0102 for p-manage-32 to work correctly?

    Resolution:
    The Parallel Indexing document needs to be updated. It says to LS the z0102 to the actual library. When you do this, you will not be able to run p_manage_32 in the parallel library. When you did this run, the job was trying to drop/create the abc01 z0102!

    You could wait and run p_manage_32 in abc01, post-parallel-indexing -- which is what the document suggests --, but actually, in v17-up, there's no reason it can't run in the parallel library.

    You need to do the following to allow this:

    * in the abc02 file_list, change:

    LS z0102 abc01

    To:

    !LS z0102 abc01
    TAB z0102 960M 0K TSnD
    IND z0102_id 960M 0K TSnX
    IND z0102_id1 960M 0K TSnX

    <changing "n" to the desired tablespace number>

    * in abc02, do util a/17/5/2 to recreate the synonyms

    * in abc02, do util a/17/5/1 to confirm that the z0102 synonym is gone

    * in abc02, do util a/17/1 for z0102 to create the table in abc02

    * run p_manage_32 in abc02.


    • Article last edited: 10/8/2013
    View article in the Exlibris Knowledge Center
    1. Back to top
      • Parallel indexing, exporting of Oracle tables / indexes
      • parallel indexing: util g/2 last-doc-number changed incorrectly
    • Was this article helpful?

    Recommended articles

    1. Article type
      Topic
      Language
      English
      Product
      Aleph
    2. Tags
      1. 18.01
      2. contype:kba
      3. Prod:Aleph
      4. 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