V9.7数据库恢复到另一个实例的权限问题
最近在v9.7的db2inst1下面创建了个数据库testdb然后做了个备份，又创建了个实例db2inst2，在这个实例下对testdb做了个重定向恢复恢复后一切都好用，db2inst2在用call get_dbsize_info的时候报错，然后准备重新绑定一下st_admin.bnd，但是报没有权限。。。以前一直用v9.5，实例用户组...显示全部
查看其它 4 个回答wencycool的回答
这个你要先把数据库在db2inst2上创建好，然后在恢复覆盖就可以了。
参考如下：
When restoring to an existing database, the restore utility performs the following actions:
Deletes table, index, and long field data from the existing database and replaces it with data from the backup image.
Replaces table entries for each table space that you are restoring.
Retains the recovery history file unless it is damaged or has no entries. If the recovery history file is damaged or contains no entries, the database manager copies the file from the backup image. If you want to replace the recovery history file, you can issue the RESTORE DATABASE command with the REPLACE HISTORY FILE parameter.
Retains the authentication type for the existing database.
Retains the database directories for the existing database. The directories define where the database is located and how it is cataloged.
Compares the database seeds. If the seeds are different, the utility performs the following actions:
Deletes the logs that are associated with the existing database.
Copies the database configuration file from the backup image.
Sets the NEWLOGPATH parameter for the RESTORE DATABASE command to the value of the logpath database configuration parameter if you specified the NEWLOGPATH parameter.
If the database seeds are the same, the utility performs the following actions:
Deletes all log files if the image is for a non-recoverable database.
Deletes empty log files if the image is for a recoverable database. Non-empty log files are not affected.
Retains the current database configuration file.
Sets the NEWLOGPATH parameter for the RESTORE DATABASE command to the value of the logpath database configuration parameter if you specified the NEWLOGPATH parameter. Otherwise, the utility copies the current log path to the database configuration file. Validates the log path. If the database cannot use the path, the utility changes the database configuration to use the default log path
参考如下：
When restoring to an existing database, the restore utility performs the following actions:
Deletes table, index, and long field data from the existing database and replaces it with data from the backup image.
Replaces table entries for each table space that you are restoring.
Retains the recovery history file unless it is damaged or has no entries. If the recovery history file is damaged or contains no entries, the database manager copies the file from the backup image. If you want to replace the recovery history file, you can issue the RESTORE DATABASE command with the REPLACE HISTORY FILE parameter.
Retains the authentication type for the existing database.
Retains the database directories for the existing database. The directories define where the database is located and how it is cataloged.
Compares the database seeds. If the seeds are different, the utility performs the following actions:
Deletes the logs that are associated with the existing database.
Copies the database configuration file from the backup image.
Sets the NEWLOGPATH parameter for the RESTORE DATABASE command to the value of the logpath database configuration parameter if you specified the NEWLOGPATH parameter.
If the database seeds are the same, the utility performs the following actions:
Deletes all log files if the image is for a non-recoverable database.
Deletes empty log files if the image is for a recoverable database. Non-empty log files are not affected.
Retains the current database configuration file.
Sets the NEWLOGPATH parameter for the RESTORE DATABASE command to the value of the logpath database configuration parameter if you specified the NEWLOGPATH parameter. Otherwise, the utility copies the current log path to the database configuration file. Validates the log path. If the database cannot use the path, the utility changes the database configuration to use the default log path
浏览1226