couldn't shutdown databae as internal:urgent

[saiprasadr]

hi
i couldn,t shutdown the database as internal
when i issue onnect internal' it is connecting
and when issue 'shutdown' diplaying 'oracle not available'

what i feel is i couldn't logon to oracle as internal through svrmgrl
i have dought om my pfile which has
mts_diapatchers="(PROTOCOL=TCP)(PRE=oracle.aurora.server.SGIopserver)"
mts_dispatcher="(PROTOCOL=TCP)(DISP=1)(mul=OFF)(pool=off)
mts_max_disaptchers=5
mts_servers=1
please analyze and give me solution.

thank you.
sai prasad reddy.

[sreddy]

Try connecting to SQL*Plus with(Oracle 8i):

Connect sys / as sydba and try shutting down using immediate/abort

[sambavan]

If it was on a Unix environment, set

export ORACLE_SID= ...

and then try to connect through the server manager, you should be fine.

Also set your MTS_SERVERS=5 b'cos your limit was too low.

You don't require this

mts_diapatchers="(PROTOCOL=TCP)(PRE=oracle.aurora.server.SGIopserver)"

Good luck,
Sam

[aarganesh]

Hi,
I think there is nothing to do with SID or any environment variable, 'cause if there is something with that, then, U cannot connect as internal first of all. For this, I need to look at the alertorcl.log file or the alertSID.log file's before proceeding further since this seems to be an abnormal issue.

[shawish_sababa]

Hi saiprasadr

can you please give us more info, becouse this reads like, as aarganesh wrote, "this seems to be an abnormal issue". what i would like you to write is step by step desc of what happend, lik: 1. i wrote shutdown in svrmgrl becouse of ... (need to to backup/problem in rbs,...)
2. after that i wait 5 minutes and i get "ora-___" saying: "oracle ...".

i can only tell you that when i practiced 8i and tryed to use the gui for startup/shutdown. i waited 5 minutes for shoutdown, ended up trying to connect as sys useing sqlplus getting "oracle not available", on the same dos window i could not connect to svrmgrl as well. i turnd to a new dos window , started a new session, connected to db useing svrmgrl, and then used shutdown abort, wich worked fine. had to go for recovery, but the only way to shutdown was like this.

[ramaral]

any recent patches made to the OS?

I have had something like this one before and it was caused by a patch on the server in which the svrmgrl prog couldn't connect to the db because the ports got screwed up. We neded up having to re-boot the server and crossed our fingers. Things started up fine but we had to un-install the OS patch.