oracle数据库启动了，但进不去，该怎么办！急！

[feng_zi]

我的oracle是在2000sever下8.16
建了两个实例orcl、gdxx
前段时间一直是好好的，两个实例都能连上
前两天我将默认的实例改为orcl后（以前是gdxx),
现在是两个实例还都启动了，orcl依然能用，但gdxx就是连不上，
将默认的实例改为gdxx,还是不行
用internal/oracle进去，说“已连接到空闲例程”
请问这该如何是好？

[penitent]

可能你改什么东西了,把你的init文件贴出来!

[feng_zi]

配置文件
#
# Copyright (c) 1991, 1998 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 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.
#
###############################################################################
db_name = "gdxx"
instance_name = gdxx
service_names = gdxx
db_files = 1024
control_files = ("D:\Oracle\oradata\gdxx\control01.ctl", "D:\Oracle\oradata\gdxx\control02.ctl", "D:\Oracle\oradata\gdxx\control03.ctl")
open_cursors = 100
max_enabled_roles = 30
db_file_multiblock_read_count = 8
db_block_buffers = 2048
shared_pool_size = 4373504
large_pool_size = 15728640
java_pool_size = 0
log_checkpoint_interval = 10000
log_checkpoint_timeout = 1800
processes = 50
parallel_max_servers = 5
log_buffer = 32768
#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 5M 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_1 = "location=D:\Oracle\oradata\gdxx\archive"
# log_archive_format = %%ORACLE_SID%%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 = ( RBS0, RBS1, RBS2, RBS3, RBS4, RBS5, RBS6 )
# Global Naming -- enforce that a dblink has same name as the db it connects to
global_names = true
# 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
oracle_trace_collection_name = ""
# define directories to store trace and alert files
background_dump_dest = D:\Oracle\admin\gdxx\bdump
#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 = D:\Oracle\admin\gdxx\udump
db_block_size = 8192
remote_login_passwordfile = exclusive
os_authent_prefix = ""
distributed_transactions = 10
compatible = 8.0.5
sort_area_size = 65536
sort_area_retained_size = 65536
mts_dispatchers = "(protocol=TCP)(disp=100)(mul=ON)(tick=15)(pool=true)(con=180)"

[thingsfly]

你在服务里启动你的gdxx服务，
然后再用svrmgrl试试！！

[feng_zi]

to thingsfly(随风):
服务里的gdxx已经启动，如果不启动的话，运行svrmgrl时说nts监听失败呀

[bzszp]

重新启动gdxx的服务，我经常碰到这种问题，重新启动它的服务就好了。

[feng_zi]

已经重启动了，还是不行，这到底是怎么回事

[mimimi]

你是怎样将默认的实例改为orcl？
说明一下
看能不能解决？

[lws0472]

把oracle的所有服务都关掉，然后重新启动

[feng_zi]

我将机子重启了，都不可以呀
我将orcl设为手机启动，重启机子也不行

将默认的实例改为orcl，是在注册表中修改的
将oracle_sid的值改为orcl，原来为gdxx，我想跟这个没有关系的

[bzszp]

在MSDOS下用SVRMGRL
CONNECT INTERNAL/ORACLE
重新启动实例
STARTUP OPEN GDXX（数据库名）
试试看

[biti_rainy]

关于这种问题，可以尝试手工启动数据库
但手工启动前，一定要将你的环境变量给设置好了

使用svrmgrl 前，先 set oracle_sid = 你要启动的数据库的sid
然后 startup pfile = ........init文件（含绝对路径）

[mimimi]

试试手动启动吧
startup open gdxx

[feng_zi]

这个我试了，
在执行报
ora-01078　处理系统参数失败

救命呀！

[feng_zi]

这个我试了，
在执行startup open gdxx时报
ora-01078　处理系统参数失败

救命呀！

[feng_zi]

结贴了，各位注意查收！