1 : what system privilege is required to create a rollback segment ? 9 W& ~5 U9 \1 ]
+ F4 [: P2 `5 x8 o" p, q 1. create database
, [' ^) O. u! N$ H; X 2. create rollback segment
! i; D3 O4 z# a9 _8 |# ?5 t* k 3. alter database 3 }6 \" V( a) M! [4 t7 O
4. create segment - h6 T: ?* {, ]2 l9 S+ o
! I k# s9 i: S& ^' P
2
, N' P' X' `# e2 Y$ l+ B# e / w. F7 F& z0 z) J
q. 2 : oracle recommends this number of minimum extents in a rollback segment + {4 I+ u0 q( Y( Z; O3 k) s7 h& L
+ |7 ?3 K6 e( \- o/ o5 C) } 1. 0 + H$ W9 E: C5 r1 A( [0 Z
2. 1 x/ S# @4 V$ y3 I* x
3. 2
, m( _2 K. I! p6 \+ P, ^; V5 A% Y+ I 4. 3
' {: W( ^" Y+ l( e; R) F2 `3 ?9 C1 p8 w
' C- T! e. I( h! z9 G5 e- |: y 3
7 J* Q5 @& _: s# r2 a
9 S) I: X* Y9 `; D. g) B- u9 D8 x q. 3 : oracle recommends that the following segment size when creating a rollback segment 4 d: W8 v; }5 T! T) y& l$ Z( n
0 c5 H# r6 G8 r
1. initial > next
' W* O4 `/ ^7 m c& T: A6 }: v# i 2. initial = next
; }) n6 w; q& O" u# v$ X* O( [ 3. initial < next
; z- R6 _/ N( M4 t$ m1 Q 4. none of the above
" l( r* u, j$ g5 d3 g
( C6 K; h* |6 {% z6 Q3 e& R, w 2 ]9 @7 @1 W$ ?' z
! Z: w3 T9 E( X8 n
q. 4 : the optimal parameter for a rollback segment should be set
" y2 C2 w# M0 l ; T6 z% j* [3 b% z( O# _( O
1. large for long-frequently running transactions, small for short transactions.
, j5 {; u/ a) M2 G; O 2. small for long-frequently running transactions, large for small transactions. , a/ d3 ^3 } a. {. {/ M; T
3. small for all transactions
% }- T9 S- q* U$ X# B7 f; O$ A 4. large for all transactions
1 c$ Z6 @* n/ A) M" a) l 4 R! I' {2 V/ r9 u$ f7 P. [- t
1 - e2 ^$ l4 f" W! a
( B6 I5 B6 b2 Q C i/ R5 v* S q. 5 : in case of system failure, this type of segment is used to undo the changes + `, L: f. ~0 a7 j! T' a: D& X/ F
$ h& }- v- ?; `' C9 C) O: g
1. data segment 3 S; D3 X3 t8 A; I( p
2. temp segment
2 U" s, J9 Y" H+ Q. C 3. redo segment 8 X6 I, I; `- Y# B8 n* F9 P( @
4. rollback segment + q' E* ~4 L ^# b
6 B1 @+ \4 I# ]& s; ? 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. + i4 j4 _6 A9 i3 D" w" Y U
! [0 \8 D8 @, E5 S/ b q. 6 : this is a valid storage parameter when creating a rollback segment
# C) f7 Z/ k) R & A0 Z, n( w! e$ z& a
1. freelists
3 Q+ J) J4 z3 H, t# B 2. optimal }5 A. z3 H: @: Q ?9 p
3. partition # m4 |/ g; S" a" ^
4. none of the above
2 f1 Z7 _. j9 u( G5 C; b. G, y; D 0 n" J/ R# @5 y" r; V
2 , a3 a) i8 r/ d2 o/ K6 o6 F
2 I8 D) u% J0 ^1 h0 O3 o
q. 7 : madhu created a couple of private rollback segments. what should he do now to make them online automatically during startup 9 k* i4 k% V4 Z W) ~- f' U
* M, M' R% Z8 |0 D2 y3 `1 x
1. grant online during startup to the segments
: k5 m5 \( Y7 k! e# f, q& j$ n) h 2. add rollback_segments=(rbs1,rbs2) in parameter file " c/ \: [& \% x; Z
3. drop segments and recreate them as protected
- L7 A% r' @( s0 o0 p) ? 4. none of the above
" x9 z/ Q1 Q, |5 [ Z : [7 X% |. J) v( k: o% y, K( C
2
* O" s. i( Y- Q9 Q4 N2 D : ^ d7 f. v* W1 f6 `
q. 8 : which is true regarding rollback segments & i4 e+ H: c! g7 j
' V) g- D* j: }& w2 L: A/ q 1. system rollback segment cannot be put in an offline mode
. q' C1 z* y" d3 h b3 a 2. tablespaces containing rollback segments with active transactions can be put in offline mode % M0 F W. |5 ~7 M9 M% C4 l
3. all of the above 7 C( a- i: @% U2 D+ U
4. none of the above |