|
Suggest you read notes 482, 410, 291, and especially 302. 302
describes what PL/SQL MIGHT be.
>> What are the problems if a customer want
>> to migrate from ORACLE V5 to V6 ?
As far as I know, there are no significant problems with this.
The customer performs an export in V5 and an import to V6. There
are some different keywords in V6 which they will have to work through.
For example, storage areas are named tablespaces in V6 but were
named partitions in V5. So, they'll have to look at command files
which contain this DDL statements. There are new placement options.
There should not be any problem with the code. My customer relinked
and away they went.
>> This customer does not want to rewrite
>> its code to upgrade it to PL/SQL.
Tell your customer to get a big bottle of wine and relax, PL/SQL is
very much an unknown at this point. I have a customer that always
has the latest release of V6 installed and the PL/SQL is still in
Beta form. Noone really knows what PL/SQL is, how much performance
will be gained from using it, etc. My theory is that PL/SQL is
designed to reduce parsing time in the intrepretive environments
such SQL*forms or dynamic SQL. Also, I believe PL/SQL is designed
to eliminate the many problems with their pre-compilers.
Your customer will gain performance from the row level locking but
caution him/her carefully about cpu utilization, it could easily
increase by 20-30% when running the same schema, programs, and metadata
under V6 !!
Jean Michel Craye.
SWAS - France
|
|
In the recent DECtp DU:IT training, there was an hour-long session
regarding Oracle, including a slide presentation (although I'm not
sure whether or not it is generally available.)
As one of the handouts for this session, we were able to get a
copy of <ahem, ahem> some information that describes exactly what
must be done in order to convert from 5 to 6. The information is
from <ahem, ahem> an indisputable source.
Perhaps you could contact someone in your area who attended this
session? If not, perhaps I could help...
Bob
|