Tuxedo ART DSNUTILB Wrong Data Conversion With Nullable Columns
(Doc ID 2356149.1)
Last updated on AUGUST 08, 2023
Applies to:
Oracle Tuxedo Application Runtime for CICS and Batch - Version 12.2.2 and laterInformation in this document applies to any platform.
Goal
User encountered the following error while using dsnutilb:
[ERROR]: [check_db_err] OCI_ERROR - ORA-00917: missing comma
[DUMP]: [load_parseRecord] CHAR, colvalue=[0000]
[DUMP]: [check_db_err] End. Check DB error.
[ERROR]: [execSQLSTMT] Failed to execute SQL(insert into tabl1(clm1,...,clm2,clm3,clm4) values(' ','systmtime1','0000',' ','systmtime1',TO_DATE('06.09.2016', 'DD.MM.YYYY'),'KO',TO_TIMESTAMP('2017-08-25-00.41.19.195635','YYYY-MM-DD-HH24.MI.SS.FF6'),'systmtime1',-000000000000000000<3,TO_TIMESTAMP(' ?','YYYY-MM-DD-HH24.MI.SS.FF6'),-00000000000000<3,TO_TIMESTAMP('systmtime1','YYYY-MM-DD-HH24.MI.SS.FF6'))). rc=-1, errode= 917, errmsg = Error - ORA-00917: missing comma
[ERROR]: [load_sqlThread] InsertThread[1]:Failed to execute INSERT statement(Record number=[1]).insertstmt=[insert into tabl1(clm1,...,clm2,clm3,clm4) values(' ','systmtime1','0000',' ','systmtime1',TO_DATE('06.09.2016', 'DD.MM.YYYY'),'KO',TO_TIMESTAMP('2017-08-25-00.41.19.195635','YYYY-MM-DD-HH24.MI.SS.FF6'),'systmtime1',-000000000000000000<3,T
[DUMP]: [load_parseRecord] CHAR, colvalue=[0000]
[DUMP]: [check_db_err] End. Check DB error.
[ERROR]: [execSQLSTMT] Failed to execute SQL(insert into tabl1(clm1,...,clm2,clm3,clm4) values(' ','systmtime1','0000',' ','systmtime1',TO_DATE('06.09.2016', 'DD.MM.YYYY'),'KO',TO_TIMESTAMP('2017-08-25-00.41.19.195635','YYYY-MM-DD-HH24.MI.SS.FF6'),'systmtime1',-000000000000000000<3,TO_TIMESTAMP(' ?','YYYY-MM-DD-HH24.MI.SS.FF6'),-00000000000000<3,TO_TIMESTAMP('systmtime1','YYYY-MM-DD-HH24.MI.SS.FF6'))). rc=-1, errode= 917, errmsg = Error - ORA-00917: missing comma
[ERROR]: [load_sqlThread] InsertThread[1]:Failed to execute INSERT statement(Record number=[1]).insertstmt=[insert into tabl1(clm1,...,clm2,clm3,clm4) values(' ','systmtime1','0000',' ','systmtime1',TO_DATE('06.09.2016', 'DD.MM.YYYY'),'KO',TO_TIMESTAMP('2017-08-25-00.41.19.195635','YYYY-MM-DD-HH24.MI.SS.FF6'),'systmtime1',-000000000000000000<3,T
User believes wrong conversion by dsnutilb where there are nullable columns, and in user's above case the problem is with NUMBER and TIMESTAMP column type.
User wants to know whether nullable column is supported or not.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |