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

    Error message in import log "Constraint P41_PRM00.R_STAFF_UK_01 violated"

    • Article Type: General
    • Product: Primo
    • Product Version: 4

    Problem Symptoms:
    The following error can be found in the import log file:

    Caused by: java.sql.BatchUpdateException: ORA-00001: unique constraint (P41_PRM00.R_STAFF_UK_01) violated

    at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(
    at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(
    at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(
    at org.hibernate.jdbc.AbstractBatcher.executeBatch(
    ... 40 more
    2014-02-28 12:24:26,714 ERROR [t-ImportConfig] [c-StopPrimoToolsExceptionHandler] - Error executing ImportConfig
    org.springframework.dao.DataIntegrityViolationException: Could not execute JDBC batch update; SQL [insert into R_STAFF (USERNAME, PASSWORD, ADDRESS, EMAIL, END_USER_ID, HOME_PHONE, MOBILE_PHONE, ORGANIZATIONAL_UNIT_ID, USER_ID, WORK_PHONE, customerid, institutionId, libraryId, CREATION_DATE, UPDATED_DATE, UPDATED_BY, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; constraint [P41_PRM00.R_STAFF_UK_01]; nested exception is org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update


    Unique constraint "R_STAFF_UK_01" is generated from username column in r_staff table.
    Identical staff usernames exists in the source and target environment.

    1) Go to Primo Back office / On Going configurations / Staff Configurations screen
    2) Compare the source environment and the target environment to find the identical username
    3) Change the username in the target environment to something different

    Category: Primo

    Subject: Export & Import

    • Article last edited: 6/27/2014