Обсуждение: Error in running DBT2
Hi All,
I run the the dbt2-pgsql-build-db -w 1
but, after some time, I faced this error
/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 45: [: c: unexpected operator
/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 53: [: c: unexpected operator
unknown stored function type: c
and script ends!!
Moreover, in between the scripts running, i was looing at the ouput i found something like
Output directory of data files: current directory
Generating data files for 1 warehouse(s)...
Generating item table data...
BEGIN
ERROR: invalid byte sequence for encoding "UTF8": 0xf9
CONTEXT: COPY item, line 1
ROLLBACK
This pattern the above found many times. Please guide me through!!!
Regards,
Rohit Goyal
On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:
This pattern the above found many times. Please guide me through!!!
IIRC, people have been working around this by setting standard_conforming_strings to "off". It really ought to be fixed in a principled way, though -- the real issue here is that dbt2 has severe bit-rot.
Peter Geoghegan
Hi Peter,
On Tue, May 13, 2014 at 9:44 PM, Peter Geoghegan <pg@heroku.com> wrote:
IIRC, people have been working around this by setting standard_conforming_strings to "off". It really ought to be fixed in a principled way, though -- the real issue here is that dbt2 has severe bit-rot.On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:This pattern the above found many times. Please guide me through!!!
Can you please elaborate, where I can make this changes :) ?
Regards,
Rohit Goyal
Rohit Goyal wrote > Hi Peter, > > On Tue, May 13, 2014 at 9:44 PM, Peter Geoghegan < > pg@ > > wrote: > >> >> On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal < > rhtgyl.87@ > > wrote: >> >>> This pattern the above found many times. Please guide me through!!! >>> >> >> IIRC, people have been working around this by setting >> standard_conforming_strings to "off". It really ought to be fixed in a >> principled way, though -- the real issue here is that dbt2 has severe >> bit-rot. >> >> Can you please elaborate, where I can make this changes :) ? Peter? The error is more typical of someone creating a database with UTF-8 encoding but then tries storing Latin-1 (or some other) encoded data. Since not all byte sequences in the source data encoding are valid in UTF-8 when one of the invalid sequences is present the import fails. PostgreSQL makes no attempt to perform data conversion on import. The solution is to create the database with the correct encoding - whatever it may be. This "DBT2" application should provide guidance on this topic. Otherwise you could use "SQL_ASCII" - which is effectively punting on the issue: http://www.postgresql.org/docs/9.3/static/sql-createdatabase.html http://www.postgresql.org/docs/9.3/static/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED IIRC given that the error happens in a SQL COPY "standard_conforming_strings" has no bearing on the outcome. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Error-in-running-DBT2-tp5803793p5803817.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.
On Tue, May 13, 2014 at 2:51 PM, David G Johnston <david.g.johnston@gmail.com> wrote: > The error is more typical of someone creating a database with UTF-8 encoding > but then tries storing Latin-1 (or some other) encoded data. I didn't say that it was the only problem. Just that I had noticed that other people were using standard_conforming_strings = off when running DBT2, on the couple of occasions were I looked through a result set. The fact that this may have accidentally worked before, when that was the default does not imply that it was ever correct, but it may at least be possible to get it to work at least as well as it ever did by doing that. DBT2 doesn't seem to have anything to say about encoding one way or the other. As I said, it has many problems. Another thing that I noticed that I didn't like was that it uses the C locale. -- Peter Geoghegan
Hi Peter,
I tried the solution suggested by you. Please problem still persists.
I run the the dbt2-pgsql-build-db -w 1
but, after some time, I faced this error
/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 45: [: c: unexpected operator
/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 53: [: c: unexpected operator
unknown stored function type: c
and script ends!!
moreover, I see that DB has been created and also 9 tables are there in Database dbt2. Please suggest how to proceed.
Regards,
rohit Goyal
On Tue, May 13, 2014 at 9:44 PM, Peter Geoghegan <pg@heroku.com> wrote:
IIRC, people have been working around this by setting standard_conforming_strings to "off". It really ought to be fixed in a principled way, though -- the real issue here is that dbt2 has severe bit-rot.On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:This pattern the above found many times. Please guide me through!!!--
Peter Geoghegan
Regards,
Rohit Goyal
Hi All,
--
Regards,
I am runnig dbt2 with last postgresql kit. pg9.4. I tried everything again after setting up awhole new machine again with ubuntu. Still facing the same error.
I run the the dbt2-pgsql-build-db -w 1
but, after some time, I faced this error
/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 45: [: c: unexpected operator
/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 53: [: c: unexpected operator
unknown stored function type: c
and script ends!!
Please guide me probable solution to get over it.
Regards,
Rohit
On Wed, May 14, 2014 at 12:43 AM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:
Hi Peter,I tried the solution suggested by you. Please problem still persists.I run the the dbt2-pgsql-build-db -w 1but, after some time, I faced this error/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 45: [: c: unexpected operator/home/abhi/dbt2_install/bin/dbt2-pgsql-load-stored-procs: 53: [: c: unexpected operatorunknown stored function type: cand script ends!!moreover, I see that DB has been created and also 9 tables are there in Database dbt2. Please suggest how to proceed.Regards,rohit Goyal
On Tue, May 13, 2014 at 9:44 PM, Peter Geoghegan <pg@heroku.com> wrote:IIRC, people have been working around this by setting standard_conforming_strings to "off". It really ought to be fixed in a principled way, though -- the real issue here is that dbt2 has severe bit-rot.On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:This pattern the above found many times. Please guide me through!!!--
Peter Geoghegan--
Regards,Rohit Goyal
Regards,
Rohit Goyal
Hi All,
--
Regards,
On Tue, May 13, 2014 at 9:44 PM, Peter Geoghegan <pg@heroku.com> wrote:
IIRC, people have been working around this by setting standard_conforming_strings to "off". It really ought to be fixed in a principled way, though -- the real issue here is that dbt2 has severe bit-rot.On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:This pattern the above found many times. Please guide me through!!!
Sorry for so asking so late. I thought the error is resolved.
I changed standard_conforming_strings to "off" in postgresql.conf. and then I run dbt2-pgsql-build-db -w 1 script again.
But, I am still facing the same error. Please tel me what else I can do to resolve the issue.
Regards,
Rohit Goyal
--
Peter Geoghegan
Regards,
Rohit Goyal
Hi All,
--
Regards,
Just adding the actual error again.
I run the the dbt2-pgsql-build-db -w 1
Output directory of data files: current directory
Generating data files for 1 warehouse(s)...
Generating item table data...
BEGIN
ERROR: invalid byte sequence for encoding "UTF8": 0xf9
CONTEXT: COPY item, line 1
ROLLBACK
This pattern the above found many times. Please guide me through!!!
Regards,
Rohit Goyal
On Tue, May 20, 2014 at 9:15 AM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:
Hi All,On Tue, May 13, 2014 at 9:44 PM, Peter Geoghegan <pg@heroku.com> wrote:IIRC, people have been working around this by setting standard_conforming_strings to "off". It really ought to be fixed in a principled way, though -- the real issue here is that dbt2 has severe bit-rot.On Tue, May 13, 2014 at 12:36 PM, Rohit Goyal <rhtgyl.87@gmail.com> wrote:This pattern the above found many times. Please guide me through!!!Sorry for so asking so late. I thought the error is resolved.I changed standard_conforming_strings to "off" in postgresql.conf. and then I run dbt2-pgsql-build-db -w 1 script again.But, I am still facing the same error. Please tel me what else I can do to resolve the issue.Regards,Rohit Goyal--
Peter Geoghegan--
Regards,Rohit Goyal
Regards,
Rohit Goyal
On 05/20/2014 03:39 AM, Rohit Goyal wrote: > Hi All, > > Just adding the actual error again. > > I run the the *dbt2-pgsql-build-db -w 1 * > > Output directory of data files: current directory > > *Generating data files for 1 warehouse(s)...* > *Generating item table data...* > *BEGIN* > *ERROR: invalid byte sequence for encoding "UTF8": 0xf9* > *CONTEXT: COPY item, line 1* > *ROLLBACK* > > This pattern the above found many times. Please guide me through!!! > > > Please stop posting this to postgresql-hackers. We've already told you it's the wrong forum. cheers andrew
On Tue, May 20, 2014 at 9:57 AM, Andrew Dunstan <andrew@dunslane.net> wrote:
On 05/20/2014 03:39 AM, Rohit Goyal wrote:Hi All,I run the the *dbt2-pgsql-build-db -w 1 *
Just adding the actual error again.*Generating data files for 1 warehouse(s)...*
Output directory of data files: current directory
*Generating item table data...*
*BEGIN*
*ERROR: invalid byte sequence for encoding "UTF8": 0xf9*
*CONTEXT: COPY item, line 1*
*ROLLBACK*
This pattern the above found many times. Please guide me through!!!
Please stop posting this to postgresql-hackers. We've already told you it's the wrong forum.
cheers
Hi Andrew,
I am so sorry, it was by mistake. :). I was not able to analyse whether the issue belong to postgresql or dbt2.
Regards,
Rohit
andrew