i have win NT-4.0 and oracle 8.1.5
I used to write about this problem several times,it has been long since i am encountering this error.
IN EVERY 1 HOUR I USED TO GET THIS ERROR IN SERVER ORA-12560.
in client side though some of them getting server ,others encountered error ora-12500 .
my db is in shared server mode with 1 shared server process and 1 dispatcher with 30 users.i thought that might be the cause.
I increased the no.of shared servers to 5
and dispatchers to3.
for sometime the error stopped but again now i can see in trace files-alert.log
skgpspawn failed:category = 27143, depinfo = 9261, op = spdcr, loc = skgpspawn
failed to start multi-threaded server 'S005', oer=27143
found dead dispatcher 'D000', pid = (15, 1)
found dead dispatcher 'D003', pid = (18, 1)
in trace file for dispatcher D000-
network error encountered setting up listening port
listening address for dispatcher is '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'
NS Primary Error: TNS-12560: TNS:protocol adapter error
NT Generic Error: TNS-00530: Protocol adapter error
32-bit Windows Error: 38: Filename too long
OPIRIP: Uncaught error 108. Error stack:
ORA-00108: failed to set up dispatcher to accept connection asynchronously
listener is running ok,still at server i can't connect to sql*plus
getting error ora-12560
what's the problem,pl help????
hello,pando,tamilselvan ,if u r there pl help
the listener is running still sql*plus not getting connected .can anybody explain whats the route of sql*plus at server getting connected to db,not thru listener,how does the connection take place???
question for pando,wjramsay,tamil
sql*plus not getting connected at server showing the error ora-12560,this happens once daily,while clients getting connection.
can anybody explain how sql*plus connect to db at server?????
no messages in alertlog ,so I think the BG processes have noerror.pl reply back
[Edited by drishti on 11-27-2000 at 08:49 AM]
i am not very sure why it happens.
but we had found a way to solve it.
Used net8 to configure the tnsnames.ora on the server system
and use the connect string while connecting
This is not the solution for your problem, but it works
anybody else can tell anything why is it happenning,sometimes after restarting the server ,i can see one shared server process getting dead,
this is from alert log-
found dead multi-threaded server 'S000', pid = (10, 1)
Tue Nov 28 08:30:59 2000
DBW0: terminating instance due to error 472
Instance terminated by DBW0, pid = 165
can anybody tell ??
Click Here to Expand Forum to Full Width