01.03.2018 05:20
Nik_75
 
Добрый день. Подскажите в чем проблема и куда копать по этой ошибке?



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
sga_max_size = 922746880
__shared_pool_size = 293601280
shared_pool_size = 293601280
__large_pool_size = 0
__java_pool_size = 25165824
__streams_pool_size = 0
shared_pool_reserved_size= 20971520
control_files = D:\ORACLE\ORADATA\HOROSHY6\HOROSHY6\CONTROL01.CTL, D:\ORACLE\ORADATA\HOROSHY6\HOROSHY6\CONTROL02.CTL, D:\ORACLE\ORADATA\HOROSHY6\HOROSHY6\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 50331648
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
_db_file_noncontig_mblock_read_count= 0
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 48507125760
undo_management = AUTO
undo_tablespace = UNDOTBS1
O7_DICTIONARY_ACCESSIBILITY= TRUE
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=HOROSHY6XDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\CDUMP
db_name = HOROSHY6
open_cursors = 300
pga_aggregate_target = 33554432
PMON started with pid=2, OS id=2392
PSP0 started with pid=3, OS id=2396
MMAN started with pid=4, OS id=2400
DBW0 started with pid=5, OS id=2436
LGWR started with pid=6, OS id=2440
CKPT started with pid=7, OS id=2444
SMON started with pid=8, OS id=2448
RECO started with pid=9, OS id=2452
CJQ0 started with pid=10, OS id=2456
MMON started with pid=11, OS id=2460
Thu Mar 01 11:02:07 2018
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=2464
Thu Mar 01 11:02:07 2018
starting up 1 shared server(s) ...
Thu Mar 01 11:02:08 2018
alter database mount exclusive
Thu Mar 01 11:02:12 2018
Setting recovery target incarnation to 2
Thu Mar 01 11:02:12 2018
Successful mount of redo thread 1, with mount id 513700400
Thu Mar 01 11:02:12 2018
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Thu Mar 01 11:02:12 2018
alter database open
ORA-1113 signalled during: alter database open...
Thu Mar 01 11:07:58 2018
Shutting down instance: further logons disabled
Thu Mar 01 11:07:58 2018
Stopping background process CJQ0
Thu Mar 01 11:07:58 2018
Stopping background process MMNL
Thu Mar 01 11:07:59 2018
Stopping background process MMON
Thu Mar 01 11:08:00 2018
Shutting down instance (immediate)
License high water mark = 2
Thu Mar 01 11:08:00 2018
Stopping Job queue slave processes, flags = 7
Thu Mar 01 11:08:00 2018
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Thu Mar 01 11:08:02 2018
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Thu Mar 01 11:08:02 2018
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Thu Mar 01 11:08:15 2018
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
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.4.0.
System parameters with non-default values:
processes = 150
sga_max_size = 922746880
__shared_pool_size = 293601280
shared_pool_size = 293601280
__large_pool_size = 0
__java_pool_size = 25165824
__streams_pool_size = 0
shared_pool_reserved_size= 20971520
control_files = D:\ORACLE\ORADATA\HOROSHY6\HOROSHY6\CONTROL01.CTL, D:\ORACLE\ORADATA\HOROSHY6\HOROSHY6\CONTROL02.CTL, D:\ORACLE\ORADATA\HOROSHY6\HOROSHY6\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 50331648
compatible = 10.2.0.3.0
db_file_multiblock_read_count= 16
_db_file_noncontig_mblock_read_count= 0
db_recovery_file_dest = D:\oracle\product\10.2.0\flash_recovery_area
db_recovery_file_dest_size= 48507125760
undo_management = AUTO
undo_tablespace = UNDOTBS1
O7_DICTIONARY_ACCESSIBILITY= TRUE
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=HOROSHY6XDB)
job_queue_processes = 10
audit_file_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\ADUMP
background_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.2.0\ADMIN\HOROSHY6\CDUMP
db_name = HOROSHY6
open_cursors = 300
pga_aggregate_target = 33554432
PMON started with pid=2, OS id=3132
PSP0 started with pid=3, OS id=2668
MMAN started with pid=4, OS id=3824
DBW0 started with pid=5, OS id=3068
LGWR started with pid=6, OS id=1840
CKPT started with pid=7, OS id=1848
SMON started with pid=8, OS id=12
RECO started with pid=9, OS id=1984
CJQ0 started with pid=10, OS id=3136
MMON started with pid=11, OS id=3656
Thu Mar 01 11:08:15 2018
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
MMNL started with pid=12, OS id=2544
Thu Mar 01 11:08:15 2018
starting up 1 shared server(s) ...
Thu Mar 01 11:08:16 2018
ALTER DATABASE MOUNT
Thu Mar 01 11:08:20 2018
Setting recovery target incarnation to 2
Thu Mar 01 11:08:20 2018
Successful mount of redo thread 1, with mount id 513686176
Thu Mar 01 11:08:20 2018
Database mounted in Exclusive Mode
Completed: ALTER DATABASE MOUNT
Thu Mar 01 11:08:21 2018
ALTER DATABASE OPEN
ORA-1113 signalled during: ALTER DATABASE OPEN...
01.03.2018 07:12
OlegON
 
Приведи файл инициализации в порядок, перегрузи базу и сделай recover database. Этого куска лога недостаточно, чтобы сказать, что именно мешает восстановлению базы, но суть именно в этом. База при открытии не может сделать recover. У меня такое было, когда файловая система повредилась из-за оперативки, но при этом мусора в логе было побольше, особенно выше куска, где она стартовала.
01.03.2018 10:01
Nik_75
 
При попытке сделать recover database ошибка повторялась. Проблему решил пересозданием базы и заливкой дампа.
01.03.2018 10:39
OlegON
 
Если бекапишь дампами, то рано или поздно тебя ожидает большая неприятность. Рекомендую оптимизатор, он бы тебе одной командой базу на место вернул. Да и, скорее всего, уже бы починил все без вмешательства.
Часовой пояс GMT +3, время: 23:03.

Форум на базе vBulletin®
Copyright © Jelsoft Enterprises Ltd.
В случае заимствования информации гипертекстовая индексируемая ссылка на Форум обязательна.