Details
-
Suggestion
-
Resolution: Won't Do
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
At present if there are database permission problems in the JIRA database and AO requires them then AO will attempt to create tables/sequences/triggers and if it fails when these attempts are made there is little indicator that this has happened aside from an AO error in the logs.
As a background, In regards to GHS-3904 and GHS-3904 it has been discovered that up until recently customers have been asked to set up their Oracle databases with missing privelages to create sequences and and triggers, this may be the case in Oracle databases, but also in any other database type and due to the permissions required by AO.
It would be great to have useful warnings and notifications of such problems on database modification failure resulting in plugins becoming disabled.
Attachments
Issue Links
- incorporates
-
JRASERVER-26958 If a plugin causes an active objects exception that plugin should be automatically disabled.
- Closed
- is cloned from
-
JRASERVER-26888 Jira 5 to stop upgrade/install if Oracle database permissions are incorrect.
- Closed
- is duplicated by
-
JRASERVER-26958 If a plugin causes an active objects exception that plugin should be automatically disabled.
- Closed
- relates to
-
JRACLOUD-26935 JIRA 5 should capture AO database modification errors, provide this information in the UI and disable the plugin that is causing the error
- Closed