![]() | Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||||||
Solution Type Problem Resolution Sure Solution 1613914.1 : Error In Running asrexacheck
In this Document
Created from <SR 3-8153479891> Applies to:Exadata Database Machine X2-2 Full Rack - Version All Versions and laterInformation in this document applies to any platform. SymptomsRunning asrexacheck I got the following error: Unable to determine Device Type, System Identifier states:
system_identifier = Exadata Database Machine X2-2 AKXXXXXXXX (AKXXXXXXXX substitutes a real serial number in this document) If system is returning a null value or (None) Please open a Service Request with the Exadata Hardware Team To help set your system Identifier.
root@host:~# /opt/ipmitool/bin/ipmitool sunoem cli 'set /SP system_identifier="Exadata Database Machine X2-2 AKXXXXXXXX"'
Connected. Use ^D to exit. -> set /SP system_identifier="Exadata Database Machine X2-2 AKXXXXXXXX" Set 'system_identifier' to 'Exadata Database Machine X2-2 AKXXXXXXXX' -> Session closed Disconnected
ChangesNew system CauseCurrent download fo asrexacheck wil not work on Solaris due to this line in the code: echo "$DEV_TYPE" | grep -i "Database Machine\|Exadata Storage Expansion" > /dev/null 2>&1
Note the vertical bar meaning an 'or' in the grep expression. This does not work on Solaris as explained by this URL: http://stackoverflow.com/questions/5918150/solaris-grep-with-or-functionality
SolutionThe solution is to replace 'grep' by 'egrep' So the new line should read: echo "$DEV_TYPE" | egrep -i "Database Machine\|Exadata Storage Expansion" > /dev/null 2>&1
A new version of asrexacheck will be uploaded to the asr URL shortly. References<BUG:17902281> - ASREXACHECK FAILS ON SOLARISAttachments This solution has no attachment |
||||||||||||||||||||
|