LinuxSir.cn,穿越时空的Linuxsir!

 找回密码
 注册
搜索
热搜: shell linux mysql
查看: 1492|回复: 12

终于装上oracle了,但又有问题了,请各位帮忙

[复制链接]
发表于 2003-12-27 13:59:18 | 显示全部楼层 |阅读模式
在此先谢谢各位linuxsir的师兄师姐们
在大家的指导之下,小弟我终于装上了oracle~!
但是。。。
我在执行了
$ lsnrctr start
$ sqlplus /nolog
SQL> connect / as sysdba
SQL> startup
之后出现如下错误:
ORA_01078:failure in processing system parameters
LRM_00109:could not open parameter file '/opt/ora9/product/9.2/dbs/initora9i.ora'

希望大家在帮帮我

以下是我按照网上的帖子装的oracle,希望友友们以后可以少费点劲
:)
   
Published on The O'Reilly Network (http://www.oreillynet.com/)
http://www.oreillynet.com/pub/a/ ... oracle_install.html
See this if you're having trouble printing code examples

Installing Oracle 9iR2 on Red Hat 9
by Roko Roic
09/04/2003
There are an ever-growing number of reasons to run the Oracle database server on a Linux-based OS. The price factor is obvious, as OS licenses can really boost the total price of your multiple workstation or clustered (RAC) server installation. Then there's the stability factor, the possibility of total remote administration, the availability of platform source code, speed, flexible filesystem, the strong Unix legacy .... Heck, even Oracle itself runs its business on what they like to call Unbreakable Linux.
Red Hat's latest and greatest Linux distribution release comes with quite a few improvements, many of which are targeted at the needs of the workstation user. As new hardware owners become early adopters, this OS will surely dominate Linux developers' workstations in the months to come. Support for cutting-edge hardware and software technologies, easier maintenance via graphical configuration tools, polished office and productivity applications, a unified interface, development tools, and, of course, Red Hat's reputation will also make it the OS of choice for many Oracle developers. Unfortunately, unless the current version was certified, Oracle installation hardly ever ran smoothly on Red Hat Linux. Still, where there's a will, there's always a way. With a little help from this article, you will have your Oracle 9iR2 server running in no time on your new Red Hat 9 box. Let us begin.
Adding Users and Groups
First, you will need to create the Oracle installation and users and groups. Oracle installation needs two Unix user groups and one runtime Oracle user.
Log in as root and issue the following commands in a terminal:
[root@miniroko]# groupadd dba
[root@miniroko]# groupadd oinstall
[root@miniroko]# useradd -g oinstall -G dba oracle
[root@miniroko]# passwd oracle
The last command will prompt you to enter the password for your oracle user. Make sure you remember it, because you will probably need it as we go along.
Creating Directories
Oracle recommends OFA, the Optimal Flexible Architecture directory structure for a deployment server, but on a development machine and for the sake of simplicity, we will install everything under /opt/ora9.
Just make sure you have at least 3.5GB available for a full installation including one database, and issue the following commands as root:
[root@miniroko]# mkdir -p /opt/ora9/product/9.2
[root@miniroko]# mkdir /var/opt/oracle
[root@miniroko]# chown oracle.dba /var/opt/oracle
[root@miniroko]# chown -R oracle.dba /opt/ora9
[root@miniroko]# chmod 755 /var/opt/oracle
You have now created Oracle runtime directories and granted write privileges to user oracle and execute privileges to group dba.
Installing Required Tools and Libraries
You will need to install the following Red Hat backward-compatibility and software-development packages before we get further underway. All of these packages can be found on Red Hat installation CDs 1-3.
gcc-3.2.2-5
cpp-3.2.2-5
glibc-devel-2.3.2-11.9
binutils-2.13.90.0.18-9
compat-gcc-7.3-2.96.118.i386.rpm
compat-libgcj-7.3-2.96.118.i386.rpm
compat-libgcj-devel-7.3-2.96.118.i386.rpm
nss_db-compat-2.2-20.i386.rpm
You can install these packages using Redhat's graphical package manager available in Start menu->System Settings->Add/Remove Applications, or from the command line, using:
rpm -Uvh <package_name>
Replace package_name with each RPM listed above.
Important notice: A shrink-wrapped Red Hat 9 and the freely downloadable version do not contain the same glibc package. The purchased version contains some patches needed for Oracle Intelligent Agent to run correctly, while the downloaded version does not contain these patches. If you are unsure which version of Red Hat you have installed, you will be on the safe side if you replace your glibc packages with prepatched glibc packages prepared by Jason McIntosh. His RPMs were built from the same source (*.rpms) files as the original ones, but with the required patches applied. If your system contains a non-empty /lib/i686 directory, fetch the i686 packages. Otherwise, you may run into trouble with misplaced libraries. Where an i686 version of the package is not available, just use whatever is.
Once you have downloaded all of the packages, use the command line rpm tool to upgrade:
% rpm -UVh package_name
Setting Kernel Parameters
Red Hat religiously sets some kernel parameters too conservatively. Check your hardware configuration and assign enough shared memory, open files, and ports, or you may run into trouble installing and running Oracle. Append these lines to /etc/sysctl.conf to set kernel parameters:
kernel.shmmax = 536870912
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.sem    = 250 32000 100 128
fs.file-max   = 65536

net.ipv4.ip_local_port_range = 1024 65000
Append these lines to /etc/security/limits.conf to modify your resource limits:
oracle soft nofile 65536
oracle hard nofile 65536
oracle soft nproc 16384
oracle hard nproc 16384
Reboot the system so the kernel changes can take effect. If rebooting is not an option, you can change the kernel params at runtime by issuing:
[root@miniroko]# echo 250 32000 100 128 > /proc/sys/kernel/sem
[root@miniroko]# echo 536870912 > /proc/sys/kernel/shmmax
[root@miniroko]# echo 4096 > /proc/sys/kernel/shmmni
[root@miniroko]# echo 2097152 > /proc/sys/kernel/shmall
[root@miniroko]# echo 65536 > /proc/sys/fs/file-max
[root@miniroko]# echo 1024 65000 > /proc/sys/net/ipv4/ip_local_port_range
For a full explanation of the /proc filesystem and available parameters, you might want to read Red Hat's Online Linux Manual.

        Related ReadingOracle Regular Expressions Pocket ReferenceBy Jonathan Gennick, Peter Linsley Table of ContentsRead Online--SafariSearch this book on Safari:      Code Fragments only

Setting up the oracle User Environment
Log in as the oracle user:
% su - oracle
I will assume that you are using the default bash shell for this user. Setting environment variables in other shells may differ from this example, so check your shell's manual page or set bash as the oracle user's shell. We will set up Oracle basic environment (users, paths, locale) and some extra values needed for Oracle to run correctly on Red Hat 9. Put the following lines at the end of ~/.bashrc:
# oracle 9i
export ORACLE_BASE=/opt/ora9
export ORACLE_HOME=/opt/ora9/product/9.2
export PATH=$ORACLE_HOME/binORACLE_HOME/Apache/Apache/binPATH
export ORACLE_OWNER=oracle
export ORACLE_SID=ora9i
export ORACLE_TERM=xterm

# Use old Linuxthreads with floating stacks instead of
# the new Native POSIX Thread Library (NPTL)
export LD_ASSUME_KERNEL=2.4.1
export THREADS_FLAG=native

# Edit paths
export LD_LIBRARY_PATH=/opt/ora9/product/9.2/libLD_LIBRARY_PATH
export PATH=/opt/ora9/product/9.2/binPATH

#
# change this NLS settings to suit your country:
# example:
# german_germany.we8iso8859p15, american_america.we8iso8859p2 etc.
#
# bawan  原文中有这句话,我把它给注释掉了
#export NLS_LANG='croatian_croatia.ee8iso8859p2'
#
# bawan  以下的是我自己填加的
export LC_ALL=”en_US.iso885819”
export LANG=”en_US.iso885819”
export LANGUAGE=”en_US.iso885819”
If you are using other national settings for Oracle (these are Croatian), consult the supported settings and change the NLS_LANG variable accordingly.
The Red Hat 9 Linux kernel comes with the new Native POSIX Thread Library, which causes Oracle installation to hang. By setting the LD_ASSUME_KERNEL variable to an older kernel version, we are making Linux use the old Linuxthreads library. For more information about the difference between these threading methods, please consult the Red Hat 9 Release notes.
       
Running the Installer
To install 9iR2 on Linux, Oracle recommends at least 512MB of RAM and at least 400MB of swap space. If you have less then 512MB of RAM and upgrading is not an option, you can resize your swap partition or create temporary swapping space. The later is a much more convenient option, as you will be needing this space only during the installation.
To set up a temporary Linux swap area, execute these lines as root:
% dd if=/dev/zero of=tmp_swap bs=1k count=900000
% chmod 600 tmp_swap
% mkswap tmp_swap
% swapon tmp_swap
After you finish installing, you can free this space:
% swapoff tmp_swap
% rm tmp_swap
Now that you have all the major obstacles out of the way, you can run the installer. Please remember that the Oracle installer must be run from X. You will need to allow the local oracle user to write to your X display:
$ xhost +127.0.0.1
Do not change to your CD-ROM mount directory (e.g., /mnt/cdrom), because you will not be able to unmount the first CD to insert others when asked. Start the installer from your home directory using:
$ su - oracle
$ /mnt/cdrom/install/linux/runInstaller
Installation
We will not describe the installation process in detail, as Oracle provides extensive documentation on that subject and it is way beyond the scope of this article. It is pretty much self-explanatory, but if you run into trouble, there's always a help button to assist you. If you need more help, check the docs directory on the Oracle CDs, the online Oracle Documentation, or Oracle Linux Center. During the installation, Oracle will ask you to insert other disks. When asked, open up a new console, unmount the current disk with umount /dev/cdrom (as root) and replace the disk. If Red Hat 9 does not mount it automagically, mount it yourself with mount /dev/cdrom and choose to continue with the installation wizard.
As you go along, your installation may produce three different errors:
·        You may see an error dialog informing about problems with ins_oemagent.mk. Ignore this one; we will fix it in post installation.

Figure 1. ins_oemagent.mk errors
·        A dialog may inform you about an Error in invoking target install of makefile $ORACLE_HOME/ctx/lib/ins_ctx.mk.

Figure 2. makefile error
When this happens, open up a new X terminal and log in as the oracle user. Execute the following commands:
[oracle@miniroko oracle]$ cd $ORACLE_HOME/install
[oracle@miniroko install]$ tail make.log
You will see a line like this:
gcc -o ctxhx -L/opt/ora9/product/9.2/ctx/lib/ -L/opt/ora9/product/9.2/lib/
-L/opt/ora9/product/9.2/lib/stubs/  /opt/ora9/product/9.2/ctx/lib/ctxhx.o
-L/opt/ora9/product/9.2/ctx/lib/ -lm -lsc_ca -lsc_fa -lsc_ex -lsc_da -lsc_ut
-lsc_ch -lsc_fi -lctxhx -lc -Wl,-rpath,/opt/ora9/product/9.2/ctx/lib -lnls9
-lcore9 -lnls9 -lcore9 -lnls9 -lxml9 -lcore9 -lunls9 -lnls9

Figure 3. The make.log
Copy this line, add -ldl at the end, and run it in $ORACLE_HOME/bin.
[oracle@miniroko]$ cd $ORACLE_HOME/bin
[oracle@miniroko bin]$ gcc -o ctxhx -L/opt/ora9/product/9.2/ctx/lib/
-L/opt/ora9/product/9.2/lib/ -L/opt/ora9/product/9.2/lib/stubs/  
/opt/ora9/product/9.2/ctx/lib/ctxhx.o -L/opt/ora9/product/9.2/ctx/lib/
-lm -lsc_ca -lsc_fa -lsc_ex -lsc_da -lsc_ut -lsc_ch -lsc_fi -lctxhx -lc
-Wl,-rpath,/opt/ora9/product/9.2/ctx/lib -lnls9 -lcore9 -lnls9 -lcore9
-lnls9 -lxml9 -lcore9 -lunls9 -lnls9 -ldl
Now you have fixed the problem, so hit the ignore button on the dialog and the installation will continue.
·        The installation may inform you that agent failed to start. Choose ignore on this one; we will also fix it in post installation.
Do not create a database at the end of the installation. Not all things are operational at this point, and we still need to perform some minor fixes. Click on Software only and continue. Don't worry, you will be able to create your database later using dbca, the Oracle database configuration assistant.

Figure 4. Do not create a database
Post-Installation
Let's fix the issues Oracle had with ins_ctx.mk and starting the agent. Open a new terminal and log in as the oracle user. Execute these lines:
[oracle@miniroko oracle]$ cd $ORACLE_HOME/network/lib
[oracle@miniroko lib]$ make -f ins_net_client.mk install
Now edit the $ORACLE_HOME/ctx/lib/ins_ctx.mk file. Change lines 13-14 from:
ctxhx: $(CTXHXOBJ)
$(LINK) $(CTXHXOBJ) $(INSO_LINK)
to
ctxhx: $(CTXHXOBJ)
$(LINK) -ldl $(CTXHXOBJ) $(INSO_LINK)
You are now ready to retry making:
[oracle@miniroko lib]$ make -f $ORACLE_HOME/ctx/lib/ins_ctx.mk install
Voila, you now have a fully working installation of Oracle 9iR2 database server. If you wish, you can now create your Oracle database using dbca.
Starting and Stopping the Database
svrmgrl is no longer supported by Oracle, so use sqlplus for startup and shutdown operations. To start the server:
[root@miniroko]# su - oracle
[oracle@miniroko oracle]$ lsnrctl start
[oracle@miniroko oracle]$ sqlplus /nolog

SQL*Plus: Release 9.2.0.1.0 - Production on ?et Svi 29 13:52:34 2003

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

SQL> connect / as sysdba
Connected to an idle instance.
#
#  bawan  我运行startup语句时出如下错误
#  ORA_01078:failure in processing system parameters
#  LRM_00109:could not open parameter
#  file’/opt/ora9/product/9.2/dbs/initora9i.ora’
SQL> startup
ORACLE instance started.

Total System Global Area   93393176 bytes
Fixed Size                   450840 bytes
Variable Size              75497472 bytes
Database Buffers           16777216 bytes
Redo Buffers                 667648 bytes
Database mounted.
Database opened.
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
To shut down the server:
[root@miniroko]# su - oracle
[oracle@miniroko oracle]$ lsnrctl stop
[oracle@miniroko oracle]$ sqlplus /nolog

SQL*Plus: Release 9.2.0.1.0 - Production on ?et Svi 29 13:55:32 2003

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

SQL> connect / as sysdba
Connected.
SQL> shutdown
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> exit
Disconnected from Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
To integrate Oracle with Red Hat's SysV init process and make startup and shutdown automatic, you can use Gurulab's Oracle9i RHL Run Package. I do not recommend Oracle's native scripts $ORACLE_HOME/bin/dbstart and $ORACLE_HOME/bin/dbshut, as they do not always work as advertised and require some changes.
Conclusion
You now have a fully featured Oracle installation on your computer. Please remember that Oracle 9.2 is not certified for Red Hat 9, and that this combination is not endorsed in production and deployment environments. As a workstation, however, it is perfectly stable and usable.
Roko Roic currently works at Tis.kis, developing core and user-level GSM related systems.

Return to the Linux DevCenter.
oreillynet.com Copyright &copy; 2003 O'Reilly & Associates, Inc.
发表于 2003-12-27 18:50:47 | 显示全部楼层
9i默认启动的时候会使用spfile,检查$ORACLE_HOME/dbs目录下有没有spfile,如果有,可以
create pfile from spfile
来创建pfile,之后startup -pfile=filename
就可以用pfile启动数据库了
 楼主| 发表于 2003-12-28 13:37:23 | 显示全部楼层
没有啊,那我该怎么办?
发表于 2003-12-28 19:49:35 | 显示全部楼层
ls $ORACLE_HOME/dbs
结果贴出来看看
 楼主| 发表于 2003-12-29 10:06:04 | 显示全部楼层
initdw.ora  init.ora
下边是我的init.ora文件
#
# $Header: init.ora 06-aug-98.10:24:40 atsukerm Exp $
#
# Copyright (c) 1991, 1997, 1998 by Oracle Corporation
# NAME
#   init.ora
# FUNCTION
# NOTES
# MODIFIED
#     atsukerm   08/06/98 -  fix for 8.1.
#     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.
#
# NOTE: Parameter values suggested in this file are based on conservative
# estimates for computer memory availability. You should adjust values upward
# for modern machines.
#
# You may also consider using Database Configuration Assistant tool (DBCA)
# to create INIT file and to size your initial set of tablespaces based
# on the user input.
###############################################################################

# replace DEFAULT with your database name
db_name=DEFAULT

db_files = 80                                                         # SMALL
# db_files = 400                                                      # MEDIUM
# db_files = 1500                                                     # 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 = 32768                                                    # SMALL
# log_buffer = 32768                                                  # MEDIUM
# log_buffer = 163840                                                 # 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/5 = 8:
# transactions = 40
# transactions_per_rollback_segment = 5

# 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, 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

# Uncomment the following line, if you want to use some of the new 8.1
# features. Please remember that using them may require some downgrade
# actions if you later decide to move back to 8.0.

#compatible = 8.1.0
 楼主| 发表于 2003-12-29 10:07:15 | 显示全部楼层
下边是我的initdw.ora文件
#***********************************************************************
# Example INIT.ORA file for data-warehousing applications
#***********************************************************************
# This file is provided by Oracle Corporation to help you customize
# your RDBMS installation for your data warehousing or
# business intelligence application. The primary purpose of this file
# is to provide a starting point for parameter settings in a
# data-warehouse. This file is designed for release 9.0.
#
# All of the parameters in this file and discussed in more detail
# in the documentation. This file should be used for guidance
# on the setting of parameters, not as a reference for parameters.
#
# 'Data warehousing' is an expansive term. In general, this parameter
# file assumes that a data warehouse is characterized by:
#   - end-users execute only queries (rather than updates)
#   - end-user queries often examine large amounts of data
#   - data-loading and updating is managed in separate operations;
#      often, data-modifications occur during batch operations although
#      some data warehouses receive new data throughout the day
#
# Some parameter settings are generic to any data-warehouse application.
# Other parameters depend upon the size of the data warehouse; different
# settings are provided for these parameters, for the following categories
# of data warehouses:
#      Category      Size of raw data      CPUs      Memory
#      DEMO          <1GB                  1         128MB
#      SMALL         <100GB                4         ~1GB
#      MEDIUM        100-500GB             4-12      4-10GB
#      LARGE         >500GB                12-16+    >10GB
# 'Raw data' refers to the size of the actual data, and does not
# include index space or temp space.
#
# The uncommented parameters in this init.ora file are configured for
# a 'demo' system. These parameters are suitable for using the 'Sales
# History' Schema (a sample data warehouse schema, which is included
# on the Oracle9i CD), which is used throughout Oracle's documentation
# and training related to data warehousing. Most customers will be
# able to install and run this schema on a single-CPU workstation.
#
# More detailed information on all parameters can be found in the
# in the documentation.
#
# This parameter file provide initial guidelines for the configuration
# parameters of a data warehouse. Using these guidelines, you should
# be able to achieve good performance for a wide variety of data
# warehouse applications. However, further tuning of these parameters
# for a specific application may yield improved performance.
#
# INSTRUCTIONS: Edit this file and the other INIT files at your site,
# either by using the values provided here or by providing your own.
# If you are using Oracle Real Application Clusters, place an IFILE=
# line into each instance-specific INIT file that points at this file.


#***********************************************************************
# Database parameters
#***********************************************************************


# Database blocks should be large in data warehouses. This improves
# performance for operations involving large amounts of data.
db_block_size = 8192

# For a large data warehouse, db_files should be set to a large value.
#db_files = 1000
                                                                                
#***********************************************************************
# Memory parameters
#***********************************************************************

# In a data warehouse, the majority of physical memory will be
# allocated for the one of the following two purposes:
#    Runtime memory: used for sorting and hashing data during query processing
#       (governed by the parameter pga_aggregate_size)
#    Data caching: used to accelerate performance by avoid disk accesses
#       (governed by the parameter db_cache_size)
# Additionally, a significant amount of memory may need to be allocated for:
#    Shared pool: used for storing shared memory constructs
#       (governed by the parameter shared_pool_size)
#    Large pool: used during parallel-execution processing
#       (governed by the parameter large_pool_size)
#
# Memory is managed globally. The DBA should first determine how much
# memory is available for Oracle to use. Then, the DBA should choose
# memory parameters so that pga_aggregate_size + db_cache_size +
# shared_pool_size + large_pool_size is roughly equal to the amount
# of memory available for the Oracle database.
#
# For example, suppose that a DBA is managing a small data mart. The
# data mart server has 1GB of physical memory. The DBA has determined
# that 500M of memory will be used by the operating system and other
# applications, so that 500M is available for Oracle.
#
# The DBA may choose the following settings:
#   shared_pool_size = 50M
#   pga_aggregate_size = 200M
#   db_cache_size = 200M
#   large_pool_size = <default>
#
# The total memory utilization is 450M plus a system-determined value
# for the large pool.
#
# The following sections discuss each of these memory-related
# parameters in more detail. These examples assume that the data
# warehouse server has 1GB, 8GB, and 16GB respectively for small,
# medium, and large configurations.


# Runtime memory (the memory used for sorting and hashing during query
# execution) is automatically and globally managed when the
# pga_aggregate_target parameter is set. For data warehouse workloads
# which involve sorts and joins of large volumes of data, the
# pga_aggregate_target should be set to a large value.
#
# pga_aggregate_target should, in general, be equal to 20-80% of the
# available memory, depending on the workload. The values below assume
# a mixed data-warehouse workload.
#
# This parameters (introduced in Oracle9i) replaces all of the
# following parameters: hash_area_size, sort_area_size,
# create_bitmap_area_size, and bitmap_merge_area_size


pga_aggregate_target = 30M                                #DEMO
#pga_aggregate_target = 200M                              #SMALL
#pga_aggregate_target = 3000M                             #MEDIUM
#pga_aggregate_target = 6000M                             #LARGE


# The database cache is also a globally-managed portion of memory. The
# database cache should be set to a large value for data warehouse
# workloads which involves short-running queries and/or the access of
# small tables and indexes.
#
# db_cache_size should, in general, be equal to 20-80% of the
# available memory, depending on the workload. The values below assume
# a mixed data-warehouse workload.
#

db_cache_size = 30M                                #DEMO
#db_cache_size = 200M                              #SMALL
#db_cache_size = 3000M                             #MEDIUM
#db_cache_size = 6000M                             #LARGE


# Shared pool size should be, in general, equal to 5-10% of the
# available memory. Data warehouses typically do not require as much
# memory for shared pool as OLTP systems.

shared_pool_size = 20M                                   #DEMO
#shared_pool_size = 50M                                  #SMALL
#shared_pool_size = 400M                                 #MEDIUM
#shared_pool_size = 800M                                 #LARGE
                                                                                

# The default for large_pool_size should appropriate for most
# environments.
#
# The Large Pool is used for several purposes. In a data warehouse the
# majority of the space in the Large Pool will be used for
# parallel-execution internal message buffers. The amount of memory
# required by parallel-execution is proportional to the product of the
# number of concurrent parallel-execution users and the square of the
# number of CPU's.
#
# The documentation describes in detail how to estimate the default size
# of the Large Pool, and the conditions under which this parameter
# should be set explicitly.
#
# Here are some very general estimates on the amount of memory required
# for the Large Pool based on the number of CPU's:
#    4 cpus:  5M  (with parallel_threads_per_cpu = 4)
#    8 cpus:  5M  (with parallel_threads_per_cpu = 2)
#    8 cpus: 20M  (with parallel_threads_per_cpu = 4)
#   16 cpus: 20M  (with parallel_threads_per_cpu = 2)
#   32 cpus: 80M  (with parallel_threads_per_cpu = 2)
#
# The Large Pool is only used for parallel-execution message buffers
# when parallel_automatic_tuning is enabled. If
# parallel_automatic_tuning is not utilitized, then parallel-execution
# message buffers are stored in the shared pool, and the
# shared_pool_size parameter should be adjusted appropriately.


#***********************************************************************
# Parallel Execution parameters
#***********************************************************************


# Parallel execution parameters were greatly simplified in Oracle8i.
# Data warehouses developed on older releases of Oracle may use
# different init.ora parameters. While these older parameters continue
# to be supported, these parameters below are recommended for all new
# data warehouses, and should be considered when upgrading data
# warehouses from previous releases.

# Setting parallel_automatic_tuning will result in the database
# configuring itself to support parallel execution.
parallel_automatic_tuning = true

# This parameter determines the default number of parallel execution
# processes. Typically, 2 parallel processes per CPU provides good
# performance. However, for systems with a smaller number of CPUs or
# for systems in which the IO subsystem is slow relative to the the
# CPU's, more parallel processes may be desired and the value of this
# parameter may be increased.
parallel_threads_per_cpu = 4                                 #SMALL
#parallel_threads_per_cpu = 2 or 4                           #MEDIUM
#parallel_threads_per_cpu = 2                                #LARGE


#***********************************************************************
# Optimizer and query parameters
#***********************************************************************

# All data warehouses should use the cost-based optimizer. All basic
# data warehouse performance features, such as star-query support,
# hash joins, parallel execution, and bitmap indexes are only
# accessible via the cost-based optimizer.
optimizer_mode = choose

# When using a star schema, set this parameter to true.
star_transformation_enabled = true


#***********************************************************************
# IO parameters
#***********************************************************************

# Multiblock reads allow for the database to retrieve multiple
# database blocks in a single IO. In general, a high multiblock read
# count provides better performance, particularly for operations on
# large volumes of data. Oracle supports IO's up to 1MB on many
# platforms. Disk striping will also affect the value for multiblock
# read count, since the stripe size should ideally be a multiple of
# the IO size.

# If you are gathering optimizer system statistics (see DBMSSTAT.SQL
# for more information), then you should set this parameter to a high
# value.
#db_file_multiblock_read_count = 64
                                                                                
# If you are not gathering optimizer system statistics, then you
# should set this parameter to a lower value.
db_file_multiblock_read_count = 16



#***********************************************************************
# Materialized view parameters
#***********************************************************************

# This parameter enables the use of materialized views for improved
# query performance.
query_rewrite_enabled = true

# This parameter determines the degree to which Oralce enforces
# integrity rules during query rewrite. In most data-warehouse
# environment, 'trusted' is the appropriate setting.
query_rewrite_integrity = trusted



#***********************************************************************
# Compatibility
#***********************************************************************

# When building a new application, both compatibility and
# optimizer_features_enabled should be set to the current release to
# take advantage of all new features. If you are upgrading an existing
# application to Oracle9i, then you may want to consider setting one
# or both of these parameters to an earlier release.
#compatible = 9.0
#optimizer_features_enabled = 9.0


#***********************************************************************
# Other Parameters
#***********************************************************************


# This section lists other parameters that, although not specific
# to data warehousing, are required for any Oracle database. By
# uncommenting these parameters, this parameter file can be used
# as a complete stand-alone init.ora file.
                                                                                
#db_name = MY_DB_NAME

# Define at least two control files by default
#control_files = (ora_control1, ora_control2)
 楼主| 发表于 2003-12-29 10:15:51 | 显示全部楼层
以下是我的rdbms/log/alert_ora9i.log文件

Thu Jun 26 14:51:38 2003
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
  processes                = 50
  shared_pool_size         = 4194304
  control_files            = ora_control1, ora_control2
  db_block_buffers         = 100
  log_buffer               = 32768
  log_checkpoint_interval  = 10000
  db_files                 = 80
  db_file_multiblock_read_count= 8
  global_names             = TRUE
  parallel_max_servers     = 5
  max_dump_file_size       = 10240
  db_name                  = DEFAULT
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
RECO started with pid=7
Thu Jun 26 14:51:43 2003
ALTER DATABASE   MOUNT
Thu Jun 26 14:51:43 2003
ORA-00202: controlfile: 'ora_control1'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Thu Jun 26 14:51:43 2003
ORA-205 signalled during: ALTER DATABASE   MOUNT...
Thu Jun 26 14:55:55 2003
alter database mount
Thu Jun 26 14:55:55 2003
ORA-00202: controlfile: 'ora_control1'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Thu Jun 26 14:55:58 2003
ORA-205 signalled during: alter database mount...
Thu Jun 26 21:03:38 2003
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
  processes                = 50
  shared_pool_size         = 4194304
  control_files            = ora_control1, ora_control2
  db_block_buffers         = 100
  log_buffer               = 32768
  log_checkpoint_interval  = 10000
  db_files                 = 80
  db_file_multiblock_read_count= 8
  global_names             = TRUE
  parallel_max_servers     = 5
  max_dump_file_size       = 10240
  db_name                  = ora9i
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
RECO started with pid=7
Thu Jun 26 21:03:42 2003
ALTER DATABASE   MOUNT
Thu Jun 26 21:03:42 2003
ORA-00202: controlfile: 'ora_control1'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Thu Jun 26 21:03:42 2003
ORA-205 signalled during: ALTER DATABASE   MOUNT...
Sun Dec 28 11:20:51 2003
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
  processes                = 50
  shared_pool_size         = 4194304
  control_files            = ora_control1, ora_control2
  db_block_buffers         = 100
  log_buffer               = 32768
  log_checkpoint_interval  = 10000
  db_files                 = 80
  db_file_multiblock_read_count= 8
  global_names             = TRUE
  parallel_max_servers     = 5
  max_dump_file_size       = 10240
  db_name                  = ora9i
PMON started with pid=2
DBW0 started with pid=3
CKPT started with pid=5
LGWR started with pid=4
SMON started with pid=6
RECO started with pid=7
Sun Dec 28 11:20:56 2003
ALTER DATABASE   MOUNT
Sun Dec 28 11:20:56 2003
ORA-00202: controlfile: 'ora_control1'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Sun Dec 28 11:20:56 2003
ORA-205 signalled during: ALTER DATABASE   MOUNT...
Sun Dec 28 11:22:31 2003
Shutting down instance: further logons disabled
Shutting down instance (normal)
License high water mark = 1
Sun Dec 28 11:22:31 2003
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Mon Dec 29 10:09:59 2003
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
SCN scheme 2
Using log_archive_dest parameter default value
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 9.2.0.1.0.
System parameters with non-default values:
  processes                = 50
  shared_pool_size         = 4194304
  control_files            = ora_control1, ora_control2
  db_block_buffers         = 100
  log_buffer               = 32768
  log_checkpoint_interval  = 10000
  db_files                 = 80
  db_file_multiblock_read_count= 8
  global_names             = TRUE
  parallel_max_servers     = 5
  max_dump_file_size       = 10240
  db_name                  = ora9i
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
RECO started with pid=7
Mon Dec 29 10:10:04 2003
ALTER DATABASE   MOUNT
Mon Dec 29 10:10:04 2003
ORA-00202: controlfile: 'ora_control1'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon Dec 29 10:10:04 2003
ORA-205 signalled during: ALTER DATABASE   MOUNT...
Mon Dec 29 10:10:22 2003
Shutting down instance: further logons disabled
Shutting down instance (normal)
License high water mark = 1
Mon Dec 29 10:10:22 2003
ALTER DATABASE CLOSE NORMAL
ORA-1507 signalled during: ALTER DATABASE CLOSE NORMAL...
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archiving is disabled
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
发表于 2003-12-30 16:36:16 | 显示全部楼层

你在安装的时候没选择创建数据库吧

如果没创建数据库,就用dbca创建一个数据库,建完后有一个文件,$ORACLE_BASE/admin/xxxx/pfile/initxxxx.ora,其中xxxx代表你创建的数据库的名字。
 楼主| 发表于 2003-12-30 17:27:26 | 显示全部楼层
Thank you very much~!
I select software only,when I installed~!
发表于 2004-1-1 17:22:45 | 显示全部楼层
有没有人在AS 3上装的很顺利啊,能否写个很详细的文档呢

需要创建一个命令解释程序脚本/etc/rc.d/init.d/ora9

您需要登录后才可以回帖 登录 | 注册

本版积分规则

快速回复 返回顶部 返回列表