Currently oracle 9.2i database was migrated to oracle 11.2g, we din't face any issue in migration, but is it possible to make oracle 11.2. to behave backward compatible to oracle 9.2 by modifying system parameter.
You may be able to set the COMPATIBLE parameter to 9.2.0.. That wouldn't make Oracle 11g act completely like 9i, but it would come as close as possible.
Related
I am configuring several Windows 10 systems that will need to reliably connect via ODBC using system DSNs to both Progress version 9.x and Progress version 10.x databases.
I have been told by one of our IT staff that interfacing with Progress versions 9.x servers require the OpenLink ODBC client software, while interfacing with Progress 10.x requires the OpenEdge ODBC client software.
I am not completely confident that this is true, but I have not been able to find any authoritative documentation citing version compatibilities between these technologies/products. Can someone please direct me to information about the compatibility between these products, pertaining specifically to versions of these products?
It was version 8 that required OpenLink.
Version 9 is unspeakably ancient and version 10 not much better. The current release is OpenEdge 12. ODBC options for v9 should include Progress/Datadirect ODBC since the SQL-92 engine was introduced in that timeframe. Documentation for such things is going to be very, very sparse.
Progress' current ODBC documentation: https://www.progress.com/odbc/openedge might get you started though.
OpenLink does also support v9 and they have some documentation here: http://wikis.openlinksw.com/UdaWikiWeb/MigratingFromSQL89ToProgress10SQL92Connectivity
In the Progress 9 windows client, there is a 32bit ODBC driver for Progress 9. However, if the program you are trying to connect to Progress from is 64 bit, this will not work directly.
We have succeeded in using an old 32bit version of SQL Server as a tunnel, creating SQL Server views on the Progress database and querying these views using a SQL Server ODBC driver from the 64 bit program.
It's messy and awkward, and I wouldn't want to vouch for the robustness of such a solution, but if this is only a stopgap then perhaps it may help.
OpenLink provide Progress SQL-92 ODBC Driver for version 9.x, 10.x & 11.x and can provide such connectivity to both 32 & 64 bit Windows applications, see http://wikis.openlinksw.com/UdaWikiWeb/InstallProgress92LiteWin32 ...
I would like to know the functionalities affected when upgrading from 11g to 12c. For example, using WM_CONCAT in 11g works whereas its incompatible with 12c. What are the other functions / features of 11g not supported in 12c.
The ostensible question is a duplicate of How do you find out about deprecated features in a new release of Oracle?
But the real issue is that WM_CONCAT was never an officially supported function. It doesn't work in earlier versions in Express Edition or in any version where the Workspace Manager component was removed. (This is partially Oracle's fault for waiting 30 years to include an official aggregate function, which forced people to look for alternates, but you still have to pay the price.)
The best solution is to replace WM_CONCAT with LISTAGG. Some people create a custom function named WM_CONCAT but that's probably not a good idea anymore. Oracle 12.2 introduced some nice new features to LISTAGG. You'll want to migrate the code eventually, you might as well do it now.
Current desktop application is developed using PowerBuilder version 9 with Oracle 9.2 as a back end. Now I need to migrate the back end Oracle to 11.2.0.2. From Googling I found PowerBuilder 9 is no longer supported. Is it possible to connect to Oracle 11.2.0.2 with PB 9? Kindly let me know if I can migrate the same application to higher version of PB like PB 11?
If you look at this response from Terry Dykstra you'll see your options under PB9 are:
the O90 driver, ODBC, OLEDB or JDBC
As for migrating to a higher version, migrating to higher versions of PB are typically comparatively small efforts (but no guarantees), assuming you have all the source code.
You mention upgrading to PB11. Keep in mind that PB11 also is no longer supported. Sybase (now an SAP company) typically supports current and previous major versions (with some overlap), so right now that means 12.5 and 12.0.
Good luck,
(another) Terry
Few months back I saw TeraData Express Edition. I have no idea of this beast. I want to know whether it still comes with Express Edition and whether it is a good idea to use this database for Windows based mid-sized apps.
It really depends on what you want to do with this application. From an application perspective, a great weakness of Teradata is that it does not support read committed transaction isolation. If you are attempting to use Teradata as an OLTP database, then you might want to try something else. If you are using it to crunch numbers, then yes, go with it. The one issue is that Teradata Express Edition is not supported that well. Express edition is essentially a snapshot of the database for a certain release. If you find and report a bug, it will take a long time for you to receive a fix. Teradata only releases the express editions once per db release. However (imo), if you buy the real version, you will receive a pretty quick patch which will be rolled into the database software.
I use teradata in my technical support work. I work on database middleware, and Teradata is one of our supported data stores. Define mid-sized? 1-200 transactions per second? I'd stand ANY commonly used database up against that. 10000 tps? Maybe not - maybe you go to the enterprise edition.
I see that the IronRuby team has documented using ActiveRecord in IronRuby with MSSQL - they indicate that some adjustments were required to the adapter.
In interview on 8/11/2009, Jimmy indicates a major drawback of IronRuby:
The main limitation is that IronRuby does not support any
of the C-based Ruby libraries
That indicates that the SQLite-Ruby library that depends on sqlite.dll is probably out of the question. However, in the same interview, he says:
For the database you can use SQLServer Express (which is free),
or any .NET based database, like the recent csharp-sqlite port.
That sounds promising, but I'm a bit overwhelmed on how to begin! How do I go about connecting Ruby's ActiveRecord to csharp-sqlite or where can I look for more guidance?
I found some more write-up on IronRuby and SQLite, but I may need some translation help?
The current solution is to port do_sqlite3 to use all .NET APIs. There are a couple ports
of SQLite to .NET, but none are widely used yet. For 1.0 we will have an ironruby-dbi gem
for using .NET based databases through the Ruby DBI API; so using SQLExpress and
SQLServer will work with an appropriate sqlserver adapter. I'm not sure if there is a
do_sqlserver adapter yet for DataMapper, but we'll leave that to the community for doing.
Does this imply that my technology stack could go something like: ActiveRecord uses SQLiteRuby, SQLiteRuby is tweaked to use ironruby-dbi (should be little change since this is the Ruby DBI API??) then ironruby-dbi has the smarts to work with a .NET based database such as c#sqlite. Of course I will need an adaptor to go between ActiveRecord and SQLiteRuby ... hopefully no change required there?
Sugggestions, Advice, Tips?
you won't be able to use activerecord as is.
You can either wrap the ADO.NET provider for SQLite or you can perhaps help with the ironruby-dbi project and provide a dbi adapter that handles sqlite correctly. From then on adding it to rails is easy as it would require replacing the connection with the dbi connection.
It is a work in progress though and at this moment most efforts have been around sql server, but I too would like to get sqlite working properly on IronRuby with rails.
Another approach would be to change the active record adapter for sqlite to work with the ADO.NET provider (that would probably require the least effort but won't help outside the rails community). I have a pretty good idea of what needs to happen to make it all work but I simply don't have the time to do all of these things, unfortunately.
Have you tried using the SQLite adapter? It might work out-of-the-box.
I haven't tried it personally though.