Upgrading to APTARE Version 10.2.00
  
Version 10.2.00P7
Upgrading to APTARE Version 10.2.00
Before You Upgrade
Resolve Issues with Oracle Patches on Windows Servers
Activate New Features and Reports
Performance Profiles and Transmitted Data
Enhancements and Resolved Issues by Category
Before You Upgrade
If you are upgrading to 10.2.00 from a version prior to 10.1.01 P5, in some situations, primarily on Windows Portals, the automatic Data Collector upgrades may not complete. Data Collectors will attempt to automatically upgrade to JRE 8. If this fails, there are two options you can select from to resolve this issue:
Uninstall the pre-10.1.01 P5 data collector and reinstall by manually running the 10.2.00 Data Collector installer
OR
Refer to the section Troubleshooting - Manual Data Collector Upgrades in the Technical Documentation available here: https://aptare.com/online_documentation_TOC/ for additional information. This covers the manual intervention required to complete a failed Data Collector upgrade.
Identify the Java Version on the Data Collector Server and ensure that a 64-bit server is used for the Data Collector Server.
Ensure that the aptare.jar is upgraded successfully.
APTARE Version 10.x.xx introduced several enhancements to attribute management, including a new attribute type, a multi-object attribute, replaces the way that attributes functioned in previous releases. In addition, because you may already have attributes in your database that have names that duplicate the system names introduced in APTARE Version 10.x.xx, the upgrade process must apply logic to prevent duplicate attribute names. Refer to Attribute Merging and Attribute Management sections in the help prior to upgrading for complete information.
During a Portal upgrade to APTARE Version 10.x.xx, all Dynamic Template Designer Methods will be modified to associate a method with an enterprise object (such as an array or host), rather than the method being associated with a product (such as Capacity Manager). Refer to Upgrade Methods to Incorporate Enterprise Objects in the help for complete information.
Release 10.2.00P5 introduces a new behavior in the upgrader. The product does not ship any database views for the user aptare_ro. During an upgrade, if aptare_ro user is found to have created database views, the upgrade process will stop with a warning message: (28317)
"WARNING. Found conflicting database views. These conflicts will cause the upgrade to fail. A list of database views are in upgrade_pre.log. Contact Support. Upgrade terminated..."
Resolve Issues with Oracle Patches on Windows Servers
APTARE provides patches to third-party products, as needed. While applying the latest Oracle 11g patch on a Windows server, the process may fail when some files are in use. A message similar to the following will indicate which files are in use.
Sample Error Message During the 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 1120 OracleServicescdb
svchost.exe 2432 RemoteRegistry
vmtoolsd.exe 2460 VMTools
TNSLSNR.EXE 2876 OraclescdbTNSListener
dllhost.exe 3304 COMSysApp
msdtc.exe 3480 MSDTC
 
4. Check if the services related to the Image Names can be stopped until the patch is applied.
Do NOT stop any Oracle services (check for service names that include Oracle).
Services names may not be exactly as you expect, as vendors may change names with new releases. You may need to do an internet search to identify the service.
5. If the services can be stopped, use the Windows Services Panel to stop the services associated with the Image Names.
6. Re-apply the patch using the patch upgrade script.
C:\opt\aptare\upgrade\patches\patch.bat
7. As a final step, go to the Windows Services Panel and re-start all the processes that you stopped in step 5.
Activate 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 APTARE StorageConsole 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 APTARE StorageConsole 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.