| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
| Cc: | Raghavendra Rao <raghavendra(dot)rao(at)enterprisedb(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: regarding schema only migration from sqlserver to postgres with runmtk.sh |
| Date: | 2016-06-15 13:00:46 |
| Message-ID: | CAKFQuwYoUEt=gy7ujmp8_Sxnkc1WCwufnKfQu5H8Q_w=XRJF8w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, Jun 15, 2016 at 8:31 AM, Durgamahesh Manne <
maheshpostgres9(at)gmail(dot)com> wrote:
> Running EnterpriseDB Migration Toolkit (Build 49.0.4) ...
>
You should contact the supplier of this tool using their support
channels. The community is not responsible for this product.
I will note that by default PostgreSQL is not setup with a password on the
postgres (bootstrap) account. If the script in question isn't doing stuff
in the background to ensure PostgreSQL will accept a JDBC connection as the
postgres user with password you will need to do that manually. The
documentation covers how to go about setting up tcp/ip based access both on
the listening specification and within pg_hba.conf, as well as how to
assign a password to a user that does not have one.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2016-06-15 13:27:32 | Re: Question about RUM-index |
| Previous Message | Durgamahesh Manne | 2016-06-15 12:31:26 | regarding schema only migration from sqlserver to postgres with runmtk.sh |