Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: A PL/SQL parameter puzzle

Re: A PL/SQL parameter puzzle

From: Craig Warman <crwarman_at_yahoo.com>
Date: Thu, 18 Nov 2004 09:40:32 -0500
Message-ID: <BDC21E90.A1FB%crwarman@yahoo.com>


On 11/17/04 1:23 PM, in article cndgjl$231$1_at_news4.zwoll1.ov.home.nl, "Frank van Bortel" <fvanbortel_at_netscape.net> wrote:

> KurtisK wrote:

>> We didn't use Migration Workbench. You are right in that the OMWB can't
>> convert stored procs. It can help in transferring data and table
>> structures. All the code did needed rewritten in Oracle PL/SQL, DML and
>> DDL. We had to resolve all the issues you mentioned with temp tables,
>> dates, implementing RI, etc.
>>
> 
> Craig did.
> OMWB *can* convert stored procedures - it just is TSQL,
> converted to PL/SQL...

Yep, I'm using OMWB on this project, but only for its capability to let me know where the problems will occur (ie. It has a reporting mechanism that lets you know where object naming issues, datatypes, etc need attention during the conversion process). It's actually a decent enough sort of tool.

I'm fortunate though in that the app I'm migrating has a facility for creating its own objects - so, where there were issues, we are just making changes in those sections of the app (both where the objects are created and where they're used). Since there's only one stored proc in the app - which generates unique IDs - I don't need OMWB for its conversion.

Craig Received on Thu Nov 18 2004 - 08:40:32 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US