Recently we worked with ASR on Exadata for multi-part customers. ASR is a great functionality that enables your 'systems' to inform Oracle when hardware failures occur. Sun hardware is using ASM for someday and given 2009/2010 this is moreover existing for Exadata.
My objective is not to re-write the record so for broad data we similar to to impute to this link.
So, where is this note about ? Well, it is about two things we gifted around surroundings up ASR. we similar to to give my experience so others may be successful with ASR swift as well. (It is however approaching that things will be
First, suppose yourself configuring SNMP traps to be sent to ASR. In this incident be certain to not erase any existing SNMP Subscribers settings for e.g. the subscription to Enterprise Manager Grid Control or whatever you already subscribed for.
So, when you have record saying to govern
The syntax allows this:
Second, when configuring SnmpSubscribers using DCLI you have to work with a cut back to elude the brackets. Be certain to authorize your SNMP settings after surroundings them because you may finish up with a joint in the 'asrs.state' file saying 'public\' in stead of 'public'.
Having the additional cut back after the word 'public' of march doesn't help when sending SNMP-traps:
All together ASR is a great add-on to Exadata that we rarely recommend. Some glorious record is created on the doing sum and existing on MyOracleSupport. See "Oracle Database Machine Monitoring (Doc authorization 1110675.1)"
Rene Kundersma
Technical Architect
Oracle Technology Services
No comments:
Post a Comment