Message-Id: <10714.124832@fatcity.com> From: "Jeffrey Beckstrom" Date: Mon, 18 Dec 2000 08:58:17 -0500 Subject: all network connections hang This is a MIME message. If you are reading this text, you may want to consider changing to a mail reader or gateway that understands how to properly handle MIME multipart messages. --=_7C277508.84E58F2F Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Content-Disposition: inline As anyone seen this: Two weeks ago on different servers, during the weekend ,an 8.1.6 production= =20 database started to refuse all network connections. Stopping and restarting= =20 the listener did not help. Stopping and restarting the database resolved = the=20 problem. Today, upon arrivial I learned this time it was happening to one of our = 8.1.6=20 development databases. This time, shutting down of the database was=20 unsuccessful (shutdown never completed). Messages in the alert.log for = the=20 shutdown as follows: Shutting down instance (immediate) License high water mark =3D 31 Mon Dec 18 07:46:22 2000 Errors in filee:\oracle\trace\ORA00488.TRC: ORA-27103: internal error ORA-01089: immediate shutdown in progress - no operations are permitted This is probably due to sessions trying to connect (this was an Oracle=20 Financials database) and the Concurrent Manager background tasks had = refused=20 shutdown, probably since could not connect to the database. Previous to this message were no other errors in the alert log so = Oracle=20 apparently did not realize it was having a problem. Other 8.1.6 databases on this same box continued to function so the = listener=20 appears to be okay. Jeffrey Beckstrom Database Administrator Greater Cleveland Regional Transit Authority 1240 W. 6th Street Cleveland, Ohio 44113 (216) 781-4204 --=_7C277508.84E58F2F Content-Type: text/plain Content-Disposition: attachment; filename="TEXT.htm"
As anyone seen this:
 
Two weeks ago on different servers, during the weekend ,an 8.1.6 production
database started to refuse all network connections. Stopping and restarting
the listener did not help. Stopping and restarting the database resolved the
problem.
Today, upon arrivial I learned this time it was happening to one of our 8.1.6
development databases. This time, shutting down of the database was
unsuccessful (shutdown never completed). Messages in the alert.log for the
shutdown as follows:
Shutting down instance (immediate)
License high water mark = 31
Mon Dec 18 07:46:22 2000
Errors in filee:\oracle\trace\ORA00488.TRC:
ORA-27103: internal error
ORA-01089: immediate shutdown in progress - no operations are permitted

This is probably due to sessions trying to connect (this was an Oracle
Financials database) and the Concurrent Manager background tasks had refused
shutdown, probably since could not connect to the database.
Previous to this message were no other errors in the alert log so Oracle
apparently did not realize it was having a problem.
Other 8.1.6 databases on this same box continued to function so the listener
appears to be okay.

 
Jeffrey Beckstrom
Database Administrator
Greater Cleveland Regional Transit Authority
1240 W. 6th Street
Cleveland, Ohio 44113
(216)