[GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

Hi sir

This is mahesh. i got following erro when i ran

./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo


below error generated as i have given correct credentials to connect
respective server & database


 how to rectify this issue sirplease let me know

Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
Source database connectivity info...
conn =jdbc:jtds:sqlserver://dns name/DataFee
d
user =trustfort
password=**
Target database connectivity info...
conn =jdbc:postgresql://dnsname:5432/
edb
user =postgres
password=**
Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.
at com.edb.MigrationToolkit.initToolkit(MigrationToolkit.java:3378)
at com.edb.MigrationToolkit.main(MigrationToolkit.java:1700)



./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo

Fwd: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

-- Forwarded message --
From: David G. Johnston 
Date: Wed, Jun 15, 2016 at 8:40 PM
Subject: Re: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: Durgamahesh Manne 


On Wed, Jun 15, 2016 at 11:00 AM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:

> as per above discussion. i already enabled tcp/ip based access on which
> the server to listen connections from client applications as well as
> already set password for required user
>
>
> may i know the recommended approach for migrate the tables from sql server
> to postgesql
>
>
> please let me know
>
>
>
​I've helped you all that I can, and I do not respond well to personal
emails asking for help.  Direct all correspondence to the list: it is ok to
CC: people who have already replied.  And, as I said, this is not the
correct forum for your question.  You are using a third-party tool so they
are the ones you should be asking.  In this case they do monitor these
lists and may chime in but as a matter of proper etiquette this discussion
is off-topic for this list.  Specifically it is a request for help on how
to use a specific non-community-PostgreSQL product.

I suspect that "dnsname" is not actually the host name for your server...if
the URL is invalid and you've munged it for email it would be impossible
for us to point out to you how/if that is so.

David J.



sir as per above discussion

conn =jdbc:postgresql://archive.tf.com:5432/
<http://archive.trustfort.com:5432/edb>edb

i earlier mentioned the host name of the server (archive.tf.com)

may i know  recommended approach to migrate the tables from sql server to
postgresql instead of using 3rd party tools

thank you

Fwd: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

-- Forwarded message --
From: Durgamahesh Manne 
Date: Wed, Jun 15, 2016 at 8:57 PM
Subject: Fwd: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: pgsql-general@postgresql.org
Cc: "David G. Johnston" 



-- Forwarded message --
From: David G. Johnston 
Date: Wed, Jun 15, 2016 at 8:40 PM
Subject: Re: [GENERAL] regarding schema only migration from sqlserver to
postgres with runmtk.sh
To: Durgamahesh Manne 


On Wed, Jun 15, 2016 at 11:00 AM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:

> as per above discussion. i already enabled tcp/ip based access on which
> the server to listen connections from client applications as well as
> already set password for required user
>
>
> may i know the recommended approach for migrate the tables from sql server
> to postgesql
>
>
> please let me know
>
>
>
​I've helped you all that I can, and I do not respond well to personal
emails asking for help.  Direct all correspondence to the list: it is ok to
CC: people who have already replied.  And, as I said, this is not the
correct forum for your question.  You are using a third-party tool so they
are the ones you should be asking.  In this case they do monitor these
lists and may chime in but as a matter of proper etiquette this discussion
is off-topic for this list.  Specifically it is a request for help on how
to use a specific non-community-PostgreSQL product.

I suspect that "dnsname" is not actually the host name for your server...if
the URL is invalid and you've munged it for email it would be impossible
for us to point out to you how/if that is so.

David J.



sir as per above discussion

conn =jdbc:postgresql://archive.tf.com:5432/
<http://archive.trustfort.com:5432/edb>edb

i earlier mentioned the host name of the server (archive.tf.com)

may i know  recommended approach to migrate the tables from sql server to
postgresql instead of using 3rd party tools

thank you

&& i already enabled the listen addresses  '*' to listen all available ip
interfaces

thank you

Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

sir

as per above discussion .the URL which i mentioned in toolkit properties
was 100% correct .i have checked db connectivity from another cluster with
psql .connection esatblished to below mentioned database
conn =jdbc:postgresql://archive.trustfort.com:5432/edb



thank you for the valuable information


On Thu, Jun 16, 2016 at 3:08 AM, Mike Sofen  wrote:

>
>
> *From:* pgsql-general-ow...@postgresql.org [mailto:
> pgsql-general-ow...@postgresql.org] *On Behalf Of *David G. Johnston
> *Sent:* Wednesday, June 15, 2016 1:31 PM
> *To:* Durgamahesh Manne 
> *Cc:* pgsql-general@postgresql.org
> *Subject:* Re: [GENERAL] regarding schema only migration from sqlserver
> to postgres with runmtk.sh
>
>
>
> On Wed, Jun 15, 2016 at 11:27 AM, Durgamahesh Manne <
> maheshpostgr...@gmail.com> wrote:
>
> may i know  recommended approach to migrate the tables from sql server to
> postgresql instead of using 3rd party tools
>
>
>
>
>
> ​I suppose SQL Server has some means to export in TSV/CSV or other
> row-oriented structured output.  The \copy psql meta-command or COPY SQL
> ​command could load that data.
>
>
>
> David J.
>
>
>
>
>
> There are MANY tools for sql server, many are built in (aka free) that
> will generate DDL, or extract data, or both, plus you can directly query
> the system catalogs, just like PG.  Utterly trivial stuff to use and
> Postgres can ingest all of it since it’s normally either flat file or ansi
> sql.
>
>
>
> MikeS
>

Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

sir

PostgreSQL always no1 in world
as per above discussion

migration not working from sql to postgreSQL  with runmtk.sh


Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.



same error repeated even there mentioned correct credentials as here i
checked multiple times

thank you

Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

hi
sir
as per above discussion same error repeated even mentioned ip address of
hostname

./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
-allTables dbo


TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
TARGET_DB_USER=postgres
TARGET_DB_PASSWORD=*



Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target EnterpriseDB database server...
MTK-10045: The URL specified for the "target" database is invalid.
Check the connectivity credentials.
Stack Trace:
com.edb.MTKException: MTK-10045: The URL specified for the "target"
database is invalid.
Check the connectivity credentials.

On Thu, Jun 16, 2016 at 7:55 PM, David G. Johnston <
david.g.johns...@gmail.com> wrote:

> On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne <
> maheshpostgr...@gmail.com> wrote:
>
>>
>> sir
>>
>> PostgreSQL always no1 in world
>> as per above discussion
>>
>> migration not working from sql to postgreSQL  with runmtk.sh
>>
>>
>> Connecting with source SQL Server database server...
>> Connected to Microsoft SQL Server, version '10.50.1600'
>> Connecting with target EnterpriseDB database server...
>> MTK-10045: The URL specified for the "target" database is invalid.
>> Check the connectivity credentials.
>> Stack Trace:
>> com.edb.MTKException: MTK-10045: The URL specified for the "target"
>> database is invalid.
>> Check the connectivity credentials.
>>
>>
>>
>> same error repeated even there mentioned correct credentials as here i
>> checked multiple times
>>
>>
> ​Maybe you should try using an IP address instead of a host name.
>
> David J.​
>
>

Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

yes sir

as per above discussion..i already looked pdf postgres plus guide you
mentioned

as well as i already set password for postgres user associated with
postgres db

On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:

> hi
> sir
> as per above discussion same error repeated even mentioned ip address of
> hostname
>
> ./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
> -allTables dbo
>
>
> TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
> TARGET_DB_USER=postgres
> TARGET_DB_PASSWORD=*
>
>
>
> Connecting with source SQL Server database server...
> Connected to Microsoft SQL Server, version '10.50.1600'
> Connecting with target EnterpriseDB database server...
> MTK-10045: The URL specified for the "target" database is invalid.
> Check the connectivity credentials.
> Stack Trace:
> com.edb.MTKException: MTK-10045: The URL specified for the "target"
> database is invalid.
> Check the connectivity credentials.
>
> On Thu, Jun 16, 2016 at 7:55 PM, David G. Johnston <
> david.g.johns...@gmail.com> wrote:
>
>> On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne <
>> maheshpostgr...@gmail.com> wrote:
>>
>>>
>>> sir
>>>
>>> PostgreSQL always no1 in world
>>> as per above discussion
>>>
>>> migration not working from sql to postgreSQL  with runmtk.sh
>>>
>>>
>>> Connecting with source SQL Server database server...
>>> Connected to Microsoft SQL Server, version '10.50.1600'
>>> Connecting with target EnterpriseDB database server...
>>> MTK-10045: The URL specified for the "target" database is invalid.
>>> Check the connectivity credentials.
>>> Stack Trace:
>>> com.edb.MTKException: MTK-10045: The URL specified for the "target"
>>> database is invalid.
>>> Check the connectivity credentials.
>>>
>>>
>>>
>>> same error repeated even there mentioned correct credentials as here i
>>> checked multiple times
>>>
>>>
>> ​Maybe you should try using an IP address instead of a host name.
>>
>> David J.​
>>
>>
>
>

Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

as per above conversation. i checked connectivity details as it is
connected to database  (even hostname i mentioned connected to database)
  psql --host 192.168.168.201 --user postgres -d raghu
Password for user postgres:
psql.bin (9.4.8, server 9.4.4)
Type "help" for help.

No entry for terminal type "xterm";
using dumb terminal settings.
raghu=#


On Thu, Jun 16, 2016 at 8:51 PM, Jan de Visser  wrote:

> Please don't top-post.
>
> On Thursday, June 16, 2016 8:30:53 PM EDT Durgamahesh Manne wrote:
> > hi
> > sir
> > as per above discussion same error repeated even mentioned ip address of
> > hostname
> >
> > ./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
> > -allTables dbo
> >
> >
> > TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
> > TARGET_DB_USER=postgres
> > TARGET_DB_PASSWORD=*
> >
> >
> >
> > Connecting with source SQL Server database server...
> > Connected to Microsoft SQL Server, version '10.50.1600'
> > Connecting with target EnterpriseDB database server...
> > MTK-10045: The URL specified for the "target" database is invalid.
> > Check the connectivity credentials.
> > Stack Trace:
> > com.edb.MTKException: MTK-10045: The URL specified for the "target"
> > database is invalid.
> > Check the connectivity credentials.
> >
>
> So have you tried the connectivity details? What does
>
> $ psql --host 192.168.168.201 --user postgres -d raghu
>
> give you?
>
> I have a sneaking suspicion you don't have TCP/IP access to the database
> configured in pg_hba.conf.
>
>
>
>
>

Re: [GENERAL] Re: regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

i got another error even i specified -targetdbtype
like
./runMTK.sh -sourcedbtype sqlserver -targetdbtype postgresql -targetSchema
public -schemaOnly -allTables dbo
Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
Source database connectivity info...
conn =jdbc:jtds:sqlserver://fxserver.trustfort.com:49883/DataFeedHandler
user =trustfort
password=**
Target database connectivity info...
conn =jdbc:postgresql://192.168.168.201:5432/raghu
user =postgres
password=**
Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target Postgres database server...
Exception in thread "main" java.lang.NoClassDefFoundError:
org/postgresql/Driver
at
com.edb.dbhandler.postgresql.PGConnection.(PGConnection.java:32)
at com.edb.common.MTKFactory.createMTKConnection(MTKFactory.java:228)
at
com.edb.MigrationToolkit.createNewTargetConnection(MigrationToolkit.java:5987)
at com.edb.MigrationToolkit.initToolkit(MigrationToolkit.java:3376)
at com.edb.MigrationToolkit.main(MigrationToolkit.java:1700)
Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver





On Thu, Jun 16, 2016 at 8:59 PM, Neil Anderson 
wrote:

> On 2016-06-16 11:13 AM, Durgamahesh Manne wrote:
>
>> yes sir
>>
>> as per above discussion..i already looked pdf postgres plus guide you
>> mentioned
>>
>> as well as i already set password for postgres user associated with
>> postgres db
>>
>> On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne
>> mailto:maheshpostgr...@gmail.com>> wrote:
>>
>> hi
>> sir
>> as per above discussion same error repeated even mentioned ip
>> address of hostname
>>
>> ./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
>> -allTables dbo
>>
>>
>> TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
>> <http://192.168.168.201:5432/raghu>
>> TARGET_DB_USER=postgres
>> TARGET_DB_PASSWORD=*
>>
>>
>>
>> Connecting with source SQL Server database server...
>> Connected to Microsoft SQL Server, version '10.50.1600'
>> Connecting with target EnterpriseDB database server...
>> MTK-10045: The URL specified for the "target" database is invalid.
>> Check the connectivity credentials.
>> Stack Trace:
>> com.edb.MTKException: MTK-10045: The URL specified for the "target"
>> database is invalid.
>> Check the connectivity credentials.
>>
>> On Thu, Jun 16, 2016 at 7:55 PM, David G. Johnston
>> mailto:david.g.johns...@gmail.com>>
>> wrote:
>>
>> On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne
>> mailto:maheshpostgr...@gmail.com
>> >>wrote:
>>
>>
>> sir
>>
>> PostgreSQL always no1 in world
>> as per above discussion
>>
>> migration not working from sql to postgreSQL  with runmtk.sh
>>
>>
>> Connecting with source SQL Server database server...
>> Connected to Microsoft SQL Server, version '10.50.1600'
>> Connecting with target EnterpriseDB database server...
>> MTK-10045: The URL specified for the "target" database is
>> invalid.
>> Check the connectivity credentials.
>> Stack Trace:
>> com.edb.MTKException: MTK-10045: The URL specified for the
>> "target" database is invalid.
>> Check the connectivity credentials.
>>
>>
>>
>> same error repeated even there mentioned correct credentials
>> as here i checked multiple times
>>
>>
>> ​Maybe you should try using an IP address instead of a host name.
>>
>> David J.​
>>
>>
>>
>>
>>
> I've never used this tool so like everyone else I am guessing here but
> having quickly looked at the documentation have you tried specifying the
> '-targetdbtype postgres' in addition to the '-sourcedbtype sqlserver' that
> you have already specified?
>
> Neil A
>
>
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>

Re: [GENERAL] regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

i already set password ..it appears when executing the runmtk.sh
jdbc already mentioned

On Thu, Jun 16, 2016 at 9:12 PM, Jan de Visser  wrote:

> 
> P L E A S E   D O N ' T   T O P  P O S T
> 
>
>
> On Thursday, June 16, 2016 9:00:48 PM EDT Durgamahesh Manne wrote:
> > as per above conversation. i checked connectivity details as it is
> > connected to database  (even hostname i mentioned connected to database)
> >   psql --host 192.168.168.201 --user postgres -d raghu
> > Password for user postgres:
> > psql.bin (9.4.8, server 9.4.4)
> > Type "help" for help.
> >
> > No entry for terminal type "xterm";
> > using dumb terminal settings.
> > raghu=#
> >
> > On Thu, Jun 16, 2016 at 8:51 PM, Jan de Visser 
> wrote:
> > > Please don't top-post.
> > >
> > > On Thursday, June 16, 2016 8:30:53 PM EDT Durgamahesh Manne wrote:
> > > > hi
> > > > sir
> > > > as per above discussion same error repeated even mentioned ip
> address of
> > > > hostname
> > > >
> > > > ./runMTK.sh -sourcedbtype sqlserver -targetSchema public -schemaOnly
> > > > -allTables dbo
> > > >
> > > >
> > > > TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
> > > > TARGET_DB_USER=postgres
> > > > TARGET_DB_PASSWORD=*
> > > >
> > > >
>
> - Just to make sure: TARGET_DB_PASSWORD is not actually set to '*',
> right?
> - Are you sure that you need 'jdbc:' in the URL?
>
>
> Also, your tone and communication style are not really helping your cause.
> Your quoting style is chaotic and you're very adversarial. I understand
> you're
> probably under pressure to get this fixed, but yelling at the volunteers
> that
> help you here is not helping.
>

Re: [GENERAL] Re: regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

thank you for the information related to postgres


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

Re: [GENERAL] Re: regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

i can able to resolve the issue on migration from sql to postgres with
runmtk.sh  without taking any support from edb

even i frustated with runmtk.sh as i wanted to use postgresql life long in
my company

thank you for information




On Thu, Jun 16, 2016 at 11:43 PM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:

> thank you for the information related to postgres
>

Re: [GENERAL] Re: regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

hi sir

as per above conversation

i need to download jdbc driver  as sameer suggested on migration with
runmtk.sh from sql to postgres

thank you sir

super fast response  only from postgres pgdg regarding postgres issues

On Fri, Jun 17, 2016 at 1:18 AM, Adrian Klaver 
wrote:

> On 06/16/2016 11:28 AM, Durgamahesh Manne wrote:
>
>> i can able to resolve the issue on migration from sql to postgres with
>> runmtk.sh  without taking any support from edb
>>
>> even i frustated with runmtk.sh as i wanted to use postgresql life long
>> in my company
>>
>
> For completeness and to help anyone else who comes across this thread when
> having the same problem, what did you do to get it to work?
>
>
>> thank you for information
>>
>>
>>
>>
>> On Thu, Jun 16, 2016 at 11:43 PM, Durgamahesh Manne
>> mailto:maheshpostgr...@gmail.com>> wrote:
>>
>> thank you for the information related to postgres
>>
>>
>>
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
>

Re: [GENERAL] Re: regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

hi sir

as you mentioned above

members in pgsql mailing list  were not frustrating  about my tone & mail
which i sent related to postgres

as i believe they are always happy to serve for postgres

as well as i like very much postgres

On Thu, Jun 16, 2016 at 9:33 PM, Sameer Kumar 
wrote:

> Disclaimer: My company is a partner of EnterpriseDB and provides services
> and consultation on EnterpriseDB tools
>
> On Thu, 16 Jun 2016, 11:52 p.m. Neil Anderson, 
> wrote:
>
>> On 2016-06-16 11:42 AM, Durgamahesh Manne wrote:
>> > i got another error even i specified -targetdbtype
>> > like
>> > ./runMTK.sh -sourcedbtype sqlserver -targetdbtype postgresql
>> > -targetSchema public -schemaOnly -allTables dbo
>> > Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
>
>
> You have to take a pause and note that people on this list are frustrated
> with you for your tone and top posting. In case the complain has gone
> unregistered or has not made sense, please read this out
> https://en.m.wikipedia.org/wiki/Posting_style
>
> Make sure you don't top post
>
> > Source database connectivity info...
>> > conn =jdbc:jtds:sqlserver://
>> fxserver.trustfort.com:49883/DataFeedHandler
>> > <http://fxserver.trustfort.com:49883/DataFeedHandler>
>> > user =trustfort
>> > password=**
>> > Target database connectivity info...
>> > conn =jdbc:postgresql://192.168.168.201:5432/raghu
>> > <http://192.168.168.201:5432/raghu>
>> > user =postgres
>> > password=**
>> > Connecting with source SQL Server database server...
>> > Connected to Microsoft SQL Server, version '10.50.1600'
>> > Connecting with target Postgres database server...
>> > Exception in thread "main" java.lang.NoClassDefFoundError:
>> > org/postgresql/Driver
>>
>
> You need to ensure that postgreSQL jdbc jar files are placed in your class
> path or under $JRE_HOME/lib/ext
>
> You might have already done this for SQL Server, do the same for
> PostgreSQL too.
>
>
> > at
>> > com.edb.dbhandler.postgresql.PGConnection.(PGConnection.java:32)
>> > at
>> com.edb.common.MTKFactory.createMTKConnection(MTKFactory.java:228)
>> > at
>> >
>> com.edb.MigrationToolkit.createNewTargetConnection(MigrationToolkit.java:5987)
>> > at com.edb.MigrationToolkit.initToolkit(MigrationToolkit.java:3376)
>> > at com.edb.MigrationToolkit.main(MigrationToolkit.java:1700)
>> > Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver
>> >
>> >
>> >
>> >
>> >
>> > On Thu, Jun 16, 2016 at 8:59 PM, Neil Anderson
>> > mailto:neil.t.ander...@gmail.com>> wrote:
>> >
>> >     On 2016-06-16 11:13 AM, Durgamahesh Manne wrote:
>> >
>> > yes sir
>> >
>> > as per above discussion..i already looked pdf postgres plus
>> > guide you
>> > mentioned
>>
>
> It is best that you contact EbterpriseDB support or someone who provides
> services for EDB tools.
>
> >
>> > as well as i already set password for postgres user associated
>> with
>> > postgres db
>> >
>> > On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne
>> > mailto:maheshpostgr...@gmail.com>
>> > <mailto:maheshpostgr...@gmail.com
>> > <mailto:maheshpostgr...@gmail.com>>> wrote:
>> >
>> > hi
>> > sir
>> > as per above discussion same error repeated even mentioned
>> ip
>> > address of hostname
>> >
>> > ./runMTK.sh -sourcedbtype sqlserver -targetSchema public
>> > -schemaOnly
>> > -allTables dbo
>> >
>> >
>> > TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
>> > <http://192.168.168.201:5432/raghu>
>> > <http://192.168.168.201:5432/raghu>
>> > TARGET_DB_USER=postgres
>> > TARGET_DB_PASSWORD=*
>> >
>> >
>> >
>> > Connecting with source SQL Server database server...
>> > Connected to Microsoft SQL Server, version '10.50.1600'
>> > Connecting with target EnterpriseDB database server...
>> > MTK-10045: The URL specified for the "target" database is
>> > invalid.
>

Re: [GENERAL] Re: regarding schema only migration from sqlserver to postgres with runmtk.sh

[Durgamahesh Manne]

On Fri, Jun 17, 2016 at 2:16 PM, Durgamahesh Manne <
maheshpostgr...@gmail.com> wrote:

> hi sir
>
> as you mentioned above
>
> members in pgsql mailing list  were not frustrating  about my tone & mail
> which i sent related to postgres
>
> as i believe they are always happy to serve for postgres
>
> as well as i like very much postgres
>
> On Thu, Jun 16, 2016 at 9:33 PM, Sameer Kumar 
> wrote:
>
>> Disclaimer: My company is a partner of EnterpriseDB and provides services
>> and consultation on EnterpriseDB tools
>>
>> On Thu, 16 Jun 2016, 11:52 p.m. Neil Anderson, 
>> wrote:
>>
>>> On 2016-06-16 11:42 AM, Durgamahesh Manne wrote:
>>> > i got another error even i specified -targetdbtype
>>> > like
>>> > ./runMTK.sh -sourcedbtype sqlserver -targetdbtype postgresql
>>> > -targetSchema public -schemaOnly -allTables dbo
>>> > Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
>>
>>
>> You have to take a pause and note that people on this list are frustrated
>> with you for your tone and top posting. In case the complain has gone
>> unregistered or has not made sense, please read this out
>> https://en.m.wikipedia.org/wiki/Posting_style
>>
>> Make sure you don't top post
>>
>> > Source database connectivity info...
>>> > conn =jdbc:jtds:sqlserver://
>>> fxserver.trustfort.com:49883/DataFeedHandler
>>> > <http://fxserver.trustfort.com:49883/DataFeedHandler>
>>> > user =trustfort
>>> > password=**
>>> > Target database connectivity info...
>>> > conn =jdbc:postgresql://192.168.168.201:5432/raghu
>>> > <http://192.168.168.201:5432/raghu>
>>> > user =postgres
>>> > password=**
>>> > Connecting with source SQL Server database server...
>>> > Connected to Microsoft SQL Server, version '10.50.1600'
>>> > Connecting with target Postgres database server...
>>> > Exception in thread "main" java.lang.NoClassDefFoundError:
>>> > org/postgresql/Driver
>>>
>>
>> You need to ensure that postgreSQL jdbc jar files are placed in your
>> class path or under $JRE_HOME/lib/ext
>>
>> You might have already done this for SQL Server, do the same for
>> PostgreSQL too.
>>
>>
>> > at
>>> > com.edb.dbhandler.postgresql.PGConnection.(PGConnection.java:32)
>>> > at
>>> com.edb.common.MTKFactory.createMTKConnection(MTKFactory.java:228)
>>> > at
>>> >
>>> com.edb.MigrationToolkit.createNewTargetConnection(MigrationToolkit.java:5987)
>>> > at com.edb.MigrationToolkit.initToolkit(MigrationToolkit.java:3376)
>>> > at com.edb.MigrationToolkit.main(MigrationToolkit.java:1700)
>>> > Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > On Thu, Jun 16, 2016 at 8:59 PM, Neil Anderson
>>> > mailto:neil.t.ander...@gmail.com>> wrote:
>>> >
>>> > On 2016-06-16 11:13 AM, Durgamahesh Manne wrote:
>>> >
>>> > yes sir
>>> >
>>> > as per above discussion..i already looked pdf postgres plus
>>> > guide you
>>> > mentioned
>>>
>>
>> It is best that you contact EbterpriseDB support or someone who provides
>> services for EDB tools.
>>
>> >
>>> > as well as i already set password for postgres user associated
>>> with
>>> > postgres db
>>> >
>>> > On Thu, Jun 16, 2016 at 8:30 PM, Durgamahesh Manne
>>> > mailto:maheshpostgr...@gmail.com>
>>> > <mailto:maheshpostgr...@gmail.com
>>> > <mailto:maheshpostgr...@gmail.com>>> wrote:
>>> >
>>> > hi
>>> > sir
>>> > as per above discussion same error repeated even mentioned
>>> ip
>>> > address of hostname
>>> >
>>> > ./runMTK.sh -sourcedbtype sqlserver -targetSchema public
>>> > -schemaOnly
>>> > -allTables dbo
>>> >
>>> >
>>> > TARGET_DB_URL=jdbc:postgresql://192.168.168.201:5432/raghu
>>> >     <http://192.168.168.201:5432/raghu>
>>> > <http

[GENERAL] regarding table migration from sql to postgres with runmtk.sh

[Durgamahesh Manne]

Hi sir
i got following erro when i ran runmtk.sh

initially i placed the jtds driver related to sql in
/opt/postgresplus/edbmtk/lib

./runMTK.sh  -sourcedbtype sqlserver -targetdbtype postgresql
feeds_morningstar_bond_sector
Running EnterpriseDB Migration Toolkit (Build 48.0.2) ...
Source database connectivity info...
conn =jdbc:jtds:sqlserver://fxserver.trustfort.com:49888/DataFeedHandler
user =trustfort
password=**
Target database connectivity info...
conn =jdbc:postgresql://192.168.24.128:5432/dbo_sql
user =postgres
password=**
Connecting with source SQL Server database server...
Connected to Microsoft SQL Server, version '10.50.1600'
Connecting with target Postgres database server...
Exception in thread "main" java.lang.NoClassDefFoundError:
org/postgresql/Driver
at
com.edb.dbhandler.postgresql.PGConnection.(PGConnection.java:32)
at
com.edb.common.MTKFactory.createMTKConnection(MTKFactory.java:228)
at
com.edb.MigrationToolkit.createNewTargetConnection(MigrationToolkit.java:5610)
at com.edb.MigrationToolkit.initToolkit(MigrationToolkit.java:3122)
at com.edb.MigrationToolkit.main(MigrationToolkit.java:1521)
Caused by: java.lang.ClassNotFoundException: org.postgresql.Driver
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)



regards
mahesh

[GENERAL] Regarding connection drops for every few minutes

[Durgamahesh Manne]

hi

the following info generating in pg_log

LOG:  could not receive data from client: Connection reset by peer
LOG:  could not receive data from client: Connection reset by peer
LOG:  could not receive data from client: Connection reset by peer
LOG:  could not receive data from client: Connection reset by peer


Can you please provide info to stop connection drops for every few minutes


do i need to change the value of tcp related parameter or else

ssl_renegotiation parameter
 please let me know sir


regards
maheh

[GENERAL] Regarding connection drops for every few minutes

[Durgamahesh Manne]

hi

the following info generating in pg_log

LOG:  could not receive data from client: Connection reset by peer
LOG:  could not receive data from client: Connection reset by peer
LOG:  could not receive data from client: Connection reset by peer
LOG:  could not receive data from client: Connection reset by peer


Can you please provide info to stop connection drops for every few minutes


do i need to change the value of tcp related parameter or else

ssl_renegotiation parameter
 please let me know sir


regards
maheh

[GENERAL] regarding postgres feedback

[Durgamahesh Manne]

Hi Sir

i am very happy to work on PostgreSQL.Super fast response only from
postgres team regarding i asked any question related to postgres

regards
mahesh

Re: [GENERAL] Regarding connection drops for every few minutes

[Durgamahesh Manne]

Hi Sir

As per above discussion.GOOD response from PostgreSQL

i am very happy to work on PostgreSQL.Super fast response only from
postgres team regarding i asked any question related to postgres

regards
mahesh

On Fri, Mar 11, 2016 at 3:28 PM, John R Pierce  wrote:

> On 3/11/2016 1:50 AM, Durgamahesh Manne wrote:
>
>  Thanks for quick response .as per above conversation. for which parameter
> i can comment to resolve the  issue & please specify the value of parameter
> sir
>
> LOG:  could not receive data from client: Connection reset by peer
>
>
> your client is disconnecting without closing, thats all that error says,
> it doesn't say why this is happening, and without knowing why, there's no
> way to suggest a fix.
>
> I suppose you could try setting tcp_keepalives_idle, if your connections
> are staying idle for a long time and your OS doesn't default to using
> tcp_keepalive, this could help.
>
> I have no idea what a suitable value is, you didn't specify an operating
> system, a postgres version, what API your client is using, or if this is a
> localhost vs a LAN vs an internet connection, or really much of anything
> else..
>
>
>
> btw, please reply to the list,  not to me privately, thank you.
>
>
>

[GENERAL] Regarding scram authentication libpq version 10 or more

[Durgamahesh Manne]

Hi sir

This is regarding scram authentication libpq version 10. From which site  i
can download to configure libpq in order to use scram authentication in
postgres 10

i got below error while i check to access pg server

psql.bin: SCRAM authentication requires libpq version 10 or more


please let me know the detail info about scram libpq


Regards

durgamahesh m

Re: [GENERAL] Regarding scram authentication libpq version 10 or more

[Durgamahesh Manne]

On Fri, Oct 6, 2017 at 3:40 PM, Michael Paquier 
wrote:

> On Fri, Oct 6, 2017 at 5:44 PM, Durgamahesh Manne
>  wrote:
> > This is regarding scram authentication libpq version 10. From which
> site  i
> > can download to configure libpq in order to use scram authentication in
> > postgres 10
> >
> > i got below error while i check to access pg server
> >
> > psql.bin: SCRAM authentication requires libpq version 10 or more
> >
> > please let me know the detail info about scram libpq
>
> Why not beginning to look at the download page of postgresql.org? Here
> is the page:
> https://www.postgresql.org/download/
> SCRAM/SASL support in libpq is provided in any build of PostgreSQL 10,
> so this depends mainly on the distribution and environment you are
> using.
>
> In order to get support for SCRAM, the documentation provides enough
> details, beginning here:
> https://www.postgresql.org/docs/10/static/auth-methods.html#auth-password
> Basically you need to consider using password_encryption =
> 'scram-sha-256', and configure pg_hba.conf with a correct entry. If
> you are upgrading from an existing instance, you need to make sure
> that users with passwords are updated with proper SCRAM-hashed
> entries.
> --
> Michael
>



Hi sir

As per above mail conversation


i have already read complete info about New Postgres 10 in postgres.org
and i have tried to access server  by adding the
scram-sha-256 authentication in hba.conf and also have already set
password_encyption = scram-sha-256 in config then reloaded the server for
multiple times

still i am getting same error i given you earlier while i check to access
pg server with required credentials

psql.bin: SCRAM authentication requires libpq version 10 or above


i am using linux mint distrib

DISTRIB_ID=LinuxMint
DISTRIB_RELEASE=17.1
DISTRIB_CODENAME=rebecca
DISTRIB_DESCRIPTION="Linux Mint 17.1 Rebecca"
::
/etc/os-release
::
NAME="Ubuntu"
VERSION="14.04.3 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.3 LTS"
VERSION_ID="14.04"


 Regards

durgamahesh m

Re: [GENERAL] Regarding scram authentication libpq version 10 or more

[Durgamahesh Manne]

On Fri, Oct 6, 2017 at 5:56 PM, Michael Paquier 
wrote:

> On Fri, Oct 6, 2017 at 8:56 PM, Durgamahesh Manne
>  wrote:
> > i have already read complete info about New Postgres 10 in postgres.org
> and
> > i have tried to access server  by adding the
> > scram-sha-256 authentication in hba.conf and also have already set
> > password_encyption = scram-sha-256 in config then reloaded the server for
> > multiple times
> >
> > still i am getting same error i given you earlier while i check to
> access pg
> > server with required credentials
> >
> > psql.bin: SCRAM authentication requires libpq version 10 or above
>
> No idea. You may be using multiple versions of PostgreSQL in parallel,
> and the client you are using may not be the client you think it is. I
> suggest that you check the infrastructure of your host as well as the
> package repository you are using. Good luck.
> --
> Michael
>



as per the above email conversation


 Yes sir . i am using multiple versions of postgresql .i found solution for
this error. libpq error repeats when i have  tried to access pg server from
older than postgres version 10 . so however i have installed postgresql 10
in linuxss then i have accessed to (pg10) pg server with psql from
postgresql 10 version only



Regards
durgamahesh m