FIX: Error message "ORA-01722: invalid number" when you replicate a table to an Oracle server subscriber in SQL Server 2008 or in SQL Server 2008 R2 if a varchar (max) column of the table contains a long value record

Article translations Article translations
Article ID: 2525165 - View products that this article applies to.
Expand all | Collapse all

On This Page

Microsoft distributes Microsoft SQL Server 2008 Service Pack 2 (SP2) or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 2 (SP2) or SQL Server 2008 R2 fix release.

SYMPTOMS

Consider the following scenario:
  • You create a table that has a varchar (max) data type column in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2.
  • You try to replicate the table to an Oracle server subscriber, and you select Transactional publication as the publication type.

    Note The initial synchronization is successful.
  • You insert or update a long value record in the varchar (max) column of the table.

    For example, the value is more than 8200 characters long.

In this scenario, the Distribution Agent does not synchronize the new record to the Oracle server subscriber. Additionally, you receive the following error message:
Replication-Replication Distibution Subsystem: agent <agent name> failed. ORA-01722: invalid numberErrorId = 160, SourceTypeId = 16
ErrorCode = '1722'
ErrorText = 'ORA-01722: invalid number'

RESOLUTION

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 9. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2567713 Cumulative Update package 9 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2567714 Cumulative Update package 2 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
2527180 Cumulative update package 4 for SQL Server 2008 SP2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 SP2 was released

STATUS

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

MORE INFORMATION

For more information about Oracle publishing, visit the following MSDN website:
General information about Oracle publishing
For more information about Oracle subscribers, visit the following MSDN website:

General information about Oracle subscribers
For more information about snapshot replication, visit the following MSDN website:
General information about snapshot replication

Properties

Article ID: 2525165 - Last Review: August 15, 2011 - Revision: 2.0
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Web
  • Microsoft SQL Server 2008 Workgroup
  • Microsoft SQL Server 2008 Service Pack 2
  • Microsoft SQL Server 2008 Standard
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Web
  • Microsoft SQL Server 2008 R2 Workgroup
Keywords: 
kbqfe kbhotfixserver kbfix kbexpertiseadvanced kbsurveynew KB2525165

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com