Fatal NI connect error 12514:

alert.log file has many entries for Fatal NI connect error.

Examples:

Fatal NI connect error 12514, connecting to:
 (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.77.3)(PORT=1971))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=brtadbstd01_DGB.brta.gov.bd)(CID=(PROGRAM=oracle)(HOST=brtadb.brta.gov.bd)(USER=oracle))))

  VERSION INFORMATION:
    TNS for Linux: Version 11.2.0.3.0 - Production
    TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.3.0 - Production
  Time: 27-JUL-2013 09:15:33
  Tracing not turned on.
  Tns error struct:
    ns main err code: 12564
   
TNS-12564: TNS:connection refused
    ns secondary err code: 0
    nt main err code: 0
    nt secondary err code: 0
    nt OS err code: 0

 Solution:

We will have an entry on the alert.log file every time a client connection of any kind fails to complete or is aborted.

One way to minimize the impact is by using the parameter SQLNET.INBOUND_CONNECT_TIMEOUT (default to 60 seconds on 10gR2 and 11g) but, sometimes, this value is not adequate.

Oracle also mentions the occurrence of this error if you use DB Console or Enterprise Manager to monitor your databases and the emagent will try to connect to the target database repeatedly and, statistically, some will fail (frequency will depend on how busy your system is).

Most of the time (certainly for DB Console and Enterprise Manager Agent) the application will try to connect again and it will succeed.

To fix the problem you could increase the value of SQLNET.INBOUND_CONNECT_TIMEOUT on the listener.ora and the sqlnet.ora file located on the server side.

If you already have a value you have considered adequate, you might want to add the following line on your listener.ora file:
DIAG_ADR_ENABLED_listener_name=OFF

This line will hide the error on the alert.log file and the error will be posted on the $ORACLE_HOME/network/log/sqlnet.log file

Memory Notification: Library Cache Object loaded into SGA
Heap size 8819K exceeds notification threshold (2048K)

Hello viewers:

Today Morning i have found that the  message on alertlog of oracle 10g r2 version 10.2.0.1. To  avoid these messages being generated, we need to adjust the size of a hidden initialization parameter. The hidden  initialization parameter is “_kgl_large_heap_warning_threshold”. We can avoid this message to set a high value or zero.

 Note:- Set  "_kgl_large_heap_warning_threshold" to a reasonable high value or zero to prevent these warning messages. Value needs to be set in bytes. The default threshold in 10.2.0.1 is 2MB. So these messages could show up frequently in some application environments. In 10.2.0.2, the threshold was increased to 50MB after regression tests, so this should be a reasonable and recommended value.

To modify this parameter:

login as sysdba

SQL> connect sys as sysdba
SQL> alter system set "_kgl_large_heap_warning_threshold"=52428800 scope=spfile ;
System altered.


SQL> shutdown immediate;
SQL> startup;


Now the following message will not come.

Why Oracle 12c?

Oracle Database 12c introduces a new multitenant architecture that makes it easy to deploy and manage database clouds. Innovations such as Oracle Multitenant, for consolidating multiple databases quickly, and Automatic Data Optimization with Heat Map, for compressing and tiering data at a higher density, maximize resource efficiency and flexibility. These unique advancements, combined with major enhancements in availability, security, and big data support, make Oracle Database 12c the ideal platform for private and public cloud deployments.

Benefits

• New multitenant architecture enables higher levels of consolidation on the cloud without the need to change existing applications
• Automatic Data Optimization features efficiently manage more data, lower storage costs, and improve database performance
• Defense-in-depth database security addresses evolving threats and stringent data privacy regulations
• Maximize availability with protection from server failure, site failure, human error, reduced planned downtime, and application continuity
• Scalable discovery of business event sequences with enhanced in-database analytics capabilities for big data
• Seamless integration with Oracle Enterprise Manager Cloud Control 12c enables administrators to easily manage the entire database lifecycle