前天一早开始,ORACLE 服务就启不开,报1067错误,
上网找了一下,很多说是因为IP地址或是计算机名修改了造成的,建议修改listener.ora、tnsnames.ora等文件的计算机名。
这两处已经确定是没有问题的了。这个1067错误发生后,重启计算机,ORACLE 服务就能启动了,但是没准什么时候又会报错,ORACLE 服务也会随之关闭。看了一下日志问题,有下面信息,不知道能肯提供一些解决问题的办法。谢谢了。Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 956301312
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 1610612736
control_files = D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 603979776
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 300
pga_aggregate_target = 847249408
PMON started with pid=2, OS id=3064
PSP0 started with pid=3, OS id=3068
MMAN started with pid=4, OS id=392
DBW0 started with pid=5, OS id=1668
DBW1 started with pid=6, OS id=1692
LGWR started with pid=7, OS id=1680
CKPT started with pid=8, OS id=1688
SMON started with pid=9, OS id=1700
RECO started with pid=10, OS id=1676
CJQ0 started with pid=11, OS id=1684
MMON started with pid=12, OS id=1704还有下面的一段日志:
db_recovery_file_dest_size of 2048 MB is 0.00% 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.不能确认是否和表空间有所关系呢,谢谢。
上网找了一下,很多说是因为IP地址或是计算机名修改了造成的,建议修改listener.ora、tnsnames.ora等文件的计算机名。
这两处已经确定是没有问题的了。这个1067错误发生后,重启计算机,ORACLE 服务就能启动了,但是没准什么时候又会报错,ORACLE 服务也会随之关闭。看了一下日志问题,有下面信息,不知道能肯提供一些解决问题的办法。谢谢了。Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 956301312
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 1610612736
control_files = D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 603979776
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=orclXDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 300
pga_aggregate_target = 847249408
PMON started with pid=2, OS id=3064
PSP0 started with pid=3, OS id=3068
MMAN started with pid=4, OS id=392
DBW0 started with pid=5, OS id=1668
DBW1 started with pid=6, OS id=1692
LGWR started with pid=7, OS id=1680
CKPT started with pid=8, OS id=1688
SMON started with pid=9, OS id=1700
RECO started with pid=10, OS id=1676
CJQ0 started with pid=11, OS id=1684
MMON started with pid=12, OS id=1704还有下面的一段日志:
db_recovery_file_dest_size of 2048 MB is 0.00% 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.不能确认是否和表空间有所关系呢,谢谢。
可重启后为什么服务自己还开了呢?
是否要加上这个域名呢?谢谢。
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraDb11g_home1
类似目录下的东西看,这个是11g的
------------------------------------------------------------------------------
Blog: http://blog.csdn.net/tianlesoftware
网上资源: http://tianlesoftware.download.csdn.net
相关视频:http://blog.csdn.net/tianlesoftware/archive/2009/11/27/4886500.aspx
DBA1 群:62697716(满); DBA2 群:62697977(满)
DBA3 群:63306533; 聊天 群:40132017
System parameters with non-default values:
processes = 150
__shared_pool_size = 889192448
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 1610612736
control_files = D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 671088640
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=ORCLXDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = ORCL
open_cursors = 300
pga_aggregate_target = 847249408
PMON started with pid=2, OS id=3728
PSP0 started with pid=3, OS id=640
MMAN started with pid=4, OS id=1568
DBW0 started with pid=5, OS id=500
DBW1 started with pid=6, OS id=332
LGWR started with pid=7, OS id=3748
CKPT started with pid=8, OS id=3492
SMON started with pid=9, OS id=3384
RECO started with pid=10, OS id=1368
CJQ0 started with pid=11, OS id=3536
MMON started with pid=12, OS id=1652
Wed Aug 25 09:05:15 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=3400
Wed Aug 25 09:05:15 2010
starting up 1 shared server(s) ...
Wed Aug 25 09:05:15 2010
alter database mount exclusive
Wed Aug 25 09:05:19 2010
Setting recovery target incarnation to 2
Wed Aug 25 09:05:19 2010
Successful mount of redo thread 1, with mount id 1884150859
Wed Aug 25 09:05:19 2010
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Aug 25 09:05:19 2010
alter database open
Wed Aug 25 09:05:19 2010
Beginning crash recovery of 1 threads
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.4.0.
System parameters with non-default values:
processes = 150
__shared_pool_size = 889192448
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 1610612736
control_files = D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 671088640
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=ORCLXDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = ORCL
open_cursors = 300
pga_aggregate_target = 847249408
MMAN started with pid=4, OS id=3348
DBW0 started with pid=5, OS id=3352
DBW1 started with pid=6, OS id=3356
LGWR started with pid=7, OS id=3360
CKPT started with pid=8, OS id=3364
SMON started with pid=9, OS id=3368
RECO started with pid=10, OS id=3372
CJQ0 started with pid=11, OS id=3376
MMON started with pid=12, OS id=3380
Wed Aug 25 09:11:49 2010
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=13, OS id=3384
Wed Aug 25 09:11:49 2010
starting up 1 shared server(s) ...
Wed Aug 25 09:11:50 2010
alter database mount exclusive
PMON started with pid=2, OS id=3340
PSP0 started with pid=3, OS id=3344
Setting recovery target incarnation to 2
Wed Aug 25 09:11:54 2010
Successful mount of redo thread 1, with mount id 1884171734
Wed Aug 25 09:11:54 2010
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Wed Aug 25 09:11:54 2010
alter database open
Wed Aug 25 09:11:54 2010
Beginning crash recovery of 1 threads
parallel recovery started with 15 processes
Wed Aug 25 09:11:54 2010
Started redo scan
Wed Aug 25 09:11:54 2010
Completed redo scan
45 redo blocks read, 7 data blocks need recovery
Wed Aug 25 09:11:54 2010
Started redo application at
Thread 1: logseq 1059, block 50826, scn 120644336
Wed Aug 25 09:11:54 2010
Recovery of Online Redo Log: Thread 1 Group 3 Seq 1059 Reading mem 0
Mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Wed Aug 25 09:11:54 2010
Completed redo application
Wed Aug 25 09:11:55 2010
Completed crash recovery at
Thread 1: logseq 1059, block 50871, scn 120664386
7 data blocks read, 7 data blocks written, 45 redo blocks read
Wed Aug 25 09:11:55 2010
Thread 1 advanced to log sequence 1060 (thread open)
Thread 1 opened at log sequence 1060
Current log# 1 seq# 1060 mem# 0: D:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO01.LOG
Successful open of redo thread 1
Wed Aug 25 09:11:55 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Wed Aug 25 09:11:55 2010
SMON: enabling cache recovery
Wed Aug 25 09:11:57 2010
Successfully onlined Undo Tablespace 1.
Wed Aug 25 09:11:57 2010
SMON: enabling tx recovery
Wed Aug 25 09:11:57 2010
Database Characterset is ZHS16GBK
Opening with internal Resource Manager plan
where NUMA PG = 1, CPUs = 16
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=31, OS id=3540
Wed Aug 25 09:12:01 2010
db_recovery_file_dest_size of 2048 MB is 0.00% 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.
Wed Aug 25 09:12:01 2010
Completed: alter database open
重建了一下EM,
想如果真是更改计算机名的问题,这样应该也是可以解决的吧?我是在重启后,当前实例开着的时候执行的,到最后出现了错误,日志如下:提示説,指定服务已存在,但是如果我把服务关了,再执行重建还可以吗?之前服务关的时候,输入SYS密码总是提示不正确,只有服务开的状态才能成功,但是确出了错误提示。
配置: 开始执行: CMD /C D:\oracle\product\10.2.0\db_1\bin\emctl.bat deploy dbconsole D:\oracle\product\10.2.0\db_1\db_orcl:3938 orcl
2010-8-25 8:54:59 oracle.sysman.emcp.util.PlatformInterface executeCommand
配置: Exit value of 255
2010-8-25 8:54:59 oracle.sysman.emcp.util.PlatformInterface executeCommand
配置: Creating shared install...
Source location: D:\oracle\product\10.2.0\db_1
Destination (shared install) : D:\oracle\product\10.2.0\db_1\db_orcl
DeployMode : dbconsoleCreating directories...
Setting console properties ...
Setting log and trace files locations for Console ...
Setting log and trace files locations for Agent ... 2010-8-25 8:54:59 oracle.sysman.emcp.util.PlatformInterface executeCommand
配置: CreateService FAILED: 指定的服务已存在。
Service creation failed. Aborting...2010-8-25 8:54:59 oracle.sysman.emcp.util.PlatformInterface executeCommand
警告: 执行 CMD /C D:\oracle\product\10.2.0\db_1\bin\emctl.bat deploy dbconsole D:\oracle\product\10.2.0\db_1\db_orcl:3938 orcl 时出错
2010-8-25 8:54:59 oracle.sysman.emcp.EMAgentConfig instantiateEMConfigFiles
配置: Failed to deploy state dirs
2010-8-25 8:54:59 oracle.sysman.emcp.EMConfig perform
严重: 实例化 EM 配置文件时出错
有关详细资料, 请参阅 D:\oracle\product\10.2.0\db_1\cfgtoollogs\emca\orcl\emca_2010-08-25_08-51-33-上午.log 中的日志文件。
2010-8-25 8:54:59 oracle.sysman.emcp.EMConfig perform
配置: Stack Trace:
oracle.sysman.emcp.exception.EMConfigException: 实例化 EM 配置文件时出错
at oracle.sysman.emcp.EMAgentConfig.updateAgentConfigFiles(EMAgentConfig.java:2689)
at oracle.sysman.emcp.EMAgentConfig.performConfiguration(EMAgentConfig.java:1206)
at oracle.sysman.emcp.EMAgentConfig.invoke(EMAgentConfig.java:230)
at oracle.sysman.emcp.EMAgentConfig.invoke(EMAgentConfig.java:208)
at oracle.sysman.emcp.EMConfig.perform(EMConfig.java:175)
at oracle.sysman.emcp.EMConfigAssistant.invokeEMCA(EMConfigAssistant.java:486)
at oracle.sysman.emcp.EMConfigAssistant.performConfiguration(EMConfigAssistant.java:1142)
at oracle.sysman.emcp.EMConfigAssistant.statusMain(EMConfigAssistant.java:470)
at oracle.sysman.emcp.EMConfigAssistant.main(EMConfigAssistant.java:419)