SQL5035N The database requires migration to the current release.

[Jep]

Any help or advice appreciated.

We have just installed and configured a new DB2 v.8.1 with latest
FixPack. Just a few days later it dies and now we have a DB that is
totally unusable.

- - - -

It went all wrong one morning when connecting gave us this msg:

SQL5035N The database requires migration to the current
release.

The DB was newly created on this server from scratch. Data imported
with IXF files. This should absolutely not give this messeage !!

After trying this and that - we tried to migrate :

SQL1704N Database migration failed. Reason code "7".

It seams we had to try a Restore :

The database alias name or database name "OSTEST" could not be
found. SQLSTATE=42705

We could not Restore into the same DB !!
But we could Restore to a new name.
The original DB cannot be dropped. We tried a lot, but now we just get
an SQL1092N most of the time ...

SQL1092N "" does not have the authority to perform the
requested command.

- - - -

Whatever is wrong, the SQL5035N should never occur.

My external support tells me to do a total rebuild of the server.

Is v.8.1 just Beta software ??
Should I go for DB2 v.7.2 - (It has to be DB2)


/Dane
Far Cry (with a smile).

[Larry]

Re: SQL5035N The database requires migration to the current release.

Did you follow the migration instructions in the Quick Beginnings for
Servers guide? You have to migrate all the instances and then the
databases ... there are two different commands.

Larry Edelstein

Jep wrote:[color=blue]
> Any help or advice appreciated.
>
> We have just installed and configured a new DB2 v.8.1 with latest
> FixPack. Just a few days later it dies and now we have a DB that is
> totally unusable.
>
> - - - -
>
> It went all wrong one morning when connecting gave us this msg:
>
> SQL5035N The database requires migration to the current
> release.
>
> The DB was newly created on this server from scratch. Data imported
> with IXF files. This should absolutely not give this messeage !!
>
> After trying this and that - we tried to migrate :
>
> SQL1704N Database migration failed. Reason code "7".
>
> It seams we had to try a Restore :
>
> The database alias name or database name "OSTEST" could not be
> found. SQLSTATE=42705
>
> We could not Restore into the same DB !!
> But we could Restore to a new name.
> The original DB cannot be dropped. We tried a lot, but now we just get
> an SQL1092N most of the time ...
>
> SQL1092N "" does not have the authority to perform the
> requested command.
>
> - - - -
>
> Whatever is wrong, the SQL5035N should never occur.
>
> My external support tells me to do a total rebuild of the server.
>
> Is v.8.1 just Beta software ??
> Should I go for DB2 v.7.2 - (It has to be DB2)
>
>
> /Dane
> Far Cry (with a smile).
>[/color]

[Fan Ruo Xin]

Re: SQL5035N The database requires migration to the current release.

Did you create db before you apply the fixpak? If so, is it possible you
forgot UPGRADE the instance?

"Jep" <dontspam_jep@j epweb.dk> wrote in message
news:8o9420t3g6 71and417b946qii cbkmg8e27@4ax.c om...[color=blue]
>
> Any help or advice appreciated.
>
> We have just installed and configured a new DB2 v.8.1 with latest
> FixPack. Just a few days later it dies and now we have a DB that is
> totally unusable.
>
> - - - -
>
> It went all wrong one morning when connecting gave us this msg:
>
> SQL5035N The database requires migration to the current
> release.
>
> The DB was newly created on this server from scratch. Data imported
> with IXF files. This should absolutely not give this messeage !!
>
> After trying this and that - we tried to migrate :
>
> SQL1704N Database migration failed. Reason code "7".
>
> It seams we had to try a Restore :
>
> The database alias name or database name "OSTEST" could not be
> found. SQLSTATE=42705
>
> We could not Restore into the same DB !!
> But we could Restore to a new name.
> The original DB cannot be dropped. We tried a lot, but now we just get
> an SQL1092N most of the time ...
>
> SQL1092N "" does not have the authority to perform the
> requested command.
>
> - - - -
>
> Whatever is wrong, the SQL5035N should never occur.
>
> My external support tells me to do a total rebuild of the server.
>
> Is v.8.1 just Beta software ??
> Should I go for DB2 v.7.2 - (It has to be DB2)
>
>
> /Dane
> Far Cry (with a smile).
>[/color]

[Jep]

Re: SQL5035N The database requires migration to the current release.

On Fri, 06 Feb 2004 01:45:32 GMT, Larry <Larry@nospam.n et> wrote:
[color=blue]
>Did you follow the migration instructions in the Quick Beginnings for
>Servers guide? You have to migrate all the instances and then the
>databases ... there are two different commands.
>
>Larry Edelstein
>[/color]

The job was done by an external consulent, but I'm pretty sure he just
downloaded, activated the 'FP4_WR21326_WS E.exe, and executed the
Installer .....

If I read Quick Beginning - I don't find what could be missed.

If I read the 'ReadMe.txt' - He could have missed the DB2STOP,
DB"admin stop and stop of Services. Could this be the reason??

If the FixPack is added from v.8.1.? to a v.8.1.4 - I can't see I need
to do 'two different commands'. Sorry.

Can you guide me a little more - please ....

/Dane

[Jep]

Re: SQL5035N The database requires migration to the current release.

On Fri, 06 Feb 2004 02:16:18 GMT, "Fan Ruo Xin"
<fanruox@sbcglo bal.net> wrote:
[color=blue]
>Did you create db before you apply the fixpak? If so, is it possible you
>forgot UPGRADE the instance?
>[/color]

Thanks for your reply.

Well. The job was done by an external expert.
- - -

I don't exactly recall the order, but ....

If I read installation instruction, I don't see he have to do anything
extra. If I search for UPGRADE in the readme.txt it do not indicate
there is any MIGRATING og UPGRADE to be done ...
Or do I miss something??

(please see another thread - with the used procedure.
He might have missed to stop misc.)

/DANE

[dba]

Re: SQL5035N The database requires migration to the current release.

Jep,

There are migration instructions in the Quick Beginning's guide ... it
is not simply a matter of executing the installer. See Chapter 4 and
Chapter 6. You must migrate the instances and then the databases. There
are commands that must be executed to do this.

Larry Edelstein

Jep wrote:
[color=blue]
> On Fri, 06 Feb 2004 01:45:32 GMT, Larry <Larry@nospam.n et> wrote:
>
>[color=green]
>>Did you follow the migration instructions in the Quick Beginnings for
>>Servers guide? You have to migrate all the instances and then the
>>databases ... there are two different commands.
>>
>>Larry Edelstein
>>[/color]
>
>
> The job was done by an external consulent, but I'm pretty sure he just
> downloaded, activated the 'FP4_WR21326_WS E.exe, and executed the
> Installer .....
>
> If I read Quick Beginning - I don't find what could be missed.
>
> If I read the 'ReadMe.txt' - He could have missed the DB2STOP,
> DB"admin stop and stop of Services. Could this be the reason??
>
> If the FixPack is added from v.8.1.? to a v.8.1.4 - I can't see I need
> to do 'two different commands'. Sorry.
>
> Can you guide me a little more - please ....
>
> /Dane
>[/color]

[PM \(pm3iinc-nospam\)]

Re: SQL5035N The database requires migration to the current release.

When you're done with your problems, you could consider installing the fp4a
since you're at fp4.

http://www-306.ibm.com/cgi-bin/db2www/data/db2/udb/winos2unix/support/download.d2w/report

"Jep" <dontspam_jep@j epweb.dk> a écrit dans le message de
news:8o9420t3g6 71and417b946qii cbkmg8e27@4ax.c om...[color=blue]
>
> Any help or advice appreciated.
>
> We have just installed and configured a new DB2 v.8.1 with latest
> FixPack. Just a few days later it dies and now we have a DB that is
> totally unusable.
>
> - - - -
>
> It went all wrong one morning when connecting gave us this msg:
>
> SQL5035N The database requires migration to the current
> release.
>
> The DB was newly created on this server from scratch. Data imported
> with IXF files. This should absolutely not give this messeage !!
>
> After trying this and that - we tried to migrate :
>
> SQL1704N Database migration failed. Reason code "7".
>
> It seams we had to try a Restore :
>
> The database alias name or database name "OSTEST" could not be
> found. SQLSTATE=42705
>
> We could not Restore into the same DB !!
> But we could Restore to a new name.
> The original DB cannot be dropped. We tried a lot, but now we just get
> an SQL1092N most of the time ...
>
> SQL1092N "" does not have the authority to perform the
> requested command.
>
> - - - -
>
> Whatever is wrong, the SQL5035N should never occur.
>
> My external support tells me to do a total rebuild of the server.
>
> Is v.8.1 just Beta software ??
> Should I go for DB2 v.7.2 - (It has to be DB2)
>
>
> /Dane
> Far Cry (with a smile).
>[/color]

[Larry]

Re: SQL5035N The database requires migration to the current release.

Jep,

There are migration instructions in the Quick Beginning's guide ... it
is not simply a matter of executing the installer. See Chapter 4 and
Chapter 6. You must migrate the instances and then the databases. There
are commands that must be executed to do this.

Larry Edelstein

Jep wrote:[color=blue]
> On Fri, 06 Feb 2004 01:45:32 GMT, Larry <Larry@nospam.n et> wrote:
>
>[color=green]
>>Did you follow the migration instructions in the Quick Beginnings for
>>Servers guide? You have to migrate all the instances and then the
>>databases ... there are two different commands.
>>
>>Larry Edelstein
>>[/color]
>
>
> The job was done by an external consulent, but I'm pretty sure he just
> downloaded, activated the 'FP4_WR21326_WS E.exe, and executed the
> Installer .....
>
> If I read Quick Beginning - I don't find what could be missed.
>
> If I read the 'ReadMe.txt' - He could have missed the DB2STOP,
> DB"admin stop and stop of Services. Could this be the reason??
>
> If the FixPack is added from v.8.1.? to a v.8.1.4 - I can't see I need
> to do 'two different commands'. Sorry.
>
> Can you guide me a little more - please ....
>
> /Dane
>[/color]

[Evaluator]

Re: SQL5035N The database requires migration to the current release.

On Sat, 07 Feb 2004 03:04:35 GMT, Larry <Larry@nospam.n et> wrote:
[color=blue]
>Jep,
>
>There are migration instructions in the Quick Beginning's guide ... it
>is not simply a matter of executing the installer. See Chapter 4 and
>Chapter 6. You must migrate the instances and then the databases. There
>are commands that must be executed to do this.
>
>Larry Edelstein
>[/color]

I'm not sure you understand my problem.

We get an error "SQL5035N The database requires migration to the
current release." Yes yes. But the IBM DB2 is making a mistake.
Everything has been done on version 8.x !!

- - -

From Quick Beginning - Here I read this :

"Migration is required if you have pre-DB2 Version 8 instances and
databases you would like to continue using with DB2 Version 8."

I have NO databases from earlier Versions!! From scratch we installed
v. 8.1, then we added FixPack4, and created a database. Data is moved
from a SQL/DS using the "EXPORT of type IXF".

Why do you want us to do a Migration??
Adding FixPack 4 should not involve Migration task??


Chapter 7 reads:

Procedure:
1. Download the latest DB2 FixPak from the IBM DB2 UDB and DB2
Connect Online Support Web site at
http://www.ibm.com/software/data/db2...s2unix/support.
2. Each FixPak contains a set of Release Notes and a README. The
README provides instructions for installing the FixPak.

And the Readme file do not add any activities to this.

/Dane

[Evaluator]

Re: SQL5035N The database requires migration to the current release.

On Fri, 6 Feb 2004 12:08:43 -0500, "PM \(pm3iinc-nospam\)"
<PM(pm3iinc-nospam)@sympati co.ca> wrote:
[color=blue]
>When you're done with your problems, you could consider installing the fp4a
>since you're at fp4.
>[/color]


That is what we have done. Added a FixPack to v.8.x.

All responses think that there is Migration involved. There is not.
It's an error message that said so. And it is simply not true.

We installed a new 8.1 (on a new scratch server). Added the fixpack
you mention. Created a new database, loaded data from IXF files. And a
few days later the messages appears.

The messages makes no sense !! Please understand that it's IBM DB2
that mentions the migration. It should not be needed.

And I'm not "done with my problem".
The DB2 killed my access to data. And restore is not possible, as you
can see from the original message.

/Dane

[Larry]

Re: SQL5035N The database requires migration to the current release.

So this database is completely new and was created and loaded only after
you installed DB2 UDB V8.1? That is strange, unless it's something to do
with the IXF file picking up version information from wherever it was
created. If that is the case, you might need to do the migration. But in
any case, I would recommend that you open a PMR with IBM to troubleshoot
this.

Larry Edelstein

Evaluator wrote:[color=blue]
> On Fri, 6 Feb 2004 12:08:43 -0500, "PM \(pm3iinc-nospam\)"
> <PM(pm3iinc-nospam)@sympati co.ca> wrote:
>
>[color=green]
>>When you're done with your problems, you could consider installing the fp4a
>>since you're at fp4.
>>[/color]
>
>
>
> That is what we have done. Added a FixPack to v.8.x.
>
> All responses think that there is Migration involved. There is not.
> It's an error message that said so. And it is simply not true.
>
> We installed a new 8.1 (on a new scratch server). Added the fixpack
> you mention. Created a new database, loaded data from IXF files. And a
> few days later the messages appears.
>
> The messages makes no sense !! Please understand that it's IBM DB2
> that mentions the migration. It should not be needed.
>
> And I'm not "done with my problem".
> The DB2 killed my access to data. And restore is not possible, as you
> can see from the original message.
>
> /Dane
>
>[/color]

[Evaluator]

Re: SQL5035N The database requires migration to the current release.

On Sat, 07 Feb 2004 14:56:56 GMT, Larry <Larry@nospam.n et> wrote:

[color=blue]
>...., I would recommend that you open a PMR with IBM to troubleshoot
>this.
>
>Larry Edelstein
>[/color]

Thanks for your input.
I guess you're right.
(Someone has to be the first to get the strange errors ...)

/Dane