To: Multiple recipients of list ORACLE-L
Subject:listener failed to start a dedicated server process
Hi,
When I tried to start one more session of oracle
SQLPLUS I got this error:
ERROR:
ORA-12500: TNS:listener failed to start a
dedicated
Assuming you are unix...
If you are on 7.3.4 it may be caused by not disabling Oracle trace.
Otherwise you have probably exceeded a unix limit, like maxuprc.
AM PST
Please respond to [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L [EMAIL
Hi,
check following issues as well,
If you are referring ORACLE_HOME in your tnsnames.ora
Value of parameter PROCESSES is too low.
HTH,
Rajesh
-Original Message-
Kurth
Sent: Sunday, November 18, 2001 7:30 PM
To: Multiple recipients of list ORACLE-L
Assuming you are unix...
If you
Hi
Sorry if I sound naive!
But do we have to boot the server in Solaris 8
TOO (!!) in order to change the kernel?
What is the procedure for changing the kernel
Thanks
- Original Message --
John Kanagaraj [EMAIL PROTECTED] wrote:
To:Multiple recipients of list
On Tue, 29 May 2001,Cyril Thankappan scribbled on the wall in glitter crayon:
-
-Hi
-
- Sorry if I sound naive!
-
- But do we have to boot the server in Solaris 8
- TOO (!!) in order to change the kernel?
-
- What is the procedure for changing the kernel
-
* Thanks
As far as I know, if you
On Solaris, you don't actually have to change the kernel, but you
do need to edit the file /etc/system, and these changes require
a reboot to become effective.
I know this to be true through 2.7, not sure about 8.
Jared
On Tuesday 29 May 2001 11:28, Cyril Thankappan wrote:
Hi
Sorry if I
Hi ,
Your problem is actually highlighted on the error message "Solaris Error: 12: Not enough space"
It is more of an Operating system resource issue. I gather that you are running about 8 instances on this machine ,right?
Shutdown couple of unused or low priority instances and see whether you
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
Thank you everybody for your suggestions. To recap, I had the following suggestions:
- purge listener.log (Shahid Nasir)
- check max number of processes vs. max number of processes per user (John Kanagaraj)
- swap space
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
-Original Message-
From: Jyoti N [mailto:[EMAIL PROTECTED]]
Your problem is actually highlighted on the error message Solaris Error: 12: Not enough space
It is more of an Operating system resource issue.
Yes
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
i
think you should check large pool size parameter in your init.ora file. You can
actullay reduce the size and restart the instance.
-Nihar
-Original Message-From: [EMAIL PROTECTED]
[mailto:[EMAIL
$ sar
sar: can't open /var/adm/sa/sa23
No such file or directory
I do see a /var/adm/sa/sa16 directory. What does this mean?
Jacques,
This is the file (not directory?!) that records the system activity
information (in binary) via the sadc program. The file is named by
day-of-the-month
Title: Sun Solaris 8 - Listener failed to start a dedicated server process
On one of our Sun (development) servers, we have 8 databases running for different versions of Oracle (7.3.4, 8.0.6, 8.1.6). I am able to connect with SQL*Plus on the server, but I can't connect from a client. I get
Hi Jacques,
You need to increase the processes parameter in the init.ora file then
restart the listener and database.
HTH,
-Rocky
--- Jacques Kilchoer [EMAIL PROTECTED] wrote:
On one of our Sun (development) servers, we have 8 databases running for
different versions of Oracle (7.3.4, 8.0.6,
Jacques,
I am not sure, but are you running out of semaphores? (possible as your
default limit may be too low for the 8 databases you serve). Look at
/etc/system together with the UIG - add us all the 'processes' in all
init.oras - they should be lesser than 'SEMMNS' (Number of semaphores).
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
Thank you for the suggestions so far.
Rocky Welch suggesting increasing the processes parameter in the init.ora
I tried that with one of the 8.1.6 databases.
The processes parameter was set to 50, I increased it to 200
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
Jacques,
I've seen a similar
error with processes and Solaris memory structures. Someone mentioned
increasing SEMMNS, this helped in my situation, however you can try decreasing
the PROCESSES parameter temporarily
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
hi jacques,
I have
a similar issue quite some time back., when everything was fine at oracle level. Try
finding problem at unix level. like memory being less, heavy swapping.
In my case, it turned out to be unix memory
Title: RE: Sun Solaris 8 - Listener failed to start a dedicated server p
It
could also be swap is filled. If you see Solaris Error: 12 in the
listener.log, there isn't enough space. Do a df -k and look for a mount
point that is 100% full. It is likely to be /tmp (swap).
Original
Hi Jacques,
One more thing to check - the max number of processes across the entire
system as well as the max. no of processes per user. I am not sure about the
names, but you get the drift, right? You may be bumping the ceiling on
either of these values...
John Kanagaraj
-Original
Everytime I have faced this problem, first thing I look at is the
listener.log file. If the size of this file is large, I just delete and
restart the listener and everything works fine. Maybe you should have a look
at this.
Shahid Nasir
Database Officer
MERCATOR
A member of the Emirates Group.
line, I get no error,
but when trying to connect any of the databases I get the error The listener
failed to start a dedicated server process.
I need help for:
first and urgent, how starting the listener correctly, I have
used the following command:
lsnrctl start
or any idea about why my
21 matches
Mail list logo
