More information about the Oracle ASM agent (4310746)

More information about the Oracle ASM agent

Additional information regarding the ASM agent (general info, Collections, Requirements, etc…)

The former ASM solution was designed to retrieve ASM information directly from the Oracle instance, served by the ASM instance .

The work assumption was based on the fact that Oracle replicates the ASM metadata views from the ASM instance to all the Oracle instance it serves, so rather than accessing both instances (Oracle and the ASM instances), we can retrieve all the required information through the Oracle instance.

After the solution was implemented and used by customers for awhile, different combinations of Oracle versions and ASM environment surfaced Oracle bugs in the information replicated from the ASM to the Oracle instance, including wrong and delayed data, which rendered the solution that collected the information from Oracle unreliable. In order to workaround these Oracle bugs (and future bugs that have yet to be revealed) we have created a dedicated ASM agent solution, in which we will be collecting the information directly from the ASM instance.

ASM Collections

• ASM Instance statistics per instance
• ASM Instance statistics aggregated to the cluster level
• ASM storage data, which is shared among the instances
• Related v$ tables:
• v$asm_diskgroup / v$asm_diskgroup_stat
• v$asm_disk / v$asm_disk_stat
• v$asm_operation

Credentials

• Required SysAsm/ SysAdm credential for access to the Oracle ASM instance
• Required OS user with the same privileges as for the Oracle agent

Installation/Configuration instructions

The ASM agent will be created manually by using FMS agent status dashboard.

It will require the following parameters:

• ASM Instance credential (required SysAsm/SysDBA user)
• OS credential (Windows/UNIX)
• Add the relevant ASM instances
• In case of ASM on RAC there will be more than one ASM instance

Once those parameters are filled, save and activate the ASM agent.

If the ASM agent is not installed, ASM information will be not be taken into consideration for the purposes of alarms or UI elements (For example, Tablespaces which reside on ASM diskgroups and have one or more datafiles marked autoextend YES, will not trigger alarms). To be able to create the ASM agent you need the Oracle Cartridge 5.6.4.330 installed, prior releases to this do not have the ASM agent installed.