We have a last minute update from client that DBA user will not be provided as well as Client DBA also will not be given access to both Rules and Data schema. In this scenario, what can be a possible workaround?
In case we generate DDL scripts, do we require DBA user which require access to both Rules and Data schema or only a schema user can execute those?
Are there any other risks involved?
Please suggest as we are working on the upgrade already.
If you could update us on the query we had, whether split schema configuration is feasible in a scenario where as per organization's policy one schema cannot have any access on the other schema, not even read only.
Hello Dhevendra, as is mentioned in the platform guide - the user will need access to Create/Update/Drop tables, hence does that mean we require DDL+DML access across schema here? Only DML access across schema will not be sufficient. Please confirm.
Deployment user requires the DDL+DML access however the baseuser which is generally data schema user requires the DDL operations along with execution of stored procedures and functions. Refer to BaseUser privileges section.
After running the scanner utility we found few issues.
Below mentioned access groups are missing. Will it impact anything in upgrade? If there is impact what is the suggested steps we have to take care before starting upgrade.
Also there are custom views,procedures,synonyms available in the V6.1 DB. So I hope those needs to be deleted before running the upgrade scripts and need to recreate once upgrade is done. Please confirm.