In the past the Oracle ASR Manager did update itself
automatically. This is not the case anymore with newer
releases.
But the manual update on Solaris is very easy.
Only two commands required
pkgrm asrmanager
pkgadd -d ./asrmanager-25.1.0-20250306063253.pkg
Learn more about Oracle ASR on
https://docs.oracle.com/cd/E37710_01/index.htm
In a few cases I expected an ASR SR would be opened, but it did not happen.
If there are special characters in the fault the ASR manager
can't handle the request.
This can be found in the ASR Manager log
/var/opt/asrmanager/log/asr-http.log
To make ASR work correctly you have to remove the old "bad"
xml files from the ASR client.
# pwd
/var/fm/asr/msgs
# ls -tlr
total 1827
-rw-r--r-- 1 noaccess noaccess 3136 Jul 30 22:32 heartbeat.xml
-rw-r--r-- 1 noaccess noaccess 910240 Jul 30 22:33 audit.xml
-rw-r--r-- 1 noaccess noaccess 10604 Jul 31 10:43 fault-f680bb98-d016-4259-bc00-941858fcaced.xml
rm fault-*.xml
Most of the time it is required to attach additional files to Oracle Support Cases,
for example ILOM/XSCF snapshots or Logfiles.
If you use the ASR Manager on Solaris it is very easy to attach
additional files. It includes a transport tool. No need to copy files to
your local machine and to upload using a Browser.
Check if you use the ASR Manager
# svcs |grep asrm
online 2024-05-08T17:29:45 svc:/application/management/asrm:default
You can just copy your files into this directory
/var/opt/asrmanager/sftransport/transfer/
The files need to start with your SR-Number, for example
3-31234567890.mylogfile
The files are transported to Oracle Support and attached
to your SR every 10 minutes.
You can check the state using
/opt/asrmanager/bin/sftransport info
