FIX: The Distribution Agent may not apply transactions when you use transactional replication with a published Oracle table and the table contains a column that uses the number data type in SQL Server 2005

This article describes the following about this hotfix release:

• The issues that are fixed by this hotfix package
• The prerequisites for installing the hotfix package
• Information about whether you must restart the computer after you install the hotfix package
• Information about whether you must make any registry changes
• The files that are contained in the hotfix package

When you use transactional replication with a published Oracle table in SQL Server 2005, the Distribution Agent may not apply the transactions. When this problem occurs, you receive the following error message:This problem occurs if the following conditions are true:

• The published Oracle table contains a column that uses the number data type.
• The column that uses the number data type defines the same precision and scale values for the number data type.
• A value of zero is inserted into the column that uses the number data type.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have SQL Server 2005 Service Pack 1 (SP1) installed to apply this hotfix. For more information about how to obtain SQL Server 2005 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:

Restart information

You must restart the computer after you apply this hotfix.

Registry information

You do not have to change the registry.

Hotfix installation information

After you apply this hotfix, you must update the SQL Server version number that is maintained at the Oracle publisher. For more information about how to update the SQL Server version number that is maintained at the Oracle publisher, click the following article number to view the article in the Microsoft Knowledge Base:

File information

This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

32-bit hotfix

64-bit hotfix

64-bit hotfix for Itanium processors

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

After you apply this hotfix, you may experience an issue that is described in Microsoft Knowledge Base article 922767. In this case, you have to use the methods in the "Workaround" section in Microsoft Knowledge Base article 922767 to work around this issue.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.