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

    p_manage_07: Oracle error: io_z13u_write; unique constraint ... violated

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

    Description:
    Oracle error: io_z13u_write
    ORA-00001: unique constraint (ABC01.Z13U_ID) violated


    I am running p_manage_07 as part of a full reindex on my test system and am getting the following errors repeatedly:

    ORA-00001: unique constraint (ABC01.Z13U_ID) violated

    This is in preparation for an over-weekend run on production.
    We're at SP 2069

    Resolution:
    unique constraint violated" occurs when Oracle tries to write a record with a column whose value duplicates an existing value where the Oracle index on the column is defined as Unique.

    In this case, p_manage_07 is failing to drop the existing z13:

    aleph_admin@ALEPHTST> 10:42:19 aleph_admin@ALEPHTST> DROP TABLE ABC01.Z13
    *
    ERROR at line 1:
    ORA-00054: resource busy and acquire with NOWAIT specified
    This may have occurred because someone was accessing the test server z13 -- either via the www_server or the pc_server -- at the time the job was submitted.

    You can just try submitting the job again. The error shown above will appear in the p_manage_07 log within 10 seconds if there's a problem.

    If you find that it still doesn't work, then try stopping the www_server and pc_server prior to running it.

    If that doesn't work, then perform the steps described in KB 8192-7896.

    [From site:]

    Thanks, I ended up dropping the two tables manually. It took 3 tries to drop z13u due to "resource busy" but it did drop successfully.

    • Article last edited: 10/8/2013