Skip to main content
ExLibris
  • Subscribe by RSS
    • Back
    Aleph
    Ex Libris Knowledge Center

    p_publish_04 running indefinitely (version 20)

    1. Last updated
    2. Save as PDF
    • Article Type: General
    • Product: Aleph
    • Product Version: 20

    Description:
    We are experiencing some difficulties with publish-04. After doing publish-05, we started publish-04 at 16H34 yesterday and it is still running. We checked the log to see if there was an error file 'p_publish_04.err'. In this file we found to errors (cycle 19 and cycle 20). We follow the indication :

    "To identify this error in your log files use the command:
    grep "FAILURE Thu May 27 21:30:00 EDT 2010" $data_scratch/*.log"

    and found in these two files p_publish_04_b_11.log and p_publish_04_b_16.log with this error message from Oracle :

    "Error: write_xml_to_clob: ORA-01691: unable to extend lob segment UQM00.Z00P_SEGNAME by 8192 in" (line ending abruptly)

    This error may have to do with this instruction in Upgrade Express 18.01 to 19.01 User Guide.pdf :

    "The publishing entity (Z00P) Oracle table should have a separate tablespace to for
    maintenance purposes. If possible, the new tablespace should be on a different
    physical disk than the already existing ALEPH tablespaces.
    Enlarge the redo file from 50MB to 500MB. This should be done by an Oracle DBA.
    It is recommended that the redo files be on a different physical disk than the
    tablespaces."

    We did not make these modifications at all. Is this the cause of the problem with publish-04 ?

    Resolution:
    Though it may help with p_publish_04 performance, having the z00p on a different disk than the abc01 z00 will *not* cause the problem you are seeing.

    The "unable to extend" message indicates that the table needs another extent and could not get it.

    The following SQL shows that the abc50 z00p table resides in the TS4D tablespace:

    abc50@ALEPH20> select TABLESPACE_NAME from all_tables where table_name = 'Z00P' and OWNER = 'ABC50';

    And we see in util o/14/1 that the largest free extent in TS4D is 63 meg:

    TABLESPACE_NAME TOTAL_FREE_SPACE MAX_EXTENT NUM_FREE_EXTENTS
    ------------------------------ ---------------- ---------- ----------------
    TS4D 530.291298 63.034626 15

    It seems that another datafile needs to be added to the TS4D tablespace.

    (Note: If this tablespace is "autoextend", then Oracle should automatically create a datafile and the cause of the message may be something else ...)

    • Article last edited: 10/8/2013