6.4 to OI 2.0 UDT Problems. Anyone else?

6.4 to OI 2.0 UDT Problems. Anyone else?

Post by kwalt.. » Fri, 09 Oct 1998 04:00:00



I recently migrated from 6.4 to OI 2.0 and I am having some rather serious problems
with our user defined datatypes, which were created under 6.4 release. They UDTs
have worked well through all 6.4 releases with only an iilink required at upgrade
time.

A number of changes have been made to the UDT specifications since 6.4 and we had
to patch up our source code just get them linked in to the OI 2.0 iimerge. Our
problems are related to the use of functions and comparisons on and with the UDTs.

I had a very difficult time actually getting the data from 6.4 to Open Ingres.
Unloaddb and copydb were useless because of lingering problems with the binary copy
program and UDTs. I ultimately had to use Ingres Star to move the data from 6.4 to
OI. Even then I had to populate all defaultable UDT columns and all non defaultable
columns that happened to be blank with bogus values.

Has anyone successfully upgraded an installation with UDTs from 6.4 to OI 2.0 or
even OI 1.x? If you have, what sort of changes did you have to make to your UDT
source code? Is there anyone else actually using UDTs out there? I heard there was
a company in Canada that was. If you are, or you now of someone that is, and you
have upgraded them, please reply. Thanks in advance.

 
 
 

6.4 to OI 2.0 UDT Problems. Anyone else?

Post by Chip Nickolet » Fri, 09 Oct 1998 04:00:00


See comments below.
--

Caribou Lake Software  http://www.CaribouLake.com  Java/RDBMS Solutions
Phone:  414-544-9954



Quote:> I recently migrated from 6.4 to OI 2.0 and I am having some rather
serious problems
> with our user defined datatypes, which were created under 6.4 release.
They UDTs
> have worked well through all 6.4 releases with only an iilink required at
upgrade
> time.

> A number of changes have been made to the UDT specifications since 6.4
and we > had
> to patch up our source code just get them linked in to the OI 2.0
iimerge. Our
> problems are related to the use of functions and comparisons on and with
the
> UDTs.

I have only had to do this once.  It was from 6.4 on a VAX to 1.2 on
an Alpha.  Changes included ANSI SQL changes, ANSI C changes, and
Alpha specific changes (e.g., changing "long" to "longnat").  It was an
OME extension to add a substring function (they were using SAS or
something, and it only allowed data in 200 byte chunks at a time).  It
was quite a mess (a 1000 line C program took about 12 hours to modify
(where it appeared to be working correctly) and another 20+ hours of
debugging (it kept crashing the server, and was being caused by a
compile flag, which took quite a while to identify).  If this would have
been UNIX the time would probably would have been reduced by 50%.  
After that it has worked fine.

Quote:

> I had a very difficult time actually getting the data from 6.4 to Open
Ingres.
> Unloaddb and copydb were useless because of lingering problems with the
binary > copy
> program and UDTs. I ultimately had to use Ingres Star to move the data
from 6.4 to
> OI. Even then I had to populate all defaultable UDT columns and all non
defaultable
> columns that happened to be blank with bogus values.

Luckily I did not have to deal with this.  You could also try Ingres/Net or
write a little dynamic SQL program that would connect to both databases,
get the table definition from the source DB, read the data and then insert
it into the target database.  This would be a fairly generic solution that
would not be too difficult to implement.

Quote:

> Has anyone successfully upgraded an installation with UDTs from 6.4 to OI
2.0 or
> even OI 1.x? If you have, what sort of changes did you have to make to
your UDT
> source code? Is there anyone else actually using UDTs out there? I heard
there > was
> a company in Canada that was. If you are, or you now of someone that is,
and you
> have upgraded them, please reply. Thanks in advance.

Mostly changes to structures (adding things like II_SQLSTATE...),
II_DT_NOBITS, etc.).  Unfortunately there are not too many places
using the Object Mgt Extension.  Back when I did this (3+ years
ago) the issues that I encountered were a total surprise to Level 2
support & development.  I think that Jerry Lohr (a former Level 2
guy) documented my findings in detail so it is possible that CA
Tech Support may have more detailed information on this.

 
 
 

1. Upgrading from 6.4 to OI 1.2 and 6.4 to OI 1.1/04

Hello out there !

Have anybody made a recipy for converting a 6.4 DB to a 1.2 DB on a Unix
server.
If someone have made a list from A-Z during making this operation, I would
like to have a copy of this list.....

I would also like a similar recipy if anyone have converted ABF
applications from 6.4 to OI 1.1/04 on VAX/VMS .....

Regards ....

Inge O. Seth

2. Table disappear when using DTS to import/export database objects

3. Varchar problem in reloading from unix 6.4 to NT OI 2.0

4. Replication Problem

5. Timezone bug in 6.4, fixed in OI 2.0?

6. Is is possible to use SQLServer to control security??

7. OI 10.20/6.4 Star query timeout problem

8. Best way to modify Access database

9. OI 2.0/ICE APIs -- Has anyone used them?

10. 6.4 compatibility with OI

11. Use Upgradefe to upgrade a database from version CA-Ingres 6.4/04 and OI 1.2/00

12. Upgrade 6.4 to OI 1.2

13. Again - upgrade from Ingres 6.4 to OI 1.2