once clients are connected, you can shut down the listener... all that
means is that no one else can connect once it is down.
size of listener.log is OS dependent, it's just a file on disk. You
can recreate it by
shutting down the listener
renaming or deleting the listener.log file
starting
Title: RE: Listener problems
The following script is one I pulled off from the list a few months ago and added a few lines. It is proving pretty useful. Note it uses the set option to redirect to a new output file
John
#!/bin/ksh
# Script to copy out listener.log and compress
Have you put the datbase mtipdb into the tnsnames.ora file? If not, you
must do so.
You could also check for the lsnrctl executable in $ORACLE_HOME/bin.
HTH,
Ruth
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Wednesday, June 20, 2001 9:40 AM
Hi
Out of space on the file system I believe.
-Original Message-
Sent: Thursday, May 31, 2001 11:16 AM
To: Multiple recipients of list ORACLE-L
Has anybody come across the following error message in the listener.log, and
know what the resolution is.
TNS-12500: TNS:listener failed to
Title: RE: Listener problems
-Original Message-
From: zabair ahmed [mailto:[EMAIL PROTECTED]]
Has anybody come across the following error message in the
listener.log, and
know what the resolution is.
TNS-12500: TNS:listener failed to start a dedicated server process
TNS
You are out of space on that filesystem.
Check the size of your log files, as they are likely
responsible for consuming a lot of space.
Also check in the cdump directory for core files.
Jared
On Thursday 31 May 2001 09:16, zabair ahmed wrote:
Has anybody come across the following error
Take a look at /var/adm/messages for any reported errors
-Original Message-
Sent: Thursday, May 31, 2001 12:16 PM
To: Multiple recipients of list ORACLE-L
Has anybody come across the following error message in the listener.log, and
know what the resolution is.
TNS-12500:
