.ora-code.com

Links
Home
Oracle DBA Forum
Frequent Oracle Errors
TNS:could not resolve the connect identifier specified
Backtrace message unwound by exceptions
invalid identifier
PL/SQL compilation error
internal error
missing expression
table or view does not exist
end-of-file on communication channel
TNS:listener unknown in connect descriptor
insufficient privileges
PL/SQL: numeric or value error string
TNS:protocol adapter error
ORACLE not available
target host or object does not exist
invalid number
unable to allocate string bytes of shared memory
resource busy and acquire with NOWAIT specified
error occurred at recursive SQL level string
ORACLE initialization or shutdown in progress
archiver error. Connect internal only, until freed
snapshot too old
unable to extend temp segment by string in tablespace
Credential retrieval failed
missing or invalid option
invalid username/password; logon denied
unable to create INITIAL extent for segment
out of process memory when trying to allocate string bytes
shared memory realm does not exist
cannot insert NULL
TNS:unable to connect to destination
remote database not found'>ora-02019
exception encountered: core dump
inconsistent datatypes
no data found
TNS:operation timed out
PL/SQL: could not find program
existing state of packages has been discarded
maximum number of processes exceeded
error signaled in parallel query server
ORACLE instance terminated. Disconnection forced
TNS:packet writer failure
see ORA-12699
missing right parenthesis
name is already used by an existing object
cannot identify/lock data file
invalid file operation
quoted string not properly terminated
Debug DDL trigger

Debug DDL trigger

2005-08-24       - By Jared Still
Reply:     <<     11     12     13     14     15     16     17  

Yes, it is true, at least in the context I meant it in.

I should have been more specific.

Try using raise_application_error, or any other error to
prevent an account from logging in.

If a user has the ADMINISTER DATABASE TRIGGER privilege, you cannot
use a trigger to prevent him from logging in.

You might take a look a look at the MetaLink note referenced earlier.

Jared

On 8/24/05, rjamya <rjamya@(protected)> wrote:
>
> Not true, see below for an example on 9204
>
> SQL> get t1.sql
> 1 conn t1/t1
> 2 create table t1.some_tbl tablespace cons
> 3 as select * from dba_objects where rownum < 100
>
...

--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist

Yes, it is true, at least in the context I meant it in.<br>
<br>
I should have been more specific.<br>
<br>
Try using raise_application_error, or any other error to <br>
prevent an account from logging in.<br>
<br>
If a user has the ADMINISTER DATABASE TRIGGER privilege, you cannot<br>
use a trigger to prevent him from logging in.<br>
<br>
You might take a look a look at the MetaLink note referenced earlier.<br>
<br>
Jared<br>
<br><div><span class="gmail_quote">On 8/24/05, <b class="gmail_sendername"
>rjamya</b> &lt;<a href="mailto:rjamya@(protected)">rjamya@(protected)</a>&gt; wrote
:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204,
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Not true, see below for an example on 9204<br>
<br>
SQL&gt; get t1.sql<br>
&nbsp; 1&nbsp; conn t1/t1<br>
&nbsp; 2&nbsp; create table t1.some_tbl tablespace cons<br>
&nbsp; 3&nbsp; as select * from dba_objects where rownum &lt; 100<br><
/blockquote></div>...<br>
<br>-- <br>Jared Still<br>Certifiable Oracle DBA and Part Time Perl Evangelist
<br><br>