Hi all,

The Outsystems instance at the company were I work was setup using an oracle database. Currently we are trying to ensure that data belonging to the platform and the data belonging to our business applications. 

For its important that the tables belonging to the business applications are separated from the platform tables, but is also equally important that data of the different projects is not mixed. So the desired is that  every new projects  has its own schema that can be maintained independently. 

Our instance is configured to support multiple schemas.

Currently we are struggling to create new schemas using the information provided on the link below.

We followed all the steps the on the link above:
  a) filling up schema details
  b) download creation script
  c) execute the creation script
  d) test the configuration

However whenever we try the step d) to test the configurations we get the following error.

Database Schema connection failed with the following error. Owner User needs to be the schema owner: ORA-01017 Invalid username/password: logon denied

We are not sure what is causing this error, however we have some questions regarding the instruction on link above.

The link states that: 

What does it mean "execute as a DBA"? can it be any user with admin permissions, or should be an specific user?  

The password entered on the form is the password on the user/schema being created or is it the password of the user that must run the script.

Is it anything else that might cause this error?

Thanks in advance


Hi Ferox Neto,

As the error states permission are needed to access DB. Try to approach your DBA or DB team to get access.


Marco Arede wrote:

Hi Ferox Neto,

As the error states permission are needed to access DB. Try to approach your DBA or DB team to get access.


Hi Marco,

Thanks for your reply!
I'm already in touch with the DB team, and they also mentioned the lack of permissions; however what is not clear is which user is lacking the permissions.

Because in theory as its stated on the tutorial, the script auto-generated scrip sets all the required permissions.

The other confusing part is that the error does not occur when we try to execute the script.
The error occurs after the execution of the script when we try to test it, and we are not sure which user is used by the platform to run this test.

Based on the print below i assume its the platform user: hubruntime. But being a platform user, if its set up correctly it should not need any elevated permissions; or it if its the case, those permissions should be set when the auto-generated script is executed as suggested by the tutorial.


Hi all,

We managed to have some progress on the issue but still cannot test the configurations successfully due to issues with privileges.

Whenever we test the configuration we get the following error: 

Database Schema connection test failed with the following error: Failed to grant read and write permissions on a table 'OSSYS_TESTTBL_1' to runtime user 'hubruntime': ORA-01950: no privileges on tablespace 'OSDAT_DEL_ADMIN'

If we test the configuration again the name of the name changes form OSSYS_TESTTBL_1   to OSSYS_TESTTBL_2 and every time we test the number associated to the name of the table is incremented

This happens if we just keeping on testing the configurations, of if before we test the configuration we grant permissions to the user hubruntime on the table displayed on the error message. 

Note that is not possible to grant permissions on table_name_n+1 (ex OSSYS_TESTTBL_15)   because the table in this case does not exist yet.

Does anyone have an idea of why this is happening? 

Hi Fernando,

This seems to be a configuration problem related to the permissions granted to the runtime user on the new schema.

Regarding the message mentioning the lack of the permissions not being clear, that is something that our engineering team has already identified as a point of improvement in the product.

That table (OSSYS_TESTTBL_X) is a table that is created during the process of testing the configuration, where the platform tries to execute some operations in the new schema (like creating tables and modify them). The number being showed, X, is related to the number of test configuration actions done.