IBM SQL3. 00. 81. N TCPIP communication errors This document lists SQL3. N TCP/IP communication protocol errors and recommended action plans associated with them. The communication protocol errors depend on the platform you are working on. Each protocol error has its own definition and corresponding action plan. Problem Details. The SQL3. N error message has the following format. SQL3. 00. 81. N A communication error has been detected. Communication protocol being used. Communication API being used. Location where the error was detected. Communication function detecting the error. Protocol specific error code(s). For example. SQL3. N A communication error has been detected. Communication protocol. TCP/IP". Communication API being used: "SOCKETS". Location. where the error was detected: "". Communication function detecting the error: "connect". Protocol specific error code(s): "1. These error messages are returned when DB2 calls operating system socket APIs that receive an error message from a component outside of DB2. These socket errors are propagated back up to DB2 which encapsulates the error inside the SQL3. N message. Root cause is outside of DB2's control which could be in the client/server network stack or network device between them. Network traces should be collected and analysed by network administrator from both client and server side to determine root cause. DB2 is the victim of SQL3. N. The following table lists protocol specific errors that can occur on different platforms and the corresponding action plans to resolve these errors. If the error code is not listed in the table, search the operating system documentation /usr/include/errno. Improve your productivity and save time. Let your system work for you. Introduction. The following document has been written to help users troubleshoot their connection problems and find a solution. To help you understand the situation. Tip. If you want the.nb! files to be kept separate from your normal files, then you can set the "Use Chunks Folder" option under Options->Aadvanced. Linux/UNIX) or System Error Codes (Windows). Windows. AIXSUNHPLinux. Short Name. Action Plan. ECONNREFUSED Connection Refused. Client attempts to establish a connection to server using an invalid IP or port. Check on server side: DB2 environment variable DB2. COMM is set such as: DB2. COMM=TCPIP DBM CFG's SVCENAME is set to the instance's port number or service name. The command to update this parameter is: "db. If service name is set by checking 'services' file to see if the name corresponds to an unused port number. Make sure DB2 server instance is started properly. Check on client's side: Node directory's entry: Service name should show the right port number or service name that corresponds to DB2 server's instance port (svcename setting) To check if server's port is opened: telnet < hostname> < port> If the command fails then the port on server is not opened and the problem is outside of DB2 area. Additional technote on ECONNREFUSED: http: //www. Windows. AIXSUNHPLinux. Short Name. Action Plan. SOCECONNABORTED Software caused a connection abort. Software closed connection If error is reported on client application which uses ODBC/CLI to connect to DB2 UDB server: Disable DB2's CLI timeout: Add 'QUERYTIMEOUTINTERVAL=0' to the db. Check if applications have any timeout. ADO timeout, VB timeout If application connects to OS3. IDTHTOIN) on OS3. This parameter sets the active thread timeout limit on OS3. Windows. AIXSUNHPLinux. Short Name. Action Plan. ECONNRESET Connection has been reset by partner. Connected partner has closed the connection. Check any timeout limit on partner side. E. g. Firewall, Application, DB2 CLI layer and etc If error is reported on client application which uses ODBC/CLI to connect to DB2 UDB server: Disable DB2's CLI timeout: Add 'QUERYTIMEOUTINTERVAL=0' to the db. Check if there's any firewall between client and server. If it has any time limit on open connection Check if applications have any timeout. ADO timeout, VB timeout. This error can also be caused by the issue described in technote_1. When a local database connection is catalogued using a different alias name than the database name, you might get error SQL3. TCPIP connection. If you get that error when when you try to connect to a database, make sure that on the machine where that database resides the database is not catalogued using a different alias name than the database name. Windows. AIXSUNHPLinux. Short Name. Action Plan. ETIMEDOUT Connection timeout. Connection has reached the network timeout limit and is terminated by network Timeout by tcpip layer TCPIP has its own timeout value, if the open connection stayed too long, TCPIP will force the connection off. Usually this is network issue Check TCPIP's KEEPALIVE setting see note. Windows. AIXSUNHPLinux. Short Name. Action Plan. EADDRINUSE The specified address already in use. A: 2 instances are starting on the same machine listening on the same port (usually would trap on db. B: A client application or agent is making an outgoing connection attempt and is using a socket that is already being used by another connection to the database or is in the wait state (2. MSL state). Usually only happens to Windows client: This is a Microsoft error. Winsock has given a port that is already in use (winsock defect) or is closed but still waiting in the wait state. Workaround for Windows: 1. Adjust the time so that a socket sits in wait state after being closed (default is 2 minutes) Tcp. Timed. Wait. Delaysee Note 3 2. Adjust the number of ports available (default is 5. Max. User. Portsee Note 4 3. Adjust the use of connect / disconnect so that it doesn't cycle so rapidly in the program (best solution). MSL). Re- using the connection handle when an application is issuing multiple statements is the best way of handling this (do not disconnect then reconnect every time a statement completes) 4. Implement client side connection pooling so that the application logic internally does not have to change. Make sure the pool is large enough to handle 8. Make sure the pool has some form of re- connect logic in the case of a disconnect while idle. Windows. AIXSUNHPLinux. Short Name. Action Plan. ENOBUFS No buffer space available. System running out of resource to complete the TCPIP call For Windows: The problem is caused by running out of Windows desktop heap or system page table entries. It is not DB2 related. Increase the Windows System. Pages registry entry. Windows. AIXSUNHPLinux. Short Name. Action Plan. EPIPE (Broken Pipe)Network connectivity problem beteween client and server, run network sniffer trace on both client and server. WSAEINTR)Connection closed by client. For DB2 z see technote. WSAEHOSTUNREACHNo route to host. For Windows client, Linux server: Unset firewall on Linux server to allow connections to go through from clients. There are some situations in which no return code is returned such as the following examples: SQL3. N A communication error has been detected. Communicationprotocol being used 'TCP/IP'. Communication API being used 'SOCKETS'. Location where error was detected "1. Communication functiondetecting the error 'Select. For. Connect. Timeout'. Protocol specific errorcode '0','*','*'. SQLSTATE=0. 80. 01. IP which was also assigned to other devices. This was causing intermittent error messages above. There could be other causes of this error message. SQL3. 00. 81. N A communication error has beendetected. Communication protocol being used: "TCP/IP". Communication. API being used: "SOCKETS". Location where the error was detected: "1. Communication function detecting the error: "recv". Protocol specific error code(s): "*", "*", "0". SQLSTATE=0. 80. 01*,*,0 indicates the connection was closed by the peer. This could be any network device (i. DB2 server, or the DB2 server itself. Check to determine if DB2 server has Workload Manager enabled in which SQL queries consuming longer than xx minutes will be disconnected. In example below it is 1. UR"WORKLOADNAME SERVICECLASSNAME- -- -- -- -- -- -- -- - - -- -- -- -- -- -- -- -- -SYSDEFAULTUSERWORKLOAD SYSDEFAULTSUBCLASSSYSDEFAULTADMWORKLOAD SYSDEFAULTSUBCLASSTEST_WL MAIN_SCdb. ENABLED from syscat. UR"WORKLOADNAME ENABLED- -- -- -- -- -- -- -- -- -- - - -- -- -- -- -SYSDEFAULTUSERWORKLOAD Y SYSDEFAULTADMWORKLOAD YTEST_WL YCREATE THRESHOLD "TEST_UOW_CONC_TH"FOR WORKLOAD TEST_WL ACTIVITIESENFORCEMENT DATABASEWHEN UOWTOTALTIME > 1. MINUTESCOLLECT ACTIVITY DATAON COORDINATOR DATABASE PARTITIONWITH DETAILSFORCE APPLICATION; Also check DB2 server to determine if there are any communications registry variables set or if there are any messages around same timestamp in db. Network sniffer traces from client and server side should be collected and analysed by network administrator to determine root cause of SQL3. Windows System Error Codes (exit codes)Code Description 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 1. The environment is incorrect. 1. An attempt was made to load a program with an incorrect format. 1. The access code is invalid. 1. The data is invalid. 1. Not enough storage is available to complete this operation. 1. The system cannot find the drive specified. 1. The directory cannot be removed. 1. The system cannot move the file to a different disk drive. 1. There are no more files. 1. The media is write protected. 2. The system cannot find the device specified. 2. The device is not ready. 2. The device does not recognize the command. 2. Data error (cyclic redundancy check). 2. The program issued a command but the command length is incorrect. 2. The drive cannot locate a specific area or track on the disk. 2. The specified disk or diskette cannot be accessed. 2. The drive cannot find the sector requested. 2. The printer is out of paper. 2. The system cannot write to the specified device. 3. The system cannot read from the specified device. 3. A device attached to the system is not functioning. 3. The process cannot access the file because it is being used by another process. 3. The process cannot access the file because another process has locked a portion of the file. 3. The wrong diskette is in the drive. Insert %2 (Volume Serial Number: %3) into drive %1. 3. Too many files opened for sharing. 3. Reached the end of the file. 3. The disk is full. 5. The request is not supported. 5. Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator. 5. You were not connected because a duplicate name exists on the network. Go to System in the Control Panel to change the computer name and try again. 5. The network path was not found. 5. The network is busy. 5. The specified network resource or device is no longer available. 5. The network BIOS command limit has been reached. 5. A network adapter hardware error occurred. 5. The specified server cannot perform the requested operation. 5. An unexpected network error occurred. 6. The remote adapter is not compatible. 6. The printer queue is full. 6. Space to store the file waiting to be printed is not available on the server. 6. Your file waiting to be printed was deleted. 6. The specified network name is no longer available. 6. Network access is denied. 6. The network resource type is not correct. 6. The network name cannot be found. 6. The name limit for the local computer network adapter card was exceeded. 6. The network BIOS session limit was exceeded. 7. The remote server has been paused or is in the process of being started. 7. No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. 7. The specified printer or disk device has been paused. 8. The file exists. 8. The directory or file cannot be created. 8. Fail on INT 2. 4. 8. Storage to process this request is not available. 8. The local device name is already in use. 8. The specified network password is not correct. 8. The parameter is incorrect. 8. A write fault occurred on the network. 8. The system cannot start another process at this time. 1. Cannot create another system semaphore. 1. The exclusive semaphore is owned by another process. 1. The semaphore is set and cannot be closed. 1. The semaphore cannot be set again. 1. Cannot request exclusive semaphores at interrupt time. 1. The previous ownership of this semaphore has ended. 1. Insert the diskette for drive %1. 1. The program stopped because an alternate diskette was not inserted. 1. The disk is in use or locked by another process. 1. The pipe has been ended. 1. The system cannot open the device or file specified. 1. The file name is too long. 1. There is not enough space on the disk. 1. No more internal file identifiers available. 1. The target internal file identifier is incorrect. 1. The IOCTL call made by the application program is not correct. 1. The verify- on- write switch parameter value is not correct. 1. The system does not support the command requested. 1. This function is not supported on this system. 1. The semaphore timeout period has expired. 1. The data area passed to a system call is too small. 1. The filename, directory name, or volume label syntax is incorrect. 1. The system call level is not correct. 1. The disk has no volume label. 1. The specified module could not be found. 1. The specified procedure could not be found. 1. There are no child processes to wait for. 1. The %1 application cannot be run in Win. Attempt to use a file handle to an open disk partition for an operation other than raw disk I/O. 1. An attempt was made to move the file pointer before the beginning of the file. 1. The file pointer cannot be set on the specified device or file. 1. A JOIN or SUBST command cannot be used for a drive that contains previously joined drives. 1. An attempt was made to use a JOIN or SUBST command on a drive that has already been joined. 1. An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted. 1. The system tried to delete the JOIN of a drive that is not joined. 1. The system tried to delete the substitution of a drive that is not substituted. 1. The system tried to join a drive to a directory on a joined drive. 1. The system tried to substitute a drive to a directory on a substituted drive. 1. The system tried to join a drive to a directory on a substituted drive. 1. The system tried to SUBST a drive to a directory on a joined drive. 1. The system cannot perform a JOIN or SUBST at this time. 1. The system cannot join or substitute a drive to or for a directory on the same drive. 1. The directory is not a subdirectory of the root directory. 1. The directory is not empty. 1. The path specified is being used in a substitute. 1. Not enough resources are available to process this command. 1. The path specified cannot be used at this time. 1. An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute. 1. System trace information was not specified in your CONFIG. SYS file, or tracing is disallowed. 1. The number of specified semaphore events for Dos. Mux. Sem. Wait is not correct. 1. Dos. Mux. Sem. Wait did not execute; too many semaphores are already set. 1. The Dos. Mux. Sem. Wait list is not correct. 1. The volume label you entered exceeds the label character limit of the target file system. 1. Cannot create another thread. 1. The recipient process has refused the signal. 1. The segment is already discarded and cannot be locked. 1. The segment is already unlocked. 1. The address for the thread ID is not correct. 1. The argument string passed to Dos. Exec. Pgm is not correct. 1. The specified path is invalid. 1. A signal is already pending. 1. No more threads can be created in the system. 1. Unable to lock a region of a file. 1. The requested resource is in use. 1. A lock request was not outstanding for the supplied cancel region. 1. The file system does not support atomic changes to the lock type. 1. The system detected a segment number that was not correct. 1. The operating system cannot run %1. 1. Cannot create a file when that file already exists. 1. The flag passed is not correct. 1. The specified system semaphore name was not found. 1. The operating system cannot run %1. 1. The operating system cannot run %1. 1. The operating system cannot run %1. 1. Cannot run %1 in Win. The operating system cannot run %1. 1. Win. 32 application. 1. The operating system cannot run %1. 1. The operating system cannot run %1. 1. The operating system cannot run this application program. 1. The operating system is not presently configured to run this application. 1. The operating system cannot run %1. 1. The operating system cannot run this application program. 2. The code segment cannot be greater than or equal to 6. K. 2. 01 The operating system cannot run %1. 2. The operating system cannot run %1. 2. The system could not find the environment option that was entered. 2. No process in the command subtree has a signal handler. 2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |