I believe I have seen a similar error before. My client was doing a .NET application and started receiving this error: ERROR [HY000] [IBM][UVODBC][1500951]Error ID: 25 Severity: FATAL Facility: OIOERR - Internal error. Please report details to your HyperSTAR Support contact: ODIO protocol error. ERROR [HY000] Although it looks like an extra 1 on the end of the error number, which may have been a typo.
They were also seeing this with multiple, high volume queries. After many rounds with IBM technical support, the final result was that my client scrapped ODBC and converted to OleDB. It performed much better, but if the connections hit the server too fast, they occasionally receive scrambled data. Their environment is UniVerse 9.5.1.1 on AIX 5.2. They are using the latest OleDB client on the Windows side.
Bob Gerrish - [EMAIL PROTECTED]
At 11:39 AM 3/22/2004, you wrote:
I have a customer who is getting the following error message when trying to do a query using Crystal Reports 8.5. The query will run up to around 172,000 records before aborting:
ODBC ERROR: [IBM][UVODBC][150095]ERROR ID: 25 SEVERITY: FATAL FACILITY: OIOERR - INTERNAL ERROR
PLEASE REPORT DETAILS TO YOUR HYPERSTAR SUPPORT CONTACT: ODOIO PROTOCOL ERROR
I have checked the files that are used, and there are no BLINK errors reported.
This is a UV 10.0.14, running on AIX 5.2.
Thanks,
Bryan Haglund Haglund Consulting Inc. Phoenix, AZ -- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
-- u2-users mailing list [EMAIL PROTECTED] http://www.oliver.com/mailman/listinfo/u2-users
