Skip to content

Archive route change triggers ORA-00001: unique constraint violated

When changing 2nd copy of an archive route to a tape pool that is already used for the 1st copy ORA-00001: unique constraint violated error message is triggered:

pcvlado /etc/cta > cta-admin ar ls | grep -i totem
            public_totem           1                    r_totem vyurchen           eosctafst0205 2021-04-23 12:44 vyurchen           eosctafst0205 2021-04-23 12:44 public_totem -> r_totem
              totem_grid           1                    r_totem vyurchen           eosctafst0205 2021-04-23 12:45 vyurchen           eosctafst0205 2021-04-23 12:45 totem_grid -> r_totem
              totem_misc           1                  r_totem_1 vyurchen           eosctafst0205 2021-04-23 12:47 vyurchen           eosctafst0205 2021-04-23 12:47 totem_misc -> r_totem_1
              totem_misc           2                  r_totem_2 vyurchen           eosctafst0205 2021-04-23 12:47 vyurchen           eosctafst0205 2021-04-23 12:47 totem_misc -> r_totem_2
pcvlado /etc/cta > cta-admin ar ch -s public_totem -c 1 -t r_totem
pcvlado /etc/cta > cta-admin ar ch -s totem_misc -c 2 -t r_totem_1
modifyArchiveRouteTapePoolName: executeNonQuery failed: executeNonQuery failed for SQL statement UPDATE ARCHIVE_ROUTE SET TAPE_POOL_ID = (SELECT TAPE_POOL_ID FROM TAPE_POOL W...: ORA-00001: unique constraint (CTA_PRODUCTION.ARCHIVE_ROUTE_SCI_TPI_UN) violated

This should be replaced by some user friendly error message.

Edited by Vladimir Bahyl