Re: Truncate with Toad and Rowid

BG wrote:

> Hello.
>
> I am having a problem with what looks like data corruption either via
> poor programming or some other cause.
>
> (1) Is it possible after a truncate and then doing inserts to have the
> a ghost image of truncated data corrupt your newly inserted data.
>
> (a) for example assume I have a table that looks like:
> COLa | COLb
> -----------
> 123 | abc
> 567 | def
> 890 | ghi
>
> (b) then do a truncate on the table
> (c) then do an insert in the table
> with "insert into table (cola, colb) values (242, ppp)
> or with "insert into table (cola, colb) values (, ppp)
>
> and then when doing a select seeing some of the old table data
> in the output. (in other words getting some "ghost" data)
>
> (2) Can someone tell me if a commit is needed after a truncate?
>
> (3) difference between "resuse space" and free "space"
>
> Thank you
> bg

A truncate is DDL and never requires a user entered commit.

The fact that you would ask this question makes me wonder about a number of things but if things are as you say they are you have something very corrupted. Drop the table, recreate it from scratch, and see if the problem persists.

What is the origin of your question about what I presume is REUSE SPACE?

In the future, when posting, include the version and edition of Oracle.

Daniel Morgan Received on Mon Jan 20 2003 - 20:33:44 CST