Re: Problem with Truncate Table

On Mar 1, 8:11 am, "BGT" <bgt0..._at_optonline.net> wrote:
> On Mar 1, 7:46 am, "gazzag" <gar..._at_jamms.org> wrote:
>
> > On 1 Mar, 11:53, "BGT" <bgt0..._at_optonline.net> wrote:
>
> > > I have since determined that this only applies to approx 4 tables out
> > > of 150.
>
> > Could you DESCRIBE each of the four tables affected and post the
> > output here, please?
>
> > HTH
>
> > -g
>
> Sure,
>
> Needles to say I have the same structure running in 10 + databases
> with no troubles except this one..
>
> SQL> desc azcms_tst.disorder_archive;
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> LABNO NOT NULL CHAR(11)
> REPTCODE CHAR(5)
> MNEMONIC CHAR(6)
> STATUS CHAR(1)
> LASTMOD DATE
> USER_ID NUMBER(3)
>
> SQL> desc azcms_tst.disorder_master;
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> LABNO NOT NULL CHAR(11)
> REPTCODE CHAR(5)
> MNEMONIC CHAR(6)
> STATUS CHAR(1)
> LASTMOD DATE
> USER_ID NUMBER(3)
>
> SQL> desc azcms_tst.disorder_avg_archive;
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> LABNO NOT NULL CHAR(11)
> REPTCODE CHAR(5)
> VALUE NUMBER(7,2)
> TESTCODE CHAR(5)
> LASTMOD DATE
> USER_ID NUMBER(3)
>
> SQL> desc azcms_tst.disorder_avg_master;
> Name Null? Type
> ----------------------------------------- --------
> ----------------------------
> LABNO NOT NULL CHAR(11)
> REPTCODE CHAR(5)
> VALUE NUMBER(7,2)
> TESTCODE CHAR(5)
> LASTMOD DATE
> USER_ID NUMBER(3)
>
> SQL> spool off

You might want to open a Tar .. or at least review Bug 3449126 The symptoms match that bug quite well.

Anurag Received on Thu Mar 01 2007 - 09:04:18 CST