Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-26840

Oracle database schema guide set incorrectly

XMLWordPrintable

    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Support have been seeing a myriad of problems in regards to the schema miconfiguration in getting the creation of sequences right.

      Please see this doco:
      http://confluence.atlassian.com/display/JIRA044/Connecting+JIRA+to+Oracle

      Note that it's missing the full range of permissions that the JIRA 5 doco has:
      http://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+Oracle

       

grant connect to <user>;
grant create table to <user>;
grant create sequence to <user>;
grant create trigger to <user>;

      AO in GH 5.8.x requires Oracle to have at least sequence creation.

          Form Name

            [JRASERVER-26840] Oracle database schema guide set incorrectly

            Giles Gaskell [Atlassian] added a comment -

            Closed again - as agreed with mandreacchio.

            Giles Gaskell [Atlassian] added a comment - Closed again - as agreed with mandreacchio .

            Giles Gaskell [Atlassian] added a comment -

            Done

            I've also mentioned this requirement in the JIRA 5.0 Upgrade Notes.

            I suspect rosie@atlassian.com may have talked to me about this at some point too. Anyhow - I think the necessary additions/updates concerning Active Objects in JIRA 5.0 and their implications on JIRA servers connected to Oracle databases (including GH), have been covered now.

            Cheers,
            Giles.

            Giles Gaskell [Atlassian] added a comment - Done I've also mentioned this requirement in the JIRA 5.0 Upgrade Notes . I suspect rosie@atlassian.com may have talked to me about this at some point too. Anyhow - I think the necessary additions/updates concerning Active Objects in JIRA 5.0 and their implications on JIRA servers connected to Oracle databases (including GH), have been covered now. Cheers, Giles.

            Michael Andreacchio added a comment -

            Hey Giles,

            Please revert the changes to the JIRA 5.x doco:
            http://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+Oracle

            They'll always be needing to have those permissions on their database on JIRA 5 regardless of GH or not, this is the move towards ActiveObjects, which GH 5.8.x uses in JIRA 4.4.x but then all plugins will be using in JIRA 5.x.

            Cheers,

            Michael

            Michael Andreacchio added a comment - Hey Giles, Please revert the changes to the JIRA 5.x doco: http://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+Oracle They'll always be needing to have those permissions on their database on JIRA 5 regardless of GH or not, this is the move towards ActiveObjects, which GH 5.8.x uses in JIRA 4.4.x but then all plugins will be using in JIRA 5.x. Cheers, Michael

            Giles Gaskell [Atlassian] added a comment -

            The following pages were amended:

            Giles Gaskell [Atlassian] added a comment - The following pages were amended: http://confluence.atlassian.com/display/JIRA044/Connecting+JIRA+to+Oracle http://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+Oracle

            Giles Gaskell [Atlassian] added a comment -

            Since this content is going into the JIRA documentation but is intended for GH, I've discussed this in more detail with mandreacchio and have clarified the following:

            • The commands above are essentially required for GH usage.
            • For customers who only intend to use JIRA (without GH), the commands above should not affect JIRA's behaviour.

            Giles Gaskell [Atlassian] added a comment - Since this content is going into the JIRA documentation but is intended for GH, I've discussed this in more detail with mandreacchio and have clarified the following: The commands above are essentially required for GH usage. For customers who only intend to use JIRA (without GH), the commands above should not affect JIRA's behaviour.

              ggaskell Giles Gaskell [Atlassian]
              mandreacchio Michael Andreacchio
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: