Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: DDL for triggers.
joel garry schrieb:
> joel garry wrote:
>> Maxim Demenko wrote: >>> joel garry schrieb: >>> >>> I don't have 9i actually to test, but i doubt, it would behave >>> differently. Here is for 10gR2 >>> >>> SQL> select * from v$version >>> 2 / >>> >>> BANNER >>> -------------------------------------------------------------------------------- >>> Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - Prod >>> PL/SQL Release 10.2.0.2.0 - Production >>> CORE 10.2.0.2.0 Production >>> TNS for Linux: Version 10.2.0.2.0 - Production >>> NLSRTL Version 10.2.0.2.0 - Production >>> >>> SQL> set long 1000000 pages 0 >>> SQL> select dbms_metadata.get_ddl('TRIGGER','FILES_TRG') from dual; >>> >> Thank you Maxim, that is indeed what I was missing. >> >> D'Oh! >>
>>From dbms_metadata, it's coming out like this:
Joel, i've never seen the behaviour like you described, but my guess
would be - sqlplus settings cause this line breaking. If you have
already solved this, maybe it is not worth the time to investigate
further, but just in case, i would try
1) to get source from the export (rows=n triggers=y) file with simple
awk formatting ( Note 29765.1 ) - i used this often before dbms_metadata
and never had any sort of issues, to see the actual source in the
database ( for one particular table and trigger "strings exp.dmp" will
be good enough as well i guess)
2) select the clob with all default settings in sqlplus ( i.e. rename
your login.sql) and only set long for appropriate size ( set long 10000)
to see , whether it is one of your sqlplus settings which produces the
newlines.
A very obscure guess - it depends on your terminal setting, so maybe it make sense to try with a dos client and get the results in remote sqlplus.
Best regards
Maxim Received on Fri Oct 27 2006 - 02:43:52 CDT