The missing steps above would include something like:
lsnrctl set log_status off
! or host mv $ORACLE_HOME/network/log/l
l
confirm with: lsnrctl status
Secondly, are your instances in archivelog mode? If not, you may be looking at a point in tie recovery based upon your last good backup.
Thirdly, your sample steps seems a bit out of order. As Oracle, FROM THE BACK END try:
sqlplus /nolog
conn / as sysdba
which should give you a session prompt with which you may SHUTDOWN IMMEDIATE then STARTUP your instance. Eliminate the client-side session until you are sure you have a vaiable, local instance.





by: egarrisonPosted on 2009-01-14 at 14:31:55ID: 23378535
Check your listener. At a dos prompt or terminal window(linux) type: LSNRCTL
LSNRCTL> STATUS
I would also do STOP and START. Double check that your listener.log file is not full. On Windoze, it can only be about 1.75GB. If it is larger, do
LSNRCTL> set log_status false
then rename it.