oracle通过oerr快速找到相应错误代码的概述及解决方案

“ORA-XXXX”是DBA们常见的错误类型，一般情况下我们可以在网上搜索带相关解释及处理方案，如果事故现场不能上互联网，而出现的错误又未曾遇到，那我们该怎么办呢？
强大的ORACLE早已为我们考虑到这一点并提供了一个简单实用的工具：oerr，在linux或unix环境下，通过这个工具，可以快速找到相应错误代码的概述及解决方案。
下面，就演示一下oerr的使用方法：


语法
操作系统命令行（管理员账号下）：oerr ora xxxx
sqlplus命令行：!oerr ora xxxx

“xxxx”代表错误数字代码

这里的ora还可以是rman、TNS、EXP、IMP、NID等

示例1：
[oracle@localhost ~]$ oerr ora 3136


03136, 00000, "inbound connection timed out"
// *Cause:  Inbound connection was timed out by the server because 
//          user authentication was not completed within the given time 
//          specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
// *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
//          2) Configure SQL*NET with a proper inbound connect timeout value
//             if necessary.
[oracle@localhost ~]$ 


示例2：
[oracle@localhost ~]$ 
[oracle@localhost ~]$ sqlplus / as sysdba


SQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 12 08:51:55 2016


Copyright (c) 1982, 2009, Oracle.  All rights reserved.




Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options


SQL> !oerr ora 3136
03136, 00000, "inbound connection timed out"
// *Cause:  Inbound connection was timed out by the server because 
//          user authentication was not completed within the given time 
//          specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
// *Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections.
//          2) Configure SQL*NET with a proper inbound connect timeout value
//             if necessary.

示例3：

[oracle@localhost ~]$ 
[oracle@localhost ~]$ oerr rman 1008
1008, 1, "the bad identifier was: %s"
// *Cause:  This is an informational message indicating the identifier token
//          that caused a syntax error.
// *Action: No action is required.
[oracle@localhost ~]$ 
[oracle@localhost ~]$ 

示例4：
[oracle@localhost ~]$ oerr TNS 12500
12500, 00000, "TNS:listener failed to start a dedicated server process"
// *Cause:  The process of starting up a dedicated server process failed.
// The executable could not be found or the environment may be set up
// incorrectly.
// *Action: Turn on tracing at the ADMIN level and reexecute the operation.
// Verify that the ORACLE Server executable is present and has execute
// permissions enabled. Ensure that the ORACLE environment is specified
// correctly in LISTENER.ORA. The Oracle Protocol Adapter that is being 
// called may not be installed on the local hard drive.  Please check that
// the correct Protocol Adapter are successfully linked.
// If error persists, contact Oracle Customer Support.

示例5：
[oracle@localhost ~]$ 
[oracle@localhost ~]$ oerr EXP 00089
00089, 00000, "invalid FILE_FORMAT specification"
// *Cause:  The FILE_FORMAT specification did not contain an
//          instance of "%s".  This wildcard string must be present.
// *Action: Correct the error and reenter the EXPORT command.
[oracle@localhost ~]$