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

Migration Problems - SQL0535/SQL1088W

P: n/a
I'm having some migration problems.

On Friday, I upgraded from DB2 7.2 (FP9) to DB2 8.2 (FP7), then applied
Fixpack 8. I'm running Windows XP.

My migrations did not work and I am trying to fix them manually. The
Control Center gives me SQL0535 for some of the databases and SQL1039C for
the others. I'll describe the SQL0535 problems in this note and make a
separate post for SQL1039C.

When I try to run MIGRATE DATABASE on the databases that didn't migrate,
the command returns SQL1088W (The database was created, but an error
occurred while binding the utilities. The utilities are not bound to the
database.). This gives the impression that the migration succeeded except
that the utilities won't work. In fact, I still get SQL0535 when I try to
view the database in the Control Center after the migration.

I thought that rebinding the utilities to the database might improve the
situation so I tried to run the bind command(s) recommended in the manual:

connect to OLD_CONT
bind @db2ubind.lst

Unfortunately, I get the SQL0535 again when I issue the connect. Naturally,
this prevents me from being able to bind the utilities. This reinforces my
impression that the database was NOT migrated.

What do I do now??

--
Henry

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Henry Reardon <He*****************@hotmail.com> wrote in
news:4w*******************@news20.bellglobal.com:

Small but important change to my post (and subject): The SQL0535 error
that I mentioned throughout the original version of this post should be
SQL5035N! Sorry, for the confusion!! I've changed the subject and have
changed the content below.
I'm having some migration problems.

On Friday, I upgraded from DB2 7.2 (FP9) to DB2 8.2 (FP7), then
applied Fixpack 8. I'm running Windows XP.

My migrations did not work and I am trying to fix them manually. The
Control Center gives SQL5035N for some of the databases and SQL1039C
for the others. I'll describe the SQL5035N problems in this note and
make a separate post for SQL1039C.

When I try to run MIGRATE DATABASE on the databases that didn't
migrate, the command returns SQL1088W (The database was created, but
an error occurred while binding the utilities. The utilities are not
bound to the database.). This gives the impression that the migration
succeeded except that the utilities won't work. In fact, I still get
SQL0535 when I try to view the database in the Control Center after
the migration.

I thought that rebinding the utilities to the database might improve
the situation so I tried to run the bind command(s) recommended in the
manual:

connect to OLD_CONT
bind @db2ubind.lst

Unfortunately, I get the SQL5035N again when I issue the connect.
Naturally, this prevents me from being able to bind the utilities.
This reinforces my impression that the database was NOT migrated.

What do I do now??


--
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.