We are having database migration and as part of migration we are not able to add foreign key for QRTZ_BLOB_TRIGGERS and QRTZ_TRIGGERS tables. In our investigation, we have found that it is because of data type difference on primary key (TRIGGER_NAME).
In below table structure we can see the datatype for TRIGGER_NAME in QRTZ_TRIGGERS table is NVARCHAR2 and datatype for TRIGGER_NAME in QRTZ_BLOB_TRIGGERS table is VARCHAR2.
Could you please help us to understand why datatype is different for primary key and what will be impact on Identity Governance application if it's not available.
Please see below table structure and error details for more details.
Release : 14.2
Component : CA IDENTITY SUITE (VIRTUAL APPLIANCE)
it had data types pointing to varchar2
CREATE TABLE qrtz_blob_triggers
TRIGGER_NAME NVARCHAR2(80) NOT NULL,
TRIGGER_GROUP NVARCHAR2(80) NOT NULL,
BLOB_DATA BLOB NULL,
PRIMARY KEY (TRIGGER_NAME,TRIGGER_GROUP),
FOREIGN KEY (TRIGGER_NAME,TRIGGER_GROUP)
Part of that command creates the foreign key
We did not need to import data to qrtz_blob_triggers, the table was empty
L2 states that there should be no issues on ear restart, as the table exists and will not need to be recreated.