Last updated on SEPTEMBER 01, 2017
Applies to:Oracle HTTP Server - Version 126.96.36.199.0 to 188.8.131.52.0 [Release Oracle11g to 12c]
Oracle Fusion Middleware - Version 184.108.40.206.0 to 220.127.116.11.0 [Release Oracle11g to 12c]
Information in this document applies to any platform.
- Applies to Oracle Database Clients 18.104.22.168 and 22.214.171.124 installed in Oracle Fusion Middleware 126.96.36.199, 12.1.2, and 12.1.3 homes
- The same 188.8.131.52 is installed in 184.108.40.206 -220.127.116.11 homes, however mod_plsql was deprecated and no longer supplied in 12.2.1. This document and patches are only applicable up to OHS 12.1.3.
This issue can occur for SQL*Plus and OHS/mod_plsql connecting to the database over TCPS. It could be any client using sqlnet layer for TCPS that experiences this problem.
- When the pl/sql procedures are using a secure connection between Oracle HTTP Server and an Oracle Database, the pl/sql procedures fail with the following errors:
This issue only occurs when using an Secure Connection between Oracle client application and an Oracle Database Server (ie. PROTOCOL=TCPS). When mod_plsql is *not* secured from Oracle HTTP Server and the Oracle Database (ie. PROTOCOL=TCP), the pl/slql procedure works. This issues also occurs when using a simple SQL*Plus connection to the database using TCPS.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms