Re: Explicit Connection Problem

Matt Schoaf wrote:
>
> Matt Schoaf wrote in message <66p5jg$b62_at_gatx_news.GATX.COM>...
> >We have ProC programs which were compiled under ProC 2.2 which ran against
 a
> >7.1.4 database. We are now trying to run them against a 7.3.2 database and
> >after some research, I have determined that the explicit connection to the
> >database is the problem.
> >
> >Has anyone else experienced this? We would certainly like to avoid
> >re-compiling all our ProC programs in order to migrate to a newer database.
> >
>
> Actually I've got a followup to this problem. It isn't the explicit
> connection. It is actually the connect string. A program compiled for a
> 7.1.4 database that doesn't use a connect string won't connect to a 7.3.2
> database. The same source code compiled for a 7.3.2 database will work
> fine...with or without a connect string. I need to find a workaround so
> that we won't have to recompile all of our C modules before we convert the
> databases.
>

I might have suffered a similar problem. I hesitate because if I explain what we experienced you will see that the 'root' cause is not what it appears.

We were running a 7.1.3 database and had a number of programs that happily ran against it.

When we upgraded to 7.3 some of these programs worked and others didn't. Investigation 'revealed' that some of the standard runtime functions were failing to work correctly. Subsequent tests demonstrated that sonmetime function calls where returning to the wrong place!

We eventually determined that the real cause of the problem was that if a program was comiled with the 7.1.3 pre-processor it produced different code than if it was compiled under 7.3. Furthermore the libraries used in the two versions where significantly different. In our particular case we had incorporated the Oracle static libraries into a shared library which meant that we could have a mismatch between a 7.1.3 program and 7.3 libraries and vice versa.The upshot of this was that if you mixed 7.1.3 and 7.3 things would go wrong but often in a misleading way. (We did work out the exact reasons for the results that we got but I've yet to have enough caffine to remember the details).

We did infact recompile everything eventually but by keeping 7.1.3 co-installed with 7.3 we reduced the impact of this.

As you can see with such a wierd problem it is differcult to say if you are experiencing the same thing but I hope that this might provide you with some assistance.

Steve Received on Fri Dec 12 1997 - 00:00:00 CST