Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: 10g startup problem on W2k Pro

Re: 10g startup problem on W2k Pro

From: Alex NSB <alexnsb_at_tin.it>
Date: Mon, 6 Dec 2004 15:39:13 +0100
Message-ID: <cp1r16$i3m$1@newsread.albacom.net> 





> Is the database being shut down cleanly before the machine is shut

> down, or are you just shutting down the machine?  Check your alert log

> for signs of a clean, compleat shutdown just before the failed

> startup.




Ed,



I usually only shut down the machine: to my knowledge, no extra steps are
required to "cleanly" close the Oracle instance.



I attach an excerpt from my alert log: it reflects the last reboot I did on
this PC (and the subsequent manual restart of the Windows Oracle service I
had to issue to get the instance running).



As usual, thanks for your time.



Alessandro


>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>


Mon Dec 06 11:40:07 2004


Starting background process EMN0


EMN0 started with pid=13, OS id=360


Mon Dec 06 11:40:07 2004


Shutting down instance: further logons disabled
Mon Dec 06 11:40:07 2004


Stopping background process CJQ0


Mon Dec 06 11:40:07 2004


Stopping background process QMNC


Mon Dec 06 11:40:07 2004


Stopping background process MMNL


Mon Dec 06 11:40:08 2004


Stopping background process MMON


Mon Dec 06 11:40:10 2004


Shutting down instance (immediate)


License high water mark = 12


Mon Dec 06 11:40:10 2004


Stopping Job queue slave processes


Mon Dec 06 11:40:10 2004


Job queue slave processes stopped


All dispatchers and shared servers shutdown
Dump file d:\oracle\product\10.1.0\admin\pmed10g\bdump\alert_pmed10g.log
Mon Dec 06 11:41:30 2004


ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3


Windows 2000 Version V5.0 Service Pack 4

CPU             : 1 - type 586
Process Affinity: 0x00000000
Memory (A/P)    : PH:616M/735M, PG:1705M/1803M, VA:1953M/2047M
Mon Dec 06 11:41:30 2004




Starting ORACLE instance (normal)


LICENSE_MAX_SESSION = 0



LICENSE_SESSIONS_WARNING = 0



Picked latch-free SCN scheme 2


KCCDEBUG_LEVEL = 0



Using LOG_ARCHIVE_DEST_10 parameter default value as
USE_DB_RECOVERY_FILE_DEST



Autotune of undo retention is turned on.
Dynamic strands is set to TRUE


Running with 1 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR



ILAT =18



LICENSE_MAX_USERS = 0



SYS auditing is disabled


Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:

  processes                = 150
  shared_pool_size         = 83886080
  large_pool_size          = 8388608
  java_pool_size           = 50331648
  control_files            =
D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\CONTROL01.CTL,


D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\CONTROL02.CTL,

D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\CONTROL03.CTL


  db_block_size            = 8192
  db_cache_size            = 25165824
  compatible               = 10.1.0.2.0
  log_archive_start        = TRUE
  db_file_multiblock_read_count= 16




  db_recovery_file_dest    = D:\oracle\product\10.1.0\flash_recovery_area
  db_recovery_file_dest_size= 6442450944

  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=PMED10GXDB)
  job_queue_processes      = 10
  background_dump_dest     = D:\ORACLE\PRODUCT\10.1.0\ADMIN\PMED10G\BDUMP
  user_dump_dest           = D:\ORACLE\PRODUCT\10.1.0\ADMIN\PMED10G\UDUMP
  core_dump_dest           = D:\ORACLE\PRODUCT\10.1.0\ADMIN\PMED10G\CDUMP
  sort_area_size           = 65536
  db_name                  = PMED10G
  open_cursors             = 300
  pga_aggregate_target     = 25165824




Deprecated system parameters with specified values:
  log_archive_start


End of deprecated system parameter listing

PMON started with pid=2, OS id=988
MMAN started with pid=3, OS id=1004
DBW0 started with pid=4, OS id=1024
LGWR started with pid=5, OS id=1012
CKPT started with pid=6, OS id=1028
SMON started with pid=7, OS id=1032
RECO started with pid=8, OS id=1068
CJQ0 started with pid=9, OS id=1088




Mon Dec 06 11:41:40 2004


starting up 1 dispatcher(s) for network address
'(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

starting up 1 shared server(s) ...


Mon Dec 06 11:43:10 2004


Shutting down instance: further logons disabled
Mon Dec 06 11:43:10 2004


Stopping background process CJQ0


Mon Dec 06 11:43:10 2004


Shutting down instance (immediate)


License high water mark = 1


Mon Dec 06 11:43:10 2004


Stopping Job queue slave processes


Mon Dec 06 11:43:10 2004


Job queue slave processes stopped


Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Mon Dec 06 11:43:17 2004


alter database close normal


ORA-1507 signalled during: alter database close normal...
Dump file d:\oracle\product\10.1.0\admin\pmed10g\bdump\alert_pmed10g.log
Mon Dec 06 11:43:18 2004


ORACLE V10.1.0.2.0 - Production vsnsta=0
vsnsql=13 vsnxtr=3


Windows 2000 Version V5.0 Service Pack 4

CPU             : 1 - type 586
Process Affinity: 0x00000000
Memory (A/P)    : PH:566M/735M, PG:1647M/1803M, VA:1953M/2047M
Mon Dec 06 11:43:18 2004




Starting ORACLE instance (normal)


LICENSE_MAX_SESSION = 0



LICENSE_SESSIONS_WARNING = 0



Picked latch-free SCN scheme 2


KCCDEBUG_LEVEL = 0



Using LOG_ARCHIVE_DEST_10 parameter default value as
USE_DB_RECOVERY_FILE_DEST



Autotune of undo retention is turned on.
Dynamic strands is set to TRUE


Running with 1 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR



ILAT =18



LICENSE_MAX_USERS = 0



SYS auditing is disabled


Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:

  processes                = 150
  shared_pool_size         = 83886080
  large_pool_size          = 8388608
  java_pool_size           = 50331648
  control_files            =
D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\CONTROL01.CTL,


D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\CONTROL02.CTL,

D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\CONTROL03.CTL


  db_block_size            = 8192
  db_cache_size            = 25165824
  compatible               = 10.1.0.2.0
  log_archive_start        = TRUE
  db_file_multiblock_read_count= 16




  db_recovery_file_dest    = D:\oracle\product\10.1.0\flash_recovery_area
  db_recovery_file_dest_size= 6442450944

  undo_management          = AUTO
  undo_tablespace          = UNDOTBS1
  remote_login_passwordfile= EXCLUSIVE
  db_domain                =
  dispatchers              = (PROTOCOL=TCP) (SERVICE=PMED10GXDB)
  job_queue_processes      = 10
  background_dump_dest     = D:\ORACLE\PRODUCT\10.1.0\ADMIN\PMED10G\BDUMP
  user_dump_dest           = D:\ORACLE\PRODUCT\10.1.0\ADMIN\PMED10G\UDUMP
  core_dump_dest           = D:\ORACLE\PRODUCT\10.1.0\ADMIN\PMED10G\CDUMP
  sort_area_size           = 65536
  db_name                  = PMED10G
  open_cursors             = 300
  pga_aggregate_target     = 25165824




Deprecated system parameters with specified values:
  log_archive_start


End of deprecated system parameter listing

PMON started with pid=2, OS id=1004
MMAN started with pid=3, OS id=988
DBW0 started with pid=4, OS id=336
LGWR started with pid=5, OS id=568
CKPT started with pid=6, OS id=1100
SMON started with pid=7, OS id=564
RECO started with pid=8, OS id=304
CJQ0 started with pid=9, OS id=692




Mon Dec 06 11:43:18 2004


starting up 1 dispatcher(s) for network address
'(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...

starting up 1 shared server(s) ...


Mon Dec 06 11:43:18 2004


alter database mount exclusive


Mon Dec 06 11:43:19 2004


Controlfile identified with block size 16384
Mon Dec 06 11:43:23 2004


Setting recovery target incarnation to 2
Mon Dec 06 11:43:23 2004


Successful mount of redo thread 1, with mount id 3796891158
Mon Dec 06 11:43:23 2004


Database mounted in Exclusive Mode.


Completed: alter database mount exclusive
Mon Dec 06 11:43:23 2004


alter database open


Mon Dec 06 11:43:24 2004


Beginning crash recovery of 1 threads


Mon Dec 06 11:43:24 2004


Started first pass scan


Mon Dec 06 11:43:24 2004


Completed first pass scan


 2 redo blocks read, 3 data blocks need recovery
Mon Dec 06 11:43:24 2004


Started redo application at


 Thread 1: logseq 765, block 13371, scn 0.0
Recovery of Online Redo Log: Thread 1 Group 2 Seq 765 Reading mem 0
  Mem# 0 errs 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\REDO02.LOG
Mon Dec 06 11:43:24 2004


Completed redo application


Mon Dec 06 11:43:24 2004


Completed crash recovery at


 Thread 1: logseq 765, block 13373, scn 0.4314142
 3 data blocks read, 3 data blocks written, 2 redo blocks read
Mon Dec 06 11:43:25 2004


LGWR: STARTING ARCH PROCESSES



ARC0 started with pid=14, OS id=1340


ARC0: Archival started


ARC1 started with pid=15, OS id=352


Mon Dec 06 11:43:25 2004


LGWR: STARTING ARCH PROCESSES COMPLETE



ARC1: Archival started


Mon Dec 06 11:43:25 2004


ARC0: Becoming the 'no FAL' ARCH


ARC0: Becoming the 'no SRL' ARCH


Mon Dec 06 11:43:25 2004


ARC1: Becoming the heartbeat ARCH


Mon Dec 06 11:43:25 2004


LGWR: Primary database is in CLUSTER CONSISTENT mode
Thread 1 advanced to log sequence 766


Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 7 at log switch


Thread 1 opened at log sequence 766


  Current log# 3 seq# 766 mem# 0:


D:\ORACLE\PRODUCT\10.1.0\ORADATA\PMED10G\REDO03.LOG

Successful open of redo thread 1


Mon Dec 06 11:43:26 2004


MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Dec 06 11:43:26 2004


ARC0: Evaluating archive   log 2 thread 1 sequence 765
Mon Dec 06 11:43:26 2004


ARC1: Evaluating archive   log 2 thread 1 sequence 765
ARC1: Unable to archive log 2 thread 1 sequence 765


      Log actively being archived by another process
Mon Dec 06 11:43:26 2004


SMON: enabling cache recovery


Mon Dec 06 11:43:26 2004


ARC1: Evaluating archive   log 2 thread 1 sequence 765
ARC1: Unable to archive log 2 thread 1 sequence 765


      Log actively being archived by another process
ARC1: Evaluating archive   log 2 thread 1 sequence 765
ARC1: Unable to archive log 2 thread 1 sequence 765


      Log actively being archived by another process
Mon Dec 06 11:43:27 2004


db_recovery_file_dest_size of 6144 MB is 40.62% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Committing creation of archivelog


'D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\PMED10G\ARCHIVELOG\2004_12_06\

O1_MF_1_765_0V8FYH98_.ARC'



Created Oracle managed file


D:\ORACLE\PRODUCT\10.1.0\FLASH_RECOVERY_AREA\PMED10G\ARCHIVELOG\2004_12_06\O

1_MF_1_765_0V8FYH98_.ARC



Mon Dec 06 11:43:29 2004


Successfully onlined Undo Tablespace 1.


Mon Dec 06 11:43:29 2004


SMON: enabling tx recovery


Mon Dec 06 11:43:29 2004


Database Characterset is WE8MSWIN1252


Mon Dec 06 11:43:29 2004


Published database character set on system events channel
Mon Dec 06 11:43:29 2004


All processes have switched to database character set
Mon Dec 06 11:43:32 2004


Starting background process QMNC


QMNC started with pid=13, OS id=1020


Mon Dec 06 11:43:36 2004


replication_dependency_tracking turned off (no async multimaster replication
found)


Mon Dec 06 11:43:38 2004


Starting background process MMON


Starting background process MMNL


MMON started with pid=16, OS id=980


MMNL started with pid=17, OS id=976


Mon Dec 06 11:43:40 2004


Completed: alter database open

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<


Received on Mon Dec 06 2004 - 08:39:13 CST












Original text of this message













  HOME |
  ASK QUESTION |
  ADD INFO |
  SEARCH |
  E-MAIL US