Huh.. db2_table_column = "Monday's" is totally different than
db2_table_column = 'Monday"s'
The 1st is setting the db2 column to ANOTHER DB2 COLUMN and
the 2nd is setting the db2 column to an 8 character literal!
You should have received an error message in case 1 complaining
about an invalid/unknown column name.
What are you using as the front end i.e. the code that calls OCI?
Is it an Oracle tool, VB, Access? We'll check on the other case
of Monday vs Monday's. I assume the DB2_table_column is at least
8 bytes long right ;-)
In article <4dj8i6$42b_at_newshost.cyberramp.net>, scis_at_cyberramp.net (Clay
Isaacs) wrote:
> In article <4dbq5v$7jf_at_news.iag.net>, delphi_at_iag.net says...
> >
> >Use a double single quote (''), This is interpreted as a single quote.
> >
> >Dr. Phil
> >
>
> We have a problem that is similar but the update goes through an Oracle
> transparent gateway (v3.0.13) to DB2/MVS. For example:
>
> UPDATE DB2_TABLE
> SET DB2_TABLE_COLUMN='Monday"s'
>
> results in the DB2 column = Monday
>
> or trying
> SET DB2_TABLE_COLUMN="Monday's" results in Monday. The results seem to
> be inconsistent in what actually gets put into the table.
>
> Has anyone run into this problem using the transparent gateway to DB2?
> How did you get it to work? Is this possibly a bug?
>
> Any help would be appreciated
>
