vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi I try to restore 2 database from V8 fix pack 12 to V9 One of them can restore OK while the other give the below error message Can any one give me some hint of how to fix this problem SQL2519N The database was restored but the restored database was not migrated to the current release. Error "-1704" with tokens "3" is returned. Explanation: The backup image contains a previous release of the database. After the database files were restored, an attempt was made to migrate the database to the current release. The migration failed. The utility finishes processing but the database was not migrated. User Response: Look at the SQLCODE (message number) in the message for more information. Make changes and submit the Migrate command before using the database. |
| |||
| I have run the command db2 migrate database DATABASENAME Then I get this error message SQL1074N database migation failed. reason code "3" Question The above error code mean not enough log space But how do I increase the log space with without being able to connect to the database? "Tuong Do" <tuong@somewhere.on.earth> wrote in message news:44e695d2$0$5108$afc38c87@news.optusnet.com.au ... > Hi > I try to restore 2 database from V8 fix pack 12 to V9 > One of them can restore OK while the other give the below error message > Can any one give me some hint of how to fix this problem > > > > SQL2519N The database was restored but the restored database was > not migrated to the current release. Error "-1704" with tokens > "3" is returned. > > Explanation: > > The backup image contains a previous release of the database. > After the database files were restored, an attempt was made to > migrate the database to the current release. The migration > failed. > > The utility finishes processing but the database was not > migrated. > > User Response: > > Look at the SQLCODE (message number) in the message for more > information. Make changes and submit the Migrate command before > using the database. > > > |
| ||||
| In article <44e6980e$0$5111$afc38c87@news.optusnet.com.au>, tuong@somewhere.on.earth says... > I have run the command > > db2 migrate database DATABASENAME > > Then I get this error message > > SQL1074N database migation failed. reason code "3" > > Question > The above error code mean not enough log space > But how do I increase the log space with without being able to connect to > the database? > > You don't need a connection to the database. Using the command 'db2 update db cfg using <logfilsiz .. logprimary .. logsecond ..> deferred' doesn't activate the db and when submitting the 'migrate db' after that the new values will be used. |