• Type: Bug
• Resolution: Fixed
• Priority: Medium
• Fix Version/s: 4.20.12
• Affects Version/s: 4.20.8
• Component/s: Assets - Import
• Labels:

  • rbst

[JSDSERVER-11950] Unable to synchronize and edit data locator of an object type mapping for a JSON import on upgraded JSM instance using Oracle as database

Orest Busel (Inactive) made changes - 27/Sep/2022 9:06 AM

Resolution		New: Fixed [ 1 ]
Status	Original: In Progress [ 3 ]	New: Closed [ 6 ]

Orest Busel (Inactive) made changes - 26/Sep/2022 1:44 PM

Status

Original: Gathering Impact [ 12072 ]

New: In Progress [ 3 ]

SET Analytics Bot made changes - 23/Sep/2022 2:12 AM

UIS

Original: 41

New: 42

SET Analytics Bot made changes - 22/Sep/2022 4:04 AM

Support reference count

Original: 2

New: 3

Michelle Chin made changes - 16/Sep/2022 12:53 PM

Description

Original: h3. Issue Summary After upgrading an JSM instance which is using Oracle as a database, it's not possible to update any data locators of an object type mapping of a JSON import, and synchronization is not possible. This affects all existing and new JSON import that has been configured. This is reproducible on Data Center: yes (i) This is not reproducible on a vanilla instance, only on upgraded instance h3. Steps to Reproduce  # Set up a JSM instance below version 4.15 with Oracle as the database.  # Set up Insight with a working [JSON import|https://confluence.atlassian.com/servicemanagementserver/json-import-1044784481.html].  # Ensure that you can edit the object type mapping to update any data locators.  # Upgrade the JSM instance to a recent version e.g. JSM 4.20.8.  # Edit the JSON import configuration to change any data locators. h3. Expected Results The list of data locator will appear without any error on the screen h3. Actual Results * The list of data locator will not appear * There's a pop-up error on the screen with text {quote} The Jira server was contacted but has returned an error response. We are unsure of the result of this operation. {quote} * After clicking on the OK button to dismiss the error dialogue, HTTP error code 500 can be seen in the browser's developer tools > Network tab. The response would look like the following. {code} {"errorMessages":["Unable to get data locators for configuration of type {}ObjectTypeBean [id=1, name=JSON]"],"errors":{}} {code} * Synchronization is not possible h3. Workaround It's possible to update the data locator from directly from the database but with caution. The SQL query below can be used to retrieve the existing object type mapping configuration. Feel free to contact support if you need help with updating data locators from the database. {code:SQL} select * from "AO_8542F1_IFJ_IMPORT_SRC_OTA" afiiso where "IMPORT_SOURCE_OTID" in ( select "ID" from "AO_8542F1_IFJ_IMPORT_SRC_OT" afiiso where "IMPORT_SOURCE_ID" = (select "ID" from "AO_8542F1_IFJ_IMPORT_SRC" where "NAME" = 'name_of_the_JSON_import_configuration')) {code}

New: h3. Issue Summary After upgrading an JSM instance which is using Oracle as a database, it's not possible to update any data locators of an object type mapping of a JSON import, and synchronization is not possible. This affects all existing and new JSON import that has been configured. This is reproducible on Data Center: yes (i) This is not reproducible on a vanilla instance, only on upgraded instance h3. Steps to Reproduce  # Set up a JSM instance below version 4.15 with Oracle as the database.  # Set up Insight with a working [JSON import|https://confluence.atlassian.com/servicemanagementserver/json-import-1044784481.html].  # Ensure that you can edit the object type mapping to update any data locators.  # Upgrade the JSM instance to a recent version e.g. JSM 4.20.8.  # Edit the JSON import configuration to change any data locators. h3. Expected Results The list of data locator will appear without any error on the screen h3. Actual Results * The list of data locator will not appear * There's a pop-up error on the screen with text {quote} The Jira server was contacted but has returned an error response. We are unsure of the result of this operation. {quote} * After clicking on the OK button to dismiss the error dialogue, HTTP error code 500 can be seen in the browser's developer tools > Network tab. The response would look like the following. {code} {"errorMessages":["Unable to get data locators for configuration of type {}ObjectTypeBean [id=1, name=JSON]"],"errors":{}} {code} * Synchronization is not possible h3. Workaround {panel} Update: This issue is not reproducible in JSM 4.0.12. It's recommended to upgrade to JSM 4.0.12 if the affected instance is on JSM 4.0.x or below. {panel} It's possible to update the data locator from directly from the database but with caution. The SQL query below can be used to retrieve the existing object type mapping configuration to be used for the update. {code:SQL} select * from "AO_8542F1_IFJ_IMPORT_SRC_OTA" afiiso where "IMPORT_SOURCE_OTID" in ( select "ID" from "AO_8542F1_IFJ_IMPORT_SRC_OT" afiiso where "IMPORT_SOURCE_ID" = (select "ID" from "AO_8542F1_IFJ_IMPORT_SRC" where "NAME" = 'name_of_the_JSON_import_configuration')) {code}

Orest Busel (Inactive) made changes - 14/Sep/2022 10:20 AM

Assignee

New: Orest Busel [ 4dcffb92068e ]

Bugfix Automation Bot made changes - 09/Sep/2022 12:36 PM

Priority

Original: Low [ 4 ]

New: Medium [ 3 ]

SET Analytics Bot made changes - 09/Sep/2022 8:10 AM

UIS

New: 41

Michelle Chin made changes - 07/Sep/2022 9:28 AM

Fix Version/s

New: 4.20.12 [ 101992 ]

SET Analytics Bot made changes - 31/Aug/2022 4:04 AM

Support reference count

Original: 1

New: 2

Load more older history items