精华内容
下载资源
问答
  • Inbound mail

    2020-11-25 12:07:41
    m currently evaluating django-anymail (with mailgun) which I will be using inbound mail with and see on your roadmap that you intend to add inbound mail support. Did you have a structure/plan in mind ...
  • Adding inbound shipment

    2020-12-09 05:32:29
    Inbound Shipment, Inbound Shipment Items and Inbound Shipment Item List. This is a new record introduced in NetSuite 2017.2 release notes</p><p>该提问来源于开源项目:NetSweet/netsuite</p></div>
  • about inbound license

    2020-12-26 02:52:14
    t find the inbound agreement in CONTRIBUTING.md. In general, the license should be 'Developer Certificate of Origin, version 1.1'. My boss want to know the inbound license of this project and...
  • Inbound references service

    2020-12-09 02:03:38
    <p>For binaries when requesting the inbound references on the <code>fcr:metadata</code> endpoint you will get both references to the actual binary URI and the <code>fcr:metadata</code> URI. ...
  • Inbound DKIM check

    2020-12-01 15:36:22
    <div><p>Hi, <p>Are there any plans to check DKIM on inbound mails? <p>Kind regards, Hans Mannaerts</p><p>该提问来源于开源项目:Pro/dkim-exchange</p></div>
  • Outbound to Inbound

    2020-12-08 23:10:05
    Should be the Inbound not Outbound <h1>Module: 00 <h2>Lab/Demo: 00 <p>Fixes # . <p>Changes proposed in this pull request: <h2>- <p>-</p><p>该提问来源于开源项目:MicrosoftLearning/AZ500-...
  • Inbound filter question

    2020-12-28 05:20:02
    <div><p>The inbound filter, defined in <code>BusAutoConfiguration.inboundFilter(), includes the condition <p><code>!serviceMatcher().isFromSelf(event)</code></p> <p>This seems to ensure that ...
  • <div><p>I accidentally added the same CIDR twice in the <code>alb.ingress.kubernetes.io/inbound-cidrs</code> annotation and the effect was all inbound rules on the security group were cleared ...
  • <div><p>As suggested by We want to bisect inbound if last good revision and first bad revision are set, so I added a condition for this. Let me know if this is the correct way to implement it.</p><p>...
  • <div><p>This change adds a codepath to the Thrift inbound encoding, such that it can answer requests with or without a Thrift envelope, responding with the same kind of envelope.</p><p>该提问来源于...
  • INBOUND_CONNECT_TIMEOUT与SQLNET.INBOUND_CONNECT_TIMEOUT小结 关于sqlnet.ora的参数SQLNET.INB...
        


    INBOUND_CONNECT_TIMEOUT与SQLNET.INBOUND_CONNECT_TIMEOUT小结


    关于sqlnet.ora的参数SQLNET.INBOUND_CONNECT_TIMEOUT,它表示等待用户认证超时的时间,单位是秒,缺省值是60秒,如果用户认证超时了,服务器日志alert.log显示出错信息"WARNING: inbound connection timed out (ORA-3136)",sqlnet.log里面出现TNS-12535: TNS:operation timed out错误信息。

       关于listener.ora的参数inbound_connect_timeout_监听器名,它表示等待用户连接请求超时的时间,单位是秒,缺省值是60秒,如果连接请求超时了,监听器日志listener.log显示出错信息"TNS-12525: TNS:listener has not received client's request in time allowed"。

       其中sqlnet.ora里面的参数为SQLNET.INBOUND_CONNECT_TIMEOUT, listener.ora里面的参数设置为INBOUND_CONNECT_TIMEOUT_listener_name ,其中根据监听名字来替换listener_name。官方文档关于两者的介绍如下所示:

     

    SQLNET.INBOUND_CONNECT_TIMEOUT parameter in sqlnet.ora  on the database server

    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.

    INBOUND_CONNECT_TIMEOUT_listener_name in listener.ora

    Specify the time, in seconds, for the client to complete its connect request to the listener after the network connection had been established.

    If the listener does not receive the client request in the time specified, then it terminates the connection. In addition, the listener logs the IP address of the client and an ORA-12525: TNS:listener has not received client’s request in time allowed error message to the listener.log file

     

    查看inbound_connect_timeout值

    1:查看SQLNET.INBOUND_CONNECT_TIMEOUT的设置值,一般进入$ORACLE_HOME/network/admin下,查看sqlnet.ora参数文件即可。

    2:查看监听INBOUND_CONNECT_TIMEOUT参数,可以查看listener.ora参数文件。但是有时候,例如默认情况,参数文件里面没有设置这个参数,或是有些动态监听没有配置listener.ora,那么可以使用lsnrctl命令查看,如下所示:

    LSNRCTL> show
    The following operations are available after show
    An asterisk (*) denotes a modifier or extended command:

    rawmode                     displaymode
    rules                       trc_file
    trc_directory               trc_level
    log_file                    log_directory
    log_status                  current_listener
    inbound_connect_timeout     startup_waittime
    snmp_visible                save_config_on_stop
    dynamic_registration

    LSNRCTL> show inbound_connect_timeout
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    LISTENER parameter "inbound_connect_timeout" set to 60
    The command completed successfully
    LSNRCTL>

    clip_image001

     

    设置SQLNET.INBOUND_CONNECT_TIMEOUT值

    我们首先设置SQLNET.INBOUND_CONNECT_TIMEOUT为30秒,这个参数修改后立即生效,不需要做任何其它操作。

    [oracle@DB-Server admin]$ vi sqlnet.ora
    # sqlnet.ora Network Configuration File: /u01/app/oracle/product/10.2.0/db_1/network/admin/sqlnet.ora
    # Generated by Oracle configuration tools.

    NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
    SQLNET.INBOUND_CONNECT_TIMEOUT=30


    C:\Users>sqlplus /@mytest

    SQL*Plus: Release 11.2.0.1.0 Production on 星期日 2月 28 10:57:09 2016

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

    ERROR:
    ORA-01017: invalid username/password; logon denied


    请输入用户名:

    clip_image002

     

    当30秒后,此时,在sqlnet.log里面就能看到新增了一条关于TNS-12535的错误记录,其中10.20.34.14是我客户端的IP地址。

    clip_image003

     

    告警日志里面你会看到WARNING: inbound connection timed out (ORA-3136)错误。 有意思的是,监听日志里面你不会看到任何错误信息。(可以用了对比这两个参数的区别)

    clip_image004

     

    设置INBOUND_CONNECT_TIMEOUT_listener_name的值

    这个参数可以通过lsnrctl命令设置,如下所示,当然最简单的还是设置listener.ora参数文件。这个参数也是立即生效,不需要重启监听。

    LSNRCTL> show inbound_connect_timeout
    NL-00853: undefined show command "inbound_connect—meout".  Try "help show"
    LSNRCTL> show inbound_connect_timeout
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    LISTENER parameter "inbound_connect_timeout" set to 60
    The command completed successfully
    LSNRCTL> set inbound_connect_timeout 20
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    LISTENER parameter "inbound_connect_timeout" set to 20
    The command completed successfully
    LSNRCTL> show inbound_connect_timeout
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    LISTENER parameter "inbound_connect_timeout" set to 20
    The command completed successfully
    LSNRCTL>

    clip_image005

    此时我们用telnet来模拟用户连接请求超时的时间,如下所示,当超过20秒,就会自动退出

    [root@test ~]# time telnet 192.168.9.124 1521
    Trying 192.168.9.124...
    Connected to 192.168.9.124 (192.168.9.124).
    Escape character is '^]'.
    Connection closed by foreign host.

    real    0m20.019s
    user    0m0.001s
    sys     0m0.003s

    此时在listener.log里面,你就能看到TNS-12525的错误,如下所示

    28-FEB-2016 11:32:20 * <unknown connect data> * (ADDRESS=(PROTOCOL=tcp)(HOST=10.20.34.14)(PORT=38051)) * establish * <unknown sid> * 12525

    TNS-12525: TNS:listener has not received client's request in time allowed

    TNS-12535: TNS:operation timed out

    TNS-12606: TNS: Application timeout occurred

    注意:set inbound_connect_timeout只对当前环境生效,如果重启监听服务,则会失效,如下所示

    LSNRCTL> set inbound_connect_timeout 18
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    LISTENER parameter "inbound_connect_timeout" set to 18
    The command completed successfully
    LSNRCTL> reload
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    The command completed successfully
    LSNRCTL> show inbound_connect_timeout
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1)))
    LISTENER parameter "inbound_connect_timeout" set to 60
    The command completed successfully

    clip_image006

    此时需要使用命令set save_config_on_stop on保存配置信息,使其永远生效。但是我测试发现,动态监听也无法使用set save_config_on_stop on保存配置信息,需要修改配置文件(注意,修改listener.ora,需要重启监听使之生效)。如下所示

    clip_image007

     

    关于两者之间的关系,一般INBOUND_CONNECT_TIMEOUT_listener_name的值应该低于SQLNET.INBOUND_CONNECT_TIMEOUT的值,官方文档介绍如下,

    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.




    About Me

    ........................................................................................................................

    ● 本文作者:小麦苗,部分内容整理自网络,若有侵权请联系小麦苗删除

    ● 本文在itpub、博客园、CSDN和个人微 信公众号( xiaomaimiaolhr)上有同步更新

    ● 本文itpub地址: http://blog.itpub.net/26736162

    ● 本文博客园地址: http://www.cnblogs.com/lhrbest

    ● 本文CSDN地址: https://blog.csdn.net/lihuarongaini

    ● 本文pdf版、个人简介及小麦苗云盘地址: http://blog.itpub.net/26736162/viewspace-1624453/

    ● 数据库笔试面试题库及解答: http://blog.itpub.net/26736162/viewspace-2134706/

    ● DBA宝典今日头条号地址: http://www.toutiao.com/c/user/6401772890/#mid=1564638659405826

    ........................................................................................................................

    ● QQ群号: 230161599 、618766405

    ● 微 信群:可加我微 信,我拉大家进群,非诚勿扰

    ● 联系我请加QQ好友 646634621 ,注明添加缘由

    ● 于 2019-09-01 06:00 ~ 2019-09-31 24:00 在西安完成

    ● 最新修改时间:2019-09-01 06:00 ~ 2019-09-31 24:00

    ● 文章内容来源于小麦苗的学习笔记,部分整理自网络,若有侵权或不当之处还请谅解

    ● 版权所有,欢迎分享本文,转载请保留出处

    ........................................................................................................................

    小麦苗的微店https://weidian.com/s/793741433?wfr=c&ifr=shopdetail

    小麦苗出版的数据库类丛书http://blog.itpub.net/26736162/viewspace-2142121/

    小麦苗OCP、OCM、高可用网络班http://blog.itpub.net/26736162/viewspace-2148098/

    小麦苗腾讯课堂主页https://lhr.ke.qq.com/

    ........................................................................................................................

    使用 微 信客户端扫描下面的二维码来关注小麦苗的微 信公众号( xiaomaimiaolhr)及QQ群(DBA宝典)、添加小麦苗微 信, 学习最实用的数据库技术。

    ........................................................................................................................

    欢迎与我联系

     

     



    来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/26736162/viewspace-2656499/,如需转载,请注明出处,否则将追究法律责任。

    展开全文
  • Inbound process in CRM

    2019-07-15 10:59:36
    如果通过ERP端的debug 能确认数据已经正确地在ERP端assemble完成并且已经正常传输到CRM端,但是最后到tcode COMMPR01里查看发现ERP端的change并没有成功更新到CRM端,则需要debug CRM端的inbound processing: ...

    Created by Jerry Wang, last modified on Sep 12, 2014

    如果通过ERP端的debug 能确认数据已经正确地在ERP端assemble完成并且已经正常传输到CRM端,但是最后到tcode COMMPR01里查看发现ERP端的change并没有成功更新到CRM端,则需要debug CRM端的inbound processing:

    对于product 的middleware scenario, CRM端的inbound processing在function module COM_PRODUCT_MAT_VALIDATE 里处理:

    clipboard1

     

    在debugger里观察输入参数:

    clipboard2

     

    clipboard3

     

    clipboard4

     

    BDOC name和其validation handler function module的mapping关系通过cl_smw_flow=>__get_validation_module获得:

    clipboard5

     

    通过tcode SMW3FDIF维护:

    clipboard6

    展开全文
  • m properly handling the inbound event via handle_inbound(event_payload) but am struggling to get at the attachment array elements. <p>Thanks, <p>Jason</p><p>该提问来源于开源项目:evendis/...
  • 定义Inbound IDOC

    2019-10-08 08:28:55
    R3接收IDOC的定义,这种办法是一步一步手工创建,也可以通过Function Module直接创建Inbound /oubbound IDOC, http://www.cnblogs.com/byfhd/archive/2008/05/10/1191063.html In the previous posts, we have ...

    R3接收IDOC的定义,这种办法是一步一步手工创建,也可以通过Function Module直接创建Inbound /oubbound IDOC,

    http://www.cnblogs.com/byfhd/archive/2008/05/10/1191063.html

     

    In the previous posts, we have covered the XI specific aspects of creating your first XI scenario. Now, let us understand what settings are required so that the R/3 partner system is able to receive and post the IDoc data. Let us start by creating the inbound function module.

    Create Inbound Function Module – Transaction SE37

    In the receiving system, create a function module Z_IDOC_INPUT_ZRZSO_MT using SE37. Below, I have described the logic for the same:

    Add Include MBDCONWF. This include contains predefined ALE constants
    Loop at EDIDC table

    • Check if the message type is ZRZORDER. Otherwise raise WRONG_FUNCTION_CALLED exception
    • Loop at EDIDD table
      • Append data from the segments to appropriate internal tables
      • For example: append data from ZRZSEG1 segment to the internal table of type ZCUSTOMERS
    • Update the DDic tables from internal tables
    • Depending on the result of the update, fill the IDoc status record (type BDIDOCSTAT) and append it to the corresponding table.
      • Status 53 => Success
      • Status 51 => Error

    You can download the sample ABAP code for the above function module here.

    Assign Function Module to Logical message – Transaction WE57

    • Create a new entry
    • Specify name of the Function Module as Z_IDOC_INPUT_ZRZSO_MT
    • Also, specify Type as F, Basic IDoc type as ZRZORDER, Message type as ZRZSO_MT and Direction as 2 (Inbound)
    • Save the entry

    Define Input method for Inbound Function Module – Transaction BD51

    • Create a new entry
    • Provide Function Module name as Z_IDOC_INPUT_ZRZSO_MT
    • Specify the Input method as 2
    • Save the entry

    Create a Process code – Transaction WE42

    • Create a new Process Code ZPCRZ
    • Select Processing with ALE Service
    • Choose Processing type as Processing by function module
    • Save the entry
    • On the next screen, select your function module from the list
    • Save the changes
    • On the next screen, select your function module from the list
    • Save the changes

    Define Logical system for the partner - Transaction SALE or BD54

    • Define a Logical system LOGSYS100 using transaction SALE or BD54 to identify the partner business system

    Create a Partner profile – Transaction WE20

    Partner Profiles - WE20

    • Go to transaction WE20 and create a partner profile corresponding to the logical system created above
    • Add the message type ZRZSO_MT and the previously created process code ZPCRZ in the inbound parameters of the partner profile
    • Save the profile

    Send and Receive Data

    • Put the input XML file in the appropriate directory on the file system
    • Monitor the directory. After a few seconds, the file should get marked as read-only
    • Choose monitoring -> Integration Engine monitoring (transaction SXMB_MONI)
    • Choose ‘Monitor for Processed XML Messages’
    • Your message should appear with a checkered flag (processed successfully)
    • Check the IDoc status in target R/3 system using transaction WE02
    • You may also verify the data records in DDic tables using SE16

    SAP Transaction WE02

    Thus using a small example, we have learned how to integrate different systems so that they can communicate with each other using SAP Exchange Infrastructure. In further posts we shall discuss more XI concepts to give you better understanding of applying your XI knowledge.

    转:http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/

     

    转载于:https://www.cnblogs.com/byfhd/archive/2008/09/15/1291282.html

    展开全文
  • INBOUND_CONNECT_TIMEOUT与SQLNET.INBOUND_CONNECT_TIMEOUT参数解读测试查看inbound_connect_timeout值SQLNET.INBOUND_CONNECT_TIMEOUTINBOUND_CONNECT_TIMEOUT_listener_name总结 参数解读 客户端先连接listener,...

    参数解读

    客户端先连接listener,然后listener fork出一个server进程,然后进行登录验证。
    连接不是说连接成功了,而是客户端先和监听建立了连接,监听然后鉴权,密码对了才给你连接到数据库。简单的过程如下:
    在这里插入图片描述
    具体这两个参数起作用的阶段不一样:
    关于sqlnet.ora的参数SQLNET.INBOUND_CONNECT_TIMEOUT,它表示等待用户认证超时的时间,单位是秒,缺省值是60秒,如果用户认证超时了,服务器日志alert.log显示出错信息"WARNING: inbound connection timed out (ORA-3136)",sqlnet.log里面出现TNS-12535: TNS:operation timed out错误信息。

    关于listener.ora的参数inbound_connect_timeout_监听器名,它表示等待用户连接请求超时的时间,单位是秒,缺省值是60秒,如果连接请求超时了,监听器日志listener.log显示出错信息"TNS-12525: TNS:listener has not received client’s request in time allowed"。

    在这里插入图片描述

    其中sqlnet.ora里面的参数为SQLNET.INBOUND_CONNECT_TIMEOUT, listener.ora里面的参数设置为INBOUND_CONNECT_TIMEOUT_listener_name ,其中根据监听名字来替换listener_name。官方文档关于两者的介绍如下所示:

    SQLNET.INBOUND_CONNECT_TIMEOUT
    Purpose

    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.

    The default value of this parameter is appropriate for typical usage scenarios. However, if you need to explicitly set a different value, then Oracle recommends setting this parameter in combination with the INBOUND_CONNECT_TIMEOUT_listener_name parameter in the listener.ora file. When specifying the values for these parameters, note 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 SQLNET.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.

    Default

    60 seconds

    Example

    SQLNET.INBOUND_CONNECT_TIMEOUT=3
    See Also:

    •“Control Parameters” for additional information about INBOUND_CONNECT_TIMEOUT_listener_name

    •Oracle Net Services Administrator’s Guide for additional information about configuring these parameters

    INBOUND_CONNECT_TIMEOUT_listener_name in listener.ora

    Specify the time, in seconds, for the client to complete its connect request to the listener after the network connection had been established.

    If the listener does not receive the client request in the time specified, then it terminates the connection. In addition, the listener logs the IP address of the client and an ORA-12525: TNS:listener has not received client’s request in time allowed error message to the listener.log file

    一个表示等待用户认证超时的时间,一个表示等待用户连接请求超时的时间.

    测试

    查看inbound_connect_timeout值

    1:查看SQLNET.INBOUND_CONNECT_TIMEOUT的设置值,一般进入$ORACLE_HOME/network/admin下,查看sqlnet.ora参数文件即可。

    2:查看监听INBOUND_CONNECT_TIMEOUT参数,可以查看listener.ora参数文件。但是有时候,例如默认情况,参数文件里面没有设置这个参数,或是有些动态监听没有配置listener.ora,那么可以使用lsnrctl命令查看,如下所示:

    [oracle@oracle11g admin]$ lsnrctl       
    
    LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 21-DEC-2020 16:30:00
    
    Copyright (c) 1991, 2013, Oracle.  All rights reserved.
    
    Welcome to LSNRCTL, type "help" for information.
    
    LSNRCTL> show 
    The following operations are available after show
    An asterisk (*) denotes a modifier or extended command:
    
    rawmode                              displaymode                          
    rules                                trc_file                             
    trc_directory                        trc_level                            
    log_file                             log_directory                        
    log_status                           current_listener                     
    inbound_connect_timeout              startup_waittime                     
    snmp_visible                         save_config_on_stop                  
    dynamic_registration                 enable_global_dynamic_endpoint       
    oracle_home                          pid                                  
    connection_rate_limit                valid_node_checking_registration     
    registration_invited_nodes           registration_excluded_nodes          
    
    LSNRCTL> show inbound_connect_timeout
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    LISTENER parameter "inbound_connect_timeout" set to 60
    The command completed successfully
    

    oracle默认为60s

    SQLNET.INBOUND_CONNECT_TIMEOUT

    我们首先设置SQLNET.INBOUND_CONNECT_TIMEOUT为10秒,
    [oracle@oracle11g admin]$ cat sqlnet.ora
    SQLNET.INBOUND_CONNECT_TIMEOUT=10
    直接编辑sqlnet.ora文件,不用重启,直接生效。

    模拟输错密码,认证失败

    [oracle@11gasm admin]$ sqlplus system/or@zhuo
    
    SQL*Plus: Release 11.2.0.4.0 Production on Mon Dec 21 15:50:22 2020
    
    Copyright (c) 1982, 2013, Oracle.  All rights reserved.
    
    ERROR:
    ORA-01017: invalid username/password; logon denied
    
    
    Enter user-name:
    

    listener.log立马会有如下显示:

    Mon Dec 21 15:51:07 2020
    21-DEC-2020 15:51:07 * (CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=zhuo)(CID=(PROGRAM=sqlplus@11gasm)(HOST=11gasm)(USER=oracle))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.1.11.12)(PORT=24635)) * establish * zhuo * 0
    

    监听日志显示,客户端和监听的连接已经建立(establish),连接成功。

    当10秒后。
    alert日志

    ***********************************************************************
    
    Fatal NI connect error 12170.
    
      VERSION INFORMATION:
            TNS for Linux: Version 11.2.0.4.0 - Production
            Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
            TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.4.0 - Production
      Time: 21-DEC-2020 15:51:17
      Tracing not turned on.
      Tns error struct:
        ns main err code: 12535
        
    TNS-12535: TNS:operation timed out
        ns secondary err code: 12606
        nt main err code: 0
        nt secondary err code: 0
        nt OS err code: 0
      Client address: (ADDRESS=(PROTOCOL=tcp)(**HOST=10.1.11.12**)(PORT=24635))
    **WARNING: inbound connection timed out (ORA-3136)**
    

    在alert里面就能看到新增了一条关于TNS-12535的错误记录,其中10.1.11.12是我客户端的IP地址。
    而且会看到WARNING: inbound connection timed out (ORA-3136)错误。有意思的是,监听日志里面你不会看到任何错误信息。

    INBOUND_CONNECT_TIMEOUT_listener_name

    这个参数可以通过lsnrctl命令设置,如下所示,当然最简单的还是设置listener.ora参数文件。在监听配置文件里面,必须重启生效
    设置listener的连接超时时间为5:
    [oracle@oracle11g admin]$ cat listener.ora
    INBOUND_CONNECT_TIMEOUT_LISTENER=5

    此时我们用telnet来模拟用户连接请求超时的时间,如下所示,当超过20秒,就会自动退出

    [oracle@11gasm admin]$ time telnet 10.1.11.8 1521
    Trying 10.1.11.8…
    Connected to 10.1.11.8.
    Escape character is ‘^]’.
    Connection closed by foreign host.

    real 1m0.034s —连接用了1s,前面的设置没生效
    user 0m0.001s
    sys 0m0.000s

    listener.log日志报错如下:

    Mon Dec 21 16:42:05 2020
    21-DEC-2020 16:42:05 * <unknown connect data> * (ADDRESS=(PROTOCOL=tcp)(HOST=10.1.11.12)(PORT=25836)) * establish * <unknown sid> * 12525
    TNS-12525: TNS:listener has not received client's request in time allowed
     TNS-12535: TNS:operation timed out
      TNS-12606: TNS: Application timeout occurred
    

    alter日志里面没有报错。

    我们接下来重启下监听:

    [oracle@oracle11g admin]$ lsnrctl stop
    [oracle@oracle11g admin]$ lsnrctl start
    [oracle@oracle11g admin]$ lsnrctl
    
    LSNRCTL for Linux: Version 11.2.0.4.0 - Production on 21-DEC-2020 16:45:46
    
    Copyright (c) 1991, 2013, Oracle.  All rights reserved.
    
    Welcome to LSNRCTL, type "help" for information.
    
    LSNRCTL> show
    The following operations are available after show
    An asterisk (*) denotes a modifier or extended command:
    
    rawmode                              displaymode                          
    rules                                trc_file                             
    trc_directory                        trc_level                            
    log_file                             log_directory                        
    log_status                           current_listener                     
    inbound_connect_timeout              startup_waittime                     
    snmp_visible                         save_config_on_stop                  
    dynamic_registration                 enable_global_dynamic_endpoint       
    oracle_home                          pid                                  
    connection_rate_limit                valid_node_checking_registration     
    registration_invited_nodes           registration_excluded_nodes          
    
    LSNRCTL> show inbound_connect_timeout
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    LISTENER parameter "inbound_connect_timeout" set to 5
    The command completed successfully
    

    看到已经生成为5s了。再次测试:
    [oracle@11gasm admin]$ time telnet 10.1.11.8 1521
    Trying 10.1.11.8…
    Connected to 10.1.11.8.
    Escape character is ‘^]’.
    Connection closed by foreign host.

    real 0m5.003s --已经生效,5s连接断开
    user 0m0.000s
    sys 0m0.000s

    listener报错如下:

    Mon Dec 21 16:46:46 2020
    21-DEC-2020 16:46:46 * <unknown connect data> * (ADDRESS=(PROTOCOL=tcp)(HOST=10.1.11.12)(PORT=25972)) * establish * <unknown sid> * 12525
    TNS-12525: TNS:listener has not received client's request in time allowed
     TNS-12535: TNS:operation timed out
      TNS-12606: TNS: Application timeout occurred
    

    此时在listener.log里面,你就能看到TNS-12525的错误
    格式为:

    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE

    总结

    在这里插入图片描述

    参考:故障排除指南 ORA-3136:WARNING Inbound Connection Timed Out (Doc ID 2331569.1)
    Description of Parameter SQLNET.INBOUND_CONNECT_TIMEOUT (Doc ID 274303.1)
    Troubleshooting ORA-3136 Connection Timeouts Errors - Database Diagnostics (Doc ID 730066.1)
    http://www.killdb.com/2020/03/18/about-ora-3136/

    展开全文
  • 语言:español 扩展是能够在Inbound Manager Pro平台上显示自己的WordPress作为Iframe在此扩展名中,您可以通过iframe在Inbound Manager Pro平台中包含您自己的WordPress。
  • t closing pending inbound peer connections on shutdown. This can prevent <code>xud</code> from shutting down gracefully. <p>Edit: Per offer, it's not a pending connection that causes this issue ...
  • Inbound.org是一个由营销专业人员组成的社区新闻网站,专注于入站营销的思想。 您可能会认为入站营销是一种很好的营销。 您知道,写博客,播客,制作视频,赞助很酷的网站(#wink)等等。 那里总是有许多有趣而有用...
  • <div><p>It is not possible to add an email account to group inbound email.</p><p>该提问来源于开源项目:espocrm/espocrm</p></div>
  • 通过 PCIE Inbound

    千次阅读 2016-04-05 23:01:27
    Inbound:PCI域访问存储器域 Outbound:存储器域访问PCI域 RC访问EP: RC存储器域->outbound->RC PCI域->EP PCI域->inbound->EP存储器域 EP访问RC:EP存储器域->outbound->EP PCI域->RC PCI域->inbound->RC...
  • INBOUND_DATA_ERROR not set

    2021-01-10 07:39:31
    <div><p>There seems to be an issue, that INBOUND_DATA_ERROR is not always set, when SecRequestBodyLimit is reached. We have set SecRequestBodyLimit to 10485760 (10 MB). If we try to upload a file with...
  • <p>The Check Inbound Mailboxes scheduler for function::pollMonitoredInboxesAOP fails to run with the following error when e-mails containing attachments are unread in IMAP inbox. <p><code>[FATAL] Job ...
  • IDoc Inbound Process

    千次阅读 2015-02-05 10:52:24
    http://erpwhiz.com/ALE_IDOC/Idoc%20inbound%20process.html IDoc Inbound Process ...The inbound process uses components such as the IDoc type, the partner profile, the port definition, posting prog
  • <div><p>PowerShell commands and model changes for configuring inbound NAT pools on the load balancer. Test cases for inbound NAT pools and their corresponding SessionRecords. Updating package version ...
  • <div><p>The documentation does not address how to send replies to inbound synchronous KDB calls. For example, if the python code registers with a KDB server and then receives synchronous requests to ...
  • Inbound tags for IRCv3

    2020-12-09 03:57:44
    <div><p>These commits add support for inbound IRCv3 tags. Applications can access them from the IrcMessageData.Tags property, which is a Dictionary indexed by tag name. The raw tags string is also ...
  • Email inbound process is done by user SAPCONNECT so that you cannot debug it via normal debugging approach. then you have to follow the steps below to debug: (1) Inside one entry like below into table...
  • <p><strong>What this PR does / why we need it</strong>: Uses the new Service interface to break out inbound NAT rule creation / deletion from the network interface service. <p><strong>Which issue(s) ...
  • Laravel开发-postmark-inbound-laravel 这是一个用于邮戳的入站分析器,用于Laravel。
  • ve been running inbound webhooks via djrill decorators for quite some time now. When suddenly they stopped working. Currently the signals are not triggering the decorated webhook functions, but the ...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 4,833
精华内容 1,933
关键字:

inbound