Re: Upgradeing to 8.1.7 what about designer/repository
Date: Wed, 2 May 2001 21:47:35 +0000 (UTC)
Message-ID: <9cpv9n$jkr$1_at_qn-195-66-31-144.quicknet.nl>
On Wed, 25 Apr 2001 18:04:22 GMT, Jodie Ray Kelley <jodie.r.kelley_at_boeing.com> wrote
in <3AE711A6.B2DED82D_at_boeing.com>:
> You will need to upgrade to Designer 6i. Then you will need to create a
> new repository in an 8.1.7 database, and use the migrate function inside
> designer to move data from your 8.1.6 repository. I strongly encourage
> you to read the directions carefully. The process works very well, but
> only if you follow the directions.
The incompatibility issues with the 8.1.7 database are caused by a bug in the PL/SQL engine that is triggered by a package in the Designer repository. Designer 6i Release 2 works around this bug, using a different syntax to accomplish the same result (OR instead of IN, in a WHERE clause). I have tried installing a Designer 2.1.2 repository in a 8.1.7 database. This triggers the same bug. Manually applying the workaround to said package seems to fix it, but I wouldn't rely on it.
Remco
-- qn-195-66-31-144: 23:40:02 up 1 day, 1:26, 5 users, load average: 1.79, 1.58, 1.44Received on Wed May 02 2001 - 23:47:35 CEST