Re: Miagrating Data from SE to ONline Engine

Ruchi Patel (.Ruchi_Patel@avid.avid.com) wrote: : I am miagrating Data From SE to Online Engine. I am going to use : DBEXPORT and DBIMPORT to do this eventually. Right now, I am using : Unload and Load statement to load tables into Online. Some of these : tables are very large and I got a message "Long Transactions". The : databases uses unbuffered logging and there are 50 logs defined with : size of 300 Kbytes. I was able to solve by changing the database to NO : LOGGING and it worked fine. Right now, I have no problem having NO : Logging to load large tables. But, Once my database in production with : UNBUFFERED Transactions then how would I handle this so I can insert : large tables without running into "Long Transacations"? Ruchi, The best tool for the job here is dbload. It allows you to set a threshold after which the data commits, completely eliminating the need to worry about logging. : Is there any : command that allows me to turn from UNBUFFERED logging to No Logging : for that one process? You can turn the logging OFF with no problem....it's just when you want to turn it back ON that you get into complications. OnLine wants this to happen in conjunction with an archive. Turning logging on and off during production operations is an almost impossible task from an operational standpoint. : How should I setup my database Logging when I use DBIMPORT to miagrate : the data to ONLINE? : When this database in production with UNBUFFERED LOGGING then How can I : prevent user from not doing long transactions? 50 logs of 300KB may not be enough. Rule of thumb says that total logspace should be 20-25% of your database size. I use 50 logs of 5MB in my apps. Unfortunately, you can only have about 60 or so logs. To get more space, you'll have to re-initialize your database with a larger LOGSIZE. Most of your long transaction problems will probably come from developers who are doing ad-hoc work. Train them about locks and long transactions. Hopefully when you run into long transaction problems in your application software (if you ever do) you'll fix them and they won't happen again. Developers, you just keep hammering on. :> : Thanks for your help in advance. Please email me to : Patel_Ruchi@avid.avid.com : Ruchi -- --------------------------------------------------------------------------- Joe Lumbley(jlumbley@netcom.com) Dallas, Texas author of: INFORMIX DBA Survival Guide from Prentice-Hall/Informix Press ISBN 0-13-124314-4 (12431-3) Now available in bookstores orders: orders@prenhall.com (515) 284-6761 fax (515) 284-2607 ----------------------------------------------------------------------------