Re: Windows 2003: 10g doesn't start automatically after reboot

From: Charles Hooper <hooperc2000_at_yahoo.com>
Date: Fri, 18 Jan 2008 04:57:10 -0800 (PST)
Message-ID: <33615e14-6f78-4c34-8abb-5f7173564ecb@z17g2000hsg.googlegroups.com>


On Jan 18, 7:27 am, Wolfram Roesler <w..._at_spam.la> wrote:
> Charles Hooper <hooperc2..._at_yahoo.com> wrote in news:66c9e70d-d895-437d-
> aa54-c92d5616d..._at_e23g2000prf.googlegroups.com:
>
> > What is the specific command that you are using to manually start the
> > database?  Does it include the location of the pfile (init.ora)?  The
> > spfile or init.ora used by Oracle by default may include a depreciated
> > setting, such as LOG_ARCHIVE_START.
>
> I'm just using this, which works fine:
>
>         echo startup | sqlplus "sys/secret as sysdba"
>
> This is a freshly installed 10g database so I don't think there
> are any deprecated settings anywhere.
>
> > Does it make a difference if you change the line in the SQLNET.ORA
> > file to read:
> > NAMES.DIRECTORY_PATH= (TNSNAMES, HOSTNAME)
>
> Sorry, this didn't help.
>
> > Have you verified that PATH environment variable contains Oracle's bin
> > folder?
>
> Yes, it does.
>
> Thanks for your help
> W. Rösler

Just a guess here. Some networks cards on Windows 2003 take a couple seconds, maybe even 20 seconds, to become online once the Windows interface displays. If Oracle attempts to start before the network interface is up, and it attempts to resolve the server's IP address, Oracle may not be able to start. You can try making an entry in the HOSTS file for the server's IP address, or modify the listener.ora and tnsnames.ora files so that server name resolution is not necessary.

The Windows event logs may provide clues to determine if this is the problem. You may need to check both the Application and System event logs on the server.

For example:
  12/24/2007 11:20:01 AM: Intel(R) PRO/1000 MT Server Adapter #2 driver had been started.
  12/24/2007 11:20:01 AM: Broadcom NetXtreme Gigabit Ethernet: Driver initialized successfully.
  12/24/2007 11:20:01 AM: Broadcom NetXtreme Gigabit Ethernet #2: Driver initialized successfully.
  12/24/2007 11:20:03 AM: Broadcom NetXtreme Gigabit Ethernet: The network link is down. Check to make sure the network cable is properly connected.
  12/24/2007 11:20:04 AM: Broadcom NetXtreme Gigabit Ethernet #2: The network link is down. Check to make sure the network cable is properly connected.
  12/24/2007 11:20:06 AM: Intel(R) PRO/1000 MT Server Adapter #2 Link has been established: 1000Mbps.
  12/24/2007 11:20:08 AM: The system detected that network adapter Intel(R) PRO/1000 MT Server Adapter #2 was connected to the network, and has initiated normal operation over the network adapter.   12/24/2007 11:20:17 AM: Audit trail: ACTION : 'CONNECT' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: NT AUTHORITY\SYSTEM CLIENT TERMINAL: MYDBSERVER STATUS: 0 .
  12/24/2007 11:20:17 AM: Audit trail: ACTION : 'STARTUP' DATABASE USER: '/' PRIVILEGE : SYSDBA CLIENT USER: NT AUTHORITY\SYSTEM CLIENT TERMINAL: Not Available STATUS: 0 .

If the last two lines appeared before the line at 12/24/2007 11:20:08 AM, the database may have failed to start. If this is the problem, it is also possible to delay the start of the service.

Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc. Received on Fri Jan 18 2008 - 06:57:10 CST

Original text of this message