Migration TD42 To TD51 : Problem with Oracle

[gibaldipontin]

We want to migrate to version Team Developer.

Current Version : TD 4.2
Tested version : TD 5.1 - SP1

OS : Windows XP
Database (server) : Oracle 10g (10.2.0.3)
Client : Oracle 9i (9.2.0.1.0)

We have made the following changes :

Saving files (.apt ) with TD 4.2
Opening files with TD 5.1 - SP1
Replace cbtti42.dll by cbtti51.dll

We have problems with accents and special characters.
=> Solution:
Change the setting up the Oracle database (NLS_LANG)
Replace AMERICAN_AMERICA.WE8MSWIN1252 by AMERICAN_AMERICA.UTF8

We have a problem with the call stored procedures.
We were forced to change the appeal of these procedures.
=> Solution :
Replace: CallSqlPLSQLCommand (hSqliUsed, spRequete)
By: Call SqlOraPLSQLPrepare (hSqliUsed, spRequete)
Call SqlOraPLSQLExecute (hSqliUsed)
But we must add ':' to each variable of the function.

We have a problem with Oracle fields over 256 characters.
TD does not recover the correct value.
Problem long string.
=> No solution

We hope that the SP2 fix its bugs.

Method connection to the database : we use Sqlora32.dll.
Call SqlConnect (hSqliUsed)
Call SqlPrepare (hSqliUsed, spRequete)
Call SqlExecute (hSqliUsed)
Call SqlFetchNext (hSqliUsed, ngFetchRetour)
Call SqlPLSQLCommand (hSqliUsed, spRequete)

[Jean-Marc Gemperle]

Hi,

I'm quite sure your hopes will be satisfied on those issues you mentioned in your post, I would not garantee it unless I get a testcase from you, but if you search on SqlPLSQCommand then on longstring, and NLS_LANG you should see other people report similar issue and those should get fixed in the SP2...

Me 2 hopping:-)

Cheers
Jean-Marc

Saving files (.apt ) with TD 4.2
Opening files with TD 5.1 - SP1
Replace cbtti42.dll by cbtti51.dll

Yes when migrating you must make sure absolutely that all the outlin is saved in APT text mode. Of course you must ensure ALL the DLL of previous version are migrated to the current, make also sure you don't use an OLD GUPTA APL in your source. Search the post on the forum about migration done by Apaula.

We have problems with accents and special characters.
=> Solution:
Change the setting up the Oracle database (NLS_LANG)
Replace AMERICAN_AMERICA.WE8MSWIN1252 by AMERICAN_AMERICA.UTF8

I believe unicode conversion failure right?...Well change to UTF8 in NLS_LANG is only an unrealistic workaroud, you should see this fixed in SP2

We have a problem with the call stored procedures.
We were forced to change the appeal of these procedures.
=> Solution :
Replace: CallSqlPLSQLCommand (hSqliUsed, spRequete)
By: Call SqlOraPLSQLPrepare (hSqliUsed, spRequete)
Call SqlOraPLSQLExecute (hSqliUsed)
But we must add ':' to each variable of the function.

I assume issue is related to executing SP in te same schema...the problem is now OCI8 is used by default and this caused the problem. In previous version of TD having USELOB=1 in the SQL.INI set globaly causes the same problem. This issue should also be fixed in SP2

We have a problem with Oracle fields over 256 characters.
TD does not recover the correct value.
Problem long string.
=> No solution

In fact the result set is CORRECT but it is returned in ANSI, if you convert back Using SalStrToWideChar() then you should get the expected result, this also is not a realistic workaround...This was a regression introduced in the SP1. You should see it fixed in SP2