Installation and Upgrade Considerations
Windows Installations and Oracle 11g Patch
If this is the first time you are installing Hitachi Storage Viewer on a Windows server, you will need to apply the mandatory Oracle 11g patch (Windows OS only). In certain circumstances, when files are in use, this patch upgrade will fail. For steps to work around this issue, see
Report Differences 8.4.x to 9.x.
Resolving Issues with the Oracle 11g Patch
If your Hitachi Storage Viewer Oracle 11g database is on a Windows server, you must apply Oracle Patch 13 (13247523) AFTER you install BOTH the Oracle 11g binaries and the Hitachi Storage Viewer Portal software. This is a mandatory patch. This Oracle 11g patch fixes a connection time-out issue that resulted in “Report Fails to Load” errors. See the Patch Download page on the Customer Portal for instructions.
While applying the mandatory Oracle 11g patch for Windows, the process may fail because some files are in use. A message similar to the following will indicate which files are in use.
Sample Error Message During Oracle 11g Windows Patch Process
[exec] Oracle Home : c:\opt\oracle
[exec] Central Inventory : C:\opt\oracle\oraInventory
[exec] OPatch version : 11.2.0.1.6
[exec] OUI version : 11.2.0.2.0
[exec] Log file location : c:\opt\oracle\cfgtoollogs\opatch\opatch2012-03-20_13-51-50PM.log
[exec]
[exec] Applying interim patch '13247523' to OH 'c:\opt\oracle'
[exec] Verifying environment and performing prerequisite checks...
[exec] Prerequisite check "CheckActiveFilesAndExecutables" failed.
[exec] The details are:
[exec]
[exec] Following files are active :
[exec] c:\opt\oracle\bin\oci.dll
[exec] Log file location: c:\opt\oracle\cfgtoollogs\opatch\opatch2012-03-20_13-51-50PM.log
[exec]
[exec] Recommended actions: OPatch needs to modify files which are being used by some processes.
Procedure to Resolve the Patch Issue
If the patch fails with a message similar to the above sample error message, follow these steps.
NOTE: These steps refer to the Sample Error Message above, but you will need to substitute the file names and services specific to your error message.
1. Open a command prompt window.
2. Run the following tasklist command to list the processes that are using the file mentioned in the error message. In our example, the file is: c:\opt\oracle\bin\oci.dll. Use the file name that is referenced in your error message.
Example Command: tasklist /m oci.dll
Note that using the full path (for example, c:\opt\oracle\bin\oci.dll) in the tasklist command will not work.
Command Output:
Image Name PID Modules
========================= ======== ========
oracle.exe 2744 oci.dll
TNSLSNR.EXE 2784 oci.dll
oravssw.exe 3064 oci.dll
3. Use the following command to identify the process associated with the Image Names from the tasklist command output.
tasklist /svc
Command Output:
Image Name PID Services
========================= ======== =======================
oracle.exe 2744 OracleServicescdb
oravssw.exe 3064 OracleVssWriterscdb
TNSLSNR.EXE 2784 OraclescdbTNSListener
4. Check if the services related to the Image Names can be stopped until the patch is applied.
5. If the services can be stopped, use the Windows Services Panel to stop the services associated with the Image Names.
6. cd c:\opt\oracle\Patches\112020_P3\13247523
7. Apply the patch using the following command:
C:\opt\oracle\Patches\12714463> C:\opt\oracle\OPatch\opatch apply -silent -ocmrf c:\opt\oracle\ocm.rsp
This step will take about 5-6 minutes to complete.
8. Load the modified .sql files into the existing database use the following commands:
> cd %ORACLE_HOME%\Bundle\Patch13
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> STARTUP
SQL> @catcpu.sql
SQL> exit
9. To ensure that all dependent objects are valid after running catcpu.sql, execute the following:
> cd %ORACLE_HOME%\rdbms\admin
> sqlplus /nolog
SQL> CONNECT / AS SYSDBA
SQL> @utlrp.sql
10. If the above script indicates any invalid objects, execute validate_sp.sql:
>cd c:\opt\oracle\database\tools
>sqlplus portal/portal
SQL> @validate_sp
11. As a final step, go to the Windows Services Panel and re-start all the processes that you stopped in step 5.
Activating New Features and Reports
When new features and reports are introduced with a new product release, after you’ve upgraded you’ll need to modify Administrative settings in the Portal to give your users access to these features.
• To enable reports that have been introduced in a new software release, see “Assigning User Privileges” in the Hitachi Storage Viewer User’s Guide.
• For this particular task, it is advantageous to configure User Groups so that you can make changes that apply to all members of the group. See the Hitachi Storage Viewer User’s Guide for details.
Performance Profiles and Transmitted Data
Performance profiles are securely transmitted (over https) as anonymous and aggregated with other customers’ profile data in Profile Central—the community pool hosted at APTARE, Inc., which is then imported into a customer’s profile for reporting purposes. This import/export task occurs in a single, daily scheduled Portal process. Using the aggregated community profiles, companies can better gauge if the metrics collected in their environments are within a normal performance range. Profile data cannot be associated with any contributor. No company or environment-specific details, such as storage array or server names, are transmitted. No personally identifiable information is collected, used, or disclosed.
Note: To enable participation in Community Performance Profiling Cloud Policies, an authorized representative of your company must opt-in. Profile data cannot be associated with any contributor. No company or environment-specific details, such as storage array or server names, are transmitted. No personally identifiable information is collected, used, or disclosed. Note that you can opt-out at any time.
Report Differences 8.4.x to 9.x
When upgrading from a previous 8.4.x version of Storage Viewer, existing reports are automatically ported to a new folder structure. During the upgrade process, the system recognizes your saved reports, and creates the appropriate folder structure under My Reports.
In previous versions of Hitachi Storage Viewer, reports were saved in a hierarchical structure under their parent template. Starting with Storage Viewer 9, saved reports are now located within the My Reports user folder on the Explorer tab with a link to the parent template. You can quickly recognize your uploaded report folders by their naming convention. Each folder is identified by the prefix up, an abbreviation of the product folder name, and the sub-folder name. These new folders are in a flat structure, so everything is on the same level.
For example, a Storage Viewer for Backup, Media Management report is located in the upBac_Media Management Reports folder. Note that if a report does not exist in a folder of your current Hitachi Storage Viewer version, a new folder is not created in the Storage Viewer 9 version.