Oracle 11 to Oracle 12 upgrade
Oracle 11 to Oracle 12 upgrade
Any good lessons learned or best practices when using ODAC and upgrading from Oracle 11 to Oracle 12?
Any settings within ODAC that should be looked at?
Any Delphi coding changes that should be considered?
Any settings within ODAC that should be looked at?
Any Delphi coding changes that should be considered?
Re: Oracle 11 to Oracle 12 upgrade
Helllo,
If the database structure has not been changed, no additional changes will be required in ODAC or in your code.
If the database structure has not been changed, no additional changes will be required in ODAC or in your code.
Re: Oracle 11 to Oracle 12 upgrade
Testing after upgrade to Oracle 12 and getting a type mismatch error for a field. Expecting integer Actual: float. Why would that be coming up now? The field length for the field in question is Number(9).
The same query works fine in Oracle 11.
The same query works fine in Oracle 11.
Re: Oracle 11 to Oracle 12 upgrade
We tested ODAC work according to the description and found no problems. We used the table with the NUMBER(9) type field in Oracle 11 and Oracle 12 and got the same results when working with both DBMS.
For further problem investigation, please provide DDL script to create the table which you are using in your project, as well as the snippet causing the described error.
For further problem investigation, please provide DDL script to create the table which you are using in your project, as well as the snippet causing the described error.
Re: Oracle 11 to Oracle 12 upgrade
That will be impossible to do with the size of our DB, but I can provide you the scenario.
TOraTable with Wave field number(9) (Data comes back fine)
TOraQuery Master that pulls from a view, Master Source is TOraTable with Wave parameter supplied by table. (Data comes back fine)
TOraQuery Child that pulls from another view, master source is Master with Wave parameter supplied by Master. This is the one that gets the mismatch error.
TOraTable with Wave field number(9) (Data comes back fine)
TOraQuery Master that pulls from a view, Master Source is TOraTable with Wave parameter supplied by table. (Data comes back fine)
TOraQuery Child that pulls from another view, master source is Master with Wave parameter supplied by Master. This is the one that gets the mismatch error.
Re: Oracle 11 to Oracle 12 upgrade
We are glad that you could identify the problem. Contact us on any questions concerning ODAC usage.
Re: Oracle 11 to Oracle 12 upgrade
Our DBAs applied the Oracle patch, but that did not resolve the issue. I sent the information via the Devart Request Support Contact Form along with an attachment. I am hoping your system received it, because requested a copy of the email be sent to me, but I never received a copy. Can you confirm receipt?
Re: Oracle 11 to Oracle 12 upgrade
We received the problem description via Devart Request Support Contact Form and started to investigate it.
Re: Oracle 11 to Oracle 12 upgrade
Sent further information via email. Can you confirm receipt?
Re: Oracle 11 to Oracle 12 upgrade
We received your message via email, however we could not get the mentioned ZIP file
Re: Oracle 11 to Oracle 12 upgrade
Maxim I sent one directly to your email, Did that not have the zip file either?
Re: Oracle 11 to Oracle 12 upgrade
Thank you for the description. We received your sample and started to investigate the problem. We will inform you about the results in the nearest time
Re: Oracle 11 to Oracle 12 upgrade
FYI, testing with TCP/IP Direct connection gives some strange results:
Adding the fields to the Fields editor, the Wave field comes back as TIntegerField at design time. However, at runtime with Direct connection, still get the Type mismatch error.
Adding the fields to the Fields editor, the Wave field comes back as TIntegerField at design time. However, at runtime with Direct connection, still get the Type mismatch error.
Re: Oracle 11 to Oracle 12 upgrade
For any others having similar issues, this was resolved with an Oracle setting:
alter session set "_optimizer_reduce_groupby_key"=false;
alter session set "_optimizer_reduce_groupby_key"=false;