Handle create tablespace ddl
Folks,
Can we re-write the create tablespace ddl via trigger or some means so as to correct the datafile location issues when non-dba user issues create tablespace statement?
Little Background of the issue
Oracle Inform Application users sometimes create tablespaces by means of running .cmd script which has inbuilt file location as c:\ or d:\. However database exists in Unix Env.
Eventually this fills $ORACLE_HOME/dbs location.
We would like to catch these sql staements, rephrase it before it gets executed.
This possible in Logical Standby, not sure about standalone database which is our case