Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
PTF Kiwi env: https://pre-kiwi-cap1.int.aws.folio.org/
-
-
eHoldings Sprint 126
-
1
-
Spitfire
-
R3 2021
Description
The following versions of modules were deployed to PTF env https://pre-kiwi-cap1.int.aws.folio.org/
mod-inventory-storage v22.0.0
mod-inventory v18.0.0
mod-source-record-storage v5.2.0
mod-source-record-manager v3.2.2
mod-data-import v2.2.0
After that, DI Create job with 100 records resulted in error in mod-source-record-storage
16:15:26.251 [vert.x-worker-thread-0] WARN RecordDaoImpl [349846448eqId] Error occurred on batch execution: ERROR: column "external_id" of relation "records_lb" does not exist 16:15:26.259 [vert.x-worker-thread-0] ERROR RecordDaoImpl [349846456eqId] Failed to save records 2021-10-22T12:15:26.260-04:00 org.jooq.exception.DataAccessException: SQL [null]; ERROR: insert or update on table "raw_records_lb" violates foreign key constraint "fk_raw_records_records"
After doing more investigation, found that in mod_source_record_storage.records_lb table, 2 columns have been renamed in Kiwi
instance_id -> external_id
instance_hrid -> external_hrid
This should have been renamed as part of the schema migration script when we upgrade to mod-source-record-storage v5.2.0 from Juniper. Looks like migration scripts are not running. How should we fix this? Here is the log mod-srs-external-id-missing.log
TestRail: Results
Attachments
Issue Links
- relates to
-
FOLIO-2283 Compensation scripts in the schema migration guideline in the RMB
-
- Open
-