How to create Explorer report with Oracle Explominer Tools

What is Oracle Explorer?

The Oracle Explorer Data Collector is a collection of shell scripts and a few binary executable that gathers information and creates a detailed snapshot of a system’s configuration and state. Explorer output enables Oracle’s engineers to perform assessments of the system by applying the output against knowledge-based rules engine.

Oracle Explorer Data Collector is part of Oracle Services Tools Bundle (STB). As Explorer uses the Remote Diagnostic Agent (RDA) tool to collect part of its information and because RDA is part of the STB, it is highly advised to install the entire STB bundle.

For more information about Explorer and STB, go to > Oracle Explorer Data Collector Installation and Services Tools Bundle (STB) User’s Guide page.

How to create Explorer report with Oracle Explominer Tools:

Explominer package only available at EIS (Enterprise Installation Service ) DVD – which is intended for Oracle employees and partner only. EIS-DVD can be download at

install Explominer:

– open EIS-DVD
– search sun – tools – explominer
– copy explominer.tar.gz to destination server
– after that please extract with “gzcat explominer.tar.gz|tar xvf –
– then go to directory ExploMiner
– then run explominer

There is difference script/package based on processor type:  i386, Sparc and x86 machine.

bash-3.00# pwd
bash-3.00# ls
explominer explominer.i386 explominer.sparc explominer.tar.gz explominer.x86

Create Explorer report:

Copy and extract the explorer output file and run explominer, below are the example:

/tmp/output/explorer.853c62da.server-2016. >>my explorer extract folder location

/export/home/explominer_report >>report folder


bash-3.00# ./explominer.x86 -h
Copyright (c) 2013, Oracle and/or its affiliates. All right reserved.
ExploMiner v2.11.6 EIS-CD 07/2013

usage: [-h] [-f expdir] [-o outdir] [-e eisdir] [-c] [-m] [-r] [-i] [-a]

In the first form prints this help message.
In the second form performs the checks and writes the
results to output files.

arguments: none

options: -h print this help message
-f expdir
find explorer output in directory expdir
default: .
-o outdir
write output files to directory outdir
default: .
-e eisdir
compare the results of the patch analysis with the patchdiag.xref and patch.list files from the
EIS-CD found at eisdir and generate the file ExploMiner_EIS_Patchlist_user
-c generate the customer report file ExploMiner_CustomerReport.txt
-m analyze message files even if > 4MByte
-r calculate eOri
-i mention internal, proprietary information as well
-a show all FMA Cases


bash-3.00# ./explominer.x86 -f /tmp/output/explorer.853c62da.server-2016. -o /export/home/explominer_report -e /cdrom/eis-dvd/sun/patch/etc/ -c -m -r -i -a

=== Copyright (c) 201X, Oracle and/or its affiliates. All rights reserved. ===
=== ExploMiner vX.XX.X EIS-CD XX/20XX ===
[explorerdir]: /tmp/output/explorer.853c62da.server-2016.
[outputdir]: /export/home/explominer_report
[eisdir]: /cdrom/eis-dvd/sun/patch/etc/

Contents Output file name
HTML_Check_Results [outputdir]/ExploMiner_Output_root.html
Alerts [outputdir]/ExploMiner_Alerts_Output_root output [outputdir]/ExploMiner_messages.out.root
Patchlist [outputdir]/ExploMiner_Patchlist_root
Ordered Patchlist [outputdir]/ExploMiner_Patchorder_root
patchdiag output [outputdir]/ExploMiner_patchdiag.out.root
filtered patchdiag output [outputdir]/ExploMiner_patchdiag.out.root_without_CURRENT
security patches output [outputdir]/ExploMiner_Security_Patches_root

Patch-Matrix-files should not be older than 45 days.
NOTICE: ExploMiner does now also include the revision of patches included in the Solaris Recommended Patch Set (see “rps:”) in addition to the latest revision (see “current:”), and – if this revision is lower than the latest patch revision – the respective release date.

IMPORTANT: ExploMiner is primarily intended for reactive, break-fix support. It shows the latest revision (see “current”) or when it’s not installed (see “missing”) of any patch that is found to be relevant,
eventually preceded by the revision of that patch that is included in the Solaris Recommended Patch Set (see “rps”) from the day when ExploMiner was run.

Patches listed in its output might be relevant to any known issues, but their presence herein does not necessarily manifest a general patch recommendation.

ExploMiner is not primarily intended for proactive patch management!

IMPORTANT: Please note: Despite the instructions on MOS, some customers may have improperly loaded attachments into this system that contain electronic protected health information (ePHI). Should you encounter any ePHI, immediately delete all copies from this system and purge any local copies. See the GCS Health Legislation Management section of the MOS Desk Manual for procedures on how to do this.
To learn about how to recognize ePHI and Oracle’s need to keep it out of GCS systems, visit the HIPAA Regulatory Compliance workspace at

NOTICE: PatchId: 119368: revision from showrev-p.out (-05) > (-04) from EIS patch.list
NOTICE: PatchId: 123893: revision from showrev-p.out (-25) > (-22) from EIS patch.list
No file ‘sysconfig/ifconfig-a-modlist.out’ found

/Patch_Clusters/SUNOS_pkgadd.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Kernel.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Library.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_SMF.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_NTP.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_vold.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_timezones.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_syslogd.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_UFS.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_MTB.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_VXFS.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Printing.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Java.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_Webconsole.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_smpatch.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_SMC.patch_matrix is older than 45 days
/Patch_Clusters/SUNOS_FMA.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_nxge.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_tcp-ip.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_ipmp.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_socket.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_TLI.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_RPC.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_nscd.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_inetd.patch_matrix is older than 45 days
/Patch_Clusters/COMMS_NFSclient.patch_matrix is older than 45 days
/Patch_Clusters/OSP_mpt.patch_matrix is older than 45 days
/Patch_Clusters/OSP_qlc.patch_matrix is older than 45 days
/Patch_Clusters/OSP_SAN.patch_matrix is older than 45 days
/Patch_Clusters/OSP_sd.patch_matrix is older than 45 days
/Patch_Clusters/OSP_DiskUtils.patch_matrix is older than 45 days
/Patch_Clusters/OSP_VXVM.patch_matrix is older than 45 days
/Patch_Clusters/OSP_VXVM-GUI.patch_matrix is older than 45 days
/Patch_Clusters/OSP_VXVM-GUI.patch_matrix is older than 45 days
rootdg: 0


Check all in one output:
HTML_Check_Results >> [outputdir]/ExploMiner_Output_root.html


Setup or configure a TFTP Server on Solaris

This is the procedure on how to setup or configure a TFTP Server on Solaris host.

/tftpboot is the default location of tftp, it can be changed through /etc/inetd.conf file. On this below example, lets juts enable the tftp line and use default /tftpboot

root@solaris10 # vi /etc/inetd.conf

*uncomment this line:
tftp dgram udp6 wait root /usr/sbin/in.tftpd in.tftpd -s /tftpboot

*create /tftpboot directory:
root@solaris10 # mkdir /tftpboot
root@solaris10 # chown root /tftpboot
root@solaris10 # chmod 755 /tftpboot
root@solaris10 # cd /tftpboot
root@solaris10 # ln -s . tftpboot

*on this below sample, I move file c2960-lanbasek9-mz.122-55.SE12.bin from root to folder /tftpboot
root@solaris10 # mv c2960-lanbasek9-mz.122-55.SE12.bin /tftpboot/

*chmod the file to 444 (owner/group/other only able to read):
root@solaris10 # chmod 444 c2960-lanbasek9-mz.122-55.SE12.bin
root@solaris10 #

*Use inetconv command to install tftp SMF (Service Management Facility) and bring it online:
root@solaris10 # inetconv -i /etc/inetd.conf
inetconv: Notice: Service manifest for 100235/1 already generated as /var/svc/manifest/network/rpc/100235_1-rpc_ticotsord.xml, skipped
tftp -> /var/svc/manifest/network/tftp-udp6.xml
Importing tftp-udp6.xml ...Done
root@solaris10 #
root@solaris10 # svcs -a | grep -i tftp
online 12:50:11 svc:/network/tftp/udp6:default
root@solaris10 #

*Let’s do tftp and test download the file:
* is the IP address of Solaris tftp server

*from other Solaris/unix host:
# tftp <tftp-server-host/IP>
tftp> get
Received xxx bytes in x.x seconds
tftp> quit

*Example from Cisco switch:
c2960-SWITCH#copy tftp: flash:
Address or name of remote host []?
Source filename [c2960-lanbasek9-mz.122-55.SE12.bin]?
Destination filename [c2960-lanbasek9-mz.122-55.SE12.bin]?
Accessing tftp://
Loading c2960-lanbasek9-mz.122-55.SE12.bin from (via Vlan1): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 9827106 bytes]
9827106 bytes copied in 187.057 secs (52535 bytes/sec)

Hardware Diagnostics for Oracle Sun systems, A Toolkit for System Administrators

The easiest way to diagnose the hardware related problem on Oracle Sun server is by using of OBP OK Prompt commands, the Power On Self Test (POST), and the status LEDs on system boards.

ou can diagnose hardware related problems on Oracle Sun server and desktop products. With these low-level diagnostics, you can establish the state of the system and attached devices. For example, you can determine if a device is recognized by the system and working properly, or you can also obtain useful system configuration information.

OBP is a powerful, low-level interface to the system and devices attached to the system (OBP is also known as the ok prompt). By entering simple OBP commands, you can learn system configuration details such as the ethernet address, the CPU and bus speeds, installed memory, and so on. Using OBP, you can also query and set system parameter values such as the default boot device, run tests on devices such as the network interface, and display the SCSI and SBUS devices attached to the system.

Below are the available commands in OBP OK prompt:
Displays the power on banner. The banner includes information such as CPU speed, OBP revision, total system memory, ethernet address and hostid.

devalias alias path
Defines a new device alias, where alias is the new alias name and path is the physical path of the device. If devalias is used without arguments, it displays all system device aliases (will run up to 120 MHz).

Displays the ethernet address

Turns the system led off or on.

nvaliasname path
Creates a new alias for a device, where name is the name of the alias and path is the physical path of the device. Note – Run the reset-all or the nvstore command to save the new alias in non-volatile memory (NVRAM).

nvunalias name path
Deletes a user-created alias (see nvalias), where name is the name of the alias and path is the physical path of the device. Note – Run the reset-all or nvstore command to save changes in NVRAM.

Copies the contents of the temporary buffer to NVRAM and discards the contents of the temporary buffer.

Powers the system off or on.

Displays all parameters, settings, and values

dentifies Fiber Channel Arbitrated Loop (FCAL) devices on a system. 1

Identifies devices attached to all SBUS slots. Note – This command works only on systems with SBUS slots.

Identifies devices attached to the onboard SCSI bus. 1

Identifies devices attached to all SCSI busses. 1

set-default parameter
Resets the value of parameter to the default setting.

Resets the value of all parameters to the default settings. Tip – You can also press the Stop and N keys simultaneously during system power-up to reset the values to their defaults.

setenv parameter value
Sets parameter to specified value. Note – Run the reset-all command to save changes in NVRAM.

Displays all the devices recognized by the system.

Displays the physical device path for disk controllers.

Displays the physical device path for frame buffers.

Displays the physical device path for network interfaces

If run after Power On Self Test (POST) is completed, this command displays the findings of POST in a readable format.

Displays devices attached to all SBUS slots. Similar to probe-sbus .

Displays the physical device path for tape controllers.

sifting string
Searches for OBP commands or methods that contain string. For example, the sifting probe command displays probe-scsi, probe-scsi-all, probe-sbus, and so on.

Displays CPU and bus speeds

test device-specifier
Executes the selftest method for device-specifier. For example, the test net command tests the network connection.

Tests all devices that have a built-in test method.

Displays OBP and POST version information.

Tests a clock function.

Monitors the network connection for the primary interface.

Monitors all the network connections.

Displays all OBP commands and methods


OBDiag also displays diagnostic and error messages on the system console.

How To Run OBDiag
To run OBDiag, simply type obdiag at the Open Boot ok prompt.
You can also set up OBDiag to run automatically when the system is powered on using the following methods:

Set the OBP diagnostics variable:   ok setenv diag-switch  true
Press the Stop and D keys simultaneously while you power on the system.
On Ultra Enterprise servers, turn the key switch to the diagnostics position and power on the system.

POST is a program that resides in the firmware of each board in a system, and it is used to initialize, configure, and test the system boards. POST output is sent to serial port A (on an Ultra Enterprise server, POST output is sent only to serial port A on the system and clock board). The status LEDs of each system board on Ultra Enterprise servers indicate the POST completion status. For example, if a system board fails the POST test, the amber LED stays lit.
You can watch POST ouput in real-time by attaching a terminal device to serial port A. If none is available, you can use the OBP command show-post-results to view the results after POST completes.

How To Run POST
– connect to serial port
– set the dig-switch to ‘true’
ok setenv diag-switch  true
– Set the desired testing level (min or max), example:
ok setenv diag-level max
– Set the auto-boot variable to ‘false’
ok setenv auto-boot  false
– run ‘reset-all’ >> ok reset-all
– Reboot or Power cycle the system

The following table describes OS commands you can use to display the system configuration, such as failed Field Replaceable Units (FRU), hardware revision information, installed patches, and so on

/usr/platform/sun4u/sbin/prtdiag -v
Displays system configuration and diagnostic information, and lists any failed Field Replaceable Units (FRU).

/usr/bin/showrev [-p]
Displays revision information for the current hardware and software. When used with the -p option, displays installed patches.

Displays system configuration information.

/usr/sbin/psrinfo -v
Displays CPU information, including clock speed.

ref# Doc ID 1005946.1

How to Upload Files to Oracle Support

As an old Sun/Oracle upload file method has been discontinued, below are the several method on how to upload files to Oracle Support based on file size.


  • FTPS & HTTPS to MOS File Upload service – 200 GB max


  1.     Set “ftps://” as the Host
  2.     Supply the appropriate credentials (MOS Support Portal username and password)
  3.     Leave the Port setting blank
  4.     After connecting, double-click on the Issue directory in the right (Remote) pane
  5.     Double-click the SR number’s directory in the right (Remote) pane
  6.     Locate the file to be transferred in the left (Local) pane
  7.     Drag-and-drop the file into the relevant SR directory
  • Diagnostic Assistant (DA), using MOS file utilities – 200 GB max

Diagnostic Assistant (DA)

DA 2.2 (included w/RDA/Explorer/STB 8.02) now supports uploads via https to MOS File Upload Service. Use DA via menus,explorer or the command line.


  1. Run diagnostic assistant menu:
  2. /<linux/solaris rda home>/da/ menu or <win rda home>dada.cmd menuDiagnosticAssistance
  3. Start with option 3: RDA, OCM,ADR, SR Creation / Packaging, and MOS ToolsDiagnosticAssistant
  4. Next select option 4: Package, Upload Diagnostic FilesDiagnosticAssistanct
  5. Complete it with option 7: Upload File Package to SRDiagnosticAssistant
  6. You will be prompted for your SR, credentials and the file.


To use DA do a command line upload: upload -p sr=<SR Number>file=path=<path to file>

To use DA to upload with explorer

explorer -w default -T DA -SR <Service Request number>

NOTE: If SR Number is not specified, the file will be uploaded to

  • Secure File Transport (SFT), part of ASR Manager – 200 GB max

# /opt/SUNWsasm/bin/sasm transport -r
Enter “1” to select:
Or, enter:

  • FTP, including SFTP, is not supported

*Reference: Doc ID 1547088.2 and Doc ID 1596914.1

How to Configure SL24 / SL48 with Netbackup

SL24 and SL48 are the Oracle’s entry level of Autoloader/Tape Library.

Check here for complete documentation.

L24/48 Library are using a single SCSI ID and two logical unit numbers (LUN). LUN 0 controls the tape drive and LUN 1 controls the robotic. So, its require an HBA that supports multiple LUNs. If multiple LUN support is not enabled, the host server cannot scan beyond LUN 0 to discover the Library. It just sees the tape drive.

To check the device and connectivity status from Solaris, please use the show_FCP_dev option: “cfgadm -o show_FCP_dev -al”, instead of “cfgadm -al” command. The robotic or changer will not shown if you use standard “cfgadm -al” command.
If the changer detected already by “cfgadm -o show_FCP_dev -al” command but still not detected by NBU sgscan command, check your NBU device configuration. You need to modify the st.conf file in order to detect the devices on two LUNs.

[Find the following line in the st.conf file:

name=”st” target=0 lun=0;

Replace that line and the following lines through target 5 with the following. Doing so modifies the st.conf file to include searches on non-zero LUNs:

name="st" target=0 lun=0;
name="st" target=0 lun=1;
name="st" target=1 lun=0;
name="st" target=1 lun=1;
name="st" target=2 lun=0;
name="st" target=2 lun=1;
name="st" target=3 lun=0;
name="st" target=3 lun=1;
name="st" target=4 lun=0;
name="st" target=4 lun=1;
name="st" target=5 lun=0;
name="st" target=5 lun=1;
name="st" parent="fp" target=0;
name="st" parent="fp" target=1;
name="st" parent="fp" target=2;
name="st" parent="fp" target=3;
name="st" parent="fp" target=4;
name="st" parent="fp" target=5;
name="st" parent="fp" target=6;

Click here for complete information on how to configure tape drive and robotic devices for Netbackup.

If the SL24/SL48 has the SAS tape drives and you are using LSI SAS HBA, please check and upgrade the SAS HBA driver.

There was an issue with the LSI SAS1 (3GB) HBA with a firmware level of 1.26.00 and below, where the HBA will not see any SAS devices connected to it. Check below document (MOS access required) for more detail.

HBA – LSI SAS HBA Firmware Issue, SAS Devices Not Being Seen by Server (Doc ID 1350564.1)

ERROR: Last Trap: Instruction Access Exception

{0} ok boot
Boot device: /pci@7c0/pci@0/pci@1/pci@0,2/LSILogic,sas@2/disk@0,0:a File and args:
Loading ufs-file-system package 1.4 04 Aug 1995 13:02:54.
FCode UFS Reader 1.12 00/07/17 15:48:16.
Loading: /platform/SUNW,Sun-Fire-T200/ufsboot
Loading: /platform/sun4v/ufsboot
ERROR: Last Trap: Instruction Access Exception

If you got above error messages when powering on Sun Server (T-series, T1000/T2000), and the boot process stuck in there, do not call Oracle support or open SR via MOS unless you try below simple troubleshooting step:

Try to unplug all USB devices – ie USB keyboard + mouse, KVM etc, then connect your laptop/PC to server via serial port then reboot the server. IF the error messages are disappeared, I believe the server will able to boot as usual.

This issue are mostly related with USB keyboard /mouse or other USB related devices. It could be the USB devices or the USB port of the server it self. Try to plug the USB device on another port then reboot the server again. For T2000 there are 4 USB port on the back and 2 USB port on the front.

How to reset/recover Integrated Lights Out Manager (ILOM) password

The default user and password of ILOM is “root/changeme”, but if you hv changed the password already and due for some reason you forgot the password, here are the step by step to revocer the ILOM password.

First of all, try to change the password with ipmitool, but if its still doesn’t work, try below step:

– You must be physically present at the server to perform this procedure.
– This procedure uses the default user account to enable you to recover a lost password or to re-create the root user account.
– You cannot change or delete the default user account.

1. Connect to ILOM via serial console and log in using the default user account.
SUNSP-xxxxxxxx login: default
Press and release the physical presence button.
Press return when this is completed…

2. Prove physical presence at your server.
Press and release the physical presence button.

The Physical Presence button on the Sun SPARC Enterprise T5xxx servers and X-Series is the Locator button:

But, for Sparc T3/T4 model, the physical presence are on rear side, except for T3-1b/T4-1b:
SPARC T3-1/T4-1: (rear) pin-hole to the left of the USB ports
SPARC T3-2/T4-2: (rear) pin-hole to the left of NET0
SPARC T3-4/T4-4: (rear) to the right of OK LED, above the USB port
SPARC T3-1b/T4-1b: (front) Locate button/Physical Presence (White LED)

3. Return to your serial console and press Enter.

You will be prompted for a password.

4. Type the password for the default user account: defaultpassword

5. Reset the account password or re-create the root account.

-> set /SP/users/root password
Enter new password: ********
Enter new password again: ********

6. Type “exit” to leave default login
7. try login with your new root password


Update for The “Physical Presence” button locations by server:

Physical Presence for SPARC T4-1 : rear, pin/hole between net3 and usb0 (red circle)


– T7-x, S7-x and all platforms forward should use the Locator button (front/rear) as the Physical Presence switch
– To perform some procedures documented in the Oracle ILOM core documentation, you must create a serial connection to the server and activate the Physical Presence switch on the server. For information about creating a serial connection, refer to the installation guide for the server.
– If the physical presence/locator button is not working and/or can not be located, then as temporary workaround the physical presence check can be disabled:
– -> show /SP check_physical_presence
– -> set /SP check_physical_presence=false
– -> show /SP check_physical_presence
and it can be later enabled
– -> show /SP check_physical_presence
– -> set /SP check_physical_presence=true
– -> show /SP check_physical_presence
– For more information look at the documents below:
– T Series Server Documentation
– Oracle Integrated Lights Out Manager (ILOM) 3.x Documentation

If you have MOS access, read more on doc : 1509660.1

Oracle Support Document 1509660.1 (How to locate the “Physical Presence” button on SPARC T3-x, T4-x, T5-x, T7-x, S7-x Servers)