You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/13 17:13:00 UTC
[jira] [Work logged] (TRAFODION-3252) odb -cp command does not
support writting to bad file
[ https://issues.apache.org/jira/browse/TRAFODION-3252?focusedWorklogId=198221&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-198221 ]
ASF GitHub Bot logged work on TRAFODION-3252:
---------------------------------------------
Author: ASF GitHub Bot
Created on: 13/Feb/19 17:12
Start Date: 13/Feb/19 17:12
Worklog Time Spent: 10m
Work Description: DaveBirdsall commented on pull request #1778: [TRAFODION-3252] odb -cp command does not support writting to bad file
URL: https://github.com/apache/trafodion/pull/1778
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 198221)
Time Spent: 40m (was: 0.5h)
> odb -cp command does not support writting to bad file
> -----------------------------------------------------
>
> Key: TRAFODION-3252
> URL: https://issues.apache.org/jira/browse/TRAFODION-3252
> Project: Apache Trafodion
> Issue Type: New Feature
> Components: db-utility-odb
> Reporter: 苏锦佩
> Assignee: 苏锦佩
> Priority: Major
> Fix For: 2.3
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> For -l command, there is an option "bad" to specify where to store bad records, but for -cp command, there is no such option.
>
> {code:java}
> odb64luo -u v7fat:trafodion -p v7fat:traf123 -d oracle:traf -cp src=KSTP_TCJHJG:tgt=v7fat.KSTP_TCJHJG:rows=1000:loadcmd=UL:parallel=6:truncate:bad=+KSTP_TCJHJGbadfile
> odb [parseopt(14353)] - Error: unknown parameter "bad"{code}
>
>
> For -cp command, there is an option "errdmp" to specify where to dump bad buffer when an error occurred. But for the Chinese user, the contents is not easy to understand. For example:
> {code:java}
> [sujinpei@localhost bin]$ cat errdump
> [1] odb [Oloadbuff(10207)] - Error loading row 1 (State: HY723, Native 0)
> [Trafodion ODBC Driver] TRANSLATIONDLL ERROR: DRIVERTODATASOURCE [01!S!].TranslateUTF8: No Unicode Translation Row: 1 Column: 2
> [1] Dumping row 1 in a block of 2 rows. ODBC row length = 78
> 000000: 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1...............
> 000016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 000032: 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 ................
> 000048: 00 e4 bd a0 e4 bb ac e5 a5 bd 20 20 20 20 20 20 ..........
> 000064: 20 20 20 20 20 00 14 00 00 00 00 00 00 00 .........
> [1] odb [Oloadbuff(10207)] - Error loading row 2 (State: HY723, Native 0)
> [Trafodion ODBC Driver] TRANSLATIONDLL ERROR: DRIVERTODATASOURCE [01!S!].TranslateUTF8: No Unicode Translation Row: 2 Column: 2
> [1] Dumping row 2 in a block of 2 rows. ODBC row length = 78
> 000000: 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2...............
> 000016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 000032: 00 00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 ................
> 000048: 00 e6 88 91 e4 bb ac e6 9d a5 e4 ba 86 20 20 20 .............
> 000064: 20 20 20 20 20 00 14 00 00 00 00 00 00 00 .........{code}
>
> So some user wants to add the intuitive option "bad" for "-cp" command and do similar things as "-l" command.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)