Re: An issue in our database museum

Problem is solved now. The core of the problem was that in this package procedures/functions definition were before constant definition. This in case of remote calling via db link from 8.0.5 and returning VARCHAR2 brought our problems. The strange is that this caused problem even while calling simple procedure that do not use any of declared constants.

Dusan Bolek

pagesflames_at_usa.net (Dusan Bolek) wrote in message news:<1e8276d6.0404010153.29f41fa2_at_posting.google.com>...
> The first of the commandments of a database development should be:
> Thou shall not keep an old database version after a desupport notice.
> We have violated and the pay for this sin is an interoperability
> issue. Our situation:
>
> - about fifty branch databases connecting into the central one using
> stored procedures via DB link
> - branch database 8.0.5 on WIN NT
> - central database 8.1.7 Solaris, should be upgraded to the 9.2.0.4
> (probably .5)
>
> Issue:
> We can't return VARCHAR2 in out variable. Error is unfamous End Of
> File on Communication Channel.
>
> Prerequesities:
> Procedure must be called via database link from 8.0.5.
> Procedure must be included in one particular package (in other package
> procedure returns VARCHARs with no problem).
> There is no PRAGMA etc. in the problematic package.
> Target database must be 9i (8.1.7 works).
>
> To be honest I do now understand what's going on. One "bad" package,
> one simple procedure:
>
> PROCEDURE TEST(cTest out VARCHAR2)
> IS
> Begin
> cTest := 'BOOOM!';
> End;
>
> and stupid error, just between 8.0.5 and 9.2. This procedure should
> not be influenced from its package by any way, but exact opposite is
> true.
> Anyone encountered something like this?
>
> P.S. I can't post the package source, because of its size.
Received on Fri Apr 02 2004 - 08:46:34 CST