Error: 32: Broken pipe

Error stack in listener log:

TNS-12518: TNS:listener could not hand off client connection

TNS-12547: TNS:lost contact

TNS-12560: TNS:protocol adapter error

TNS-00517: Lost contact

IBM/AIX RISC System/6000 Error: 32: Broken pipe

Cause:

The error 32 indicates the communication has been broken while the listener is trying to hand off the client connection to the server process or dispatcher process.

Action:

1. One of reason would be processes parameter being low, and can be verified by the v$resource_limit view.

2. In Shared Server mode, check the 'lsnrctl services' output and see if the dispatcher has refused any connections, if so, then consider increasing the number of dispatchers.

3. Check the alert log for any possible errors.

4. Memory resource is also another cause for this issue. Check the swap, memory usage of the OS.

______________________________________________________________________________________________________________________________________

Error: 11: Resource temporarily unavailable

Error stack in listener log:

TNS-12518: TNS:listener could not hand off client connection

TNS-12549: TNS:operating system resource quota exceeded

TNS-12560: TNS:protocol adapter error

TNS-00519: Operating system resource quota exceeded

IBM/AIX RISC System/6000 Error: 11: Resource temporarily unavailable

Cause:

As the error indicates operating system resource has exceeded.

Action:

1. Increase the appropriate OS kernal parameters for 'maximum number of processes allowed per user'.

For example for HP-UX the parameters are maxuprc and nproc.

______________________________________________________________________________________________________________________________________

Error: 12: Not enough space

Error stack in listener log:

TNS-12518: TNS:listener could not hand off client connection

TNS-12549: TNS:operating system resource quota exceeded

TNS-12560: TNS:protocol adapter error

TNS-00519: Operating system resource quota exceeded

IBM/AIX RISC System/6000 Error: 12: Not enough space

Cause:

This is a memory related issue. The error indicates that there is not enough memory available to spawn and hand off the client connections.

Typical problems are:

- Out of system memory / swap

- Out of process slots in the process table

- Streams resources depleted

- Out of File Handles

- sga memory usage

Action:

1. Check in the alert log for any possible memory related error.

2. Increase swap/Virtual memory if possible the available memory.

3. SGA and PGA can be reduced to address the memory consumption.

4. MTS mode can be used to reduce the amount of process and memory consumption.

________________________________________________________________________________________________________________________________________

Error: Connection Pooling limit reached

Error stack in listener log:

TNS-12518 TNS:listener could not hand off client connection

TNS-12564 TNS:connection refused

TNS-12602 TNS: Connection Pooling limit reached

Action:

1. Try increasing initial number of dispatcher.

_______________________________________________________________________________________________________________________________________

Error: 2: No such file or directory

Error stack in listener log:

TNS-12518: TNS:listener could not hand off client connection

TNS-12560: TNS:proto adapter error

TNS-00530: Proto adapter error

32-bit Windows Error: 2: No such file or directory

Error Description:

ERROR_FILE_NOT_FOUND

2

The system cannot find the file specified.

Cause:

This indicates the database service is not actually available

Ation:

1.Verify if the inteneded database really up and accepting local BEQ connections.

________________________________________________________________________________________________________________________________________

=========================================================================================================================

Section III: Errors Specific to Windows

It is also recommended that you refer the Section I above for a generic troubleshooting approach to the error TNS-12518.

This section briefly describes about the errors that are encountered on Windows Operating System. TNS-12518 most commonly occurs on 32-bit OS due to its memory constraint, however TNS-12518 can occur on 64-bit OS as well.

_______________________________________________________________________________________________________________________________________

Error: 233: Unknown error

Error stack in listener log:

TNS-12518: TNS:listener could not hand off client connection

TNS-12560: TNS:protocol adapter error

TNS-00530: Protocol adapter error

32-bit Windows Error: 233: Unknown error

Error Description:

ERROR_PIPE_NOT_CONNECTED

233

No process is on the other end of the pipe.

Cause:

The communication has been broken while the listener is trying to hand off the client connection to the server process or dispatcher process.

Action:

Refer Note 371983.1

_______________________________________________________________________________________________________________________________________

Error: 54: Unknown error

Error stack in listener log:

TNS-12518: TNS:listener could not hand off client connection

TNS-12571: TNS:packet writer failure

TNS-12560: TNS:protocol adapter error

TNS-00530: Protocol adapter error

32-bit Windows Error: 54: Unknown error

Error Description:

ERROR_NETWORK_BUSY

54

0x36

The network is busy.

Cause:

This indicates a bottleneck at the network layer(TCP/IP).

Action:

1.Try increasing dispatchers and shared servers.

2 Responses so far.

  1. Anonymous says:

    Hi

    Can you please assist me in identifying the issue in this case:




    TNS-12546: TNS:permission denied

    TNS-12560: TNS:protocol adapter error

    TNS-00516: Permission denied

    IBM/AIX RISC System/6000 Error: 55: Operation now in progress





    Thanks and Regards,
    ellraven@gmail.com

  2. Anonymous says:

    Hi

    Can you please assist me in identifying the issue in this case:




    TNS-12546: TNS:permission denied

    TNS-12560: TNS:protocol adapter error

    TNS-00516: Permission denied

    IBM/AIX RISC System/6000 Error: 55: Operation now in progress





    Thanks and Regards,
    ellraven@gmail.com

DOAG 2016

Powered by Blogger.

Page Views

- Copyright © Emre Baransel - Oracle Blog -Metrominimalist- Powered by Blogger - Designed by Johanes Djogan -