By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
444,246 Members | 1,451 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 444,246 IT Pros & Developers. It's quick & easy.

Migration Problems - SQL1039C

P: n/a
I need some help with migration.

As I mentioned in my previous post, I am having migration problems after
updating DB2 7.2 to DB2 8.2 and then applying FP8. I am running on
Windows XP.

None of my databases migrated successfully during the upgrade to version
8 of DB2. Some are returning SQL5035N when I look at them in the Control
Center; I am trying to migrate these manually but encountering problems;
I've mentioned them in my previous post.

The other databases are returning SQL1039C (An I/O error occurred while
accessing the database directory.) Interestingly enough, these databases
are all on Drive E: of my PC. If I list the local directory on drives C:
and D:, all goes well but the directory for drive E: returns SQL1039C.
So does any attempt to view these databases in the Control Center.

The recommended action for SQL1039C is to restore the databases that
were cataloged there from backup versions and catalog them. When I try
to restore these databases from their backups, I get SQL1013N (The
database alias name or database name cannot be found.) The article for
this error suggests checking the system database directory. When I do
that, the database is there; this is the entry:

Database alias = SFL
Database name = SFL
Database drive = E:\DB2
Database release level = a.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =

Since this is an 'Indirect' entry, the article suggests ensuring that
the database entry exists in the specified local database directory;
list database directory on e gives me SQL1039C.

I've looked at the files in the file system and they look okay, although
I'm not sure what I'm looking for.

It appears that the local database directory on E: is hosed. How do I
repair it??

--
Henry

Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.