User_source or DBA_source for procedures and USER_TRIGGERS or DBA_TRIGGERS for
triggers.
Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-Original Message-
Sent: Friday, September 05, 2003 11:35 AM
To: Multiple recipients of list ORACLE-L
third party tools?
Hi List,
Could you
set long 32656
col trigger_body for a80 word
select trigger_body from dba_triggers where owner='xxx' and trigger_name =
'yyy';
At 07:34 AM 9/5/2003 -0800, you wrote:
Hi List,
Could you please help me to get the source code of
the trigger without using any third party tools?
Thanks in advance,
You can use view all_triggers or user_triggers to get the entire text. trigger_body has the trigger text. triggering_event, trigger_type , REFERENCING_NAMES etc have other details. You can also use enterprise manager to get it. One trick in enterprise manager is to add some spaces somewhere (a non
Well, the idea of extracting it from user_triggers or dba_triggers is a
little far fetched
and unnatural, but should work.
--
Mladen Gogala
Oracle DBA
-Original Message-
Oracle DBA
Sent: Friday, September 05, 2003 11:35 AM
To: Multiple recipients of list ORACLE-L
party tools?
Hi
Why is it far fetched and unnatural ? In my view that is the only way to
be sure to get the correct source.
At 08:09 AM 9/5/2003 -0800, you wrote:
Well, the idea of extracting it from user_triggers or dba_triggers is a
little far fetched
and unnatural, but should work.
Wolfgang Breitling
Select from DBA/ALL/USER_SOURCE; if the source code looks
like a bunch of garbage, then it means the source code has
been wrapped, which is Oracle's facility of obfuscate it
so that you can't read it.
-Original Message-
Sent: Friday, September 05, 2003 11:35 AM
To: Multiple recipients
Just kidding.
--
Mladen Gogala
Oracle DBA
-Original Message-
Wolfgang Breitling
Sent: Friday, September 05, 2003 12:34 PM
To: Multiple recipients of list ORACLE-L
Why is it far fetched and unnatural ? In my view that is the only way to
be sure to get the correct source.
At 08:09
You can ofcourse use enterprise manager. You would have to get the body and other things like triggering event etc.
To use the "Show SQL"option : one trick to use is a space some place (basically non-change)and hit "Show SQL". That should give you the whole trigger sql. Good luck.
* Jared : I
Title: Message
Or,
you can set event 10046, level 12 and look into the trace file. All SQL
statements in the trigger should be in there,
which
should give you a pretty good idea about what's in the trigger
itself.
Or,
you could do a systemdump level 10 and extract the trigger text from
