[
https://issues.apache.org/jira/browse/OOZIE-2143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325172#comment-14325172
]
Robert Kanter commented on OOZIE-2143:
--------------------------------------
We saw that if a table with the Oozie schema already exists in another table
owned by another user, the mapping tool wouldn't create it; so the OozieDBCLI
tool was missing a lot of SQL statements. The workaround was to restrict the
permissions of the second Oozie server's database user to not be able to see
the other table, so the mapping tool wouldn't get confused (we previously
normally just grant all privileges).
> Making two Oozie schemas in an Oracle Database does not behave correctly
> ------------------------------------------------------------------------
>
> Key: OOZIE-2143
> URL: https://issues.apache.org/jira/browse/OOZIE-2143
> Project: Oozie
> Issue Type: Bug
> Reporter: Robert Kanter
>
> If you have an Oracle Database and try to create a second Oozie schema in it
> (for a second separate Oozie server), it will not work correctly unless you
> have some very specific permissions set. This is due to a bug in OpenJPA's
> mapping tool, which has been open for many years with little-to-no activity.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
