“ORA-XXXX”是DBA们常见的错误类型，一般情况下我们可以在网上搜索带相关解释及处理方案，如果事故现场不能上互联网，而出现的错误又未曾遇到，那我们该怎么办呢？强大的ORACLE早已为我们考虑到这一点并提供了一个简单实用的工具：oerr，在linux或unix环境下，通过这个工具，可以快速找到相应错误代码的概述及解决方案。下面，就演示一下oerr的使用方法：语法操作系统命令行（管理员账号下）：oerr ora xxxxsqlplus命令行：!oerr ora xxxx“xxxx”代表错误数字代码这里的ora还可以是rman、TNS、EXP、IMP、NID等示例1：[oracle@localhost ~]$ oerr ora 31360, &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 sysdbaSQL*Plus: Release 11.2.0.1.0 Production on Tue Jul 12 08:51:55 2016Copyright (c) , Oracle. &All rights reserved.Connected to:Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit ProductionWith the Partitioning, OLAP, Data Mining and Real Application Testing optionsSQL& !oerr ora 31360, &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 10081008, 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 125001, &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 000890, &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 ~]$&
最新教程周点击榜
微信扫一扫Error 522: Connection timed out & Cloudflare Support
A 522 error means we were unable to reach the origin web server at all.
There are a few main causes of this:
The origin server was too overloaded to respond.
The origin web server has a firewall that is blocking our requests, or packets are being dropped within the host’s network.
The origin web server is offline, or the IP address set for it in the DNS settings with us incorrect (i.e. the request from us was to sent to the wrong place).
There is a network routing issue between us and the origin web server.
The origin server has keepalives disabled.
In all these cases, it’s worth checking that the origin web server is active and accepting HTTP requests before going further here, and also that the DNS settings in your account with us are set correctly.
The origin server was too overloaded to respond
Ensure that the origin server isn’t overloaded. If it is, it could be dropping requests. Generally speaking, a good thing to check is the load average. On Linux/Unix, you can check that by running the command ‘w’ on the command line, or by checking using the ‘top’ command. What constitutes a high load based on the load value can differ depending on the computer and the software running on it, but generally speaking a load average of over 10-20 or so could mean that the server is overloaded. It’s best to check with your hosts or a system administrator about this if you are unsure.
The origin has a firewall (or rate-limiter) that is blocking our requests
This is the most common cause of intermittent 522 errors. Key things to check initially are-
Make sure that you're not blocking Cloudflare IPs in .htaccess, iptables , or your firewall.
Make sure your hosting provider isn't rate limiting or blocking IP requests from the Cloudflare IPs and ask them to whitelist the IP addresses mentioned at the address
When traffic flows through Cloudflare for a website, the origin will initially see the requests as coming from us. Most of the requests for the website through Cloudflare will appear to come from only a handful of our IP addresses. Because of that, this can often trigger firewalls and IP rate-limiters to block requests from us, thinking that the website is under attack. CPHulk (which comes with cPanel) and other services have been known to do this. Top stop that from happening, make sure that the IP addresses mentioned
have been whitelisted, or disable the rate-limiter altogether.
There is a network routing issue between Cloudflare and the origin web server
This is is more difficult to troubleshoot than the other causes, and it’s best to make sure that the other potential causes have been ruled-out before checking this. If you believe this is the case, please raise a support ticket with our support team. Useful information to provide with this would be-
Information on what you have checked so far.
An MTR or traceroute from your server to one of our IP addresses, preferably to one of the IP addresses you have seen requests from us in the past. You can find more information on how to run an MTR or Traceroute .
The origin server has keepalives disabled
Cloudflare uses
to improve performance. Disabling it will cause connections from to fail and return 522s in some circumstances. This feature is enabled by default in current versions of most major web servers, so unless you've explicitly disabled it, this shouldn't be an issue.
What actually triggers a 522 error?
A 522 error response is returned when Cloudflare could not establish a TCP connection to the website’s origin server.
When someone visits a Cloudflare-enabled website, a connection is established between Cloudflare and the website's origin server. To establish a connection, TCP uses a three-way handshake.
SYN: Cloudflare sends three SYN packets to the origin server.
SYN+ACK: In response, the origin server replies with a SYN+ACK.
ACK: Finally, Cloudflare sends an ACK back to the origin server.
At this point, both Cloudflare and the origin server have received an acknowledgement of the connection and communication is established. If the origin server does not send a SYN+ACK back to Cloudflare within 15 seconds, a 522 error will occur and the connection is closed.
Here is a diagram illustrating a successful TCP handshake:
Here is an example where the SYN+ACK is not returned from the origin server within 15 seconds, triggering the 522 timeout:
Another condition for the 522 timeout occurs when the origin responds with a SYN+ACK and established a TCP connection, but never responds to the request with an ACK within 90 seconds (A 524 condition ACKs the request, but waits too long to send the response). Here is an illustration detailing this scenario:
Checking for these conditions with your server administrator or hosting provider is the best way to resolve these errors. If there is a network problem, a
or MTR from the site origin can be useful (linked to below).
If you continue to see 522 errors after ruling out the aforementioned possibilities and troubleshooting the issue, contact Cloudflare Support for further investigation.
Reference Material
149 out of 305 found this helpful
Popular questions: , ,Oracle 客户端连接时报ORA-01019错误总结-Oracle教程-数据库-壹聚教程网Oracle 客户端连接时报ORA-01019错误总结
本文章总结了大多数网友在使用orace数据库是出现的一个客户端连接时报ORA-01019错误收集总结，有需要的朋友可参考一下。
在.net+oracle开发中,发布web程序的时候,有是会遇到该错误 ora-01019
ORA-01019 unable to allocate memory in the user side
Cause: The user side memory allocator returned an error.
Action: Increase the size of the process heap or switch to the old set of calls.
或者 错误,不能从进程获得上下文.
此错误是由于oracle或者microsoft的bug引起.(其实是,iis的访问权限的控制太高).
解决方法:&
一:为ORACLE_HOME目录,添加network services 用户组的访问权限,并将权限继承到子目录.重启机器.
二:提高虚拟路径对应的应用程序池,执行用户的权限.(该方法本人认为对带来不安全因素)
令,本错误有时候提示是,需要安装oracle7.13版本客户端以上.解决方法同上.
在Win8企业版64位环境下，连接Oracle11g 服务端，搞了整整两天，特将过程分享出来，供有需要的同学参考。
本机环境：
1、服务端：Oracle 11g R2 64位，安装路径E:/Org12
官方下载：/technetwork/database/enterprise-edition/downloads/index.html
2、客户端：
（1）Instant Client ，轻量级，安装路径E:/Oracle11/client
/technetwork/database/features/instant-client/index-097480.html
（2）32-bit Oracle Data Access Components (ODAC) with Oracle Developer Tools for Visual Studio,安装路径E:/Org12/Product/11.2.0/client_1
/technetwork/topics/dotnet/utilsoft-086879.html?ssSourceSiteId=otncn&
&用客户端三种工具去连Oracle服务端，结果：
第一种：Oracle自带的SQL Deveploer工具，基本没问题！也不需要什么客户端配置。
/technetwork/developer-tools/sql-developer/downloads/index.html
第二种，用PL/SQL 9.0去连，需要copy服务端的XXapporacleproduct11.2.0servernetworkADMINtnsnames.ORA文件到客户端（1）的networkADMIN下，并删除不需要的部分，保留内容大致如下：
& (DESCRIPTION =
&&& (ADDRESS_LIST =
&&&&& (ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
&&& (CONNECT_DATA =
&&&&&& (SID =ORCL)
并用如下方式启动PL/SQL
set Path=E:/Oracle11/client
rem 服务端路径： E:Org12product11.2.0dbhome_1BIN
set ORACLE_HOME=E:/Oracle11/client
set TNS_ADMIN=E:/Oracle11/client
set NLS_LANG=AMERICAN_AMERICA.AL32UTF8
start E:/Oracle11/PL_SQL/plsqldev.exe此时OK。
这个问题网上查找很久，尝试的解决方法很多，但最终我的方案是：
1、删除Oracle服务端；方法可以在网上搜，要删干净；
2、删除ODAC及所有组件；
3、保留Instant Client及其安装目录，主要是networkADMINtnsnames.ORA
4、重新安装Oracle服务端；
此时接所有客户端连接完全正常！
1、刚开始怀疑是64位Oracle驱动路径（x86）引起的bug，最后得出的结论是同一台机器，最好不要装两个Oracle客户端 ，服务端+客户端也不推荐，会引起一些潜在的问题，原因不明。
2、64位的Oracle服务端+32位的Oracle客户端，会有一些潜在的问题，最好32位对32位。
3、安装Oracle 11g R2 EX时，会在环境变量Path前面加上&e:Org12apporacleproduct11.2.0;&，注意是两个分号，须删除一个；这个不知道是安装程序的BUG？
今天开发的同事碰到了这个ORA-1019错误。
详细的错误信息为：
Microsoft OLE DB Provider for ODBC Drivers错误''
[Microsoft][ODBC driver for Oracle][Oracle]Error while trying to retrieve text for error ORA-01019
/includes/data_func.asp，行12
而Oracle文档上对这个错误的描述为：
ORA-01019: unable to allocate memory in the user
Cause: The user side memory allocator returned error.
Action: Increase the processes heap size or switch to the old set of calls.
从错误描述上看，似乎是内存分配的问题，但是客户端服务器上的内存有2G，而且并没有启动什么程序，显然不是简单的内存不足的问题。
不过问题多半是出在客户端程序上，检查了一下metalink，发现文档ID 91906.1中提到的问题可能和当前类似。导致这个问题的原因似乎是ODBC没有使用Oracle提供的驱动程序，而是使用了ORACLE_HOME之外系统提供的驱动。
又通过GOOGLE搜索了一下，找到了一篇文章，其中包含下面的描述：
You must set the following environment variables:
ORACLE_HOME
&Specifies the top-level directory in which Oracle is installed.
&Specifies the location of configuration files, for example, $ORACLE_HOME/network/admin. After installation Oracle creates the configuration files under /var/opt/oracle. If listener.ora and tnsnames.ora are in this directory, you might not need to set TNS_ADMIN, because by default Oracle uses /var/opt/oracle.
If you do not set these environment variables properly, Oracle returns the ORA-1019 error code the first time you attempt to connect. For information on error handling,
看来问题很可能是由于没有正确设置ORACLE_HOME环境变量造成的，
在WINDOWS中设置系统环境变量，重启系统后，问题消失。
上一页： &&&&&下一页：相关内容博客访问： 745778
博文数量： 124
博客积分： 2422
博客等级： 大尉
技术积分： 1397
注册时间：
IT168企业级官微
微信号：IT168qiye
系统架构师大会
微信号：SACC2013
分类： 服务器与存储
Oracle 11g 超时问题的处理办法
在Oracle 11G中如果一个与Oracle的通讯，长时间空闲，Oracle会将其识为Timeout，主动Kill这个Session。如何你的应用端编写的程序不能提供自动重连的功能，这样的场景你需要做以下的配置以避免应用不可用。
具体如下： 按官方文档所说，原则上INBOUND_CONNECT_TIMEOUT_listener_name应小于INBOUND_CONNECT_TIMEOUT
Oracle 11g has a problem that is session timeout problem. You can add
a row to sqlnet.ora file and listener.ora file to resolve session
timeout problem.
sqlnet.ora
Note : Add this line to below of sqlnet.ora file.
INBOUND_CONNECT_TIMEOUT=3600
listener.ora
Note : Add this line to below of listener.ora file.
INBOUND_CONNECT_TIMEOUT_LISTENER=2400
注意：如何你的LISTENER名字为SBSBSB的话，上面的listener.ora& 就要改成 sbsbsb.ora ：INBOUND_CONNECT_TIMEOUT_SBSBSB=2400
如果你不是SB的话，上面的说明应该可以看明白的。
官方说明文档：
SQLNET.INBOUND_CONNECT_TIMEOUT
Use the SQLNET.INBOUND_CONNECT_TIMEOUT parameter to specify the time, in seconds, for a client to connect with the database server and provide the necessary authentication information.
If the client fails to establish a connection and complete authentication in the time specified, then the database server terminates the connection. In addition, the database server logs the IP address of the client and an ORA-12170: TNS:Connect timeout occurred error message to the sqlnet.log file. The client receives either an ORA-12547: TNS:lost contact or an ORA-12637: Packet receive failed error message.
Without this parameter, a client connection to the database server can stay open indefinitely without authentication. Connections without authentication can introduce possible denial-of-service attacks, whereby malicious clients attempt to flood database servers with connect requests that consume resources.
To protect both the database server and the listener, Oracle Corporation recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying values for these parameters, consider the following recommendations:
&&& Set both parameters to an initial low value.
&&& Set the value of the INBOUND_CONNECT_TIMEOUT_listener_name parameter to a lower value than the SQLNET.INBOUND_CONNECT_TIMEOUT parameter.
For example, you can set INBOUND_CONNECT_TIMEOUT_listener_name to 2 seconds and INBOUND_CONNECT_TIMEOUT parameter to 3 seconds. If clients are unable to complete connections within the specified time due to system or network delays that are normal for the particular environment, then increment the time as needed.
Oracle Net Services Administrator's Guide for information about configuring these parameters
60 seconds
SQLNET.INBOUND_CONNECT_TIMEOUT=3
阅读(10314) | 评论(1) | 转发(2) |
相关热门文章
给主人留下些什么吧！~~
这家伙不错，学习了&&http://www.taohaoxueli.net一直在关注你
请登录后评论。