Re: [Squirrel-sql-users] Accessing Same Database Name in Different Environments

[David C. <dl...@wi...>]

Note that I found how to catalog a database alias, but I don't understand
why I am getting this error.

db2 catalog database txvision as txvision_dev at node devnode
> SQL0104N  An unexpected token "txvision_dev" was found following "AS".
Expected tokens may include:  "<database-alias>".  SQLSTATE=42601

Sincerely,

Dave Clark
--
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio  45439  USA
(937) 294-5331


On Mon, Oct 6, 2025 at 9:11 AM David Clark <dl...@wi...> wrote:

> We have a DB2/LUW database in a full development life-cycle environment.
> As such, the same database name exists on different servers.  SQUirrell,
> itself, supports the use of aliases to handle this situation.  However, how
> do I do the same thing from the DB2 perspective?  Meaning, I already have
> the following for the development environment.
>
> db2 catalog tcpip node devnode remote larsond01 server 50000
> db2 catalog database txvision at node devnode
>
> But when I attempt to do the same for the QA environment, I get an error
> message.
>
> db2 catalog tcpip node qanode remote larsonq01 server 50000
> > DB20000I  The CATALOG TCPIP NODE command completed successfully.
> db2 catalog database txvision at node qanode
> > SQL1005N  The database alias "txvision" already exists in either the
> local
> database directory or system database directory.
>
> I can specify a unique TCPIP node name for the new server name, but not
> the same database name at the new node.  Is there a DB2 alias I can specify
> in this situation?
>
> Sincerely,
>
> Dave Clark
> --
> Winsupply Group Services
> 3110 Kettering Boulevard
> Dayton, Ohio  45439  USA
> (937) 294-5331
>