This appendix outlines common error codes that can be triggered by the ASR Manager software.
The ASR Auto Update feature automatically updates your ASR Manager software. For this feature to function properly, you must:
Be running ASR Manager 4.9, 5.0.3, or later.
Have ASR Auto Update enabled (it is enabled by default).
ASR Manager 4.9 only: Be running OASM 1.4.2 or later. See Doc ID 1185493.1 in My Oracle Support to download the latest version of OASM. (OASM is not required for ASR Manager 5.x and later).
Once the ASR Auto Update process is complete, you will receive an e-mail notification of a successful upgrade of the ASR Manager software, or you will be notified that the update process failed. There are a number of reasons why the ASR Auto Update process could fail, and the e-mail notification will include an error code. A full list of the ASR Auto Update error codes is provided below.
A typical e-mail notification of an ASR Auto Update failure would look like this:
| Hostname: <your host name>
Serial#: <your ASR Manager serial number, if activated> -or- ASR SiteID: <your ASR Manager site ID, if the ASR Manager is not activated> Oracle Auto Service Request (ASR) Manager was unable to complete Auto Update due to a failure. New version: 4.6.0 Current version: 4.5 Error code: ASR_INSTALL_FAILED_RESTORED_PREVIOUS_VERSION Review Doc Id: 1503107.1. The Oracle Auto Service Request documentation can be accessed on http://oracle.com/asr. Please use My Oracle Support https://support.oracle.com for assistance. When available, a reference to a workaround or solution to the error code will be provided. If you are unable to resolve the issue after following the troubleshooting information, please open a Service Request using My Oracle Support @ http://support.oracle.com. Use Problem Type: "My - Auto Service Request (ASR) Installation and Configuration Issues" |
The following error codes are described:
Problem: The ASR Manager is unable to connect to Oracle.
Resolution: Check the connection between the ASR Manager to the Oracle ASR infrastructure. The Oracle ASR infrastructure endpoint is:
https://transport.oracle.com
Ensure that the ASR Manager is able to reach above URL on port 443. Also, ensure that the ASR Manager is registered to Oracle ASR infrastructure with a valid user name and password.
Problem: ASR Auto Update cannot connect to the ASR software update server. The following message will be added to the sw-asr.log file:
sw-asr.log.0 contains: Oct 24, 2012 9:48:32 AM com.sun.svc.autoupdate.AsrAutoUpdateService autoUpdatePrep SEVERE: ASR backend server https://transport.oracle.com/em/upload is not available for auto update. Oct 24, 2012 9:48:32 AM com.sun.svc.autoupdate.AsrAutoUpdateService autoUpdate SEVERE: Autoupdate preparation failed. Quiting the process.
When running Auto Update to update ASR Manager 4.9 to ASR Manager 5.x, then the log file to check is:
/var/opt/SUNWsasm/log/sw-asr.log.0
When running Auto Update to update ASR Manager 5.x to a later version of ASR Manager 5.x, then the log file to check is:
/var/opt/asrmanager/log/asr.log
Resolution:
Run the asr test_connection command to ensure the ASR Manager is registered properly with Oracle.
Run the following command to check the Auto Update endpoint connection:
asr> show_version
Note:
If using an NTLM proxy, then running Auto Update from 4.9 or 5.0.x to 5.2 is not working because of a bug that has since been fixed in ASR 5.2. Update to ASR Manager 5.2 manually.Verify that the ASR Manager has an internet connection and is able to reach the ASR software update server:
https://transport.oracle.com/em/upload
Problem: Failed to download the package from the Oracle ASR infrastructure. It could because of slow network connection.
Resolution: Check the connection between the ASR Manager to the ASR software update server. The ASR Auto Update service endpoint is:
https://transport.oracle.com/em/upload
Problem: Failed to obtain new package version from ASR Backend server. One possibility is that the ASR Manager was not able to connect to the Oracle ASR infrastructure.
Resolution: Make sure you can access the https://transport.oracle.com/em/upload URL from the ASR Manager.
Problem: OASM version is older than 1.4.2
Resolution: Upgrade the OASM version to 1.4.2 or above
Problem: ASR Auto Update failed because OASM is disabled or offline
Resolution: Enable OASM:
For Solaris: svcadm enable sasm
For Linux: /opt/SUNWsasm/bin/sasm start-instance
After OASM is brought online, retry ASR Auto Update manually or wait for ASR Auto Update to retry after 24 hours automatically.
Problem: Current ASR Manager backup failed.
Resolution: As part of the ASR Auto Update process, a backup of the existing SWASR package will be attempted. If this process fails, then the ASR Auto Update process will not continue. To check the installed SWASR version, run:
When running Auto Update to update from ASR 4.9 to ASR 5.x, check the installed ASR Manager version:
Solaris: pkginfo -l SUNWswasr
Linux: rpm -qa SUNWswasr
When running Auto Update to update from ASR 5.x to a later version of ASR 5.x, then check the installed ASR Manager version, run:
Solaris: pkginfo -l asrmanager
Linux: rpm -qa asrmanager
If this command returns an error or if the installed version is not current, then remove the current package and install the latest ASR package manually. See Verifying Software Requirements for information on downloading the appropriate software packages.
Problem: Failed to verify existing/downloaded package versions.
Resolution: Verify the existing ASR and OASM versions.
For ASR Manager 5.x and later:
Solaris: pkginfo -l SUNWswasr
Linux: rpm -qa SUNWswasr
For ASR Manager 4.x:
Solaris:
pkginfo -l SUNWswasr pkginfo -l SUNWsasm
Linux:
rpm -qa SUNWswasr rpm -qa SUNWsasm
Make sure both ASR 4.9 and OASM (1.4.2 or higher) are at minimum required versions required for ASR Auto Update.
Problem: Failed to remove the current Oracle ASR package (SWASR or ASRMANAGER).
Resolution: Manually remove the existing Oracle ASR package and update to latest version of the package.
Problem: Failed to execute the deployment script.
Resolution:
When running Auto Update to update from ASR 5.x to a later version of ASR 5.x:
The ASR Auto Update process could not set the execute permissions for the deployment script. Check the user ID, which is set on the /opt/asrmanager and /var/opt/asrmanager directories.
If the user ID on these folder is set to root or asrm, then try to run the autoupdate command manually using the asr command line:
/opt/asrmanager/bin/asr autoupdate
When running Auto Update to update from ASR 4.x to ASR 5.x:
The ASR Auto Update process could not set the execute permissions for the deployment script. Check the user ID, which is set on the /opt/SUNWswasr and /optSUNWsasm directories.
If the user ID on these folder is set to root or oasm, then try to run the autoupdate command manually from the asr command line:
/optSUNWswasr/bin/asr autoupdate
If ASR Auto Update fails again, then manually upgrade the ASR Manager software.
Problem: While a new version of the ASR software update may have been downloaded, ASR Auto Update was not able to install it. The previous version was restored. A status of COMPLETE_FAILED is returned in the following log file, depending on the version of ASR being updated:
When running Auto Update to update from ASR 5.x to a later version of ASR 5.x, then the COMPLETE_FAILED status is returned in a /var/opt/asrmanager/log/asr.log log file.
When running Auto Update to update from ASR 4.9 to ASR 5.x, then COMPLETE_FAILED status is returned in a /var/opt/SUNWsasm/log/sw-asr.log.0 log file.
Resolution: The ASR software package must be removed and then re-installed manually. To remove the current package:
ASR Manager 5.x:
Solaris: pkgrm asrmanager
Linux: rpm -e asrmanager
ASR Manager 4.x:
Solaris: pkgrm SUNWswasr
Linux: rpm -e SUNWswasr
See Verifying Software Requirements for information on downloading the appropriate software packages. See Installing ASR Manager Software for information on installing the ASR package.
Problem: The ASR Auto Update process failed to complete due to unknown error.
Resolution: The ASR software package must be removed and then re-installed manually. To remove the current package:
ASR Manager 5.x:
Solaris: pkgrm asrmanager
Linux: rpm -e asrmanager
ASR Manager 4.x:
Solaris: pkgrm SUNWswasr
Linux: rpm -e SUNWswasr
See Verifying Software Requirements for information on downloading the appropriate software packages. See Installing ASR Manager Software for information on installing the ASR package.
Problem: If you are running JRE 1.6._04 or above (instead of JDK 1.6._04 or above), then ASR Auto Update will fail because of a missing Java jar utility. This Java jar utility that ASR Auto Update uses is not available with JRE. This issue can be corrected by using the JDK instead of the JRE.
Note:
If you have any issues with using the JDK instead of the JRE, you can manually download and upgrade to ASR Manager 4.5 from:http://oracle.com/asr
ASR Manager Release 4.5 corrects the Java jar utility issue, which will allow ASR Auto Update to work with the JRE.
Resolution: To check for the Java jar utility, run the following command as root on the ASR Manager server:
# jar
If the Java jar utility is not available, the following output will be shown:
jar: command not found
If you receive this error message, then run the following command to check the JRE location:
# ls -al /usr/java
Output should look like this:
lrwxrwxrwx 1 root root 21 Dec 15 09:14 /usr/java -> /usr/j2se/jre1.6.0_xx
To resolve this missing Java jar utility issue:
Update Java to JDK (from JRE):
Change the Java pointing to JDK instead of JRE:
# rm /usr/java
Add a link with the JDK version (instead of JRE). For example:
# ln -s /usr/jdk/jdk1.6.0_xx /usr/java
Test the link:
# ls -al /usr/java
Output should look like this:
lrwxrwxrwx 1 root root 15 Apr 16 14:52 /usr/java -> /usr/ jdk/jdk1.6.0_xx
Note:
Replace_xx in the above example with the specific JDK version running on the ASR Manager server.
Also, ensure that you are using the same Java version in the /var/opt/SUNWsasm/configuration/config.ini file for the java.exec property.
Verify the Java jar utility is available. As root on the ASR Manager, run:
# jar
Note:
You may need to manually create the symbolic link for jar. For example:ln -s /usr/java/bin/jar /usr/bin
Get the Auto Update status after fixing the Java issue. From the ASR Manager, run:
asr> show_version
You should now see a message that newer version of ASR Manager is available for download.
Run Auto Update. From the ASR Manager, run:
asr> autoupdate
Once the Auto Update process is complete, run the following commands to verify the Auto Update and Connectivity status:
asr> show_version asr> test_connection asr> heartbeat
Problem: ASR Auto Update will not work on Linux, if the Linux server is missing the rpm-build package. If the rpm-build package is missing you will see the following message during ASR rpm install:
Warning: rpm-build package is not installed on this server. ASR Manager Auto Update functionality will not work unless the rpm-build package is installed. Auto Update functionality will be disabled until rpm-build package is installed. Please install the rpm-build package and then enable Auto Update by running \"asr enable_autoupdate\".
This error message will also appear in a log file if the Auto Update fails because of the missing rpm-build package. The log file is located at:
If Auto Update is running from ASR Manager is 4.9 to 5.x, then the log file is located at:
/var/opt/SUNWsasm/log/sw-asr-autoupdate.log
If Auto Update is running from 5.x to 5.x, then the log file is located at:
/var/opt/asrmanager/log/autoupdate.log
Resolution: Manually upgrade to ASR 5.3 or later. See Using Auto Update to Manually Upgrade ASR Manager Software for details.
Problem: ASR Auto Update will not work on Linux if the Linux server has the seLinux variable is not set in "permissive" mode. If the SELinux variable is set in enforcing mode, then the following message will be displayed on the command line if the autoupdate command is executed manually.If the autoupdate command is started via timer, then the following message will be displayed in following log file:
SELINUX is set in \"enforcing\" mode. Cannot continue with autoupdate. Please refer to the troubleshooting section of ASR Installation guide to resolve this issue. /var/opt/asrmanager/log/asr.log
Resolution: Manually upgrade to ASR 5.3 or later. See Using Auto Update to Manually Upgrade ASR Manager Software for details.
Problem: The ASRM package version is not available.
Resolution: Verify that the ASR Manager package installation is valid:
Solaris: pkginfo -l asrmanager
Linux: rpm -qa asrmanager
Remove the ASR Manager package manually and install the latest version manually:
Solaris: pkgrm asrmanager
Linux: rpm -e asrmanager
Download the latest ASR Manager from MOS download site and follow the instructions in Installing ASR Manager Software to install the software manually.
Problem: Oracle Single Sign-on (SSO) user name is not available.
Resolution: Ensure ASR Manager is registered with Oracle Infrastructure:
asr> test_connection
If the test connection fails, then register ASR Manager with Oracle Infrastructure:
asr> register
Problem: The Auto Update process is not able to get the operating system (OS) information from the server.
Resolution: Identify the current operating system information:
uname
Only the Oracle Solaris and Linux operating systems are supported.
If the server is running the Solaris OS, then the result should be:
SunOS
If the server is running the Linux OS, then the result should be:
Linux
Problem: Some of the scripts and tools required for Auto Update do not have execute permissions.
Resolution: Ensure the ASR Manager user has execute permission for the contents in the /var/opt/asrmanager directory.
Problem: The Auto Update jar unpacking has failed on the ASR client. Most likely cause for this issue is lack of disk space on the ASR Manager server.
Resolution: Run the df -k command to check the disk space on the server.
If the server is running low on disk space, then try to clear the space or add more disk space on the server.
Problem: After Auto Update has run, the updated ASR Manager may not be able to bind the SNMP listener port. In that situation, Auto Update will fail and restore to the existing version.
The following message will appear in the /var/opt/asrmanager/log/asr.log log file:
After upgrading to $DOWNLOAD_PKG_NAME SNMP port binding failed. Restored to existing version.
Resolution: The next Auto Update attempt should complete successfully. If it fails with the same error code, Manually upgrade to the latest version.
See Using Auto Update to Manually Upgrade ASR Manager Software for details.
Problem: The Auto Update package is missing the deployment script.
Resolution: The Auto Update jar file could be corrupted. Download and install the ASR packages manually from My Oracle Support (https://support.oracle.com). See Manually Upgrading ASR Manager Software for more details.
Problem: This error occurs when ASR Manager server runs our of space. This could be java heap space or physical disk space.
Resolution: The default Java Virtual Machine (JVM) maximum heap size is 1536 MB (1.5 GB) and meets the ASR Manager requirements. Make sure your ASR Manager system has 1 GB or more memory available for allocation.
Also if the ASR Manager is running low of physical disk space, then try to add more disk space to allow the Auto Update process to download the new ASR Manager package and upgrade the software.