Oracle ZFS Storage Appliance: Snap Management Utility (SMU) Uses Wrong Oracle Home After Database Upgrade

Asset ID:	1-72-2324472.1
Update Date:	2017-11-17
Keywords:

Solution Type Problem Resolution Sure

Solution 2324472.1 : Oracle ZFS Storage Appliance: Snap Management Utility (SMU) Uses Wrong Oracle Home After Database Upgrade

Applies to:

Sun Storage 7110 Unified Storage System - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS5-4 - Version All Versions and later
Oracle ZFS Storage Appliance Racked System ZS5-2 - 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

After upgrading an Oracle database, ORACLE_HOME changed from dbhome_3 to dbhome_4. This caused SMU to fail to create backups with the following error:

Task[2417]:backup db01 as D20171031_0606_db01
Request
Application: db01
Type: Oracle Database
Database Name: db01
Data Host: node1
Storage: zfs01
Backup: D20171031_0606_db01
Type: OFFLINE
Actions
Validate the backup request
Lookup backup record: OK
Connect to the application: OK

Validate database requirements
ERROR: node1: /bin/env ORACLE_SID=db01 ORACLE_HOME=/u01/app/oracle/product/11.2.0.4/dbhome_3 ORACLE_BASE=/u01/app/oracle /u01/app/oracle/product/11.2.0.4/dbhome_3/bin/sqlplus -S -L / as sysdba<<'EOF'
whenever oserror exit 1;
clear columns;
set echo off timing off newp 0 spa 0 pages 0 feed off head off trims on tab off wrap off linesize 4096 numf "" numw 15;
select name || '=' || value from v$parameter where value is not null;
exit sql.sqlcode;
EOF: select name || '=' || value from v$parameter where value is not null
*
ERROR at line 1:
ORA-01034: ORACLE not available
Process ID: 0
Session ID: 0 Serial number: 0

Undo backup
Disconnect from the application: OK
Result

State: FAILED

Changes

Problem can occur if you have Oracle Databases that were backed up previously with Snap Management Unit and upgrade the Database and the ORACLE_HOME directory changes.

Cause

Once a database clone is created, its associated share, storage, database and host information are contained in xml file form in its clone profile, located in the $SMU_WORKING_DIR/store directory.

This clone profile is used to deprovision the clone database whenever the database instance is unavailable.

If the clone profile is missing or corrupted, or if the clone database information has changed, the SMU command utility reprofile can be used to recreate the latest information for the clone profile in the SMU database.

The xml file may still contain the old oraHome directory and need to be reprofiled.

cd /var/opt/ORCLsmu/store

grep oraHome db01.xml

<oraHome>/export/home/oracle/app/oracle/product/11.2.0.4/dbhome_3</oraHome>

Solution

Solution for Linux:

On the SMU host,

1. /sbin/service smud stop
2. Edit the xml files in /var/opt/oracle/smu/store and correct the oraHome path
3. /opt/Orclsmu/bin/reprofile
4. /sbin/service smud start

Solution for Solaris:

On the SMU host,

1. svcadm disable svc:/application/management/smu:default
2. Edit the xml files in /var/opt/oracle/smu/store and correct the oraHome path
3. /opt/Orclsmu/bin/reprofile
4. svcadm enable svc:/application/management/smu:default

Solution for Windows:

On the SMU host,

1. C:\> sc stop "Oracle SMU Service"
2. Edit the xml files in $SMU_WORKING_DIR\store
3. reprofile.bat
4. C:\> sc start "Oracle SMU Service"

Attachments

This solution has no attachment