.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  

On 8/23/05, Wolfgang Breitling <breitliw@(protected)> wrote:
>
> Looks to me like it's firing:
>
>
Hi Wolfgang,

Yes, you are correct of course.

I misrembered some testing I had done with these a couple months ago.

Logon triggers do indeed fire if you have the DBA role, or more specifically
the ADMINSTER DATABASE TRIGGER privilege.

The difference is that users with this privilege cannot be prevented from
logging into the database by raising and error in the trigger. All other
users may be prevented from logging on.

See MetaLink note 265012.1

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

<br><div><span class="gmail_quote">On 8/23/05, <b class="gmail_sendername"
>Wolfgang Breitling</b> &lt;<a href="mailto:breitliw@(protected)">breitliw
@(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;">
Looks to me like it's firing:<br><br></blockquote></div><br>
Hi Wolfgang,<br>
<br>
Yes, you are correct of course.<br>
<br>
I misrembered some testing I had done with these a couple months ago.<br>
<br>
Logon triggers do indeed fire if you have the DBA role, or more specifically<br>
the ADMINSTER DATABASE TRIGGER privilege.<br>
<br>
The difference is that users with this privilege cannot be prevented from <br>
logging into the database by raising and error in the trigger.&nbsp; All other
<br>
users may be prevented from logging on.<br>
<br>
See MetaLink note <font face="helvetica">265012.1</font><br>
<br>
-- <br>Jared Still<br>Certifiable Oracle DBA and Part Time Perl Evangelist<br>
<br>