Just logon to the instance and do a shutdown immediate (connect
internal/YOURPASSOWRD or connect sys/PASSWORD as dbaoper and then shutdown
immediate) Don't shutdown the database by stopping the services! This is
like removing the program from memory while it is running. I would do it
once a week.(cold reboot) Better to have a planned restart than an unplanned
one. I am sure other people have had different experiences with NT's
stability and if you never have problems that is wonderful. But I have
customers that experience great stability on NT and others that have
terrible stability on NT and it is not clear to me why? (No clear reasons.)
So we encourage people to have a planned reboot once a week; if that works
for them great. Again better to reboot when things are not as busy then in
the midst of battle.
Jim
David Spaisman wrote in message <369981B5.31D188A6_at_intercall.com>...
>ello :
>
>I have noticed that NT server does not easily
>release memory and periodically the server needs to
>be shutdown to recoup the memory.
>
>My questions are :
>
>1) To shutdown the NT server, either manually or ny
>batch, do I always need to stop the two oracle
>services first? Is not, will the database crash?
>
>Is there anyway to to gracefully shutdown the
>instance on NT if the server needs to be rebooted
>without manually stoppping the Oracle services?
>
>2) How often do I nned to have the NT server
>rebooted? Although I realize this is
>application-specific, has anyone experienced the
>need to reboot the server periodically ? How often?
>Any problems with Oracle or any other applications
>being able to start?
>
>Any information that can be provided will be
>greatly appreciated? Thanks.
>
>David Spaisman
>
>
Received on Sun Jan 10 1999 - 23:47:53 CST
