A raw table in Buffered DB in IDS 11.7 behavior
Greeting !! I've a IDS 11.7x running in RHEL 5.x , I've noticed that while I load a large data insert into a raw table reside in Buffered DB , the logical log does not increase size , that works fine , but surprisely physical log increase size , and finally has a checkpoint .. A raw table won't need to use logical log , in this case , Why it need physical log ? I mean , load from xxx.unl insert into xxx , if it failed , just like a table in no log DB , why should it use physical log in the raw table's large load command ? Any suggestion are welcome !!
On recovery the engine has to be able to restore its state to exactly what it was at the last completed checkpoint. To do that it needs the preimages of all modified pages in the physical log, even for RAW tables. Art Art S. Kagel Advanced DataTools (www.advancedatatools.com) Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Thu, Apr 5, 2012 at 3:27 AM, MARS CHEN <hedgezzz@yahoo.com.tw> wrote: > Greeting !! > > I've a IDS 11.7x running in RHEL 5.x , I've noticed that while > I load a large data insert into a raw table reside in Buffered DB , > the logical log does not increase size , that works fine , but > surprisely physical log increase size , and finally has a checkpoint .. > > A raw table won't need to use logical log , in this case , > Why it need physical log ? I mean , load from xxx.unl insert into xxx , > if it failed , just like a table in no log DB , > why should it use physical log in the raw table's large load command ? > > Any suggestion are welcome !! > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --e89a8f3ba5039ff40f04bcee0460