Which statement indicates the proper time to change the compatible.rdbms disk group attribute to 11.2?

The disk groups on the current ASM instance at version 11.2 were configured to support a version
10.2 database instance. The 10.2 instance has the COMPATIBLE parameter defined as 10.2.0.
The compatible.asm attribute is set to 11.2 for each disk group. The database has been upgraded
to 11.2. Which statement indicates the proper time to change the compatible.rdbms disk group
attribute to 11.2?

The disk groups on the current ASM instance at version 11.2 were configured to support a version
10.2 database instance. The 10.2 instance has the COMPATIBLE parameter defined as 10.2.0.
The compatible.asm attribute is set to 11.2 for each disk group. The database has been upgraded
to 11.2. Which statement indicates the proper time to change the compatible.rdbms disk group
attribute to 11.2?

A.
Change the disk group attribute after the database instance COMPATIBLE parameter is
upgraded to 11.2.

B.
Change the disk group attribute after the database instance is started with the 11.2 software.

C.
Change the disk group attribute after the database instance optimizer_features_enabled
parameter is set to 11.2.

D.
Change each disk group after the 11.2 features are required for use on the disk group.

E.
Never, upgrading the attribute is not reversible.

Explanation:
COMPATIBLE.RDBMS
The value for the disk group COMPATIBLE.RDBMS attribute determines the minimum
COMPATIBLE database initialization parameter setting for any database instance that is allowed
to use the disk group.
Before advancing the COMPATIBLE.RDBMS attribute, ensure that the values for the
COMPATIBLE initialization parameter for all of the databases that access the disk group are set to
at least the value of the new setting for COMPATIBLE.RDBMS.
Oracle Automatic Storage Management Administrator’s Guide
11g Release 2 (11.2)



Leave a Reply 1

Your email address will not be published. Required fields are marked *


L. Zhu

L. Zhu

A is right. compatable.rdbms <= compatible on db init
B is wrong. not just the software, but compatible init parameter
C is wrong. nothing to do with optimizer
D is wrong.
E is wrong.

So A is correct