I'm looking for experiences using OTG for DB2 on OS/390 - good or bad. A potential customer claims IBM is telling them it will lock up an application based on DB2. Has anyone ever experienced such a situation? The Oracle server is running Solaris and Oracle 8i (8.1.7), possibly being upgraded to Oracle 9.2
I'm also despairing of an Oracle 8.1.7 application accessing DB2 7.1 for z/OS data that's having a very poor RT: 12 secs to bring over the same single row from a COUNT(*) that has sub-sub-second RT natively over SPUFI.
Also stability problems, we loose connections for no apparent reason.
Any obvious tuning parameters we may be missing? Query also flies natively on Oracle, BTW, OTG seems to be the bottleneck. The SQL only has a single WHERE predicate, and gives back the count of the qualifying rows.
I would suggest to use OTG only to query the data from z/os just like a oracle client. But if you have a real time application accessing/updating DB2 on z/os then go for DB2 connect. I implemented an application using DB2 Connect and a java thin client. Its very fast and reliable. I didnt face any problem till now. DB2 connect licenses are not that expensive also.