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

On Fri, Jun 17, 2016 at 2:16 PM, Durgamahesh Manne <
maheshpostgres9(at)gmail(dot)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 <sameer(dot)kumar(at)ashnik(dot)com>
> 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, <neil(dot)t(dot)anderson(at)gmail(dot)com>
>> 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.<init>(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
>>> > <neil(dot)t(dot)anderson(at)gmail(dot)com <mailto:neil(dot)t(dot)anderson(at)gmail(dot)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
>>> > <maheshpostgres9(at)gmail(dot)com <mailto:maheshpostgres9(at)gmail(dot)com>
>>> > <mailto:maheshpostgres9(at)gmail(dot)com
>>> > <mailto:maheshpostgres9(at)gmail(dot)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.
>>> > 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(dot)g(dot)johnston(at)gmail(dot)com
>>> > <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>
>>> > <mailto:david(dot)g(dot)johnston(at)gmail(dot)com
>>> > <mailto:david(dot)g(dot)johnston(at)gmail(dot)com>>> wrote:
>>> >
>>> > On Thu, Jun 16, 2016 at 10:19 AM, Durgamahesh Manne
>>> > <maheshpostgres9(at)gmail(dot)com
>>> > <mailto:maheshpostgres9(at)gmail(dot)com>
>>> > <mailto:maheshpostgres9(at)gmail(dot)com
>>> > <mailto:maheshpostgres9(at)gmail(dot)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(at)postgresql(dot)org
>>> > <mailto:pgsql-general(at)postgresql(dot)org>)
>>> > To make changes to your subscription:
>>> > http://www.postgresql.org/mailpref/pgsql-general
>>> >
>>> >
>>>
>>> That appears to be an issue finding the right Java library to connect to
>>> Postgres. The documentation here outlines where to download and install
>>> the JDBC drivers
>>>
>>> https://www.enterprisedb.com/docs/en/9.5/migrate/Postgres_Plus_Migration_Guide.1.13.html#
>>>
>>>
>>> --
>>> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
>>> To make changes to your subscription:
>>> http://www.postgresql.org/mailpref/pgsql-general
>>>
>> --
>> --
>> Best Regards
>> Sameer Kumar | DB Solution Architect
>> *ASHNIK PTE. LTD.*
>>
>> 101 Cecil Street, #11-11 Tong Eng Building, Singapore 069 533
>>
>> T: +65 6438 3504 | M: +65 8110 0350 | www.ashnik.com
>>
>
>

as per above conversation

Sorry for top post to respected team who replied back regarding issue on
migration from sql to postgres with runmtk.sh

earlier i got this error by running runmtk.xh
MTK-10045: The URL specified for the "target" database is
invalid.

Now i fixed that issue for postgres database connectivity on data
migration from sql to postgres

now i connected to postgreSQL

Connecting with target EnterpriseDB database server...
Connected to PostgreSQL, version '9.1.22'
Importing sql server schema dbo...

andrian sir correct you mentioned

postgres connection established when i mentioned edb instead of postgresql
at TARGET URL in tool properties

now some error in copy the tables into postgres from sql

i can try to reslove the same

Great postgresql always world leading no1 database

(jdbc driver required that was related to another error not required now)

thanks for the information