We could narrow it down to the value of the sequence exceeding
16777216 (2 to the power of 24)
This looks familiar as described in bug 2573172

This bug describes to change the type in the odefin call to type 3 but this doesn't help.

I know this is not really a dba issue now anymore but I'm desperate for any advice because I don't have any developers

left with oci-knowledge

Tnx,

Jeroen

 

 

-----Oorspronkelijk bericht-----
Van: Jeroen van Sluisdam
Verzonden: Wednesday, November 26, 2003 16:40
Aan: '[EMAIL PROTECTED]'
Onderwerp: migration sequence oci problem

 

 

Hi,

 

We're testing an oracle 9.2.0.4 database with an oracle 7 client.

This is a C++ client, using OCI to go to oracle.

We see strange behaviour when using a sequence which worked

nicely before. The sequence is not incremented when issueing

"select res_id.nextval from dual

 

When I test this with an oracle 7 sqlplus client this works also

as expected.

 

Is there any known bug or issue known with migrating oci-applications.

According to manuals it shouldn't be a problem and I cannot find any problems

on metalink about this.

 

Thanks in advance,

 

Jeroen

Reply via email to