Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2004
    Posts
    3

    Unhappy Unanswered: Trouble with uncataloging a database

    I have uncataloged this DB from the local and system catalog, but it is still there. Any ideas?

    db2 => uncatalog database trade3db
    SQL1013N The database alias name or database name "trade3db" could not be
    found. SQLSTATE=42705

    db2 => drop database trade3db
    SQL1013N The database alias name or database name "TRADE3DB" could not be
    found. SQLSTATE=42705

    db2 => create db trade3db
    SQL1005N The database alias "TRADE3DB" already exists in either the local database directory or system database directory.

  2. #2
    Join Date
    Sep 2002
    Posts
    41
    On Unix,
    This can happen if your NODE0000 directory still has pointer of Database you are creating.

    If you don't have any other working database on that instance then you can delete that NODE0000 directory and your pointers will go away and when you create database next time DB2 creates NODE0000 directory and database creates sucessfully.

    This is on Solaris. I hope this applies to other plateforms too.

    Hope this will help.
    Kuckoo

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    catalog database TRADE3DB on c:

    will catalog the local db directory on system db directory ...

    drop database TRADE3DB

    will drop the database ...

    Cheers
    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  4. #4
    Join Date
    Mar 2004
    Location
    Toronto, ON, Canada
    Posts
    513
    Gory detail:

    There are two catalogs (or more!), a system catalog and then one for each path you've created a database on.

    db2 LIST DATABASE DIRECTORY
    -> System catalog

    db2 LIST DATABASE DIRECTORY ON /my/path/where/databases/are
    -> Physical database catalog

    You can only connect/drop/etc. if they are in the System catalog.

    In general, you DON'T want to delete the NODE0000 directory... you can always get around this by re-cataloging and dropping like sathyaram_s suggests!
    --
    Jonathan Petruk
    DB2 Database Consultant

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •