CREATE TABLE for another OWNER/SCHEMA and in another TABLESPACE?

Question

I am logged in a SYSTEM user. Now I want to create a table aaa. The owner of this table should not be SYSTEM but user KARL. and the TABLESPACE should not be SYSTEM but the (existing) TABLESPACE tttt.
As far as I know I can achieve this by issuing the following command:
CREATE TABLE KARL.aaa ( a INTEGER, .......) TABLESPACE tttt;
Regarding the TABLESPACE parameter I am not sure. Is it possible to allocate a TABLE for User Karl in a TABLESPACE which is not assigned to him?
Furthermore I have an additional problem.
I have a script with hundreds of CREATE TABLE + ALTER TABLE + CREATE INDEX DDL statements.
All of them are not prepended with Schema/Owner and an TABLESPACE clause.
Can I put somehow one single instruction at the top of the script which telles Oracle
to use
- OWNER Karl as Schema/Owner for all subsequent DDL stements
- TABLESPACE tttt as TABLESPACE for all subsequent DDL stements
In MYsql there is a "use <database>" statement. Is there soemthing similar for Oracle?
Thank you
Peter

Answer 1

Yes... you can do that. Take for example a user A who has a secret password that you don't wish to give out... like an application schema. User B needs to make tables/objects in schema A and you want to track what user B is doing. First setup Oracles Fine Grained Auditing and then grant "connect through" from user A to user B as follows:
SQL> create user b identified by abc123
  2    quota unlimited on users;
User created.
SQL> grant create session to b;
SQL> create user a identified by abc123
  2    quota unlimited on users;
User created.
SQL> grant create table
  2      , create session
  3     to a;
Grant succeeded.
SQL> alter user a grant connect through b;
User altered.
SQL> connect b[a]/abc123@a486
Connected.
SQL> show user
USER is "A"
SQL> create table a.my_proxy_table
  2  ( c1 number
  3  , c2 varchar2(50)
  4  , c3 date
  5  );
Table created.-----
See that I connected using the "username[proxyuser]" syntax. Also notice that user B is by proxy user A, illustrated by my "show user" command. The connect through can be granted/revoked as needed without divulging A's password to B. In addition, your audit tables or xml logs will track the fact that user B created table a.my_proxy_table.
Hope this helps,
John