SQL5035N数据库需要迁移到当前版本。 [英] SQL5035N The database requires migration to the current release.
问题描述
感谢任何帮助或建议。
我们刚安装并配置了最新的DB2 v.8.1
FixPack。几天后它就死了，现在我们有了一个完全无法使用的数据库。
- - - -
一天早上，当连接给我们这个消息时，它出错了：
SQL5035N数据库需要迁移到当前的
版本。
数据库是从头开始在此服务器上新创建的。使用IXF文件导入数据
。这绝对不应该给出这个消息！
尝试了这个之后 - 我们尝试迁移：
SQL1704N数据库迁移失败。原因代码7。
接缝我们必须尝试恢复：
数据库别名或数据库名称OSTEST ;无法找到
。 SQLSTATE = 42705
我们无法恢复到同一个数据库!!
但我们可以恢复到一个新名称。
原始数据库无法删除。我们尝试了很多，但现在我们大部分时间只得到一个SQL1092N
...
SQL1092N""没有权限执行
请求的命令。
- - - -
无论出错，SQL5035N永远不会发生。
我的外部支持告诉我要完全重建服务器。
是v.8.1只是Beta软件??
我应该选择DB2 v.7.2 - （它必须是DB2）
/ Dane
孤岛惊魂（带微笑）。
您是否按照
服务器快速入门中的迁移说明进行操作指南？你必须迁移所有实例然后再转移
数据库......有两个不同的命令。
Larry Edelstein
Jep写道：感谢任何帮助或建议。
我们刚刚安装并配置了一个带有最新版本FixPack的新DB2 v.8.1。几天后它就死了，现在我们有一个完全无法使用的数据库。
- - - -
一天早上连接时出错了给了我们这个消息：
SQL5035N数据库需要迁移到当前的版本。
数据库是从头开始在这个服务器上新创建的。使用IXF文件导入数据。这绝对不应该给这个消息！
尝试了这个之后 - 我们尝试迁移：
SQL1704N数据库迁移失败。原因代码7。
我们必须尝试恢复它的接缝：
数据库别名或数据库名称OSTEST无法找到。 SQLSTATE = 42705
我们无法恢复到同一个数据库!!
但我们可以恢复到一个新名称。
原始数据库不能被删除。我们尝试了很多，但现在我们大部分时间都得到一个SQL1092N ......
SQL1092N""没有权限执行请求的命令。
- - - -
无论出现什么问题，SQL5035N都不应该出现。
<我的外部支持告诉我要完全重建服务器。
是v.8.1只是Beta软件吗？
我应该去DB2 v.7.2 - （它有成为DB2）
/ Dane
孤岛惊魂（带着微笑）。
你之前创建过db吗？你应用fixpak？如果是这样，你有可能忘记升级实例吗？
Jep <做********** @ jepweb.dk>在消息中写道
news：8o ******************************** @ 4ax.com ...
感谢任何帮助或建议。
我们刚刚安装并配置了一个带有最新版本FixPack的新DB2 v.8.1。几天后它就死了，现在我们有一个完全无法使用的数据库。
- - - -
一天早上连接时出错了给了我们这个消息：
SQL5035N数据库需要迁移到当前的版本。
数据库是从头开始在这个服务器上新创建的。使用IXF文件导入数据。这绝对不应该给这个消息！
尝试了这个之后 - 我们尝试迁移：
SQL1704N数据库迁移失败。原因代码7。
我们必须尝试恢复它的接缝：
数据库别名或数据库名称OSTEST无法找到。 SQLSTATE = 42705
我们无法恢复到同一个数据库!!
但我们可以恢复到一个新名称。
原始数据库不能被删除。我们尝试了很多，但现在我们大部分时间都得到一个SQL1092N ......
SQL1092N""没有权限执行请求的命令。
- - - -
无论出现什么问题，SQL5035N都不应该出现。
<我的外部支持告诉我要完全重建服务器。
是v.8.1只是Beta软件吗？
我应该去DB2 v.7.2 - （它有成为DB2）
/ Dane
孤岛惊魂（带着微笑）。
2月6日星期五2004 01:45:32 GMT，Larry< La *** @ nospam.net>写道：
您是否按照
服务器快速入门指南中的迁移说明进行操作？你必须迁移所有实例然后转移
数据库...有两个不同的命令。
Larry Edelstein
这项工作是由外部消费者完成的，但我很确定他只是下载了
，激活了''FP4_WR21326_WSE.exe，并执行了
安装程序.. ...
如果我读快速入门 - 我找不到可能错过的东西。
如果我读了'' ReadMe.txt'' - 他可能错过了DB2STOP，
DB" admin stop and stop of Services。这可能是原因吗？
如果从v.8.1添加了FixPack。？到v.8.1.4 - 我看不出我需要
做''两个不同的命令''。对不起。
你能指导一下吗 - 请....
/ Dane
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).
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: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).
Did you create db before you apply the fixpak? If so, is it possible you
forgot UPGRADE the instance?
"Jep" <do**********@jepweb.dk> wrote in message
news:8o********************************@4ax.com...
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).
On Fri, 06 Feb 2004 01:45:32 GMT, Larry <La***@nospam.net> wrote:
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
The job was done by an external consulent, but I''m pretty sure he just
downloaded, activated the ''FP4_WR21326_WSE.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
这篇关于SQL5035N数据库需要迁移到当前版本。的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
