Are you starting everything up in the proper order ?
- Database first (8.1.?)
- 8.1.? listener
- running your applications environment file (APPSORA.env)
- the other processes you listed
Just a guess.
-Original Message-
Sent: Wednesday, October 31, 2001 3:55 PM
To: Multiple recipients
Well, yes and no.
1) Database up
2) Listener up
3) Log in as Apps person (hence source in appsora.env)
4) Other processes listed
-Original Message-
Sent: Thursday, November 01, 2001 8:10 AM
To: Multiple recipients of list ORACLE-L
Are you starting everything up in the proper
Folks --
I got it. Seems that what happened was that one of the scripts that needed
to be run by the applications user shuts the listener down and attempts (but
fails) to restart it. Now, the problem was that the lsnr process was out
there, but that there were no associated services with it,
What exactly happens? What is the problem? Anything in the log files
for Oracle, listener, OS, Apache?
-Original Message-
Sent: Wednesday, October 31, 2001 4:55 PM
To: Multiple recipients of list ORACLE-L
Friends --
Our pesky users are having problems logging on from the Web front end
The error is that the database login failed. There is nothing in the bdump
alert log of any interest and no entries whatsoever in the tns alert log or
in $APPLLOG. No clue where to look for Apache stuff...
Bambi.
-Original Message-
Sent: Wednesday, October 31, 2001 4:41 PM
To:
recipients of list ORACLE-L
Subject: RE: 11.5.4 Easy Question (?)
The error is that the database login failed. There is
nothing in the bdump
alert log of any interest and no entries whatsoever in the
tns alert log or
in $APPLLOG. No clue where to look for Apache stuff...
Bambi
search ML on db hang states
they recommend taking system and process state dumps
in such situations.
did not work in our case one time where we had a
situation where even internal connection was refused.
no freakin error in alert or bdump. finally ended up
having to kill pmon and other oracle
of list ORACLE-L
Subject: RE: 11.5.4 Easy Question (?)
The error is that the database login failed. There is
nothing in the bdump
alert log of any interest and no entries whatsoever in the
tns alert log or
in $APPLLOG. No clue where to look for Apache stuff...
Bambi
