Ora-03113 报错

在实际的开发过程中，碰到了ora-03113 的报错，related information :end-of-file had check....

 

soluition :

 

增加sqlnet.ora 文件：

 

hgdsfe01:[/]#cat ./oracle/app/oracle/product/11g/db/network/admin/sqlnet.ora
DIAG_ADR_ENABLED =OFF

 

Oracle 11g 默认DIAG_ADR_ENABLED =ON，即启用了Automatic Diagnostic Repository特性。

将DIAG_ADR_ENABLED =OFF，即恢复到11g之前的client trace产生的方式，在测试环境网络不稳定的情况下，是有帮助的，但是如果网络稳定的情况下不建议在生产环境中将DIAG_ADR_ENABLED =OFF，因为使用Oracle 11g的adr集中日志和trace管理方式对日后的数据库日常管理是有帮助的。



Understanding Automatic Diagnostic Repository

The automatic diagnostic repository (ADR) is a systemwide tracing and logging central repository. The repository is a file-based hierarchical data store for depositing diagnostic information, including network tracing and logging information.

The ADR home is the unit of the ADR directory that is assigned to an instance of an Oracle product. Each database instance has its own ADR home. Similarly, each listener, Oracle Connection Manager, and client instance has its own ADR home.

The location of an ADR home is given by the following path, which starts at the ADR base directory:

diag/product_type/product_id/instance_id

另外的解决方案：

1: the hostname of  file: listener.ora should be changed from Upper case to lower case as below:

 

(ADDRESS = (PROTOCOL = TCP)(HOST = HGDSFE01)(PORT = 1521))  à (ADDRESS = (PROTOCOL = TCP)(HOST = hgdsfe01)(PORT = 1521))  

 

因为：

#cat /etc/hosts

43.82.201.185   hgdsfe01

 

主机名是小写：hgdsfe01

 

2: Do relink operation. And first, we should shut down the Database, then do following command:

 

 $relink all

（因为按装的时候是copy安装的，一定要做relink）

 

3:检查client 的plsql 中的system32 中的host 文件的配置：也要为小写，还有oracle/network/admin/tnsnames.ora 的配置。

 

4：注意：改这些配置，要关掉database 的，如果是生产机的，要放到周末来做。

 

要在linux aix 看error information 的话，必须以oracle 用户进入：

 

hgdsfe01:[/]#su - oracle
hgdsfe01:[/oracle]$oerr ora 03113
03113, 00000, "end-of-file on communication channel"
// *Cause: The connection between Client and Server process was broken.
// *Action: There was a communication error that requires further investigation.
//          First, check for network problems and review the SQL*Net setup.
//          Also, look in the alert.log file for any errors. Finally, test to
//          see whether the server process is dead and whether a trace file
//          was generated at failure time.

 

否则报错：

hgdsfe01:[/]#oerr ora 03113
ksh: oerr:  not found.