Hi Mark,
 
Thanks for the feedback.  On your suggestion I mailed my report to
support.  I would have done so in the first instance but I wasn't that
confident that it was FME.  It wouldn't be the first time I'd done
something daft!
 
Regards
 
Richard Wilkinson 
Systems Analyst 
Resources - ICT Services 
Leicestershire County Council 
0116 2657709 
[EMAIL PROTECTED] 

        -----Original Message-----
        From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf
Of mark2atsafe
        Sent: 07 May 2007 23:01
        To: [email protected]
        Subject: [fme] Re: Bug Report - Writing VARCHAR2 to Oracle DB
        
        

        Hi Richard,
        I didn't even need to file a PR over this - your email was
passed on
        to one of our developers who reproduced the problem and made a
fix.
        I'll let you know when it's available, but it will definitely be
in
        the final release of FME2007.
        
        Regards,
        
        Mark
        
        Mark Ireland, Senior Product Specialist
        Safe Software Inc. Surrey, BC, CANADA
        [EMAIL PROTECTED] <mailto:support%40safe.com>
http://www.safe.com <http://www.safe.com> 
        Solutions for Spatial Data Translation, Distribution and Access
        
        --- In [email protected] <mailto:fme%40yahoogroups.com> ,
"Richard Wilkinson" <[EMAIL PROTECTED]> wrote:
        >
        > Hi,
        > 
        > I have just encountered a problem with what was a working
transform that
        > has stopped working after I downloaded the latest build of
FME. Seems
        > like a bug to me but I would appreciate any comments from
others who may
        > have also seen this.
        > 
        > The error is `ORA-01461: can bind a LONG value only for insert
into a
        > LONG column'
        > 
        > Occurrs when writing a varchar2 field in oracle database if
and only if
        > the length exceeds 3998 bytes.
        > 
        > <<Varchar2Test.log>> <<Varchar2Test.fmw>> 
        > 
        > The attached transform, Varchar2Test.fmw, is an extract from
my live
        > production environment to illustrate the problem.
        > FME 2007 build 4333 is OK
        > FME 2007 build 4364 fails with error above.
        > 
        > Regards
        > 
        > Richard Wilkinson
        > Systems Analyst
        > Resources - ICT Services
        > Leicestershire County Council
        > 0116 2657709
        > [EMAIL PROTECTED]
        > 
        > 
        > __________________________________________________________
        > Leicestershire County Council - rated a 'four-star' council by
the
        Audit Commission
        > __________________________________________________________
        > 
        > 
        > This e-mail and any files transmitted with it are
confidential. If
        you are not the intended recipient, any reading, printing,
storage,
        disclosure, copying or any other action taken in respect of this
        e-mail is prohibited and may be unlawful. If you are not the
intended
        recipient, please notify the sender immediately by using the
reply
        function and then permanently delete what you have received.
        > 
        > Incoming and outgoing e-mail messages are routinely monitored
for
        compliance with Leicestershire County Council's policy on the
use of
        electronic communications. The contents of e-mails may have to
be
        disclosed to a request under the Data Protection Act 1998 and
the
        Freedom of Information Act 2000.
        > 
        > The views expressed by the author may not necessarily reflect
the
        views or policies of the Leicestershire County Council.
        > 
        > Attachments to e-mail messages may contain viruses that may
damage
        your system. Whilst Leicestershire County Council has taken
every
        reasonable precaution to minimise this risk, we cannot accept
any
        liability for any damage which you sustain as a result of these
        factors. You are advised to carry out your own virus checks
before
        opening any attachment.
        >
        
        

         

Reply via email to