Product Support Notice

Transcription

1 PSN # PSN004170u Product Support Notice 2014 Avaya Inc. All Rights Reserved. Original publication date: 07-May-14. This is Issue #01, published date: 07-May-14. Severity/risk level Medium Urgency When convenient Name of problem Avaya IQ Servers Require Updates to Support Oracle Upgrade Products affected Avaya IQ: Releases 5.1.x and 5.2.x Software Only Problem description For Avaya IQ Software Only customers who plan to upgrade their Oracle database server and client version, this document provides the Avaya IQ update procedure to implement during such an upgrade. The PSN resolution must be implemented when: - Oracle major or maintenance release number changes. For example, is upgraded to x. The supported Oracle versions are identified in the Avaya IQ 5.2 Product Version Interoperability document, Third-party Products section (available at: support.avaya.com). This document provides the Avaya IQ update procedure to implement when Oracle upgrade is planned on Software Only configuration. Resolution The following sections provide the procedure for sequencing the Oracle database server upgrade, Oracle Client upgrade, and the Avaya IQ Update procedure for updating IQ servers to align with the Oracle upgrades. Before Upgrading the Oracle database server Shutdown Avaya IQ on each IQ server, enter: Upgrade Oracle database server Implement Oracle database server upgrade. After Upgrading the Oracle database server Oracle Client Will Not Be Upgraded If an Oracle Client Upgrade is NOT planned, Avaya IQ updates are not required. Execute the following: o Startup Avaya IQ on each IQ server, enter: o Verify IQ operations. The steps in Update Procedure step 6 (Verification steps) and step 8 (Verify IQ operations) can be used for this verification. Verify the sqlplus steps on each Avaya IQ server with Oracle Client installed. The following IQ servers have Oracle Clients installed: All Functions Host on Dual Host or All In One configurations; Administration Host and Reporting Host(s) on Multi-Host configurations. Oracle Client Will Be Upgraded The following IQ server(s) have Oracle Clients installed: 1. All Functions Host on Dual Host or All In One configurations; 2. Administration Host and Reporting Host(s) on Multi-Host configurations. Note: For Multi-Host configurations, implement the IQ update procedure on Administration Host, then Reporting Host(s). Install the Oracle x Client on each Avaya IQ server(s). Install in separate Oracle home directory (i.e., /u01/app/oracle/product/11.2.0/db_1). Do not remove existing Oracle Client until IQ Update procedure and verification is complete. Note the following requirements: o The Oracle 32-bit client is required for Avaya IQ. You must install the Oracle x 32-bit Client Avaya Inc. All Rights Reserved. Page 1

2 o The Oracle x 64-bit Client cannot be used for Avaya IQ interfaces. For additional information, see the following document: Oracle Database Client Installation Guide 11g Release 2 (11.2) for Linux: Separate 32- Bit Client Software for 64-Bit Platforms. If you require the Oracle 64-bit client for other purposes, it can be installed in a separate ORACLE_HOME location. Important: The ORACLE_HOME for the x Client is the <new Oracle home path> in Avaya IQ Update Procedure. Avaya IQ Update Procedure The Avaya IQ server(s) that have an Oracle client installed and require update are: 1. All Functions Host on Dual Host or All In One configurations; 2. Administration Host and Reporting Host(s) on Multi-Host configurations. Implement update procedure on Administration Host, then Reporting Host(s). Terminology The following terms are used: Term <old Oracle home path> <new Oracle home path> <UserID> <password> Definition Original client path for $ORACLE_HOME i.e., /u01/app/oracle/product/11.1.0/db_1 Upgraded client path for $ORACLE_HOME i.e., /u01/app/oracle/product/11.2.0/db_1. Actual User ID for the profile which needs to be updated Actual password for database user Implement the following procedure steps on each applicable IQ server(s) after Oracle client upgrade. 1. Log on as root to the Avaya IQ server. 2. Shutdown Avaya IQ, enter: 3. Backup Avaya IQ Oracle configuration files, enter: mkdir ora_client_backup_<date> (e.g., ora_client_backup_ ) cd ora_client_backup_<date> cp -p /opt/avaya/ccr/current.conf. cp -p /opt/avaya/ccr/util/cat/connection.out. cp -p /root/.bash_profile root_bash_profile cp -p /home/oracle/.bash_profile oracle_bash_profile 4. Execute the following for each User ID accessing Oracle client replacing <UserID> with the actual User ID cp -p /home/<userid>/.bash_profile <UserID>_bash_profile 5. Update files with ORACLE_HOME references a. Update Oracle tnsnames configuration file (tnsnames.ora), enter: cp -p <old Oracle home /tnsnames.ora <new Oracle home b. If the new Oracle client was not installed with Oracle Universal Installer or the network configured with Oracle Net Configuration Assistant or Oracle Enterprise Manager, create the configuration files, by entering: cp p <old Oracle home /listener.ora <new Oracle home cp p <old Oracle home /sqlnet.ora <new Oracle home c. Replace <old Oracle home path> references with <new Oracle home path> references in IQ files. The following files require update: /opt/avaya/ccr/current.conf JDBCDriver=<new Oracle home path>/jdbc/lib/ojdbc5.jar /opt/avaya/ccr/util/cat/connection.out 2014 Avaya Inc. All Rights Reserved. Page 2

3 JDBCDRIVER=<new Oracle home path>/jdbc/lib/ojdbc5.jar /root/.bash_profile ORACLE_HOME=<new Oracle home path> /home/oracle/.bash_profile ORACLE_HOME=<new Oracle home path> /home/userid/.bash_profile For each user requiring Oracle access, edit.bash_profile for each user. ORACLE_HOME=<new Oracle home path> 6. Verification steps: verify the following. root Oracle client access (if RPT_HIST_OWNER_USR is not historical database user, replace with actual historical database user. Replace <password> with actual the password. Replace avayaiq with actual connection alias.). oracle user Oracle client access (if RPT_HIST_OWNER_USR is not historical database user, replace with actual historical database user. Replace <password> with actual the password. Replace avayaiq with actual connection alias. ) su - oracle exit; If other users have Oracle access, for each user: verify Oracle client access (if RPT_HIST_OWNER_USR is not historical database user, replace with actual historical database user. Replace <password> with actual the password. Replace avayaiq with actual connection alias.). su - UserID exit; If there is an issue with one of the above steps, verify listener.ora and tnsnames.ora updates. 7. Startup Avaya IQ, enter: 8. After all IQ servers have been updated, Verify IQ operations. Verify OAM access and OAM navigation. Verify Real-time and historical report execution via Report Client. If Multi-Host configuration, verify Report Client from each Reporting Host. Verify RTD report usage via ApcUI. If an IQ operational issue exists after the above updates have been performed, carefully verify each Update Procedure step has been properly implemented. If an error or omission is identified, implement the following step: s. 1. Shutdown Avaya IQ, enter: 2. Implement the update correction. 3. Execute Update Procedure step 6 (Verification steps); 4. Startup Avaya IQ, enter: 2014 Avaya Inc. All Rights Reserved. Page 3

4 5. Execute Update Procedure step 8 (Verify IQ operations). If the above approach does not correct IQ operational issues, the IQ updates can be backed out to restore IQ operations. To do this, execute Backout Procedure. NOTE: the original Oracle client can interface with an upgraded Oracle database server. Backout Procedure Implement the following procedure steps on each applicable IQ host to backout IQ updates. 1. Log on as root to the Avaya IQ server. 2. Shutdown Avaya IQ, enter: 3. Restore Avaya IQ Oracle configuration files, enter: cd /root/ora_client_backup_<date> (backup directory e.g., ora_client_backup_ ) cp -p current.conf /opt/avaya/ccr/current.conf cp -p connection.out /opt/avaya/ccr/util/cat/connection.out cp -p root_bash_profile /root/.bash_profile cp -p oracle_bash_profile /home/oracle/.bash_profile Execute the following for each User ID accessing Oracle client replacing <UserID> with the actual User ID cp -p <UserID>_bash_profile /home/<userid>/.bash_profile 4. Execute Update Procedure step 6 (Verification steps); 5. Startup Avaya IQ, enter: 6. Execute Update Procedure step 8 (Verify IQ operations). Workaround or alternative remediation Remarks Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch Download Patch install instructions Verification Failure Patch uninstall instructions Service-interrupting? No Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks 2014 Avaya Inc. All Rights Reserved. Page 4

5 Avaya Security Vulnerability Classification Not Susceptible Mitigation If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use. Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED AS IS. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS AVAYA ), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners Avaya Inc. All Rights Reserved. Page 5