Good morning,
We are seeing this error in our JIRA instance and it seems to be writing to a table that doesn't exist, I just wanted someone to take a look at this and see maybe what we could do to remedy it. It's not affecting functionality, but our DB Admins are seeing this error very frequently;
...Current username=SERVICE_DESK
...Application: JDBC Thin Client Action:
2022-08-24T07:49:05.626567-04:00
WARNING: too many parse errors, count=1953900 SQL hash=0x018df152
PARSE ERROR: ospid=6576, error=904 for statement:
2022-08-24T07:49:05.626652-04:00
select "MIGRATION"."MIGRATION_ID", "MIGRATION"."PLAN_ID", "MIGRATION"."START_MIGRATION_CONTEXT_JSON", "MIGRATION"."IN_PROGRESS_STATUS_JSON", "MIGRATION"."OUTCOME_JSON", "MIGRATION"."APP_OUTCOME_JSON", "MIGRATION"."STARTED_BY", "MIGRATION"."CREATED_TIMESTAMP", "MIGRATION"."UPDATED_TIMESTAMP", "MIGRATION"."PROTOCOL_JSON" from "AO_6FF49D_MIGRATION_ENTITY" "MIGRATION" where "MIGRATION"."OUTCOME_JSON" is null and "MIGRATION"."UPDATED_TIMESTAMP" > :1
Additional information: hd=0x954a2de8 phd=0x954a4540 flg=0x100476 cisid=658 sid=658 ciuid=658 uid=658 sqlid=98d3rb80svwak
...Current username=SERVICE_DESK
I think we traced some of it back to the migration assistant which we've disabled but still see the error. Any guidance would be appreciated, thanks!
Harry Aiken
Systems Administrator II
404-651-8843
Georgia Dept of Audits and Accounts
Information Technology Division
Hi @Harry Aiken
Have you checked if you have custom fields tied to the migration assistance app? The custom fields don't tend to get removed even if an app is disabled.
There could be other artifacts as well but many apps add artifacts in random schemes throughout Jira
Best,
Clark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.