Verify that db2iupdt was run against both instances before trying the
backup. I've seen a number of updates where that step wasn't performed
against all instances. If you are running the administration server;
verify that its update was also run.
The explanation for this error also indicates that the service level is
also stored in the database catalog which would be moved with the
backup. Check the readme file for the last fixpack installed and verify
that all of the installation steps have been performed.
You made no mention of using a redirected restore so I assume that your
two systems use identical disk layouts. Use of online backup also means
that you should be moving the appropriate log files to the new system.
Since rollforward appeared to work; I assume you did this.
Check the db2diag.log file to see if there is additional information
available about the error. You should find it in ...\sqllib\db2dump.
If you still can't figure anything out; try the following:
1. Create a new database.
2. Take an offline backup of the new database and restore it to your
other system.
3. Try to access the restored database's catalog tables.
You can do this using both systems as the starting point. Seeing what
works and doesn't work will help you isolate where the problem lies.
Phil Sherman
Andy J wrote:
HI Phlilip
From db2.log , both servers are at Service Level: WR21294 as show below.
Version: 7, Release: 2, Modification: 5, Service Level: WR21294
Querying the system...
Windows 2000 Version
Regards
Andy
Philip Sherman <ps******@ameritech.net> wrote in message news:<5h*******************@newssvr19.news.prodigy .com>...
Did you check that BOTH systems are at the same service level?
Phil Sherman
