I think he already said its legacy software. I dont know that you can handle longs in a trigger though. Is the value even accessible to the trigger? On 9/21/07, Powell, Mark D <mark.powell@xxxxxxx> wrote: > > If the data value is less than 4K why are you using a obsolete since > version 8.0 datatype of long when a varchar2(4000) would work? > Otherwise use a CLOB. > > One of the basic design rules is to store data in the most appropriate > type column. Then you would not have this issue. > > -- Mark D Powell -- > Phone (313) 592-5148 > > > -----Original Message----- > From: oracle-l-bounce@xxxxxxxxxxxxx > [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of dba1 mcc > Sent: Friday, September 21, 2007 10:41 AM > To: oracle-l@xxxxxxxxxxxxx > Subject: How to process "long" in trigger? > > we have table with column type "long" in it(actually this "long" field > store ASCII text and less than 4000 characters). The ORACLE database is > 9ir2. We tried to create "logical standby database", but "logical > stansdby database" does NOT update "long" field. > > The way I tried to do is use "trigger" when update "long" table, insert > new data (since this "long" store ASCII data) into another table with > "varchar2". The problem I got is "trigger" can NOT handle "long". > > Anyone has way to handle this? > > Thanks. > > > > > > ________________________________________________________________________ > ____________ > Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: > mail, news, photos & more. > http://mobile.yahoo.com/go?refer=1GNXIC > -- > http://www.freelists.org/webpage/oracle-l > > > -- > http://www.freelists.org/webpage/oracle-l > > > -- Andrew W. Kerber 'If at first you dont succeed, dont take up skydiving.'