long transaction

Hello, I have to import 16,500,000 records in a table (using the BaaN tool bdbpost6.1). This results in error 1255 (thus -255) = long transaction (correct ?) So, I want to increase the physical-log size (correct?) but only temporarely. I can't use onparams -p since the raw device is full. Do I have to create an extra chunk to the plogdbs (on another device)? -- *** remove spam twice when replying ***

"Daniel Willems" <spamwillemsspam@soudal.com> wrote: >Hello, > >I have to import 16,500,000 records in a table (using the BaaN tool >bdbpost6.1). This results in error 1255 (thus -255) = long transaction >(correct ?) >So, I want to increase the physical-log size (correct?) but only >temporarely. No, you hve to increase the LOGICAL LOG space. The physical log is sufficient if checkpoints are happening when scheduled by the CKPTINTVL parameter and not earlier by the physical log filling to 75% of capacity. The physical log has nothing to do with long transaction rollbacks, the logical logs do. You will have to make sure that you have enough locks: (#rows * (1 + #indexes)) then add logical logs and take a level zero archive to activate the new logs. If you had to increase LOCKS you will have to stop and restart the engine to have the change take effect. Art S. Kagel >I can't use onparams -p since the raw device is full. >Do I have to create an extra chunk to the plogdbs (on another device)? > > >-- >*** remove spam twice when replying *** > > > > Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free! http://www.keen.com

1. If "business" allows, disable logging on your database for the load. Loading will be faster and your "long transaction" problem will go away. 2. If your database must maintain logging during the load, you could consider splitting your file in smaller pieces. 3. Consider increasing the size of your Logical logs 4. Examine the usage of your Baan tool. Surely, it must be having some parameters to COMMIT periodically. BTW, where did error number 1255 come from? Baan? (finderr doesn't return anything) Rudy Daniel Willems wrote: > Hello, > > I have to import 16,500,000 records in a table (using the BaaN tool > bdbpost6.1). This results in error 1255 (thus -255) = long transaction > (correct ?) > So, I want to increase the physical-log size (correct?) but only > temporarely. > > I can't use onparams -p since the raw device is full. > Do I have to create an extra chunk to the plogdbs (on another device)? > > -- > *** remove spam twice when replying ***

Rudy Fernandes schrieb: > 1. If "business" allows, disable logging on your database for the load. > Loading will be faster and your "long transaction" problem will go away. > > 2. If your database must maintain logging during the load, you could > consider splitting your file in smaller pieces. > > 3. Consider increasing the size of your Logical logs > > 4. Examine the usage of your Baan tool. Surely, it must be having some > parameters to COMMIT periodically. > And one more: 5. If your BAAN tool is able to load without the need for transactions and your server is AD/XP or DS 7.31 and higher (not sure if it is possible with 7.30 already, but i guess not), you could drop the constraints and indexes from the table, put it table in RAW mode (alter table ...), load (no logging!) and recreate all neccessary indexes and constraints. So your database could still maintain logging for all other tables during the load. Best regards Dirk Bornhütter ----- Dipl. Inf. Dirk Bornhütter EDV-Beratung dirk.bornhuetter@edv-bornhuetter.de (49)-2261-921094