课程第18次（2018-07-17星期二）

botang

在做11a实验之前：
1. 检查磁带机。2.准备catalog。3.连接catalog做一个

1. RMAN> backup tag '100T_WHOLE_FULL'  database plus archivelog delete all input;
   

复制代码

1. [root@station90 桌面]# su - oracle
   
2. [oracle@station90 ~]$ sqlplus /nolog
   
3. 
   
4. SQL*Plus: Release 11.2.0.3.0 Production on Tue Jul 17 20:14:56 2018
   
5. 
   
6. Copyright (c) 1982, 2011, Oracle.  All rights reserved.
   
7. 
   
8. SQL> conn / as sysdba
   
9. Connected to an idle instance.
   
10. SQL> startup
    
11. ORACLE instance started.
    
12. 
    
13. Total System Global Area 6664212480 bytes
    
14. Fixed Size                    2240944 bytes
    
15. Variable Size                 3640659536 bytes
    
16. Database Buffers         3003121664 bytes
    
17. Redo Buffers                   18190336 bytes
    
18. ORA-00205: error in identifying control file, check alert log for more info
    
19. 
    
20. 
    
21. SQL> exit
    
22. Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    
23. With the Partitioning, OLAP, Data Mining and Real Application Testing options
    
24. [oracle@station90 ~]$ rman target /
    
25. 
    
26. Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jul 17 20:15:35 2018
    
27. 
    
28. Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    
29. 
    
30. connected to target database: ORCL (not mounted)
    
31. 
    
32. RMAN> list failure;
    
33. 
    
34. using target database control file instead of recovery catalog
    
35. List of Database Failures
    
36. =========================
    
37. 
    
38. Failure ID Priority Status    Time Detected Summary
    
39. ---------- -------- --------- ------------- -------
    
40. 645        CRITICAL OPEN      17-JUL-18     Control file +FRA/orcl/controlfile/current.256.816169633 is missing
    
41. 642        CRITICAL OPEN      17-JUL-18     Control file +DATA/orcl/controlfile/current.260.816169631 is missing
    
42. 
    
43. RMAN> advise failure;
    
44. 
    
45. List of Database Failures
    
46. =========================
    
47. 
    
48. Failure ID Priority Status    Time Detected Summary
    
49. ---------- -------- --------- ------------- -------
    
50. 645        CRITICAL OPEN      17-JUL-18     Control file +FRA/orcl/controlfile/current.256.816169633 is missing
    
51. 642        CRITICAL OPEN      17-JUL-18     Control file +DATA/orcl/controlfile/current.260.816169631 is missing
    
52. 
    
53. analyzing automatic repair options; this may take some time
    
54. allocated channel: ORA_DISK_1
    
55. channel ORA_DISK_1: SID=131 device type=DISK
    
56. analyzing automatic repair options complete
    
57. 
    
58. Mandatory Manual Actions
    
59. ========================
    
60. 1. If file +FRA/orcl/controlfile/current.256.816169633 was unintentionally renamed or moved, restore it
    
61. 2. If file +DATA/orcl/controlfile/current.260.816169631 was unintentionally renamed or moved, restore it
    
62. 3. If this is a primary database and you have a CREATE CONTROLFILE script, use it to create a new control file
    
63. 4. Contact Oracle Support Services if the preceding recommendations cannot be used, or if they do not fix the failures selected for repair
    
64. 
    
65. Optional Manual Actions
    
66. =======================
    
67. 1. If this is a primary database and a standby database is available, then perform a Data Guard failover initiated from the standby
    
68. 
    
69. Automated Repair Options
    
70. ========================
    
71. no automatic repair options available
    
72. 
    
73. RMAN> exit
    
74. 
    
75. 
    
76. Recovery Manager complete.
    
77. [oracle@station90 ~]$ rman target /  catalog u90/oracle_4U@rcat
    
78. 
    
79. Recovery Manager: Release 11.2.0.3.0 - Production on Tue Jul 17 20:16:23 2018
    
80. 
    
81. Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    
82. 
    
83. connected to target database: ORCL (not mounted)
    
84. RMAN-04007: WARNING from recovery catalog database: ORA-28002: the password will expire within 7 days
    
85. 
    
86. connected to recovery catalog database
    
87. 
    
88. RMAN> list backup of controlfile;
    
89. 
    
90. 
    
91. List of Backup Sets
    
92. ===================
    
93. 
    
94. 
    
95. BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    
96. ------- ---- -- ---------- ----------- ------------ ---------------
    
97. 248     Full    9.50M      SBT_TAPE    00:00:16     22-MAY-17      
    
98.         BP Key: 259   Status: AVAILABLE  Compressed: NO  Tag: TAG20170522T204208
    
99.         Handle: c-1343950367-20170522-00   Media: station90-000001
    
100.   Control File Included: Ckp SCN: 2026879      Ckp time: 22-MAY-17
     
101. 
     
102. BS Key  Type LV Size       Device Type Elapsed Time Completion Time
     
103. ------- ---- -- ---------- ----------- ------------ ---------------
     
104. 254     Full    9.50M      SBT_TAPE    00:00:16     17-JUL-18      
     
105.         BP Key: 265   Status: AVAILABLE  Compressed: NO  Tag: TAG20180717T200543
     
106.         Handle: c-1343950367-20180717-00   Media: station90-000001
     
107.   Control File Included: Ckp SCN: 3896211      Ckp time: 17-JUL-18
     
108. 
     
109. BS Key  Type LV Size       Device Type Elapsed Time Completion Time
     
110. ------- ---- -- ---------- ----------- ------------ ---------------
     
111. 352     Full    9.50M      SBT_TAPE    00:00:16     17-JUL-18      
     
112.         BP Key: 356   Status: AVAILABLE  Compressed: NO  Tag: LABS-11A-CONTROLFILE
     
113.         Handle: 1ut88jno_1_1   Media: station90-000001
     
114.   Control File Included: Ckp SCN: 3896535      Ckp time: 17-JUL-18
     
115. 
     
116. BS Key  Type LV Size       Device Type Elapsed Time Completion Time
     
117. ------- ---- -- ---------- ----------- ------------ ---------------
     
118. 353     Full    9.50M      SBT_TAPE    00:00:16     17-JUL-18      
     
119.         BP Key: 357   Status: AVAILABLE  Compressed: NO  Tag: TAG20180717T201202
     
120.         Handle: c-1343950367-20180717-01   Media: station90-000001
     
121.   Control File Included: Ckp SCN: 3896555      Ckp time: 17-JUL-18
     
122. 
     
123. RMAN> restore controlfile;
     
124. 
     
125. Starting restore at 17-JUL-18
     
126. allocated channel: ORA_DISK_1
     
127. channel ORA_DISK_1: SID=131 device type=DISK
     
128. allocated channel: ORA_DISK_2
     
129. channel ORA_DISK_2: SID=192 device type=DISK
     
130. allocated channel: ORA_DISK_3
     
131. channel ORA_DISK_3: SID=8 device type=DISK
     
132. allocated channel: ORA_DISK_4
     
133. channel ORA_DISK_4: SID=69 device type=DISK
     
134. allocated channel: ORA_DISK_5
     
135. channel ORA_DISK_5: SID=132 device type=DISK
     
136. allocated channel: ORA_DISK_6
     
137. channel ORA_DISK_6: SID=193 device type=DISK
     
138. allocated channel: ORA_DISK_7
     
139. channel ORA_DISK_7: SID=9 device type=DISK
     
140. allocated channel: ORA_DISK_8
     
141. channel ORA_DISK_8: SID=70 device type=DISK
     
142. allocated channel: ORA_SBT_TAPE_1
     
143. channel ORA_SBT_TAPE_1: SID=133 device type=SBT_TAPE
     
144. channel ORA_SBT_TAPE_1: Oracle Secure Backup
     
145. allocated channel: ORA_SBT_TAPE_2
     
146. channel ORA_SBT_TAPE_2: SID=10 device type=SBT_TAPE
     
147. channel ORA_SBT_TAPE_2: Oracle Secure Backup
     
148. 
     
149. channel ORA_SBT_TAPE_1: starting datafile backup set restore
     
150. channel ORA_SBT_TAPE_1: restoring control file
     
151. channel ORA_SBT_TAPE_1: reading from backup piece c-1343950367-20180717-01
     
152. channel ORA_SBT_TAPE_1: piece handle=c-1343950367-20180717-01 tag=TAG20180717T201202
     
153. channel ORA_SBT_TAPE_1: restored backup piece 1
     
154. channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:25
     
155. output file name=+DATA/orcl/controlfile/current.263.981749841
     
156. output file name=+FRA/orcl/controlfile/current.259.981749847
     
157. Finished restore at 17-JUL-18
     
158. 
     
159. RMAN> alter database mount;
     
160. 
     
161. database mounted
     
162. released channel: ORA_DISK_1
     
163. released channel: ORA_DISK_2
     
164. released channel: ORA_DISK_3
     
165. released channel: ORA_DISK_4
     
166. released channel: ORA_DISK_5
     
167. released channel: ORA_DISK_6
     
168. released channel: ORA_DISK_7
     
169. released channel: ORA_DISK_8
     
170. released channel: ORA_SBT_TAPE_1
     
171. released channel: ORA_SBT_TAPE_2
     
172. 
     
173. RMAN> recover database;
     
174. 
     
175. Starting recover at 17-JUL-18
     
176. Starting implicit crosscheck backup at 17-JUL-18
     
177. allocated channel: ORA_DISK_1
     
178. channel ORA_DISK_1: SID=133 device type=DISK
     
179. allocated channel: ORA_DISK_2
     
180. channel ORA_DISK_2: SID=194 device type=DISK
     
181. allocated channel: ORA_DISK_3
     
182. channel ORA_DISK_3: SID=10 device type=DISK
     
183. allocated channel: ORA_DISK_4
     
184. channel ORA_DISK_4: SID=71 device type=DISK
     
185. allocated channel: ORA_DISK_5
     
186. channel ORA_DISK_5: SID=132 device type=DISK
     
187. allocated channel: ORA_DISK_6
     
188. channel ORA_DISK_6: SID=193 device type=DISK
     
189. allocated channel: ORA_DISK_7
     
190. channel ORA_DISK_7: SID=9 device type=DISK
     
191. allocated channel: ORA_DISK_8
     
192. channel ORA_DISK_8: SID=70 device type=DISK
     
193. Finished implicit crosscheck backup at 17-JUL-18
     
194. 
     
195. Starting implicit crosscheck copy at 17-JUL-18
     
196. using channel ORA_DISK_1
     
197. using channel ORA_DISK_2
     
198. using channel ORA_DISK_3
     
199. using channel ORA_DISK_4
     
200. using channel ORA_DISK_5
     
201. using channel ORA_DISK_6
     
202. using channel ORA_DISK_7
     
203. using channel ORA_DISK_8
     
204. Finished implicit crosscheck copy at 17-JUL-18
     
205. 
     
206. searching for all files in the recovery area
     
207. cataloging files...
     
208. no files cataloged
     
209. 
     
210. using channel ORA_DISK_1
     
211. using channel ORA_DISK_2
     
212. using channel ORA_DISK_3
     
213. using channel ORA_DISK_4
     
214. using channel ORA_DISK_5
     
215. using channel ORA_DISK_6
     
216. using channel ORA_DISK_7
     
217. using channel ORA_DISK_8
     
218. allocated channel: ORA_SBT_TAPE_1
     
219. channel ORA_SBT_TAPE_1: SID=131 device type=SBT_TAPE
     
220. channel ORA_SBT_TAPE_1: Oracle Secure Backup
     
221. allocated channel: ORA_SBT_TAPE_2
     
222. channel ORA_SBT_TAPE_2: SID=8 device type=SBT_TAPE
     
223. channel ORA_SBT_TAPE_2: Oracle Secure Backup
     
224. 
     
225. starting media recovery
     
226. 
     
227. archived log for thread 1 with sequence 164 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_164.287.981749483
     
228. archived log for thread 1 with sequence 165 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_165.288.981749485
     
229. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_164.287.981749483 thread=1 sequence=164
     
230. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_165.288.981749485 thread=1 sequence=165
     
231. unable to find archived log
     
232. archived log thread=1 sequence=166
     
233. RMAN-00571: ===========================================================
     
234. RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
     
235. RMAN-00571: ===========================================================
     
236. RMAN-03002: failure of recover command at 07/17/2018 20:18:20
     
237. RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 166 and starting SCN of 3896514
     
238. 
     
239. RMAN> list failure ;
     
240. 
     
241. List of Database Failures
     
242. =========================
     
243. 
     
244. Failure ID Priority Status    Time Detected Summary
     
245. ---------- -------- --------- ------------- -------
     
246. 676        CRITICAL OPEN      17-JUL-18     System datafile 1: '+DATA/orcl/datafile/system.256.816169553' needs media recovery
     
247. 673        CRITICAL OPEN      17-JUL-18     Control file needs media recovery
     
248. 8          HIGH     OPEN      17-JUL-18     One or more non-system datafiles need media recovery
     
249. 
     
250. RMAN> advise failure;
     
251. 
     
252. List of Database Failures
     
253. =========================
     
254. 
     
255. Failure ID Priority Status    Time Detected Summary
     
256. ---------- -------- --------- ------------- -------
     
257. 676        CRITICAL OPEN      17-JUL-18     System datafile 1: '+DATA/orcl/datafile/system.256.816169553' needs media recovery
     
258. 673        CRITICAL OPEN      17-JUL-18     Control file needs media recovery
     
259. 8          HIGH     OPEN      17-JUL-18     One or more non-system datafiles need media recovery
     
260. 
     
261. analyzing automatic repair options; this may take some time
     
262. using channel ORA_DISK_1
     
263. using channel ORA_DISK_2
     
264. using channel ORA_DISK_3
     
265. using channel ORA_DISK_4
     
266. using channel ORA_DISK_5
     
267. using channel ORA_DISK_6
     
268. using channel ORA_DISK_7
     
269. using channel ORA_DISK_8
     
270. using channel ORA_SBT_TAPE_1
     
271. using channel ORA_SBT_TAPE_2
     
272. analyzing automatic repair options complete
     
273. 
     
274. Mandatory Manual Actions
     
275. ========================
     
276. no manual actions available
     
277. 
     
278. Optional Manual Actions
     
279. =======================
     
280. 1. If you have the correct version of the control file, then shutdown the database and replace the old control file
     
281. 2. If you restored the wrong version of data file +DATA/orcl/datafile/system.256.816169553, then replace it with the correct one
     
282. 3. If you restored the wrong version of data file +DATA/orcl/datafile/sysaux.257.816169553, then replace it with the correct one
     
283. 4. If you restored the wrong version of data file +DATA/orcl/datafile/undotbs1.258.816169553, then replace it with the correct one
     
284. 5. If you restored the wrong version of data file +DATA/orcl/datafile/users.259.816169553, then replace it with the correct one
     
285. 6. If you restored the wrong version of data file +DATA/orcl/datafile/example.265.816169651, then replace it with the correct one
     
286. 
     
287. Automated Repair Options
     
288. ========================
     
289. Option Repair Description
     
290. ------ ------------------
     
291. 1      Perform incomplete database recovery  
     
292.   Strategy: The repair includes point-in-time recovery with some data loss
     
293.   Repair script: /u01/app/oracle/diag/rdbms/orcl/orcl/hm/reco_2346318570.hm
     
294. 
     
295. RMAN> repair failure preview;
     
296. 
     
297. Strategy: The repair includes point-in-time recovery with some data loss
     
298. Repair script: /u01/app/oracle/diag/rdbms/orcl/orcl/hm/reco_2346318570.hm
     
299. 
     
300. contents of repair script:
     
301.    # database point-in-time recovery until a missing log
     
302.    restore database until scn 3896514;
     
303.    recover database until scn 3896514;
     
304.    alter database open resetlogs;
     
305. 
     
306. RMAN> run {
     
307. 2> set until sequence  166  thread 1;
     
308. 3> restore database;
     
309. 4> recover database;
     
310. 5> }
     
311. 
     
312. executing command: SET until clause
     
313. 
     
314. Starting restore at 17-JUL-18
     
315. using channel ORA_DISK_1
     
316. using channel ORA_DISK_2
     
317. using channel ORA_DISK_3
     
318. using channel ORA_DISK_4
     
319. using channel ORA_DISK_5
     
320. using channel ORA_DISK_6
     
321. using channel ORA_DISK_7
     
322. using channel ORA_DISK_8
     
323. using channel ORA_SBT_TAPE_1
     
324. using channel ORA_SBT_TAPE_2
     
325. 
     
326. channel ORA_SBT_TAPE_1: starting datafile backup set restore
     
327. channel ORA_SBT_TAPE_1: specifying datafile(s) to restore from backup set
     
328. channel ORA_SBT_TAPE_1: restoring datafile 00001 to +DATA/orcl/datafile/system.256.816169553
     
329. channel ORA_SBT_TAPE_1: restoring datafile 00005 to +DATA/orcl/datafile/example.265.816169651
     
330. channel ORA_SBT_TAPE_1: reading from backup piece 1rt88jb3_1_1
     
331. channel ORA_SBT_TAPE_2: starting datafile backup set restore
     
332. channel ORA_SBT_TAPE_2: specifying datafile(s) to restore from backup set
     
333. channel ORA_SBT_TAPE_2: restoring datafile 00002 to +DATA/orcl/datafile/sysaux.257.816169553
     
334. channel ORA_SBT_TAPE_2: restoring datafile 00003 to +DATA/orcl/datafile/undotbs1.258.816169553
     
335. channel ORA_SBT_TAPE_2: restoring datafile 00004 to +DATA/orcl/datafile/users.259.816169553
     
336. channel ORA_SBT_TAPE_2: reading from backup piece 1qt88jb3_1_1
     
337. channel ORA_SBT_TAPE_1: piece handle=1rt88jb3_1_1 tag=100T_WHOLE_FULL
     
338. channel ORA_SBT_TAPE_1: restored backup piece 1
     
339. channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:55
     
340. channel ORA_SBT_TAPE_2: piece handle=1qt88jb3_1_1 tag=100T_WHOLE_FULL
     
341. channel ORA_SBT_TAPE_2: restored backup piece 1
     
342. channel ORA_SBT_TAPE_2: restore complete, elapsed time: 00:01:05
     
343. Finished restore at 17-JUL-18
     
344. 
     
345. Starting recover at 17-JUL-18
     
346. using channel ORA_DISK_1
     
347. using channel ORA_DISK_2
     
348. using channel ORA_DISK_3
     
349. using channel ORA_DISK_4
     
350. using channel ORA_DISK_5
     
351. using channel ORA_DISK_6
     
352. using channel ORA_DISK_7
     
353. using channel ORA_DISK_8
     
354. using channel ORA_SBT_TAPE_1
     
355. using channel ORA_SBT_TAPE_2
     
356. 
     
357. starting media recovery
     
358. 
     
359. archived log for thread 1 with sequence 160 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_160.283.981749477
     
360. archived log for thread 1 with sequence 161 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_161.284.981749479
     
361. archived log for thread 1 with sequence 162 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_162.285.981749481
     
362. archived log for thread 1 with sequence 163 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_163.286.981749481
     
363. archived log for thread 1 with sequence 164 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_164.287.981749483
     
364. archived log for thread 1 with sequence 165 is already on disk as file +FRA/orcl/archivelog/2018_07_17/thread_1_seq_165.288.981749485
     
365. channel ORA_SBT_TAPE_1: starting archived log restore to default destination
     
366. channel ORA_SBT_TAPE_1: restoring archived log
     
367. archived log thread=1 sequence=159
     
368. channel ORA_SBT_TAPE_1: reading from backup piece 1st88jbu_1_1
     
369. channel ORA_SBT_TAPE_1: piece handle=1st88jbu_1_1 tag=100T_WHOLE_FULL
     
370. channel ORA_SBT_TAPE_1: restored backup piece 1
     
371. channel ORA_SBT_TAPE_1: restore complete, elapsed time: 00:00:25
     
372. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_159.258.981750195 thread=1 sequence=159
     
373. channel default: deleting archived log(s)
     
374. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_159.258.981750195 RECID=158 STAMP=981750194
     
375. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_160.283.981749477 thread=1 sequence=160
     
376. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_161.284.981749479 thread=1 sequence=161
     
377. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_162.285.981749481 thread=1 sequence=162
     
378. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_163.286.981749481 thread=1 sequence=163
     
379. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_164.287.981749483 thread=1 sequence=164
     
380. archived log file name=+FRA/orcl/archivelog/2018_07_17/thread_1_seq_165.288.981749485 thread=1 sequence=165
     
381. media recovery complete, elapsed time: 00:00:02
     
382. Finished recover at 17-JUL-18
     
383. 
     
384. RMAN> alter database open resetlogs;
     
385. 
     
386. database opened
     
387. new incarnation of database registered in recovery catalog
     
388. starting full resync of recovery catalog
     
389. full resync complete
     
390. 
     
391. RMAN>
     

复制代码