На тестовой базе доигрался до того, что не стартует ни listener ни instance (Oracle 11.2)
вот алерт лог
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28.
29.
30.
31.
32.
33.
34.
35.
36.
37.
38.
39.
40.
41.
42.
43.
44.
45.
46.
47.
48.
49.
50.
51.
52.
53.
54.
55.
56.
57.
58.
59.
60.
61.
62.
63.
64.
65.
66.
67.
68.
69.
70.
71.
72.
73.
74.
75.
76.
77.
78.
79.
80.
81.
82.
83.
84.
85.
86.
87.
88.
89.
90.
91.
92.
93.
94.
95.
96.
97.
98.
99.
100.
101.
102.
103.
104.
105.
106.
107.
108.
109.
110.
111.
112.
113.
114.
115.
116.
117.
118.
119.
120.
121.
122.
123.
124.
125.
126.
127.
128.
129.
130.
131.
132.
133.
134.
135.
136.
137.
138.
139.
Thread 1 opened at log sequence 10
Current log# 5 seq# 10 mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Current log# 5 seq# 10 mem# 1: E:\REDO_LOG\REDO05_1.LOG
Successful open of redo thread 1
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Mon Dec 17 11:52:45 2018
SMON: enabling cache recovery
Mon Dec 17 11:52:45 2018
ARC3 started with pid=57, OS id=3572
Archived Log entry 119724 added for thread 1 sequence 9 ID 0x1e5c776d dest 1:
Successfully onlined Undo Tablespace 2.
Verifying file header compatibility for 11g tablespace encryption..
Verifying 11g file header compatibility for tablespace encryption completed
SMON: enabling tx recovery
Database Characterset is CL8MSWIN1251
No Resource Manager plan active
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_smon_2060.trc (incident=7401214):
ORA-00600: internal error code, arguments: [4136], [8.32.524718], [0], [0], [], [], [], [], [], [], [], []
Incident details in: d:\app\diag\rdbms\basembd\basembd\incident\incdir_7401214\basembd_smon_2060_i7401214.trc
replication_dependency_tracking turned off (no async multimaster replication found)
ARC3: Archival started
ARC0: STARTING ARCH PROCESSES COMPLETE
Starting background process QMNC
Mon Dec 17 11:52:49 2018
QMNC started with pid=58, OS id=1976
Completed: alter database open
Mon Dec 17 11:52:51 2018
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_mmon_4844.trc (incident=7401230):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: d:\app\diag\rdbms\basembd\basembd\incident\incdir_7401230\basembd_mmon_4844_i7401230.trc
Mon Dec 17 11:52:57 2018
ORACLE Instance basembd (pid = 16) - Error 600 encountered while recovering transaction (8, 32).
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_smon_2060.trc:
ORA-00600: internal error code, arguments: [4136], [8.32.524718], [0], [0], [], [], [], [], [], [], [], []
Mon Dec 17 11:52:58 2018
Trace dumping is performing id=[cdmp_20181217115258]
Starting background process SMCO
Mon Dec 17 11:52:58 2018
SMCO started with pid=22, OS id=2512
Mon Dec 17 11:53:04 2018
Doing block recovery for file 3 block 7791
Resuming block recovery (PMON) for file 3 block 7791
Block recovery from logseq 10, block 71 to scn 1018093368
Recovery of Online Redo Log: Thread 1 Group 5 Seq 10 Reading mem 0
Mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Mem# 1: E:\REDO_LOG\REDO05_1.LOG
Block recovery stopped at EOT rba 10.78.16
Block recovery completed at rba 10.78.16, scn 0.1018093367
Doing block recovery for file 3 block 144
Resuming block recovery (PMON) for file 3 block 144
Block recovery from logseq 10, block 71 to scn 1018093351
Recovery of Online Redo Log: Thread 1 Group 5 Seq 10 Reading mem 0
Mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Mem# 1: E:\REDO_LOG\REDO05_1.LOG
Block recovery completed at rba 10.71.16, scn 0.1018093352
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_smon_2060.trc (incident=7401215):
ORA-00600: internal error code, arguments: [4194], [8.32.524718], [0], [], [], [], [], [], [], [], [], []
Incident details in: d:\app\diag\rdbms\basembd\basembd\incident\incdir_7401215\basembd_smon_2060_i7401215.trc
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_mmon_4844.trc (incident=7401231):
ORA-00600: internal error code, arguments: [kewrose_1], [600], [ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], []
Incident details in: d:\app\diag\rdbms\basembd\basembd\incident\incdir_7401231\basembd_mmon_4844_i7401231.trc
Trace dumping is performing id=[cdmp_20181217115307]
Mon Dec 17 11:53:09 2018
db_recovery_file_dest_size of 409600 MB is 0.02% 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.
Mon Dec 17 11:53:13 2018
Trace dumping is performing id=[cdmp_20181217115313]
Mon Dec 17 11:53:17 2018
Doing block recovery for file 3 block 7791
Resuming block recovery (PMON) for file 3 block 7791
Block recovery from logseq 10, block 71 to scn 1018093368
Recovery of Online Redo Log: Thread 1 Group 5 Seq 10 Reading mem 0
Mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Mem# 1: E:\REDO_LOG\REDO05_1.LOG
Block recovery completed at rba 10.78.16, scn 0.1018093369
Doing block recovery for file 3 block 144
Resuming block recovery (PMON) for file 3 block 144
Block recovery from logseq 10, block 71 to scn 1018093369
Recovery of Online Redo Log: Thread 1 Group 5 Seq 10 Reading mem 0
Mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Mem# 1: E:\REDO_LOG\REDO05_1.LOG
Block recovery completed at rba 10.79.16, scn 0.1018093370
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_smon_2060.trc:
ORA-01595: error freeing extent (3) of rollback segment (2))
ORA-00600: internal error code, arguments: [4194], [8.32.524718], [
Mon Dec 17 11:53:18 2018
Starting background process CJQ0
Mon Dec 17 11:53:18 2018
CJQ0 started with pid=64, OS id=3124
Mon Dec 17 11:53:19 2018
Sweep [inc][7401214]: completed
Mon Dec 17 11:53:37 2018
Sweep [inc][7401231]: completed
Sweep [inc][7401230]: completed
Sweep [inc][7401215]: completed
Sweep [inc2][7401231]: completed
Sweep [inc2][7401230]: completed
Sweep [inc2][7401215]: completed
Sweep [inc2][7401214]: completed
Mon Dec 17 11:54:44 2018
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0x709CD1F8] [PC:0x9087D88, kgegpa()+38]
Dump file d:\app\diag\rdbms\basembd\basembd\trace\alert_basembd.log
Mon Dec 17 11:54:44 2018
ORACLE V11.2.0.1.0 - 64bit Production vsnsta=0
vsnsql=16 vsnxtr=3
Windows NT Version V6.2
CPU : 32 - type 8664, 16 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:47206M/64957M, Ph+PgF:56623M/74685M
Mon Dec 17 11:54:44 2018
Errors in file
ORA-07445: caught exception [ACCESS_VIOLATION] at [kgegpa()+38] [0x0000000009087D88]
Mon Dec 17 11:54:47 2018
Doing block recovery for file 3 block 7791
Resuming block recovery (PMON) for file 3 block 7791
Block recovery from logseq 10, block 71 to scn 1018093368
Recovery of Online Redo Log: Thread 1 Group 5 Seq 10 Reading mem 0
Mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Mem# 1: E:\REDO_LOG\REDO05_1.LOG
Block recovery completed at rba 10.78.16, scn 0.1018093369
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_pmon_4092.trc (incident=7401102):
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
Incident details in: d:\app\diag\rdbms\basembd\basembd\incident\incdir_7401102\basembd_pmon_4092_i7401102.trc
Mon Dec 17 11:54:52 2018
Doing block recovery for file 3 block 7791
Resuming block recovery (PMON) for file 3 block 7791
Block recovery from logseq 10, block 71 to scn 1018093368
Recovery of Online Redo Log: Thread 1 Group 5 Seq 10 Reading mem 0
Mem# 0: D:\APP\ORADATA\BASEMBD\REDO05.LOG
Mem# 1: E:\REDO_LOG\REDO05_1.LOG
Block recovery completed at rba 10.78.16, scn 0.1018093369
Errors in file d:\app\diag\rdbms\basembd\basembd\trace\basembd_pmon_4092.trc:
ORA-00600: internal error code, arguments: [4194], [], [], [], [], [], [], [], [], [], [], []
PMON (ospid: 4092): terminating the instance due to error 472
Mon Dec 17 11:55:06 2018
Instance terminated by PMON, pid = 4092
вот lsnr лог
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
Mon Dec 17 12:37:56 2018
файлом системных параметров является d:\app\product\11.2.0\dbhome_1\network\admin\listener.ora
сообщения протокола записаны в d:\app\diag\tnslsnr\ESDNEW\listener\alert\log.xml
информация протокола записана в d:\app\diag\tnslsnr\ESDNEW\listener\trace\ora_2692_1392.trc
текущим уровнем протокола является 0
Запущен с pid=2692
Прослушивается: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
Прослушивается: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ESDNEW.city.loc)(PORT=1521)))
Listener completed notification to CRS on start
TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
17-ДЕК-2018 12:37:58 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=__jdbc__)(USER=ESDNEW$))(SERVICE_NAME=basembd)) * (ADDRESS=(PROTOCOL=tcp)(HOST=192.168.0.0)(PORT=57155)) * establish * basembd * 12514
TNS-12514: TNS:прослушиватель в данный момент не имеет данных о службе, запрашиваемой в дескрипторе соединения
Вопрос - как бы мне инстанс в режиме nomount стартануть?
Есть control файлы, pfile , полный backup database
сервер- windows 2012
Можно конечно Oracle переставить- но может быть есть еще варианты?
PS Вообще говоря все развалилось после того, как я вручном режиме закреайтил undo tablespace и сделал его активным.
(еще там было ALTER SYSTEM SET "_allow_resetlogs_corruption"= TRUE SCOPE = SPFILE;)
После этого перевел undo_management в авто AUTO и перестартовал и убил предыдущий undo. Но это уже другая история.
На данный момент вопрос - как убитый инстанс оживить в nomount режиме? |
