Re: GPF in ora7win.dll

Terry,
We're running PeopleSoft HRMS with PeopleTools 3.1.3, and are thinking of upgrading to Oracle 7.1.6. According to information provided to me by PeopleSoft:

There is an issue with 7.1.6 and the ORA7WIN.DLL. The -ugly - (my term, not theirs) workaround is to use the ORA71WIN.DLL instead of the ORAWIN7.DLL.

The only hitch, is that PSTOOLS.EXE is hardcoded to look for ORA7WIN.DLL, so you would have to rename ORA71WIN.DLL to ORA7WIN.DLL.

Furthermore, you may need to upgrade your V1 SQL*Net to 1.1.9.0a, because only the more recent versions are shipped with the ORA71WIN.DLL. Simply adding ORA71WIN.DLL to an existing older version will NOT work.

Hope this helps.
==========Terry G. Phelps, 1/29/96==========

I was running along just find with ORACLE 7.1.3 on AIX, and SQL*net 1.1.7.* on my Windows 3.1 clients. I have two semi-identical databases, for production and testing. My application is Peoplesoft Financials, if it matters. I upgraded the test database to 7.1.6, did some minor testing, and found it seemingly okay. Later, we discovered that some function the application is doing, is causing a GPF in ora7win.dll. File Manager tells me this DLL is version 7.0.16.2.0, size 272448, dated 11/29/93. The GPF occurs at 0001:341d.

The same application function on the old 7.1.3 database works fine. Late flash: I've downgraded my 7.1.6 database to 7.1.3, and the problem has gone away, so it's definitely RDBMS version sensitive.

I can't tell for sure what the app is doing at the time of the crash, but my guess is it's doing an insert of something with about 25 columns, if that helps any.

Oracle support says, oh, you need to upgrade your clients to SQL*NET 1.1.9.*, and they'll ship that right out.

Anyone encounter this kind of problem? Do I really need to upgrade 100 PC's? No, I can't upgrade to SQL*NET 2. The app supports only version 1. I swear.

Terry Received on Wed Jan 31 1996 - 00:00:00 CET