Oracle Auto Service Request (ASR) is designed to automatically request Oracle service when specific faults occur. This chapter identifies the features and enhancements provided by Oracle Auto Service Request Release 5.2.1.
The Oracle ASR Manager Release 5.2.1 software upgrade is quick to install and is available for download from
All customers are urged to upgrade to this release at their earliest convenience. See Using Auto Update to Upgrade Oracle ASR for instructions on how to upgrade to the latest version of the ASR Manager.
Note:Support for Oracle Auto Service Request is limited to the current release and the two previous releases. Oracle now supports ASR 5.2.1, 5.2, and 5.0.3. It is recommended that you upgrade to the latest version. See Using Auto Update to Upgrade Oracle ASR for more information.
Corrects an issue for Solaris sites auto updated from ASR Manager 5.0.3 to ASR Manager 5.2 where the
activate_blade commands are not working.
Corrects an issue where some sites auto updated to ASR Manager 5.2 incorrectly received a warning notification that the auto update process did not complete. This incorrect warning notification will not be received for future auto updates.
Corrects an issue where for some ASR Manager 5.2 sites the
show_version command is resulting in log4j errors being written to the console.
Corrects issues ASR Manager 5.0.x versions have working with NTLM proxies, including Auto Update and the ASR
Improvements to ASR command line text.
Numerous fixes and improvements to the ASR Auto Update process including better failure messaging and information.
Corrects an issue where "?" is not displaying the list of ASR commands at the
Corrects an issue where ASR heartbeat events are not properly processing serial numbers that have "+" in them.
Starting with ASR 5.0.3, the default Oracle ASR infrastructure end point, if available, is changed to
transport.oracle.com (220.127.116.11), if not already set. The following two ASR end points are eventually going to be terminated:
transport.sun.com (18.104.22.168) and
transport.sun.co.uk (22.214.171.124). Additionally, ASR Auto Update will not work for sites using these end points.
The following known issues for ASR Manager 5.0.0, 5.0.1, and 5.0.2 have been corrected with the release of ASR Manager 5.0.3, including:
Corrects an issue where ASR Managers are running in a multi-network interface environment and are not properly binding to SNMP trap receivers, and as a result, traps are not being received from these assets.
Corrects an issue where sites using a proxy with authentication enabled are having connecting to the Oracle ASR infrastructure.
Corrects an issue where sites using a general proxy are having with ASR Auto Update not working.
Corrects an issue with some Solaris ASR Auto Update enabled sites where ASR Manager 5.0.0, 5.0.1, and 5.0.2 sites are not or will not Auto Update. These sites have Auto Update enabled but are not Auto Updating as a result of the issue.
Corrects an issue where diagnostic log file send is not working for sites using a proxy (with or without authentication).
Corrects an issue where some Solaris ASR Manager 4.9 sites with Auto Update enabled are not auto updating. These 4.9 sites have Auto Update enabled but are not able to Auto Update.
Corrects an issue where the
show_version commands are intermittently not responding.
Corrects an issue where there is an SNMP port conflict resulting from running OASM for SFT on the same server as ASR Manager.
Corrects an issue where the ASR Manager local SR notification trap is not including the default OID.
Corrects an issue where if the ASR Manager local SR notification trap is enabled, duplicate traps are being sent.
Corrects an issue where the test SNMP
get command (
test_snmp_get) is not working if using a non
public community string.
Transport URL change required: ASR Auto Update will not work for ASR Managers using either of these two end points:
You may need to update your configuration to use transport.oracle.com (126.96.36.199).
Instructions for how to determine if this change is needed and how to make the change is provided in My Oracle Support (MOS) Doc ID 1954819.1: