Ah, OK now we're getting somewhere. Remember a few days back I said "the
only time I ever saw this error was when there is a mixup between V7 and V8,
but I had no reason to suspect that in this case"? When I said that I
didn't know you had removed V8 and installed V7. I'm quite sure now that
this is *exactly* the problem.
Here's what I suggest you do. Assuming there are no databases on your
local system that you need to keep (sound like you can't access them
anyway).
1) Remove existing Local Database Directories and database physical files
On *any* partition that has a database on it, you should have a directory
by the same name as the DB2 Instance you are using (e.g., "C:\DB2"). Either
remove or rename those directories so they are out of the way.
2) Remove the System Database Directory
Either remove or rename "%DB2PATH%\%DB2INSTANCE%\sqldbdir" so it is out
of the way.
After this you should be able to create new local databases.
Here's what I believe happened... When you installed V7 and created local
databases, DB2 created the Local Database Directory on your hard disk (e.g.,
"C:\DB2\NODE0000\SQLDBDIR"). In Version 8, the internal structure of that
Local Database Directory changed, so when you installed V8 it was migrated.
Then when you uninstalled V8 the databases and the Local Database Directory
are left intact. When you re-installed V7, it is trying to use the Local
Database Directory, but it is still migrated to V8. DB2 cannot "un-migrate"
a database or a Local Database Directory.
--
Larry Menard
IBM Workstation Database (DB2) Performance Team
Defender of Geese and of All Things Natural
"Liao" <member32143@dbforums.com> wrote in message
news:3124601.1058489435@dbforums.com...
>
> Larry,
>
> I am sorry to bother you. Thanks a lot for your help.
>
> db2 => create database testdb
> SQL1039C An I/O error occurred while accessing the database directory.
> SQLSTATE=58031
>
>
> db2 => list node directory
>
> Node Directory
>
> Number of entries in the directory = 1
>
> Node 1 entry:
>
> Node name = DB2CTLSV
> Comment =
> Protocol = LOCAL
> Instance name = DB2CTLSV
>
>
> > I noticed that your SATCTLDB seems to be cataloged as a REMOTE
> > database.
>
> I have done nothing to SATCTLDB. I am also supprised to see the result
> you mentioned. What I have done is" installed DB2 8.1 first then
> uninstall DB2 8.1 and install 7.2". I happen to do the same thing as Hu
> song and get the same result. I don't know what should I do now. Maybe I
> have to format my disk, reinstall window2000 and DB2. Because even I
> have uninstalled db2 7.2(the db2 director dispeared), reinstalled db2
> 7.2, I got the same result.
>
>
> Liao
>
> --
> Posted via http://dbforums.com