Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Migration from 9i to 10g.

3 views
Skip to first unread message

Serguei.G...@cibc.ca

unread,
Aug 21, 2007, 1:43:41 PM8/21/07
to
Dear Experts,
Our organization is moving from Oracle 9i to 10g. I know about some
technical issues during migration of the database itself, but what
about the user application level (SQL/PL scripts, triggers, sequences,
indexes and so on)? Is there something Experts could recommend to do
or to avoid? Are there any user related problems in the 10g
environment?
Regards,
Serguei.

DA Morgan

unread,
Aug 21, 2007, 2:28:18 PM8/21/07
to

Strip all 9i hints from all code.

Dump all cursor loops and replace with array processing using BULK
COLLECT and FORALL.

Turn on warnings before compiling any code and follow up on all
warning messages. To do this look at this page:
http://www.psoug.org/reference/dbms_warning.html
The demos will show you how it works.

Note: 11g contains new warnings not present in 10g so some demos will
not work in 10g. PLW-06002 is one that works in both 10g and 11g.
--
Daniel A. Morgan
University of Washington
damo...@x.washington.edu (replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org

Jan Krueger

unread,
Aug 22, 2007, 2:26:29 PM8/22/07
to
DA Morgan wrote:
> Serguei.G...@cibc.ca wrote:
>> Dear Experts,
>> Our organization is moving from Oracle 9i to 10g. I know about some
>> technical issues during migration of the database itself, but what
>> about the user application level (SQL/PL scripts, triggers, sequences,
>> indexes and so on)? Is there something Experts could recommend to do
>> or to avoid? Are there any user related problems in the 10g
>> environment?
>> Regards,
>> Serguei.
>
> Strip all 9i hints from all code.
>
> Dump all cursor loops and replace with array processing using BULK
> COLLECT and FORALL.
You should have done so already in 9i. And if you didn't have a
performance issue in 9i there is no need to do it in 10g.

> Turn on warnings before compiling any code and follow up on all
> warning messages. To do this look at this page:
> http://www.psoug.org/reference/dbms_warning.html
> The demos will show you how it works.

Interesting idea.

Also I would recommend to perform a test upgrade with a duplicated
environment and perform a full regression test.

Jan

0 new messages