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

The 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 Indepth for SQL Server:

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 is installed on your system, go to AdminPoint>Patches and verify that the IN_INFP_751_007 patch is installed on your Symantec i³ FocalPoint server.

In cases where an installation of Symantec i3 does not yet include the installation of the Indepth for SQL Server product framework (FocalPoint), it is highly recommended to install this patch before the installation of the product. Doing so will ensure that Indepth for SQL Server framework and Collector agents work with the latest patch update.

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.

This patch is a cumulative patch for Indepth for SQL Server and contains all enhancements and problem fixes that were previously released in bundle patch BU_SQ_751_003 (  http://support.veritas.com/docs/290465 ), therefore making that bundle patch obsolete.

• Incident 1003160: GUI shows tables that belong to a different database due to applying incorrect mapping.

• Incident 1030015: An Availability file corruption occurs.

• Incident 1035904: A Current workspace error of stack overflows in high-activity environments. (Due to an pssq_pv stack overflow in the output tree creation).

• Incident 1017584: pssq_tuner.exe crashes if the amount of SQL text equals the maximum of 200KB.

• Incident 1017585: A division by zero occurs in the Statistics workspace when there is a connection problem.

• Incident 1017586: When associating to Statements in the Activity workspace, the user interface is hanging or an error is displayed due to a time out.

• Incident 1010778: The Pssq_truner crashes, which can happen when:

- stmtIdInBatch is negative.

- parsing the argument with no parenthesis.

- there is an access violation. This is caused by the number of closing parenthesis in the same clause that exceeds 50.

• Incident 813535 (PR #5927): The Load process fails with an access violation when the amount of text reaches 200KB.

• Incident 1035903: Errors in Explain statements process:

- The error message "Invalid length parameter passed to the SUBSTRING function message" is received when associating to the Locked Objects entity in the Activity workspace.

- The Collect Schema Changes process shows the following error in the log file (pw_schema_changes_load.log):

SQL error while Preparing SQL statement. Message text from [Microsoft][ODBCSQL Server Driver][SQL Server]Implicit conversion of varchar value to varchar cannot be performed because the collation of the value is unresolved due to a collation conflict. SQLCODE=457

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

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

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