SQLNET.LOG reporting "Fatal NI connect error 12560" error

I am getting the following errors intermitently reported in the SQLNET.log file,

Fatal NI connect error 12560, connecting to:

        TNS for IBM/AIX RISC System/6000: Version - Production
        TCP/IP NT Protocol Adapter for IBM/AIX RISC System/6000: Version - Production
  Time: 01-DEC-2004 16:24:23
  Tracing not turned on.
  Tns error struct:
    nr err code: 0
    ns main err code: 12560
    TNS-12547: TNS:lost contact
    ns secondary err code: 12560
    nt main err code: 517
    TNS-00517: Lost contact
    nt secondary err code: 32
    TNS-12560: TNS:protocol adapter error
    ns secondary err code: 0
    nt main err code: 530
    TNS-00530: Protocol adapter error
    nt secondary err code: 73
    nt OS err code: 0

An application that's running is trying to connect via SQL*PLUS and is failing to do so after three attempts.  Has anyone experienced this problem before?  Oracle think that it is a file sharing problem based on the nt secondary err ocde: 32 message.  I'm running on AIX 5.2, DB is
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

any networking problems ?
Cab you ping the database server while this happens ?


This seems to be a batch job of some kind?

What is the time during which u get this error.

Verify if u have any cron jobs scheduled at this time. If yes also verify that ur database or listener is running (accepting connections) at this time.

Check with
tnsping <database>


DLyallAuthor Commented:

The scenario in which this problem occurs is as follows,

I issue a request that results in about a two hundred individual jobs being queued on our scheduler.  Each job extracts data for a particular user and runs identically except that the parameters to each one will be slightly different (i.e. user id).  There may be 2 or three jobs that fail with the error I have shown above out of the two hundred.  Jobs are run in parallel (which is configurable 1 to nn), but normally up to 2 at a time, and I have observed that the more jobs that are run in parallel, the more that fail.  When jobs are run one at a time, the problem occurs much less frequently.
Some more thoughts

1. there may be limitation of how much connections one listener handles.
2. How your database is configured ( Parallel Server or Multi Threaded).

You can try out this...

Configure listener to listen on additional ports 1526 along with 1521 and then check out if it goes.

Also change the db configuration if possible.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.