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

Home -> Community -> Usenet -> c.d.o.misc -> Re: ORA-01034: ORACLE not available

Re: ORA-01034: ORACLE not available

From: Thomas Fischer <himself_at_tfischer.de>
Date: Mon, 06 Mar 2000 04:05:00 GMT
Message-ID: <38c32d3f.11186395@news.uni-kassel.de> 





Hi,



On Sun, 05 Mar 2000 23:44:42 GMT, "joon" <joopark_at_home.com> wrote:



>Control files are essential, database must have this file
>Can you find ora_contron1.ora in your system/



what is in them? can I build one myself?
where do they belong in the dirtree?


>Send me init.ora and last potion of alert.log
>I will get back to you tommrow
>and I will solve the problem yaa!!!!






alert_ARCH.log ends like this:





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

  processes                = 50
  shared_pool_size         = 3500000
  control_files            = ora_control1, ora_control2
  db_block_buffers         = 100
  log_buffer               = 8192
  log_checkpoint_interval  = 10000
  db_files                 = 80




  db_file_multiblock_read_count= 8


  sequence_cache_entries   = 10


  sequence_cache_hash_buckets= 10

  global_names             = TRUE
  db_name                  = ARCH
  parallel_max_servers     = 5
  max_dump_file_size       = 10240
PMON started with pid=2
DBW0 started with pid=3
LGWR started with pid=4




CKPT started with pid=5


SMON started with pid=6


Sun Mar  5 16:06:04 2000


alter database  mount


Sun Mar  5 16:06:04 2000


ORA-00202: controlfile: 'ora_control1'


ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3


Sun Mar  5 16:06:04 2000


ORA-205 signalled during: alter database  mount...
RECO started with pid=7





init.ora looks like this:





# 


# $Header: init.ora 05-jun-97.14:56:46 hpiao Exp $ 


# 


# Copyright (c) 1991, 1997 by Oracle Corporation


# NAME



#   init.ora


# FUNCTION



# NOTES



# MODIFIED



#     hpiao      06/05/97 -  fix for 803


#     glavash    05/12/97 -  add oracle_trace_enable comment


#     hpiao      04/22/97 -  remove ifile=, events=, etc.


#     alingelb   09/19/94 -  remove vms-specific stuff


#     dpawson    07/07/93 -  add more comments regarded archive start


#     maporter   10/29/92 -  Add vms_sga_use_gblpagfile=TRUE 


#     jloaiza    03/07/92 -  change ALPHA to BETA 


#     danderso   02/26/92 -  change db_block_cache_protect to


_db_block_cache_p


#     ghallmar   02/03/92 -  db_directory -> db_domain 


#     maporter   01/12/92 -  merge changes from branch 1.8.308.1 


#     maporter   12/21/91 -  bug 76493: Add control_files parameter 


#     wbridge    12/03/91 -  use of %c in archive format is


discouraged 


#     ghallmar   12/02/91 -  add global_names=true,


db_directory=us.acme.com 


#     thayes     11/27/91 -  Change default for cache_clone 


#     jloaiza    08/13/91 -         merge changes from branch


1.7.100.1 


#     jloaiza    07/31/91 -         add debug stuff 


#     rlim       04/29/91 -         removal of char_is_varchar2 


#   Bridge     03/12/91 - log_allocation no longer exists


#   Wijaya     02/05/91 - remove obsolete parameters


#


##############################################################################


# Example INIT.ORA file


#


# This file is provided by Oracle Corporation to help you customize


# your RDBMS installation for your site.  Important system parameters


# are discussed, and example settings given.


#


# Some parameter settings are generic to any size installation.


# For parameters that require different values in different size


# installations, three scenarios have been provided: SMALL, MEDIUM


# and LARGE.  Any parameter that needs to be tuned according to 


# installation size will have three settings, each one commented


# according to installation size.


#


# Use the following table to approximate the SGA size needed for the 


# three scenarious provided in this file:


#


#                     -------Installation/Database Size------


#                      SMALL           MEDIUM           LARGE



#  Block         2K    4500K            6800K           17000K


#  Size          4K    5500K            8800K           21000K


#


# To set up a database that multiple instances will be using, place


# all instance-specific parameters in one file, and then have all


# of these files point to a master file using the IFILE command.


# This way, when you change a public


# parameter, it will automatically change on all instances.  This is 


# necessary, since all instances must run with the same value for many


# parameters. For example, if you choose to use private rollback


segments, 


# these must be specified in different files, but since all gc_* 


# parameters must be the same on all instances, they should be in one


file.


#


# INSTRUCTIONS: Edit this file and the other INIT files it calls for


# your site, either by using the values provided here or by providing


# your own.  Then place an IFILE= line into each instance-specific


# INIT file that points at this file.


###############################################################################





# replace DEFAULT with your database name



db_name=ARCH                 # I did this, Tom





db_files = 80


# SMALL  



# db_files = 400


# MEDIUM 



# db_files = 1000


# LARGE  




db_file_multiblock_read_count = 8


# SMALL  



# db_file_multiblock_read_count = 16


# MEDIUM 



# db_file_multiblock_read_count = 32


# LARGE  




db_block_buffers = 100


# SMALL  



# db_block_buffers = 550


# MEDIUM 



# db_block_buffers = 3200


# LARGE  




shared_pool_size = 3500000


# SMALL



# shared_pool_size = 5000000


# MEDIUM



# shared_pool_size = 9000000


# LARGE




log_checkpoint_interval = 10000



processes = 50


# SMALL  



# processes = 100


# MEDIUM 



# processes = 200


# LARGE  




parallel_max_servers = 5


# SMALL



# parallel_max_servers = 4 x (number of CPUs)


# MEDIUM



# parallel_max_servers = 4 x (number of CPUs)


# LARGE




log_buffer = 8192


# SMALL



# log_buffer = 32768


# MEDIUM



# log_buffer = 163840


# LARGE




sequence_cache_entries = 10


# SMALL  



# sequence_cache_entries = 30


# MEDIUM 



# sequence_cache_entries = 100


# LARGE  




sequence_cache_hash_buckets = 10


# SMALL  



# sequence_cache_hash_buckets = 23


# MEDIUM 



# sequence_cache_hash_buckets = 89


# LARGE  






# audit_trail = true            # if you want auditing


# timed_statistics = true       # if you want timed statistics


max_dump_file_size = 10240      # limit trace file size to 5 Meg each



# Uncommenting the line below will cause automatic archiving if


archiving has


# been enabled using ALTER DATABASE ARCHIVELOG.


# log_archive_start = true      


# log_archive_dest = disk$rdbms:[oracle.archive]


# log_archive_format = "T%TS%S.ARC"





# If using private rollback segments, place lines of the following


# form in each of your instance-specific init.ora files:


# rollback_segments = (name1, name2)   





# If using public rollback segments, define how many


# rollback segments each instance will pick up, using the formula


#   # of rollback segments = transactions /


transactions_per_rollback_segment


# In this example each instance will grab 40/10 = 4:


# transactions = 40 


# transactions_per_rollback_segment = 10 





# Global Naming -- enforce that a dblink has same name as the db it


connects to


global_names = TRUE



# Edit and uncomment the following line to provide the suffix that


will be


# appended to the db_name parameter (separated with a dot) and stored


as the


# global database name when a database is created.  If your site uses 


# Internet Domain names for e-mail, then the part of your e-mail


address after


# the '@' is a good candidate for this parameter value.





# db_domain = us.acme.com 	# global database name is


db_name.db_domain



# FOR DEVELOPMENT ONLY, DEFAULT TO SINGLE-PROCESS



# single_process = TRUE





# FOR DEVELOPMENT ONLY, ALWAYS TRY TO USE SYSTEM BACKING STORE



# vms_sga_use_gblpagfil = TRUE





# FOR BETA RELEASE ONLY.  Enable debugging modes.  Note that these can





# adversely affect performance.  On some non-VMS ports the


db_block_cache_* 


# debugging modes have a severe effect on performance. 





#_db_block_cache_protect = true                       # memory protect


buffers


#event = "10210 trace name context forever, level 2" # data block


checking


#event = "10211 trace name context forever, level 2" # index block


checking


#event = "10235 trace name context forever, level 1" # memory heap


checking


#event = "10049 trace name context forever, level 2" # memory protect


cursors



# define parallel server (multi-instance) parameters


#ifile = ora_system:initps.ora





# define two control files by default




control_files = (ora_control1, ora_control2)



# Uncomment the following line if you wish to enable the Oracle Trace


product


# to trace server activity.  This enables scheduling of server


collections


# from the Oracle Enterprise Manager Console.  


# Also, if the oracle_trace_collection_name parameter is non-null, 


# every session will write to the named collection, as well as


enabling you 


# to schedule future collections from the console.





# oracle_trace_enable = TRUE





Received on Sun Mar 05 2000 - 22:05:00 CST












Original text of this message













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