Minimum COMPATIBLE Attributes for ACFS Replication and Encryption
A cluster running 19c Grid Infrastructure supports both Oracle 11g to 19c RAC databases using ASM. The COMPATIBLE.ASM, COMPATIBLE.RDBMS, and COMPATIBLE.ADVM parameters are currently set to 11.2 for all diskgroups. You must support these capabilities in all diskgroups: 1. ACFS Replication 2. ACFS Encryption To what minimum values must the compatible attributes be set?
Community Votes
100% of anonymous learners picked answer D. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
The exam tests your knowledge of feature-specific compatibility levels, specifically the trap that ACFS replication/encryption requires COMPATIBLE.ADVM >= 12.1 even if the database version is older.
To enable ACFS Replication and Encryption on Oracle RAC diskgroups, specific minimum values for COMPATIBLE.ASM, COMPATIBLE.RDBMS, and COMPATIBLE.ADVM attributes must be configured. This question establishes that while ASM compatibility can remain at 11.2, the ADVM attribute requires a higher version to support these advanced features.
Many candidates incorrectly choose option B (setting all to 12.1) because they assume uniform upgrades are needed. However, setting COMPATIBLE.RDBMS to 12.1 prevents Oracle 11g databases from accessing the diskgroup, violating the requirement to support existing 11g RAC databases.
Community Discussion (3 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
Option D is correct because it balances backward compatibility with new feature requirements. To use ACFS Replication and Encryption, the COMPATIBLE.ADVM attribute must be set to at least 12.1. The COMPATIBLE.ASM attribute can remain at 11.2 as long as the GI is 19c, but crucially, COMPATIBLE.RDBMS must stay at 11.2 to allow Oracle 11g databases to mount the diskgroups. Setting COMPATIBLE.ASM to 12.1 is optional but often done; however, the critical differentiator here is that COMPATIBLE.RDBMS cannot be raised to 12.1.Why the Other Options Are Wrong
Option B sets COMPATIBLE.RDBMS to 12.1, which would prevent Oracle 11g databases from mounting the diskgroups, directly contradicting the scenario's requirement to support 11g RAC. Option A and C leave COMPATIBLE.ADVM at 11.2, which does not support ACFS Replication or Encryption. Option E leaves all at 11.2, failing to enable the required features. Option D is the only one that raises ADVM to 12.1 while keeping RDBMS at 11.2.Community Comment Notes
The community consensus strongly supports Option D. As user krwi1 noted, setting COMPATIBLE.RDBMS to 12.1 will break 11.2 database access. Another commenter pointed out that while some features existed in earlier patches, the standard exam logic for 'Replication' and 'Encryption' generally points to the 12.1 threshold for ADVM compatibility in modern contexts, making the mixed attribute set in D the technically valid choice for this specific constraint set.Exam Strategy
When asked about compatibility levels, always check if any legacy database versions need to access the storage. If an older RDBMS version (e.g., 11g) must connect, COMPATIBLE.RDBMS cannot exceed that version's major release number, regardless of other feature requirements.
Frequently Asked Questions
Why can't COMPATIBLE.RDBMS be set to 12.1?
Setting COMPATIBLE.RDBMS to 12.1 prevents Oracle 11g databases from mounting the diskgroup. Since the scenario requires supporting 11g RAC, this attribute must remain at 11.2.
Does COMPATIBLE.ASM need to be 12.1 for ACFS encryption?
Not strictly for the feature itself, but COMPATIBLE.ADVM must be 12.1. In Option D, ASM is raised to 12.1 likely for best practice or specific GI interactions, but the critical factor is ADVM >= 12.1 and RDBMS <= 11.2.