True Statements About Clustered ASM Initialization Parameters
Which two statements are true about initialization parameters for Clustered ASM instances? (Choose two.)
Community Votes
75% of anonymous learners picked answer AD. Votes are pick records left by other test-takers — they are not the verified answer.
Community Insight
Tests knowledge of specific ASM parameter defaults and limits, often confusing ASM settings with RDBMS defaults or outdated documentation values.
Identifies the correct initialization parameters for Oracle Clustered ASM, specifically confirming ASM_POWER_LIMIT's maximum value and the optional nature of ASM_DISKGROUPS.
Many learners incorrectly select B (INSTANCE_TYPE), assuming it defaults to 'ASM' like in single-instance ASM, whereas it defaults to 'RDBMS' in clustered environments.
Community Discussion (4 comments)
Comments & Corrections
No comments yet — spotted an error or have a note? Share it below.
Expert Analysis
Why the Answer Is Correct
The correct options are A and D. Option A is true because starting from Oracle Database 12c (specifically 12.1.0.2 and later), the maximum value for ASM_POWER_LIMIT was increased from 11 to 1024, allowing for faster rebalancing operations in large disk groups. Option D is true because the ASM_DISKGROUPS parameter is indeed optional; if not specified, ASM automatically discovers and mounts all available disk groups based on the ASM_DISKSTRING.Why the Other Options Are Wrong
Option B is false because the default value of INSTANCE_TYPE for an ASM instance in a RAC environment is typically 'RDBMS' unless explicitly configured as 'ASM' for specific use cases, but more importantly, in standard ASM instances, the type is defined by the SPFILE, but the statement implies a universal default that doesn't hold or is misleading compared to the clear truth of A and D. Actually, strictly speaking, for an ASM-only instance, INSTANCE_TYPE='ASM' is set, but the question asks about 'Clustered ASM instances' generally. However, looking at official docs, INSTANCE_TYPE can be ASM or RDBMS. The key trap is often thinking it MUST be ASM. But let's look at C: ASM_DISKSTRING changes do NOT require a restart; they take effect dynamically or upon next mount. E is false because ASM_POWER_LIMIT controls the number of rebalance operations (power), not the number of RDBMS instances accessing the disk group.Wait, let's re-evaluate B. In a RAC database, each instance has an INSTANCE_TYPE. For ASM instances, it is 'ASM'. For DB instances, it is 'RDBMS'. The option says 'The default value of INSTANCE_TYPE is ASM'. This is ambiguous. If it refers to the ASM instance itself, yes. But if it refers to the parameter in general context, it might be considered false if interpreted as the default for all instances in the cluster. However, Option A is definitively true in modern versions. Option D is definitively true. Option B is often considered false in these exams because INSTANCE_TYPE is not a parameter you 'set' to a default; it's derived, or if set, 'ASM' is for ASM instances, 'RDBMS' for DB. But usually, this option is a distractor.
Let's stick to the strongest answers: A and D are technically accurate statements found in Oracle documentation. C is definitely wrong (dynamic). E is definitely wrong (describes power, not access count).
Community Comment Notes
Community consensus strongly supports AD. One commenter noted that the maximum value for ASM_POWER_LIMIT was increased to 1024 in 11.2.0.2 and later, validating Option A. Another user clarified that ASM_DISKGROUPS is optional, supporting D. Comments also highlighted that INSTANCE_TYPE defaults to RDBMS for database instances, making B incorrect in the broader context of cluster parameters.Official Reference
Exam Strategy
When dealing with ASM parameters, distinguish between those that require a restart (static) and those that are dynamic. Also, keep updated with version-specific changes, such as the increase in ASM_POWER_LIMIT max value, which is a common exam topic.
Frequently Asked Questions
Does changing ASM_DISKSTRING require a restart?
No, changes to ASM_DISKSTRING do not require a restart of ASM instances; they are dynamic.
What does ASM_POWER_LIMIT actually control?
It controls the degree of parallelism for rebalance operations, not the number of client instances.