CSE server is on one AWS server and its Oracle 19c Database is on another AWS server.
Seeing error: "CSEXI0214E Requester Code Page is not supported", when trying to open the Encyclopedia Client on the CSE server.
After checking the CSE logs the iefmd.log shows:
Requester code page 1252 is not supported
SQL Error in function: DXgEncy
SQL Communication Area
SQLERRMC: ORA-03113: end-of-file on communication channel
Process ID: 16684
Error:ORA-03113: end-of-file on communication channel
Process ID: 16684
Session ID: 2549 Serial number: 41955
Release : 8.5
Component : Gen Client Server Encyclopedia
The root cause is not the usual client codepage problem for the CSEXI0214E Error Message but the Oracle DB connection from the CSE (Oracle client) to the Database has been broken in some way.
After review of Oracle alert log file (Oracle Server Version 18.104.22.168.0 on LINUX) there are 2 main errors:
1. TNS-12535: TNS:operation timed out (ns secondary err code: 12609)
Referring to Oracle article:
Oracle Net SQLNET.SEND_TIMEOUT and SQLNET.RECV_TIMEOUT Parameters and errors ORA-12170 TNS-12535 ORA-12609 ORA-12608 (Doc ID 1335630.1)
It states that the parameter SQLNET.RECV_TIMEOUT should not be set on the server side.
SQLNET.RECV_TIMEOUT and / or SQLNET.SEND_TIMEOUT set in the client / server SQLNET.ORA files
SQLNET.RECV_TIMEOUT is not set by default. It introduces an idle timer when used on the server side. This is often not understood when implemented.
Since the server side process is in RECV mode whenever it is waiting on work from the client, if the client is to go idle then that timer is clocking and can be hit therefore causing idle disconnections.
Therefore the parameter really should not be set on the server side.
2. Fatal NI connect error 12170.
This article from Oracle alludes to the possibility of a firewall existing between the Oracle client and server.
Alert Log Errors: 12170 TNS-12535/TNS-00505: Operation Timed Out (Doc ID 1628949.1)
This document describes a problem that arises when a firewall exists between the client and the database server.
NOTE: Both of these errors are Oracle or network related and not related to the CSE itself, so support's suggestion is to contact your Oracle DBA/support person for assistance
In this particular scenario the root cause of problem was related to article #1 i.e. SQLNET.RECV_TIMEOUT and SQLNET.SEND_TIMEOUT were set in the client sqlnet.ora file and after removing them the problem was resolved. Per the article setting them to higher values may also resolve the problem.