258 views

Description

When a JDBC Data Source loads an import set table and binary large object (BLOB] field is mapped, the binary object should be automatically converted into an Attachment record (sys_attachment table)." However, if the sys_attachment record is not being created if an Oracle source table includes a BLOB field.

Steps to Reproduce

  1. Set up a MID Server and point to the instance on the Helsinki release.

  2. Create a data source with the following attributes:

    • Import set table label: oracle_blob_import
    • Import set table name: u_oracle_blob_import
    • Type: JDBC
    • Use MID Server: <name of the MID server created>
    • Format: Oracle
    • Database name: <Your database name>
    • Database port:<Your database port (usually 1521)>
    • User name: <Your DB username>
    • Password: <Your DB password>
    • Server: <Your DB server>
    • Query: All rows from the table (you can also test a specific SELECT statement)
    • Table name: A table in the Oracle database that contains BLOBs 3
  3. Run the import

    Note that no sys_attachment record is generated for the BLOB fields in the Oracle table.

Workaround

Downgrade the JDBC driver on the MID server if possible. Oracle JDBC Driver 11g Release 2 (11.2) no longer supports the getString method for retrieving BLOB column values.


Related Problem: PRB708904

Seen In

Helsinki Patch 1
Helsinki Patch 2

Fixed In

Jakarta

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-08-29 07:13:31
Published:2016-11-15