我的数据库不能启动了,是何故?

[复制链接]
查看11 | 回复9 | 2005-6-2 16:38:45 | 显示全部楼层 |阅读模式
OS: Redhat 7.1 + Oracle 8i for Linux
我的数据库曾经装好了,没有问题一切正常。
后来,我重装了。(卸载了Oracle重装的)
补丁也打过了!但生成数据库实例时,出错!
我试着启动数据库,
SVRMGR>startup pfile=/u02/admin/orcl/pfile/initorcl.ora nomount
ORA-00439: feature not enabled:Managed Standby
我查了一下日志文件:/u02/admin/orcl/bdump/alert_orcl.log
内容如下:
Thu Mar 21 19:18:37 2002
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
-----------------------
这是哪里出问题了?谢谢!
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
贴出来initsid.ora看看?
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
晚上贴上来!那个是在家里的机器上!
上次安装的时候,比较顺利!前几天觉得那个字符集有问题
,就卸载了整个Oracle,重装。打好补丁后,想建个实例。
说是数据库不可用。
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
#
# Copyright (c) 1991, 2000 by Oracle Corporation
#
##############################################################################
# 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 2K4500K
6800K 17000K
#Size
4K5500K
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.
#
###############################################################################
db_name = "orcl"
instance_name = orcl
service_names = orcl

control_files = ("/u02/oradata/orcl/control01.ctl", "/u02/oradata/orcl/control02.ctl", "/u02/oradata/orcl/control03.ctl&quot


open_cursors = 300
max_enabled_roles = 30
db_block_buffers = 2048
shared_pool_size = 4194304
large_pool_size = 614400
java_pool_size = 0
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
processes = 150
log_buffer = 163840
# audit_trail = false# if you want auditing
# timed_statistics = false# if you want timed statistics
# max_dump_file_size = 10000# limit trace file size to 5M each

##### For archiving if enabled #####
log_archive_start = true
log_archive_dest_1 = "location=/u02/admin/orcl/arch"
log_archive_format = arch_%t_%s.arc
# If using private rollback segments, place lines of the following
# form in each of your instance-specific init.ora files:
#rollback_segments = ( RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6 )
# Global Naming -- enforce that a dblink has same name as the db it connects to
# global_names = false
# 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
# define directories to store trace and alert files
background_dump_dest = /u02/admin/orcl/bdump
core_dump_dest = /u02/admin/orcl/cdump
#Uncomment this parameter to enable resource management for your database.
#The SYSTEM_PLAN is provided by default with the database.
#Change the plan name if you have created your own resource plan.# resource_manager_plan = system_plan
user_dump_dest = /u02/admin/orcl/udump
db_block_size = 8192
remote_login_passwordfile = exclusive
os_authent_prefix = ""
compatible = "8.0.5"
sort_area_size = 65536
sort_area_retained_size = 65536
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
是标准版还是企业办?
试试这个:log_archive_dest_1 = "location=/u02/admin/orcl/arch"
改成log_archive_dest='/u02/admin/orcl/arch'试试看?
不是很确信
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
改前:
SVRMGR> startup pfile=/u02/admin/orcl/pfile/initorcl.ora nomount
ORA-00439: feature not enabled: Managed Standby
改后:
SVRMGR> startup pfile=/u02/admin/orcl/pfile/initorcl.ora nomount
ORA-16032: parameter LOG_ARCHIVE_DEST destination string cannot be translated
ORA-07286: sksagdi: cannot obtain device information.
Linux Error: 2: No such file or directory
我的是企业版的!
内存:128M
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
后来这问题是怎么解决的?
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
天拉。这个是什么时候的帖子啊。
那时候俺也刚开始学ORACLE呢。
怀念那个时候的版主。
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
我现在就遇到
ORA-00439:feature not enable: managed standby
这个问题
不知道怎么解决
回复

使用道具 举报

千问 | 2005-6-2 16:38:45 | 显示全部楼层
chao_ping回答了的问题,俺怕有狗尾续貂之嫌。
回复

使用道具 举报

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

本版积分规则

主题

0

回帖

4882万

积分

论坛元老

Rank: 8Rank: 8

积分
48824836
热门排行