APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Understanding schema and schema password in Oracle APEX 18c XE

M.EmmanuelDec 22 2018 — edited Dec 23 2018

When you install Oracle APEX 18.2, and before creating a new application you create an SCHEMA.

A password is given to that schema.

Then you create an admin user and you can create other users.

My understanding is that the SCHEMA is an actual database user which can be used to log into the database.

If I connect as SYS to the PDB where APEX is installed with SQL Developer I can see in "Other Users" my schema user.

However, when I try to connect to database using it it does not work:

So this works fine:

sqlplus sys/password@localhost:1521/xepdb1 as sysdba

But this (given that my schema is scott and the password is tiger) does not work:

sqlplus scott/tiger@localhost:1521/xepdb1

ERROR:

ORA-01017: invalid username/password; logon denied

As the schema user is not working, I start to think that I misunderstood what a schema is and what shall be used for.

I have the following questions:

1. Shall the schema created by APEX be available as a database user?

2. Shall I use it when I want to access externaly to APEX (for example, another external progra which needs to interact with APEX application tables). If so, how can I check that the user/schema can be accessed? Could it be a permissions issue?

3. If not, why I am providing a schema password, and how shall I achieve point 2 (accessing the database externaly to interact with APEX application tables)

Thanks

Paulzip

You only have to worry about objects that reference the invalid objects (directly or through other dependencies), not objects that the invalid objects reference (caveated that they are not referenced by another invalid object).

E.g. Dropping PLAP/TEMP_DIS_CONSTR/PROCEDURE, won't affect SYS/ALL_CONS_COLUMNS/VIEW

1 person found this helpful

BEDE

That depends...

Some of those invalid packages/procedures/functions/views may need to have their code changed so that they may be used later on. So, I don't think it is the case to rush into such spring cleaning. First use dbms_utility.compile_schema(x_schema,false) to see what can recompile, then send all the developers you know to be working on that database a list of the invalid objects, eventually including also the errors, with the warning that, if in within two weeks they won't fix them, then they will be dropped.

Yet, if your concern is space, tables are those that take most of the space.

1 person found this helpful

4089142

Thanks so much! That's exactly what I did. First I tried to see what invalid objects I could recompile (except I used @utlrp.sql). Then, I sent all the developers a list of the invalid objects with each error included so that they can look through and fix the code if need be.

4089142

Thanks for the clear and concise answer Paulzip! This is exactly what I needed to know!

APEX

Understanding schema and schema password in Oracle APEX 18c XE

Comments

Post Details