Symantec Indepth (tm) for Oracle 7.5.1 - Bundle Patch BU_OR_751

Document ID: 292410
http://support.veritas.com/docs/292410

E-Mail this document to a colleague

Symantec Indepth (tm) for Oracle 7.5.1 - Bundle Patch BU_OR_751_015

Details:

This bundle patch is the Symantec Indepth for Oracle version 7.5.1 Maintenance and Platform Support Pack, September 2007 release. It contains the following patches:

UI_GUIFP_751_001
OR_ORFP_751_013
OR_ORCOL_751_014
OR_INFP_751_015_STAGING

This bundle patch adds the following enhancements:

Support for:
Oracle 10.2.0.2 on Alpha TRU-64
Solaris 10 on AMD64
HP-UX 11iv3 on PA RISC
RHEL 5 on AMD64
Oracle 10.2.0.3 on HP ia64

More enhancements and all fixed issues have been described in the bundle patch release information document included in the downloaded bundle patch ZIP file.

For the latest information on platform and products support, refer to the Symantec i³ version 7.5.1 Support Matrix ( http://support.veritas.com/docs/283453 ).

The following issues are fixed in the Indepth for Oracle Collector agent:

Incident 1044214 - Two stored procedures with the same object ID from two different databases are correlated to the same text.
Incident 1059114 - In double byte environments, long textual values cause failures during the load to the Performance Warehouse and faulty truncations of the values.
Incident 1002658 - Module and Action appears as N/A in Oracle 10.2.0.2 on AIX due to a faulty sampling of the SGA.
Incident 1030971 - When the Collector agent is stopped, pressing Verify in AdminPoint can restart it.
Incident 1052261 - When the Storage Extension is installed, associating with Storage Devices in the Activity workspace shows "Unknown" in the Device Type columns, instead of the storage array type.
Incident 1060496 - Indepth for Oracle agents do not start when multiple Oracle instances are installed on the same Solaris AMD host due to faulty NLS files.
Incident 1086152 - The Statement Execution counter is lower than it should be when the shared pool is flushed.
Incident 1090921 - Ability to track SQL texts sampling faults is without debug information.
Incident 1014932 - Veritas Point Storage Extension fails for raw devices. As a result all devices are shown as N/A.
Incident 1092809 - The cumulative value of "In Oracle Time" for statements that are less than a second is incorrect.
Incident 1086160 - A bug in the blocking mechanism may cause Interpoint for SAP to exhaust all SAP working processes.

The following issues are fixed in the Indepth for Oracle FocalPoint:

Incident 1054098 - Recommend crashes when a functional index is defined.
Incident 1060844 - The parser crashes during the format of a statement with TABLE and two level sub-queries.

Requirements

Before applying this patch, you must apply the IN_INFP_751_007 ( http://support.veritas.com/docs/290432 ) patch. If you have not yet applied the IN_INFP_751_007 patch, abort the current installation, apply the IN_INFP_751_007 patch and then re-apply this patch. To check whether the IN_INFP_751_007 patch has been installed on your system, go to AdminPoint>Patches and verify that the IN_INFP_751_007 patch has been installed on your Symantec i³ FocalPoint server.

Installation directive

When you apply the version 7.5.1 bundle patch BU_I3_750_001 on a server, any relevant version 7.5.1 MP bundle patch or patch (for example BU_OR_751_015) that was previously applied to that server should be re-applied to that server after you complete the version 7.5.1 bundle patch installation.

See Also: Installing new components after applying Symantec i3 v7.5.1 ( http://support.veritas.com/docs/284321 )

The following is an example scenario:

1. You have installed a Symantec i³ version 7.5.0 server with a .NET Collector agent.

2. You have applied the version 7.5.1 bundle patch BU_I3_750_001 to the server. The server version is now version 7.5.1.

3. You have installed the Indepth for Microsoft .NET version 7.5.1 MP bundle Patch BU_DN_751_003. The server version that is shown is still version 7.5.1.

4. Let us assume that the MP2 bundle patch has not been installed on Indepth for Oracle. You install the Indepth for Oracle FocalPoint on the server. Because the MP2 bundle patch for this product has not been applied, it does not fall under the staging process, the server version is now version 7.5.0.

5. You now need to re-apply version 7.5.1 bundle patch BU_I3_750_001. After applying the version 7.5.1 bundle patch, the server version is version 7.5.1.

6. At this stage you must reapply the Indepth for Microsoft .NET bundle patch BU_DN_751_003 to bring your server to the same state as it was before you applied the version 7.5.1 bundle patch BU_I3_750_001 in the previous step.

Note: It is also recommended to install the latest Indepth for Oracle bundle patch currently BU_OR_751_015.

Obsolete

The bundle patch contains all enhancements and fixed issues of the following bundle patches (making them obsolete):

BU_OR_751_012 ( http://support.veritas.com/docs/290435 )
BU_OR_751_006 ( http://support.veritas.com/docs/286710 )

Bundle patch BU_OR_751_012 contains the following enhancements:

Support for Indepth for Oracle to monitor:
Oracle version 10.2.0.3.
Oracle version 9.2.0.7 on a Linux AMD 64-bits platform.
Oracle version 10.2.0.2 on a Linux Itanium platform.

Bundle patch BU_OR_751_006 contains the following enhancements:

Support for:
Oracle version 9.2.0.8 on multiple platforms.
Oracle version 10.1.0.5 on HP Itanium.
Oracle version 10.2.0.2 on Solaris 10 x86-64.
Daylight Saving Time.

Bundle patch BU_OR_751_012 fixes the following issues in the Oracle Collector:

Incident 859713 - For Oracle version 10.2.0.2 on SunOS SPARC 64-bits and HP-UX PA-RISC and IA 64-bits: The Objects association does not show any associated object name in the Activity workspace.
Incidents 898603, 963264 - For Oracle version 10.2.0.2 on AIX 64-bits: The Objects association does not show any associated object name in the Activity workspace. The debug file (oracle.collector.dbg) is getting filled with a lot of messages although no debug flag is set.
Incident 923267 - For Oracle version 10.1.0.4 on HP-UX PA-RISC and IA 64-bits: The Objects association does not show any associated object name in the Activity workspace.
Incident 963403: In the monitored instance pss_pcs process, CPU consumption rises significantly after upgrading to Symantec i³version 7.5.1. Investigation shows that this happens in instances in which new objects are created at an extreme rapid pace.
Incident 972248: The interface of the ESS utility with the Storage Extension for IBM on an AIX server fails.
Incident 965472: When installing a Storage Extension, all data of the Oracle instance is not delivered to the Performance Warehouse. This is due to the creation of huge OREX "prepared" files.
Incident 892472: Interpoint for Oracle Applications causes the system performance to go down due to fragmentation of the shared pool.
Incident 932718: When the Oracle database is working on a Sun Solaris that uses the ISM (Intimate Shared Memory) option, the Indepth for Oracle Collector agent will fail to start because it cannot attach the SGA.
Incident 929565: Multiple error messages in the oracle.collector.trc file: "createObjectRowCache: invalid SGA address for Objects Chain: Start=0 Last=XXXXXXX".
Incident 849594: Change the statements counters Execution, Rows_Processed and Buffer_Gets sample methods to be more accurate.
Incident 1025857: In Oracle 10.2.0.2 on Windows platforms, long text statements are cut off.
Incident 1048706: Explain of a statement fails on the SQL workspace, due to incorrect sampling of the parsing user on a monitored Oracle 9.2.0.8 instance.

Bundle patch BU_OR_751_006 fixes the following issues in the Oracle Collector

Incident 3496 (811720) There is no data in the Activity workspace, or there are many data.N files on the monitored server due to a corrupted data or control file.
Incident 3964 (813566) The mapping process fails on the Collector agent's startup, when Storage Extension for EMC is installed on HP-UX. The following error message is shown: Can't open a shared library: /sql_nfs/precise/symapi/V4/hp/shlib/libsymlvm.sl No such file or directory.
Incident 5187 (812883) The Collector agent starts slowly due to a very large amount of objects in the collector's objects file.
Incident 5398 (813001) The Alerts sampled metrics show a CPU usage of more than 100% when Oracle Applications Interpoint is installed.
Incident 5510 (814084) The ESScli mapping process in Storage Extension for IBM fails. The symptoms are:
When associating with IBM Storage Devices there is only one line "N/A".
In the trace file you can find the following error message: CLI failed for UNIX device.
Incident 5577 (813215) The Extended Collections on a Japanese Windows environment fails due to a crash of the trcstart.exe process.
Incident 5653 (813918) In Oracle version 10.2.0.2, sessions involved in a lock are not reported.
Incident 5738 (813436) The Extended Collection fails in UNIX. The following error message is shown:

Cannot schedule extended collection due to crontab problems. Please check that Symantec/i3 Unix user can create crontab.

Incident 5809 (813919) In Oracle version 10.2.0.1 and version 10.2.0.2 running on multiple platforms, the buffer gets are reported with wrong values.
Incident 5817 (813560) In multiple Oracle versions running on multiple platforms, processed rows are reported with wrong values.
Incident 5860 (813565) In Oracle version 10.2.0.1 running on AIX 64-bit, Object Monitoring data is missing.
Incident 5871 (813504) Information is not correlated to SAP (the SAP activity is not recognized) when Interpoint for SAP is installed.
Incident 5905 (813505) When Interpoint for Oracle Applications is installed, most of the data in the Activity workspace is displayed as Non-ERP. This is due to an overflow of Oracles's pipe.
Incident 6012 (813643) In Oracle version 10.2, statistics are reported with wrong values.
Incident 6159 (813933) The Indepth for Oracle agent fails to start in Oracle version 8.1.6.0. The following error message is shown:

Oracle version 8.1.6.0 not supported.

Incident 6294 (813921) In Oracle version 10.2.0.2 running on Sun 64-bit, the Module and Action are reported with wrong values.
Incident 6325 (814087) In Oracle version 10.2.0.2 running on AIX 64-bit, SQL text is partially sampled. The result is that long SQL statements may be shown cut in the user interface.
Incident 6359 (814085) The Storage Extension mapping process fails running on VxVM with a vxinfo file that uses logical device names.
Incident 828081 In Oracle version 10.2.0.2 on Sun 64-bit, MTS wait events are reported with wrong values.

Bundle patch BU_OR_751_012 fixes the following issues in the Oracle FocalPoint:

Incident 1010534: On the Statistics workspaces, N/A is displayed in the Sub-State column of the Wait events.
Incident 1010539: No Oracle forms data is available in Insight.

Bundle patch BU_OR_751_006 fixes the following issue in the Oracle FocalPoint:

Incident 6588 (814182) In large installations where many objects are modified on a daily basis, the weekly SmarTune process may run for many hours, consuming lots of CPU and memory resources and eventually crashes the Indepth for Oracle FocalPoint.

Bundle patch BU_OR_751_012 fixes the following issues in the Oracle Tuner:

Incident 811962: Analyze Changes (SmarTune) process queries are terminated as a result of a Performance Warehouse timeout (the oracle.focal.trc file contains a SEVERE message: "user cancel of current operation").
Incident 970079: The Purge Data process takes a long time due to numerous full table scans of the ps_orsm_schema_changes_log file.
Incident 967053: "Collect Instance Statistics" PREV tables contain old and unnecessary data that need to be deleted.
Incident 846063: Fix problems when running the Explain statement with a non-default Explain user.
Incident 970080: The tuner crashes when Explaining statements refer to user-defined types using synonym.

Bundle patch BU_OR_751_006 fixes the following issues in the Oracle Tuner:

Incident 3909 (811962) In large installations where many objects are modified on a daily basis, the weekly SmarTune process may run for many hours, consuming lots of CPU and memory resources and eventually crashes the Indepth for Oracle FocalPoint.
Incident 4941 (812637) The Near-Capacity tablespace alert (1506) fails. The following error message is shown:

ora-1722 (invalid number)

Incident 5344 (813076) Performance Warehouse process "Collect instance statistics" fails. The following error message is shown:

ORA-12899 value too large for column %s (actual: %s,maximum: %s).

Incident 5736 (813437) The Performance Warehouse process "Collect Schema Changes" runs very slowly due to receiving a wrong hint.
Incident 5748 (813523) The Objects workspace is timing out when associating from Oracle-File to Tables or from Statement to Tables. The following error message is shown:

Cannot communicate with the server.

Incident 5759 (813349) The Alerts metric near capacity tablespace fails when filling the include/exclude fields. The following error message is shown:

ORA-00904.

Incident 5878 (813485) The tuner crashes when it encounters SQL statements with an asterisk in the select and the PARTITION keyword in the from.
Incident 6017 (813632) The Oracle Applications workspace is timing out when clicking Requests. The following error message is shown:

Cannot communicate with the server.

Known Problems

The Indepth for Oracle Collector agent running on RedHat Linux servers gives an "Errors Reported" status in AdminPoint.

Description:
No valid status is returned during the verification of the Indepth for Oracle Collector agent. The issue is caused by the fact that the system 'echo' command is not aliased with 'echo -e' (which is the default out-of-the-box setting in most RedHat versions apart from RedHat 5).

Solution:

1. Stop the Indepth for Oracle Collector agent (the stop will not be indicated in AdminPoint).

2. Log on to the server with the monitored instance/s using the i3 user.

3. Make the following change to the <i3_root>/products/oracle/bin/pss_start.sh file:

Before:

[Line 18] if [ "`uname`" = "Linux" ] ; then

[Line 19] export GETOPT_COMPATIBLE=YES

[20] fi

After:

[Line 18] if [ "`uname`" = "Linux" ] ; then

[New] alias echo="echo -e"

[Line 19] export GETOPT_COMPATIBLE=YES

[20] fi

Known issue during the installation

The installation of a SunOS_x86 server fails when you install the Indepth for Oracle bundle patch without pre-installing the prerequisite infrastructure patch IN_INFP_751_007 ( http://support.veritas.com/docs/290432 ).

Known issue failure details

The following two options are available for the server installation:

Installation using the UNIX Automatic mode
Manual installation (aka installation of UNIX server without a Telnet connection)

When you install the SunOS_x86 server using the UNIX Automatic mode, the installation fails with the following error:

The i3 Listener could not start. In order to perform the installation, use the 'Unix without telnet connection' installation type. Make sure the selected port is free and not used by any other application.

When you install the SunOS_x86 server manually, only the setup.xml file is created. The psin_ba_SunOS_x86 file is not created (this means that there is actually no installation file to run).

Known issue solution

To solve this known issue, install the prerequisite infrastructure patch IN_INFP_751_007 ( http://support.veritas.com/docs/290432 ) and then install the server using the same option as you tried before.

Notes

It is highly recommended to install the patch on all the Symantec i³ servers. If you only want to install it on some of the servers, you must make sure that the first installation of this Bundle Patch includes all servers that contain Symantec i³ FocalPoint agents or any of the other product FocalPoint agents.
The Bundle Patch mechanism will display all Pre- and Post-Patch requirements for all individual patches that are part of the Symantec Indepth for Oracle version 7.5.1 BU_OR_751_015 patch and are relevant to the installed environment. It is highly recommended that you will use View in Browser at this stage, and save the action items to a file for later reference, as some of these action items are dynamically calculated and displayed. The list of these Pre- and Post-action items is also saved in the following log file on the Symantec i³ FocalPoint server:

UNIX:

<i3_root>/logs/infra.bundle.patch.action.items.log

Windows:

<i3_root>\logs\infra.bundle.patch.action.items.log

Do not install the patches in the bundle separately. If you do so, this may lead to unexpected results.
During the installation of this patch, the Oracle Collector agents are automatically stopped and restarted on the patched server(s). However, this is not the case for HP Tru64 UNIX servers or servers that contain a storage extension. On these servers you will need to run the root.sh script and manually restart the Collector agent at the end of the installation.

Installation instructions

1. Download and save the patch self extract file.

2. Run the patch self extract zip file and extract all files that are inside.

3. Open the Symantec i3 AdminPoint.

4. Go to the Patches View.

5. Choose the option Apply Patch.

6. Browse to the location to which you unzipped the patch.

7. Select and install the patch via the patch installation screens.

No pre installation tasks are required

Post installation tasks

After you finish the installation, perform the following steps:

1. Close all browser and Symantec i³ (vtsI3.exe) windows on the machine from which you installed the patch.

2. Open the browser.

3. Open Internet Options and select Delete Files... to clean the browser cache.

Steps 1, 2, and 3 should be performed on all machines in your organization on which you access Symantec i³ version 7.5.1.

Download Now - 153559 K
File Name: BU_OR_751_015_292410.exe
File Type: Patch

Click Below to Browse the FTP files by Product:
ftp.support.veritas.com/pub/support/products

Related Documents:

http://support.veritas.com/docs/278380

http://support.veritas.com/docs/283453

http://support.veritas.com/docs/284321

http://support.veritas.com/docs/286710

http://support.veritas.com/docs/290432

http://support.veritas.com/docs/290435

Products Applied:
Indepth for Oracle 7.5.1

Last Updated: December 20 2007 11:57 AM GMT
Expires on: 12-17-2017

Subscribe to receive critical updates about this document

Subjects:
Indepth for Oracle
General Question: General Question

Languages:
English (US)

Operating Systems:
Windows 2000

Advanced Server SP2, Advanced Server SP3, Advanced Server SP4, Professional SP2, Professional SP3, Professional SP4, Server SP2, Server SP3, Server SP4

AIX

4.3, 4.3.3, 5.1, 5.2, 5.3

TRU64

5.0, 5.1, 5.1B

HP-UX

11.11, 11.20, 11.22, 11i v2 (IA64), 11i v2 (PA-RISC)

Solaris

10 (64-bit), 7.0, 8.0, 9.0 (64-bit)

Linux

RHEL 3.0 (AS, ES, WS), RedHat 7.2, RedHat Enterprise Server 2.1 (AS, ES, WS), Redhat 8.0, Redhat 9.0, SuSe 8.0, SuSe 9.0

Windows XP

5.2, Home 5.1, Home 5.1 SP1, Home 5.1 SP2, Pro 5.1, Pro 5.1 64 bit SP1, Pro 5.1 64 bit SP2, Pro 5.1 64-bit, Pro 5.1 SP1, Pro 5.1 SP2

Windows Server 2003

Enterprise Server, R2, Standard Server

Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com

THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.