I created an instance called KALI and then copied the sample database "sample" folder from the
dafault DB2 instance directory "C:\DB2\NODE0000" to my new instance "C:\KALI\NODE0000" directory
and the run "catalog database sample as mysample", the command executes succesfully
but when I try to connect, I get the database alias name cannot be found, but it is listed in the
I am using windows 7 db2 express-c 9.7
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
4 replies Latest Post - 2012-11-23T10:43:55Z by SystemAdmin
Pinned topic database fails to connect after catalog
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2012-11-23T10:43:55Z at 2012-11-23T10:43:55Z by SystemAdmin
Re: database fails to connect after catalog2012-11-21T12:05:10Z in response to SystemAdminHello,
The command "catalog database" creates instructs the DB2 client about an existing database on the server side, by updating the "system catalog directory".
But on the server side, the "local database directory" lists the database known and managed by the server.
When you copy the database directory, the server is not aware about the database being duplicated.
Hope it is clear...
Re: database fails to connect after catalog2012-11-22T12:12:47Z in response to SystemAdminHello,
One way to duplicate a database is to backup the database on the original instance, and restore it on the other instance.
For the new instance owner to be able to manage the new copy, you might want to :