Re: Manually starting services in Windows XP

DA Morgan" <damorgan_at_x.washington.edu> wrote in message news:41f52c0c$1_2_at_127.0.0.1...
> Jining Han wrote:
>
>> If I remember correctly, Oracle instructs to start the listeners first,
>> then database
>>
>> Jining Han
>
> Correct. The database will automatically register with the listener
> if the listener is already started.

As the questioner referred to 10g I suspect a discussion about the dbconsole service would not be out of place (and anyway it just so happened I'd sent one elsewhere last week on how to stop the automatic behaviour). The only thing I missed out was the comment about starting the listener first.

The short answer is to also set the OracleDBConsole<SID> service to manual startup (or perhaps not choose to use database control to manage the database when you create it with dbca).

More technically

The dbconsole service is dependent upon the service for the database itself. You can see this if you view the dependencies tab of the service from the services.cpl mmc snap-in.

The service for the database itself can be set to autostart with the OS or not, in addition the instance can be set to start with the service or not.

The service startmode is set, as you have done, in the services control panel applet. The instance start behaviour is controlled by the value of the registry entry HKLM\SOFTWARE\ORACLE\<oracle home key>\ORA_<SID>_AUTOSTART and is set by the oradim command line utility using oradim -edit <sid> -startmode manual|auto. (in previous releases this set the starttype for both the service and the instance so if you wanted them different you had to either use the control panel or edit the registry), but in 10g the utility has been enhanced so that you can control the startmode for both the instance and the service separately from the command line (eg oradim -edit -sid <sid> -startmode manual -srvcstart system will give an autostarting service but leave the instance down) - I suspect approximately 3 people will use this enhancement.

So your behaviour looks like the default to me which is

  a.. an autostarting dbconsole service which in turn autostarts the database service which in turn starts up the instance. setting the dbconsole to manual will do the job. If however you do wish to embrace the brave new world of web based database management you could set the startup type of the instance to manual and leave the dbconsole and database services set to autostart with the os. The instance itself could then be controlled from the dbconsole web pages. Personally I leave everything set at manual and script it.

HTH

-- 
Niall Litchfield
Oracle DBA
http://www.niall.litchfield.dial.pipex.com