SQL & PL/SQL

Hi,

in my oracle 9.2 db resides two schemas. The "Intern" schema represents the core functionalities and the "Extern" schema handles customer specific extensions.

We track any ddl changes into a table with a schema trigger but we are facing the problem that the extern schema is used by our internal staff and customer staff. We track object, sql, machine, osuser, db user (all infos we can get).

Our support do need to distinguish ddl changes caused by internal staff and customer staff in the "Extern" schema. We can't always distinguish between this two groups (same os-accounts can be used by the different staffs).

To achieve this goal one suggestion is to set up another schema "CUSTOMER_EXTERN". This user should not create objects in his own schema, but he is allowed to create and modify objects in "Extern". He defintitly should not create or modify objects in the "Intern" schema, to which he only should have read access.

As far as i understand the handling of access rights the "CUSTOMER_EXTERN" user has to be granted the "CREATE ANY TABLE" privilege in order to create tables in an other schemas. I can't control which schema can be accessed, i can only set up quotas on different tablespaces.

Can i restrict the object creation of a specific user (only used to track the change info) to another specific schema?

Are there any possible alternatives (we don't want to use "CUSTOMER_EXTERN" as a "real" third schema, we only need the user as a dummy to distinguish between different groups).

Thanks in advance

Matthias