![]() | |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#3
| |||
| |||
|
|
Thank you for posting -- we will indeed see if we can replicate here, too. What file format are you running? 7.x? 8.x? 9.0? 9.5? As a workaround, if you have newer files, then you can disable the Limit Segment Size" setting and rebuild the files. Not only should this avoid the issue, but it should also provide some performance gains for these sites. Goldstar Software Inc. Pervasive-based Products, Training & Services Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive Training - March 2010 in Chicago *** Michael Last wrote: Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#4
| |||
| |||
|
|
Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#5
| |||
| |||
|
|
Michael: I've duplicated your issue on the x64 engine, too. It definitely is nasty and brings the system to its knees. BB Michael Last wrote: Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#6
| |||
| |||
|
|
Hi Bill, Pervasive entered a bug, Aus#58685 and did send us a devbuild today . Have tested it and the problem is solved now. The problem only occurs with PSQL10, older versions PSQL9 or PSQL8 did not have that problem. Michael Last "BtrieveBill" <billbach (AT) goldstarsoftware (DOT) com> schrieb im Newsbeitrag news:CtydncXOD4DZm77WnZ2dnUVZ_gSdnZ2d (AT) speakeasy (DOT) net... Michael: I've duplicated your issue on the x64 engine, too. It definitely is nasty and brings the system to its knees. BB Michael Last wrote: Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#7
| |||
| |||
|
|
Glad it worked for you. I tried on a Vista64 machine, and it didn't help me yet. Goldstar Software Inc. Pervasive-based Products, Training & Services Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive Training - March 2010 in Chicago *** Michael Last wrote: Hi Bill, Pervasive entered a bug, Aus#58685 and did send us a devbuild today . Have tested it and the problem is solved now. The problem only occurs with PSQL10, older versions PSQL9 or PSQL8 did not have that problem. Michael Last "BtrieveBill" <billbach (AT) goldstarsoftware (DOT) com> schrieb im Newsbeitrag news:CtydncXOD4DZm77WnZ2dnUVZ_gSdnZ2d (AT) speakeasy (DOT) net... Michael: I've duplicated your issue on the x64 engine, too. It definitely is nasty and brings the system to its knees. BB Michael Last wrote: Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#8
| |||
| |||
|
|
Which devbuild version did you use? "BtrieveBill" <billbach (AT) goldstarsoftware (DOT) com> schrieb im Newsbeitrag news:RNydndIdEZ1ebLLWnZ2dnUVZ_t-dnZ2d (AT) speakeasy (DOT) net... Glad it worked for you. I tried on a Vista64 machine, and it didn't help me yet. Goldstar Software Inc. Pervasive-based Products, Training & Services Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive Training - March 2010 in Chicago *** Michael Last wrote: Hi Bill, Pervasive entered a bug, Aus#58685 and did send us a devbuild today . Have tested it and the problem is solved now. The problem only occurs with PSQL10, older versions PSQL9 or PSQL8 did not have that problem. Michael Last "BtrieveBill" <billbach (AT) goldstarsoftware (DOT) com> schrieb im Newsbeitrag news:CtydncXOD4DZm77WnZ2dnUVZ_gSdnZ2d (AT) speakeasy (DOT) net... Michael: I've duplicated your issue on the x64 engine, too. It definitely is nasty and brings the system to its knees. BB Michael Last wrote: Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#9
| |||
| |||
|
|
They sent me one which included 10.21.999. All of the dev builds are the same. However, I was running a 64-bit server, so perhaps it just didn't fix it. BB Michael Last wrote: Which devbuild version did you use? "BtrieveBill" <billbach (AT) goldstarsoftware (DOT) com> schrieb im Newsbeitrag news:RNydndIdEZ1ebLLWnZ2dnUVZ_t-dnZ2d (AT) speakeasy (DOT) net... Glad it worked for you. I tried on a Vista64 machine, and it didn't help me yet. Goldstar Software Inc. Pervasive-based Products, Training & Services Bill Bach BillBach (AT) goldstarsoftware (DOT) com http://www.goldstarsoftware.com *** Pervasive Training - March 2010 in Chicago *** Michael Last wrote: Hi Bill, Pervasive entered a bug, Aus#58685 and did send us a devbuild today . Have tested it and the problem is solved now. The problem only occurs with PSQL10, older versions PSQL9 or PSQL8 did not have that problem. Michael Last "BtrieveBill" <billbach (AT) goldstarsoftware (DOT) com> schrieb im Newsbeitrag news:CtydncXOD4DZm77WnZ2dnUVZ_gSdnZ2d (AT) speakeasy (DOT) net... Michael: I've duplicated your issue on the x64 engine, too. It definitely is nasty and brings the system to its knees. BB Michael Last wrote: Hi, We have noticed a big problem with continuous mode using butil -startbu / endbu. We have several installations with "Limit Segment size to 2GB" enabled. If continuous mode is active it will NOT create a new extension file if it is necessary and the database file is damaged and cannot be recovered. Example: We have the following files before starting continuous mode: comm_message.mkd 2.147.483.648 bytes comm_message.^01 2.147.483.648 bytes comm_message.^02 2.147.483.648 bytes comm_message.^03 2.140.000.000 bytes Now we start continuous mode and the file comm_message.^^^ grows to 30MB. Now we stop continuous mode and the comm_message.^03 will be filled up until it reach 2.147.483.648 bytes. THEN NOTHING MORE HAPPENED. It will NOT create the next extension file comm_message.^04. Butil -endbu is hanging but the database file is no longer in use by butil. The only way is now to restart Pervasive services but afterwards the database file is damaged. We can reproduce this behaviour any time using 10.10 SP2 Patch1. We already opened a support ticket at Pervasive, but just be interested, if somebody else was running into this problem before. Thanks. Michael Last |
#10
| |||
| |||
|
|
The fix is now included in "Pervasive PSQL v10 SP3, Update 1" |
![]() |
| Thread Tools | |
| Display Modes | |
| |