Hi Steve, A couple of questions to clarify the environment please. 1. When you say the developers get the official version of the database, what does 'get' actually do? Does it get a copy of the tables, or get a backup copy? or ...? 2. Is db2admin always a local userid? Is it also defined as a domain userid? 3. What is the dbm cfg setting for SYSADM_GROUP, SYSCTRL_GROUP, SYSMAINT_GROUP? 4. What are the registry settings, specifically for DB2_GRP_LOOKUP?
Regards, Bruce Allen -----Original Message----- From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, 3 April 2002 9:38 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: [DB2EUG] UDB Remote database questions Firstly apologies if this becomes a ramble. I suspect that I have a "you're doing it the wrong way" problem rather than a "here's the fix" problem. Ob platform: UDB 7.2 NT + CoolGen I am in the process of setting up standards and procedures for a bunch of developers. I build databases from CoolGen which automagically creates and runs the DDL. I need to be able to play around on my machine but want to have a 'central' place from which developers can get the official current version of databases. I have set up UDB on a remote pc (next desk) and from my own I have managed to 'build' databases via CoolGen. To do this I have fiddled with a setting which is obviously an instance name, so when I do the build it happen on the remote and not the local. Sounds good so far but..... In order to protect the central pc the userid/password for the remote is different from the 'standard'. All developers have db2admin as their id for UDB as they can do anything they want so long as it is local. Now when I create the database on the remote I am logged on to my machines UDB as db2admin, like any developer, if I now create a database on the remote pc it appears as DBASEX owned by db2admin. If I now try to drop the remote database (because it needs changing) I am disallowed (invalid userid/password). The userid db2admin is also defined on the remote machine and I suspect this is part of the problem. Even though I am apparently that user UDB 'knows' that it is different from db2admin on my local machine. However it will not allow me to drop the database I just created. What seems odd to me is that if I log on to the remote machine as db2admin(the other one) I _am_ able to drop the database that was created from my workstation. Phew! Well if anyone can tell me I am doing this the wrong way and advise of the right way I would be most grateful, alternatively can you see an error in the way I am trying to do it this way? Regards, Steve T - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
