Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-3613

Problem installing on Oracle schema when other schemas in the same database have one or more tables sharing the same name as any of Confluence's tables

    XMLWordPrintable

Details

    Description

      This is a list of the tables in used in Confluence as of version 1.4.2:

      SPACEPERMISSIONS
      TRACKBACKLINKS
      CONTENTLOCK
      PAGETEMPLATES
      os_user_group
      EXTRNLNKS
      NOTIFICATIONS
      ATTACHMENTS
      os_user
      SPACES
      os_group
      CONTENT
      ANCESTORS
      LINKS
      OS_PROPERTYENTRY

      If any of these tables in exist in other oracle schemas in the "same database", those tables will not be created, impairing bits of Confluence functionality that depend on those table(s).

      The bug is tied to this hibernate SchemaUpdate bug:

      http://opensource.atlassian.com/projects/hibernate/browse/HB-534

      This problem also affects PostgreSQL.

      Workaround

      This issue only occurs if the database user you are connecting to Oracle with has permission to view all tables across the database, not just those that relate to its own schema. You need to ensure you have followed all the steps in the Database Setup for Oracle document. The relevant ones here are the local all objects view, and ensuring that 'select any table' is not granted. However, all steps in that document need to be followed to avoid running into other issues down the track.

      Attachments

        1. logs.zip
          26 kB
          Rodrigo Prado Brandao [Atlassian]

        Issue Links

          Activity

            People

              Unassigned Unassigned
              dave@atlassian.com dave (Inactive)
              Votes:
              22 Vote for this issue
              Watchers:
              34 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: