Re: SQL - PL/SQL Question. Please Help!!

It still sounds like you would benefit from using the view scenario I discussed. It would allow you to extract the data in the way that you need yet you would be able to keep the nulls in the Oracle tables as you should.

If you really must modify the data in the tables, then use pl/sql and perform commits every hundred rows or so. If you working strictly in sqlplus, then enter SET AUTOCOMMIT ON before you start the update statement. Or, if you know that this will not be a reoccuring task, create a large temporary tablespace and then create a large rollback segment in the tablespace and before you start the transaction enter SET TRANSACTION USE ROLLBACK SEGMENT XXX; where xxx is the name of your special rollback segment. When the operation is ultimately complete, take the rollback segment off-line, drop it, and then drop the special tablespace.

Ken

"George Gifford

> I guess that an explanation for my need to do this is in order.
>
> Before converting our data over to Oracle my company was running an old
> legacy system utilizing DataFlex Code utilizing data stored in DataFlex
> Tables.
>
> We were able to utilize a 3rd party utility that allows us to retain our
> 1000+ DataFlex code files and use data converted over to Oracle. The
> DataFlex language does not recognize Null values. This is a major problem
> now with our code as the 3rd party utility that converted our data over to
> Oracle converted all empty fields not used in any index as Null. There is
> nothing in the DataFlex code language that will allow us to recognize or
> substitue a Null value; therefore, the solution for us right now is to
> convert ALL Null values (VarChar2, Date, and Number) over to Non-Null values
> such as ' ' for VarChar2 Null values, 0 for Number Null values, and
> TO_DATE("01-01-0001","MM-DD-YYYY") for Date Null values.
>
>
Received on Thu Jun 17 1999 - 14:02:56 CDT