SQL30061N Cannot find remote DB 'RSAMPLE'
Jean-Marc Blaise
I have a strange error in cataloging a remote DB. Got the message:
SQL30061N The database alias or database name "RSAMPLE " was
not
found at the remote node.
If I catalog the remote db as RSAMPL, it works ...
Below is the testcase, hope you can reproduce.
Best regards,
Jean-Marc
Testcase:
CLIENT is Windows V8 FP5
SERVER is Linux Stinger
- create sample db linux
from the client:
- catalog tcpip node rnode ... remote_instance db2inst1 ... (attach is OK)
- catalog db sample as rsample at node rnode
- connect to rsample ==> KO (don't get SQL30082 but SQL30061)
- uncatalog db rsample and catalog as rsampl
- connect to rsampl ==> OK (get SQL30082)
PM (pm3iinc-nospam)
What happens when you db2 terminate before connect to rsample ?
PM
"Jean-Marc Blaise" <bla...@nospam.com> a écrit dans le message de
news:c641t8$5g22$1...@news.boulder.ibm.com...
Jean-Marc Blaise
I don't think this is a refresh problem, because I did on the client the
operations indicated without any terminate:
-catalog db sample as rsample
-connect to rsample -> SQL30061 ko
-uncatalog db rsample
-catalog db sample as rsampl
-connect to rsampl -> SQL30082 ok
If I test this in the configuration:
CLIENT is Linux V8 FP5
SERVER is Windows Stinger
a catalog db ... as rsample then connect to rsample gives SQL30082...
Seems strange, unless I was not awake ... can you reproduce ?
I will try the test to issue a TERMINATE before the connect.
Cheers,
JM
"PM (pm3iinc-nospam)" <Pm3iinc...@sympatico.ca> a écrit dans le message
de news:c64lk0$66pc$1...@news.boulder.ibm.com...
PM (pm3iinc-nospam)
All i can currently do is local/windows.
Not sure if the following is enough to mimic real remote operations.
I built my own version of catalog tcpip node to make it work.
(i get the hex Application Id though=remote used)
-----------------------------------------------------
rem DB2 CREATE DATABASE TEST
IF NOT %ERRORLEVEL%==0 GOTO :ERR
rem DB2 catalog tcpip node DB2TCPR0 REMOTE_INSTANCE DB2 SYSTEM pm3izzzz
DB2 catalog tcpip node DB2TCPR0 remote 127.0.0.1 SERVER DB2c_DB2
REMOTE_INSTANCE DB2
IF NOT %ERRORLEVEL%==0 GOTO :ERR
DB2 ATTACH TO DB2TCPR0 USER something USING something
IF NOT %ERRORLEVEL%==0 GOTO :ERR
DB2 catalog db TEST as rTEST at node DB2TCPR0
IF NOT %ERRORLEVEL%==0 GOTO :ERR
DB2 connect to rTEST USER something USING something
IF NOT %ERRORLEVEL%==0 GOTO :ERR
DB2 uncatalog db rTEST
IF NOT %ERRORLEVEL%==0 GOTO :ERR
DB2 catalog db TEST as rTEST at node DB2TCPR0
IF NOT %ERRORLEVEL%==0 GOTO :ERR
GOTO :ENDCMD
:ERR
@ECHO FOUND ERRORS BEFORE END OF SCRIPT
:ENDCMD
@ECHO NORMAL END OF SCRIPT
-----------------------------------------------------
I think there were restrinctions in v8 for create db from downlevel clients.
(maybe similar restrictions exist for catalog?)
Usage notes
The database manager creates the node directory when the first node is
cataloged (that is, when the first CATALOG...NODE command is issued). On a
Windows client, it stores and maintains the node directory in the instance
subdirectory where the client is installed. On an AIX client, it creates the
node directory in the DB2 installation directory.
SQL30082 RC=?
Anything special in your db2set or command line variables? (and/or windows
environment variables DB2* )
I remember having some problems with windows environment DB2INSTANCE not
overriding db2set.
PM
"Jean-Marc Blaise" <bla...@nospam.com> a écrit dans le message de
news:c641t8$5g22$1...@news.boulder.ibm.com...
Jean-Marc Blaise
from the client I did a CATALOG DB RSAMPLE AT NODE LINUX
Then connected, and got an error
so UNCATALOGued
Then CATALOG DB SAMPLE AS RSAMPLE AT NODE LINUX
... and ended up with the error described.
I should have done a TERMINATE before attempting to CATALOG again.
Strange behaviour that with the application that did the CATALOG, an
UNCATALOG does not eliminate the entry in the cache ...
Thanks again for your help & Best regards,
Jean-Marc
"PM (pm3iinc-nospam)" <Pm3iinc...@sympatico.ca> a écrit dans le message
de news:c678oj$54cc$1...@news.boulder.ibm.com...