FIX: An event may be logged when you use BizTalk Adapter for Oracle Database (919607)



The information in this article applies to:

  • Microsoft BizTalk Adapter for Oracle Database

SYMPTOMS

Consider the following scenario. You use Microsoft BizTalk Adapter for Oracle Database to update an Oracle database table. You use the INSERT method to insert a row into the Oracle database table. The Oracle database table contains one or more DATE fields. The XML message that is submitted to BizTalk Adapter for Oracle Database does not contain all the DATE fields that are contained in the Oracle database table. In this scenario, an event that resembles the following may be logged:Event Type: Error
Event Source: Microsoft BizTalk Adapters for Enterprise Applications
Event Category: None
Event ID: 0
Description:
System defined exception
Call to Insert@OracleDb://VALDB/PSSUSR/Tables/VALINV
Implementation = OracleDb://VALDB/PSSUSR/Tables/VALINV

Source: OracleDb
Cause: OracleDb://exception=DBException (Unique ID <none>)
22003 : [Oracle][ODBC]Numeric value out of range.

Exception data:
struct DBException =
WideString StatusCode = "22003"
WideString Description = "[Oracle][ODBC]Numeric value out of range."

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next BizTalk Adapter for Oracle Database service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix if the Oapcba.dll file is in process when you apply this hotfix. To avoid restarting the computer, exit all Microsoft BizTalk Server applications that are using BizTalk Adapter for Oracle Database before you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

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.
File nameFile versionFile sizeDateTime
Oapcba.dll1.0.1082.0253,19202-Jun-200621:27
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

WORKAROUND

To work around this problem, include all the DATE fields in the XML message that is submitted to BizTalk Adapter for Oracle Database.

STATUS

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

MORE INFORMATION

This problem may occur if the XML message does not contain all the DATE fields that are contained in the Oracle database table. For example, you use the following statement to create an Oracle database table.
CREATE TABLE DATETBL ("NAME" VARCHAR2(15 byte), 
"STARTDATE" DATE, "ENDDATE" DATE, "SALARY" 
NUMBER(6))
The following XML message fails when you use the INSERT method to update the Oracle database table.
<ns0:Insert xmlns:ns0="http://schemas.microsoft.com/[OracleDb://MYDB/PSSUSR/Tables/DATETBL]">
  <ns0:Rows>
    <ns0:InsertRecord>
      <ns0:NAME>Some Name</ns0:NAME>
      <ns0:STARTDATE>2006-05-31T13:20:00.000-05:00</ns0:STARTDATE>
      <ns0:SALARY>30000</ns0:SALARY>
    </ns0:InsertRecord>
  </ns0:Rows>
</ns0:Insert>
However, the following XML message that contains the ENDDATE field works as expected.
<ns0:Insert xmlns:ns0="http://schemas.microsoft.com/[OracleDb://MYDB/PSSUSR/Tables/DATETBL]">
  <ns0:Rows>
    <ns0:InsertRecord>
      <ns0:NAME>Some Name</ns0:NAME>
      <ns0:STARTDATE>2006-05-31T13:20:00.000-05:00</ns0:STARTDATE>
      <ns0:ENDDATE></ns0:ENDDATE>
      <ns0:SALARY>30000</ns0:SALARY>
    </ns0:InsertRecord>
  </ns0:Rows>
</ns0:Insert>

REFERENCES

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

824684 Description of the standard terminology that is used to describe Microsoft software updates

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.

Modification Type:MinorLast Reviewed:9/15/2006
Keywords:kbBTSAdapters kbBTS kbbug kbfix kbQFE kbpubtypekc kbhotfixserver KB919607 kbAudDeveloper kbAudITPRO