Re: Forms 6i vs. rdbms 12.2

Juan,

I've read the docid in MOS, which makes sense, Oracle is trying to finally draw a line in the sand on all of the really old versions. The only trick left that might work is the one I eluded to in my previous reply. Specifically, you could try installing the Oracle 11.2 binaries
into a separate Oracle home on the same server as the 12.2 instance. Then create a new 11.2 listener (with a new name and separate port#). Finally, in the new listener definition set the ORACLE_HOME to the Oracle 12.2 home directory.  I did a quick mock up in my homelab and this works, the 11.2 listener does successfully connect to the 12.2 database. I did not however, have on hand any old application code which might require Oracle 9 or 10, to test the connection to 12.2 thru the 11.2 listener. Make sure you also set the password for the oracle 12.2 account to uppercase. I still think method will work, but it is clear its the end of the line for really old applications and connections.

cheers,

j

On 6/28/18 1:02 PM, Juan Carlos Reyes Pacheco wrote:
> From a previous post
>
> ORA-3137*[kpoal8Check-5] From Incompatible Client Version Connecting
> To 12.2 Database (Doc ID 2296523.1)*
>
>
> Solution
>
> Unlike previous version, Oracle has added some strict checks on RDBMS
> 12.2.0.1 and client apps must comply with these checks.
>
> In order to resolve this, upgrade client version to compatible level.
>
>
>
> 2018-06-26 23:46 GMT-04:00 John Kelly <jckelly_at_aidhm.com
> <mailto:jckelly_at_aidhm.com>>:
>
> Hi Patrice,
>
> It sounds like you've already found the
> SQLNET.ALLOWED_LOGON_VERSION parameters. Did you try setting these
> on both the client and
> the server?  The other option might be to install both the Oracle
> 12.1 and 12.2 binaries and use a 12.1 listener to communicate with
> the 12.2 database. I did something similar back in Oracle 11 and I
> believe this should still work. The additional advantage to this
> approach
> is that with the separate oracle home you won't have to downgrade
> all of the SQLNET connections to the older version and you get better
> security.
>
> cheers,
>
> John Kelly
>
> sample syntax:
> SQLNET.ALLOWED_LOGON_VERSION=8
> SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
> SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
>
>
>
> On 6/26/18 3:39 PM, Patrice sur GMail wrote:
>> (don't laugh; I know Forms 6i is concurrent with Oracle 7.3 and
>> it's not secure.  The app maintenance people know the apps should
>> have been upgraded years ago)
>>
>> We have a couple of really old intranet apps written using Forms
>> 6i, so far we have managed to keep them running without upgrading
>> them.  One of them is composed of over 200 forms (not counting
>> plls, menus, reports).
>>
>> I upgraded a dev database from 11.2 to 12.2., did what I could
>> think of to allow the old apps to connect, downgraded the
>> listener compatibility mode from 12 to 11, then to 8 though I
>> think 9i might have been okay.  I even turned off mixed case
>> logins in the database but Forms 6i still can't connect.
>>
>> Is there any way to allow Forms 6i apps to connect to 12.2?
>> ​One discussion online mentions that Forms 6i could connect to
>> 12.1, but as of 12.2. it really is the end of the road for this
>> old version of forms.​
>>
>> https://www.databaseusers.com/article/5966488/is+forms+6i+on+Oracle+Database+12.2+compatible%3F
>> <https://www.databaseusers.com/article/5966488/is+forms+6i+on+Oracle+Database+12.2+compatible%3F>
>>
>>
>> ​I'll post on the Oracle Forms community forum and log an SR,
>> though I can predict what Oracle Support will tell me with their
>> funeral director voice.​
>>
>> -- Patrice
>>
>> My profiles: Facebook
>> <http://www.facebook.com/home.php?#%21/profile.php?id=100000206805521>LinkedIn
>> <http://ca.linkedin.com/pub/patrice-boivin/a/933/5a9>Twitter
>> <http://www.twitter.com/PatriceBoivin>
>
>

--
http://www.freelists.org/webpage/oracle-l