 | |
Re: updgrade from 5.5 to 8.0.2
sybase.public.sqlanywhere.replication sybase.public.sqlanywhere.replication
 |
| | Thread Tools | Display Modes |
#1
 
| |||
| |||
|
Re: updgrade from 5.5 to 8.0.2 -
12-22-2004
, 12:29 PM
|
I am in the middle of testing an updgrade of a database, the consolidated db, from 5.5 to 8.0.2. I know about the limited support and other issues. I follow the directions as detailed in help doc: 1. Shut down the existing database. 2. Perform a full off-line backup by copying the database and transaction log files to a secure location. 3. Run the dbtran utility to display the starting offset and ending offset of the database's current transaction log file. Note the ending offset for later use. 4. Rename the current transaction log file so that it is not modified during the unload process, and place this file in the off-line directory. 5.Start the existing database. 6. Unload the database. 7. Shut down the existing database. This database and any log file created in this and the previous step is no longer needed. 8. Initialize a new database. 9. Reload the data into the new database. 10. Shut down the new database. 11. Erase the current transaction log file for the new database. 12. Use dblog on the new database with the ending offset noted in step 3 as the -z option, and also set the relative offset to zero. dblog -x 0 -z 137829 database-name.db 13. When you run the Message Agent, provide it with the location of the original off-line directory on its command line. What happens is that I get the following error: I. 12/22 08:15:30. Scanning logs starting at offset 018416416494 E. 12/22 08:15:30. Unable to find log offset 018416416494 E. 12/22 08:15:30. Sending messages failed I. 12/22 08:15:31. Execution completed The archived log file ending offset is 18416426984. What can I do at this point? TIA Steve DeWitt |
#2
| |||
| |||
|
|
Posted originally on the sybase.public.sqlanywhere.general newsgroup: =============================================== Since the ending offset of the version 5 log file is 18,416,426,984 and that is greater than 18,416,416,494 (by about 10,490) the error E. 12/22 08:15:30. Unable to find log offset 018416416494 can only mean one of 3 things 1 - You did not provide dbremote with the (correct?) off-line directory path; the one where you move the renamed version 5.x log (from step#4) to. 2 - Your 5.x log happens to also be newer than that offset. (doing a dbtran again, as in step #3 and note if the starting offset is also greater than that offset) If it is, you should have older, already renamed transaction logs from before that time, and you should also copy those into this same directory. OR 3 - You have hit some ancient incompatability. I believe the the version 8 dbremote/dbtool8 facility can still handle version 5 transaction logs, but if neither of the above prove to be your problem, we may have to look into this possiblity. "Steve DeWitt" <everythingguitars (AT) hotmail (DOT) com> wrote in message news:41c9a44f$1 (AT) forums-1-dub (DOT) .. I am in the middle of testing an updgrade of a database, the consolidated db, from 5.5 to 8.0.2. I know about the limited support and other issues. I follow the directions as detailed in help doc: 1. Shut down the existing database. 2. Perform a full off-line backup by copying the database and transaction log files to a secure location. 3. Run the dbtran utility to display the starting offset and ending offset of the database's current transaction log file. Note the ending offset for later use. 4. Rename the current transaction log file so that it is not modified during the unload process, and place this file in the off-line directory. 5.Start the existing database. 6. Unload the database. 7. Shut down the existing database. This database and any log file created in this and the previous step is no longer needed. 8. Initialize a new database. 9. Reload the data into the new database. 10. Shut down the new database. 11. Erase the current transaction log file for the new database. 12. Use dblog on the new database with the ending offset noted in step 3 as the -z option, and also set the relative offset to zero. dblog -x 0 -z 137829 database-name.db 13. When you run the Message Agent, provide it with the location of the original off-line directory on its command line. What happens is that I get the following error: I. 12/22 08:15:30. Scanning logs starting at offset 018416416494 E. 12/22 08:15:30. Unable to find log offset 018416416494 E. 12/22 08:15:30. Sending messages failed I. 12/22 08:15:31. Execution completed The archived log file ending offset is 18416426984. What can I do at this point? TIA Steve DeWitt |
#3
| |||
| |||
|
|
I have checked and re-checked and had someone else check the results and we have followed the directions to the letter. We are going to do the whole thing over to be sure we have followed the directions. This takes some 5 hours to do. The database is 7+ Gig. I will let you know what happens. thanks Steve Nick Elson wrote: Posted originally on the sybase.public.sqlanywhere.general newsgroup: =============================================== Since the ending offset of the version 5 log file is 18,416,426,984 and that is greater than 18,416,416,494 (by about 10,490) the error E. 12/22 08:15:30. Unable to find log offset 018416416494 can only mean one of 3 things 1 - You did not provide dbremote with the (correct?) off-line directory path; the one where you move the renamed version 5.x log (from step#4) to. 2 - Your 5.x log happens to also be newer than that offset. (doing a dbtran again, as in step #3 and note if the starting offset is also greater than that offset) If it is, you should have older, already renamed transaction logs from before that time, and you should also copy those into this same directory. OR 3 - You have hit some ancient incompatability. I believe the the version 8 dbremote/dbtool8 facility can still handle version 5 transaction logs, but if neither of the above prove to be your problem, we may have to look into this possiblity. "Steve DeWitt" <everythingguitars (AT) hotmail (DOT) com> wrote in message news:41c9a44f$1 (AT) forums-1-dub (DOT) .. I am in the middle of testing an updgrade of a database, the consolidated db, from 5.5 to 8.0.2. I know about the limited support and other issues. I follow the directions as detailed in help doc: 1. Shut down the existing database. 2. Perform a full off-line backup by copying the database and transaction log files to a secure location. 3. Run the dbtran utility to display the starting offset and ending offset of the database's current transaction log file. Note the ending offset for later use. 4. Rename the current transaction log file so that it is not modified during the unload process, and place this file in the off-line directory. 5.Start the existing database. 6. Unload the database. 7. Shut down the existing database. This database and any log file created in this and the previous step is no longer needed. 8. Initialize a new database. 9. Reload the data into the new database. 10. Shut down the new database. 11. Erase the current transaction log file for the new database. 12. Use dblog on the new database with the ending offset noted in step 3 as the -z option, and also set the relative offset to zero. dblog -x 0 -z 137829 database-name.db 13. When you run the Message Agent, provide it with the location of the original off-line directory on its command line. What happens is that I get the following error: I. 12/22 08:15:30. Scanning logs starting at offset 018416416494 E. 12/22 08:15:30. Unable to find log offset 018416416494 E. 12/22 08:15:30. Sending messages failed I. 12/22 08:15:31. Execution completed The archived log file ending offset is 18416426984. What can I do at this point? TIA Steve DeWitt |
#4
| |||
| |||
|
|
Then maybe you did hit a case where #3 holds. You could consider doing a 'remote reset' to force dbremote to skip the version 5.5 log. If you can reach a point where all your remotes and consolidated are quiesced (fully caught up and no pending operations). You can consider doing this. "Steve DeWitt" <everythingguitars (AT) hotmail (DOT) com> wrote in message news:41c9dc4a (AT) forums-1-dub (DOT) .. I have checked and re-checked and had someone else check the results and we have followed the directions to the letter. We are going to do the whole thing over to be sure we have followed the directions. This takes some 5 hours to do. The database is 7+ Gig. I will let you know what happens. thanks Steve Nick Elson wrote: Posted originally on the sybase.public.sqlanywhere.general newsgroup: =============================================== Since the ending offset of the version 5 log file is 18,416,426,984 and that is greater than 18,416,416,494 (by about 10,490) the error E. 12/22 08:15:30. Unable to find log offset 018416416494 can only mean one of 3 things 1 - You did not provide dbremote with the (correct?) off-line directory path; the one where you move the renamed version 5.x log (from step#4) to. 2 - Your 5.x log happens to also be newer than that offset. (doing a dbtran again, as in step #3 and note if the starting offset is also greater than that offset) If it is, you should have older, already renamed transaction logs from before that time, and you should also copy those into this same directory. OR 3 - You have hit some ancient incompatability. I believe the the version 8 dbremote/dbtool8 facility can still handle version 5 transaction logs, but if neither of the above prove to be your problem, we may have to look into this possiblity. "Steve DeWitt" <everythingguitars (AT) hotmail (DOT) com> wrote in message news:41c9a44f$1 (AT) forums-1-dub (DOT) .. I am in the middle of testing an updgrade of a database, the consolidated db, from 5.5 to 8.0.2. I know about the limited support and other issues. I follow the directions as detailed in help doc: 1. Shut down the existing database. 2. Perform a full off-line backup by copying the database and transaction log files to a secure location. 3. Run the dbtran utility to display the starting offset and ending offset of the database's current transaction log file. Note the ending offset for later use. 4. Rename the current transaction log file so that it is not modified during the unload process, and place this file in the off-line directory. 5.Start the existing database. 6. Unload the database. 7. Shut down the existing database. This database and any log file created in this and the previous step is no longer needed. 8. Initialize a new database. 9. Reload the data into the new database. 10. Shut down the new database. 11. Erase the current transaction log file for the new database. 12. Use dblog on the new database with the ending offset noted in step 3 as the -z option, and also set the relative offset to zero. dblog -x 0 -z 137829 database-name.db 13. When you run the Message Agent, provide it with the location of the original off-line directory on its command line. What happens is that I get the following error: I. 12/22 08:15:30. Scanning logs starting at offset 018416416494 E. 12/22 08:15:30. Unable to find log offset 018416416494 E. 12/22 08:15:30. Sending messages failed I. 12/22 08:15:31. Execution completed The archived log file ending offset is 18416426984. What can I do at this point? TIA Steve DeWitt |
|
« Previous Thread
|
Next Thread »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.