No Listener Error Message - But Listener was Running

Links

Frequent Oracle Errors

•	TNS:could not resolve the connect identifier specified
•	Backtrace message unwound by exceptions
•	invalid identifier
•	PL/SQL compilation error
•	internal error
•	missing expression
•	table or view does not exist
•	end-of-file on communication channel
•	TNS:listener unknown in connect descriptor
•	insufficient privileges
•	PL/SQL: numeric or value error string
•	TNS:protocol adapter error
•	ORACLE not available
•	target host or object does not exist
•	invalid number
•	unable to allocate string bytes of shared memory
•	resource busy and acquire with NOWAIT specified
•	error occurred at recursive SQL level string
•	ORACLE initialization or shutdown in progress
•	archiver error. Connect internal only, until freed
•	snapshot too old
•	unable to extend temp segment by string in tablespace
•	Credential retrieval failed
•	missing or invalid option
•	invalid username/password; logon denied
•	unable to create INITIAL extent for segment
•	out of process memory when trying to allocate string bytes
•	shared memory realm does not exist
•	cannot insert NULL
•	TNS:unable to connect to destination
•	remote database not found'>ora-02019
•	exception encountered: core dump
•	inconsistent datatypes
•	no data found
•	TNS:operation timed out
•	PL/SQL: could not find program
•	existing state of packages has been discarded
•	maximum number of processes exceeded
•	error signaled in parallel query server
•	ORACLE instance terminated. Disconnection forced
•	TNS:packet writer failure
•	see ORA-12699
•	missing right parenthesis
•	name is already used by an existing object
•	cannot identify/lock data file
•	invalid file operation
•	quoted string not properly terminated

No Listener Error Message - But Listener was Running

No Listener Error Message - But Listener was Running

2006-07-17 - By Sam Bootsma

Hello List,

Our RMAN backup failed early this morning with the message "RMAN-04004:
error from recovery catalog database: ORA-12541 (See ORA-12541.ora-code.com): TNS:no listener ". I
checked the listener log files, and observed that there were connections
immediately before and after the time that this backup is started, so
the database listener was definitely up. But for some reason, RMAN was
not able to find the listener.

We did have a planned power outage yesterday morning from 8:00a to
2:00p, but because our database server is on UPS and a backup generator,
it was completely unaffected. And, the failed RMAN backup was started
12 hours after the planned power outage was finished.

The only thing I can think of is that a network device was down
somewhere between RMAN and the listener; however, RMAN would not be
aware of this so it may just conclude there is no listener and then
deliver a message saying that.

I checked around noon today, and I was able to connect RMAN to the
database, so I expect the backup will take place tonight.

Does anybody have any other ideas on what might have been the porblem?
Thanks!

Sam Bootsma

Oracle Database Administrator

Information Technology Services
George Brown College

Phone: 416-415-5000 x4933
Fax: 416-415-4836
E-mail: sbootsma@(protected) <mailto:sbootsma@(protected)>

<html>

<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">

<style>

</style>

</head>

<body lang=EN-US link=blue vlink=purple>

<div class=Section1>

Hello List,

 

Our RMAN backup failed early this morning with the message
"RMAN-04004: error from recovery catalog database: ORA-12541 (See ORA-12541.ora-code.com): TNS:no
listener ".  I checked the listener log files, and observed that there
were connections immediately before and after the time that this backup is
started, so the database listener was definitely up.  But for some reason,
RMAN
was not able to find the listener.  

 

We did have a planned power outage yesterday morning from
8:00a to 2:00p, but because our database server is on UPS and a backup
generator, it was completely unaffected.  And, the failed RMAN backup was
started 12 hours after the planned power outage was finished.  

 

The only thing I can think of is that a network device was
down somewhere between RMAN and the listener; however, RMAN would not be aware
of this so it may just conclude there is no listener and then deliver a message
saying that. 

 

I checked around noon today, and I was able to connect RMAN
to the database, so I expect the backup will take place tonight.

 

Does anybody have any other ideas on what might have been
the porblem?  Thanks!

 

Sam Bootsma

Oracle Database Administrator

Information Technology Services
 
George Brown College

Phone: 416-415-5000 x4933 
Fax: 416-415-4836 
E-mail: <a
href="mailto:sbootsma@(protected)">sbootsma@(protected)</a>

 

</div>

</body>

</html>