[
http://www.jahia.net/jira/browse/DOCU-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37364#action_37364
]
Damien Saulnier commented on DOCU-56:
-------------------------------------
For Jahia 6.0:
CONNECT
ALTER ANY INDEX
ALTER ANY SEQUENCE
ALTER ANY TABLE
ALTER ANY TRIGGER
CREATE ANY INDEX
CREATE ANY SEQUENCE
CREATE ANY TABLE
CREATE ANY TRIGGER
DROP ANY INDEX
DROP ANY SEQUENCE
DROP ANY TABLE
DROP ANY TRIGGER
UNLIMITED TABLESPACE
> Script migration from 5.0.x to 5.0.x+ under oracle
> --------------------------------------------------
>
> Key: DOCU-56
> URL: http://www.jahia.net/jira/browse/DOCU-56
> Project: Jahia Documentation
> Issue Type: Task
> Components: Migration Guide
> Reporter: Damien Saulnier
> Priority: Major
> Fix For: DOC 5.0 SP5
>
>
> To perform a script migration, we connect a newer version of Jahia to the
> database. This makes hibernate update the schema at Jahia startup, before we
> run update scripts. But with Oracle, we can encounter some problems depending
> from Oracle user granted privileges.
> the following privileges are required:
> CONNECT
> ALTER ANY INDEX
> ALTER ANY TABLE
> CREATE ANY INDEX
> CREATE ANY TABLE
> DROP ANY INDEX
> DROP ANY TABLE
> UNLIMITED TABLESPACE
> but user must not have DBA role.
> See JAHIA-2416 for potential consequences
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
jira_list@jahia.org
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
