Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
5
-
Folijet
-
Lotus (R1 2022) Bug Fix
-
Related dependency upgrade
Description
When upgrading from srm 3.3.6 to srm 3.3.7 we receiving this error:
{ "id" : "a6550c0f-628b-49f9-b8fd-50765f52e4f2", "complete" : true, "startDate" : "2022-04-07T20:26:38.571493Z", "endDate" : "2022-04-07T20:26:40.219906Z", "modules" : [ { "id" : "mod-source-record-manager-3.3.7", "from" : "mod-source-record-manager-3.3.5", "action" : "enable", "message" : "Tenant operation failed for module mod-source-record-manager-3.3.7: SQL error\n CREATE INDEX IF NOT EXISTS job_execution_source_chunks_jobexecutionid_index ON job_execution_source_chunks USING BTREE (jobExecutionId);\nERROR: column \"jobexecutionid\" does not exist (42703)", "stage" : "invoke" }
Need to correct database migration script for Lotus deployment.
Interested parties: hleb_surnovich Rachana Murnal
TestRail: Results
Attachments
Issue Links
- blocks
-
MODSOURMAN-769 Release v3.3.8 (R1 Lotus Bugfix)
-
- Closed
-
- clones
-
MODSOURMAN-762 Supporting update SRM on envs
-
- Closed
-
- defines
-
UXPROD-3262 NFR: Data Import R1 2022 Lotus Technical, NFR, & Misc work
-
- Closed
-