Jukka Rahkonen jukka.rahkonen at mmmtike.fi writes:
Jukka Rahkonen jukka.rahkonen at mmmtike.fi writes:
I suspect that the reason for the trouble is that this field is a
17 character wide VARCHAR2 and I have in the data values like
ÖVRE SÖDERGÄRDAN . Database is using UTF-8 and Ö,Ö and
Eli Adam eadam at co.lincoln.or.us writes:
Jukka,
Could it be possible that OCI driver reserves too little of some
resoursesand
fails because of that with large records? I am now running a query
with minimum
set of columns in my query and ogr2ogr is running well and I believe
it
Jukka,
If the field is 17 char wide (rather than 17 bytes wide) then that is your
problem. A varchar2 column can use either char or byte specifications.
http://docs.oracle.com/cd/E11882_01/server.112/e26088/sql_elements001.htm#i
45694
If neither char or byte is specified, it defaults to your
Jukka Rahkonen jukka.rahkonen at mmmtike.fi writes:
I suspect that the reason for the trouble is that this field is a
17 character wide VARCHAR2 and I have in the data values like
ÖVRE SÖDERGÄRDAN . Database is using UTF-8 and Ö,Ö and Ä are
taking more than one byte each. Perhaps OCI driver
Hi,
I have one view in Oracle 11 that I just cannot convert to another format with
ogr2ogr.
If I use -sql parameter SELECT * FROM view the conversion stops after couple
of thousands of lines with the following error
ERROR 1: ORA-01406: fetched column value was truncated
in OCIStmtFetch
I
Jukka,
Could it be possible that OCI driver reserves too little of some resourses and
fails because of that with large records? I am now running a query with
minimum
set of columns in my query and ogr2ogr is running well and I believe it will
convert all the million rows from the view now.
