- 最后登录
- 2017-5-4
- 在线时间
- 81 小时
- 威望
- 999
- 金钱
- 2391
- 注册时间
- 2013-9-11
- 阅读权限
- 150
- 帖子
- 1124
- 精华
- 5
- 积分
- 999
- UID
- 1220
|
1#
发表于 2017-4-15 21:33:05
|
查看: 1342 |
回复: 0
数据库跑在无备份状态(既没有归档备份,也没有在线日志),操作系统直接关机,重启操作系统,然后重启数据库,数据库启动到mount阶段,没有问题,执行open时报1113错误,这种情况要怎么解决?
我觉得是因为直接关机导致数据文件和控制文件的SCN不一致产生的错误,是否可以通过alter database open resetlogs;命令启动数据库?因为还在拷贝文件,很慢,暂时还没有尝试。谢谢
非常感谢大家回复,因为比较忙所以没有及时回复大家。
下面把最近的
报警日志如下:
Dump file f:\oracle\qas\saptrace\background\alert_qas.log
Tue Nov 13 10:33:30 2012
ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows Server 2003 Version V5.2 Service Pack 1
CPU : 2 - type 8664, 1 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:2715M/4093M, Ph+PgF:24288M/25240M
Tue Nov 13 10:33:30 2012
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =10
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes = 80
sessions = 96
event = 10191 trace name context forever, level 1
sga_max_size = 1426063360
__shared_pool_size = 335544320
shared_pool_size = 335544320
__large_pool_size = 16777216
__java_pool_size = 16777216
__streams_pool_size = 0
shared_pool_reserved_size= 32196526
filesystemio_options = setall
sga_target = 1426063360
control_files = D:\ORACLE\QAS\ORIGLOGA\CNTRL\CNTLRQAS.DBF, D:\ORACLE\QAS\ORIGLOGB\CNTRL\CNTRLQAS.DBF, F:\ORACLE\QAS\SAPDATA1\CNTRL\CNTRLQAS.DBF
control_file_record_keep_time= 30
db_block_size = 8192
__db_cache_size = 1040187392
db_cache_size = 335544320
compatible = 10.2.0
log_archive_dest = D:\oracle\QAS\oraarch\QASarch
log_buffer = 14274560
log_checkpoint_interval = 0
db_files = 254
log_checkpoints_to_alert = TRUE
dml_locks = 4000
undo_management = AUTO
undo_tablespace = PSAPUNDO
undo_retention = 43200
recyclebin = off
remote_os_authent = TRUE
remote_login_passwordfile= EXCLUSIVE
job_queue_processes = 1
background_dump_dest = F:\ORACLE\QAS\SAPTRACE\BACKGROUND
user_dump_dest = F:\ORACLE\QAS\SAPTRACE\USERTRACE
core_dump_dest = F:\ORACLE\QAS\SAPTRACE\BACKGROUND
optimizer_features_enable= 10.2.0.1
sort_area_size = 2097152
sort_area_retained_size = 0
db_name = QAS
open_cursors = 800
_optim_peek_user_binds = FALSE
pga_aggregate_target = 429287014
workarea_size_policy = AUTO
statistics_level = typical
PSP0 started with pid=3, OS id=5484
MMAN started with pid=4, OS id=5392
DBW0 started with pid=5, OS id=5112
LGWR started with pid=6, OS id=4560
CKPT started with pid=7, OS id=5768
SMON started with pid=8, OS id=5288
RECO started with pid=9, OS id=4884
CJQ0 started with pid=10, OS id=4848
MMON started with pid=11, OS id=5312
MMNL started with pid=12, OS id=4896
PMON started with pid=2, OS id=6024
Tue Nov 13 10:33:35 2012
ALTER DATABASE MOUNT
Tue Nov 13 10:33:39 2012
Setting recovery target incarnation to 1
Tue Nov 13 10:33:40 2012
Successful mount of redo thread 1, with mount id 2188708415
Tue Nov 13 10:33:40 2012
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Tue Nov 13 10:33:41 2012
ALTER DATABASE OPEN
ORA-1589 signalled during: ALTER DATABASE OPEN...
这台是SAP服务器,以前是用来测试的,因为一些难以说清楚的原因,最近临时转为正式环境。SAP是外包给第三方公司的,但第三方公司主要去做SAP应有方面的维护了,basis方面管的较少(且在数据库方面他们了解的也不多)。昨天让他们来重启服务器,由于数据量较大(大约200多G)且服务器性能不好,备份时间较长,他们没有完成备份就重启操作系统了,之前也没有关闭数据库,结果启动的时候就出问题了,然后他们也不知道怎么解决数据库上面的问题。
现在由于在做文件备份(由于服务器也存在问题,200G要拷大约6小时),保护现场,其他的动作也没有去做。现在只是在考虑等一下要怎么去做...
|
|