Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / DB2 Topics / February 2006

Tip: Looking for answers? Try searching our database.

2 default database paths have been used - how do I not screw up?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
aj - 16 Feb 2006 14:45 GMT
I used the Create Database Wizard in CC to create a quick test
database.  However, I screwed up when it asked about what
database path (DFTDBPATH) to use.  Rather than using the DFTDBPATH
that is the default in my dbm cfg, I specified a database path
one subdir *under* my default DFTDBPATH.

So now I have 2 database dirs w/ SQL00001 dirs in them.  One is
the test DB, the other is my production DB.   If I drop the test
DB, will DB2 actually drop my production DB?

How can I safely drop that test DB so that I can recreate it under
the correct default DFTDBPATH?

Any help appreciated.

aj
aj - 16 Feb 2006 16:56 GMT
Yes, I know -- it was a newbie question.  But I create and drop
DB's infrequently, so I was skittish.

I found a very helpful post by Larry Menard:
http://tinyurl.com/8epwg

Using the System and Local Database Directory, and the
db2 list database directory
command, I could see that DB2 knew what was what and where
with the test DB.

thanks

aj

> I used the Create Database Wizard in CC to create a quick test
> database.  However, I screwed up when it asked about what
[quoted text clipped - 12 lines]
>
> aj
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.