q. 1 : what system privilege is required to create a rollback segment ?
; g3 `' T8 o1 f$ I0 P1 ] 5 @# N2 C: N9 F7 _5 {* e
1. create database
- W, M. B6 B! V2 n 2. create rollback segment % b D- D6 I9 l
3. alter database
: H9 v" z* z; _ 4. create segment " v$ R# n# g3 G0 n6 j. v
5 e( G y- L: q7 v Z 2 ! b* z3 z& N# e) @' K+ d% o8 R2 x6 j$ \
: E# X. X% S8 s7 x0 f z
q. 2 : oracle recommends this number of minimum extents in a rollback segment ; W& [/ O' M& S2 {' c( T
Q4 M% a' L9 {! i) E( L) ?
1. 0
- m0 I9 b6 R8 b" y) s 2. 1 8 h4 ~& z2 U6 j" |1 ]# K8 F D
3. 2
/ t [7 D/ o7 j7 z) v0 f) L& \. B 4. 3 ! y9 L+ X7 k$ m' G8 X+ z3 v
% j$ g* P6 E* v' B r4 ~0 ]! Z
3
( K: Z2 F4 Z* k. e( a* d, b7 `
8 @/ ^5 D; X# G- o& Z: E- K# p q. 3 : oracle recommends that the following segment size when creating a rollback segment . o3 q, X- i1 M/ s7 C- p2 b8 P
! ]' u& V0 k0 B6 c/ I
1. initial > next * r) C3 w6 K9 f" y$ J1 _# P0 P
2. initial = next 9 x6 ?! [8 ?' H" ~. ~3 [# l
3. initial < next 5 k+ P' A5 Z/ S
4. none of the above
$ o" y- Z# m6 `; g0 _7 } # A# x6 e8 i6 N+ O
2
( h3 n K4 d+ A+ U, c + k1 w; c5 `2 _7 k& G
q. 4 : the optimal parameter for a rollback segment should be set - V( N# t- G; N0 h" ~6 e
% @6 F9 i- g9 }; n1 I 1. large for long-frequently running transactions, small for short transactions. : V: m5 G. g ]. t7 a
2. small for long-frequently running transactions, large for small transactions.
5 W# C" B+ h* G% M 3. small for all transactions
& ?: ^8 H8 b/ A4 X+ y! V! x 4. large for all transactions
# w X" G7 v) Z. V- T, y& h9 G! N
" R/ w( {# O+ r- _2 {. C 1 & K4 ~; O% d9 r5 o1 z" Y; x
" o: \5 ]( p* B5 t* a+ A4 M" [# S( V q. 5 : in case of system failure, this type of segment is used to undo the changes
+ v: Q5 w+ a& f2 U F5 F' d - A- E- e& u9 J' m n
1. data segment
! _* B0 X3 D6 e4 ~ l( ] 2. temp segment , c# { q& h% l
3. redo segment a) U* }4 `% ^
4. rollback segment + o. Y- z8 P8 w
0 l# B- L/ M6 N- C8 r, N0 ~, c+ |1 B# c( ?. X
4 : rollback segments are used to rollback information that has already been applied to database. during recovery, the database is rolled forward and then backwards to a consistent state. ( U4 i- J1 Q9 M0 F* a! y0 I0 z
/ z' x5 v9 [! T9 b& Y8 I& ~+ Y q. 6 : this is a valid storage parameter when creating a rollback segment
; o* i; X. A9 Y- E 5 A+ z7 P9 b2 G
1. freelists
+ `: x8 Z. @' X6 O2 U- n/ n 2. optimal 7 C9 C9 L- b- W9 J- F. R* B
3. partition
. n3 [, g J8 [* [0 L- E6 m$ L 4. none of the above
; U) M) k/ @6 O' y/ ~
: C! F2 ?" j- l/ _% I2 y 2 # z) z5 z- `# r4 Q$ c9 D' q" x' D% U
+ U2 {/ p; j3 {/ ` q. 7 : madhu created a couple of private rollback segments. what should he do now to make them online automatically during startup + z) d8 {" u. S: E
+ r6 _. ~6 a3 U: J* u
1. grant online during startup to the segments
5 k6 r) [' H8 Q 2. add rollback_segments=(rbs1,rbs2) in parameter file 2 N) e8 G" O3 z' Y m/ R
3. drop segments and recreate them as protected 0 V/ h. B' z: \ ^
4. none of the above ) P8 b+ \# f5 p& N8 c
4 _4 f" u$ [" A4 C 2 ' b" a( ? x6 I! Q) Y# J
$ q j, A0 d( ?* @* W" n9 p. L; ] q. 8 : which is true regarding rollback segments
7 E4 j; Y9 q, ]1 @5 ^0 C' c, z 8 R* P( W( V! m8 q( x; Y
1. system rollback segment cannot be put in an offline mode ( v1 ~6 n0 U# w' i; K2 ~
2. tablespaces containing rollback segments with active transactions can be put in offline mode , {/ Y, S0 P& \- T: }5 p1 }* d q: y
3. all of the above ' _1 w0 @# ^5 |4 j, N" m5 }
4. none of the above |