Oracle ZFS Storage Appliance: Snap Management Utility (SMU) for Oracle Database

Asset ID:	1-72-2086075.1
Update Date:	2017-10-05
Keywords:

Solution Type Problem Resolution Sure

Solution 2086075.1 : Oracle ZFS Storage Appliance: Snap Management Utility (SMU) for Oracle Database - BUI Unresponsive after Login

Applies to:

Oracle ZFS Storage ZS3-2 - Version All Versions and later
Oracle ZFS Storage ZS3-4 - Version All Versions and later
Oracle ZFS Storage ZS3-BA - Version All Versions and later
Oracle ZFS Storage ZS4-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS4-4 - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

Reported in SMU 1.2.0.27

The Oracle Snap Management Utility for Oracle Database (SMU) BUI hangs after login while displaying the administration interface.

No spinning cursor. Clicking has no effect.

The SMU command line utility works fine.

When launching the BUI, the following errors are logged in smu.log:

WARNING: ADF_FACES-60098:Faces lifecycle receives unhandled exceptions in phase RENDER_RESPONSE 6
org.apache.jasper.el.JspELException: /components/smuWorkgroupApps.jspx(534,115) '#{appRegieHandler.appsData}' Error reading 'appsData' on type com.oracle.smu.bui.config.ApplicationRegieHandler
..
Caused by: java.lang.NumberFormatException: For input string: ""
..
  at com.oracle.smu.bui.config.ApplicationData.(ApplicationData.java:51)
  at com.oracle.smu.bui.config.ApplicationRegieHandler.createCloneList(ApplicationRegieHandler.java:177)
  at com.oracle.smu.bui.config.ApplicationRegieHandler.fetchAppsData(ApplicationRegieHandler.java:140)
  at com.oracle.smu.bui.config.ApplicationRegieHandler.getAppsData(ApplicationRegieHandler.java:104)
..

Changes

Application accounts were added or modified.

Cause

One or more application accounts has an empty "port" setting causing the BUI to hang while fetching the configuration.

This can be confirmed in the CLI output below:

smu> accounts get all
..
ORADB-C1    name    ORADB-C1
ORADB-C1      type APPLICATION
ORADB-C1      protocol ORACLE_DATABASE
..
ORADB-C1      port <===   port not set
..

ORADB-B2    name    ORADB-B2
ORADB-B2      type APPLICATION
ORADB-B2      protocol ORACLE_DATABASE
..
ORADB-B2      port <===   port not set
..

Default port 1521 should have been automatically set where no port number was entered, but the field was left empty due to a known bug.

Solution

Use the CLI to provide a port value for application accounts where this field is empty:

smu> accounts modify -o port=<listener_port> ORADB-C1

smu> accounts modify -o port=<listener_port> ORADB-B2

where <listener_port> is the port number of the SQL*Net listener for each database instance.

The fix is planned for SMU 1.3.0.

References

<BUG:22293255> - SMU BUI UNRESPONSIVE
<NOTE:1522925.1> - Snap Management Utility for the Oracle Database - Information and Troubleshooting

Attachments

This solution has no attachment