logical log entries for unlogged db
Posted in 1999
Topics: Logging & Checkpoints, Third-Party Tools & Monitoring
Hi all.. I have a db that is defined as "not logged". When my user executes a particular job, he fills logical log files with the following entries. The code he executes is from a third-party vendor and we cannot get a look at the source, however, the UNIQID entry is for a serial being assigned to a row. My question is how can you have begin/commit entries for a non-logged db? addr len type xid id link 18 40 BEGIN 168 9737 0 12/02/1999 23:26:41 4102 gim2u sr 40 36 UNIQID 168 0 18 80000c 1860673 64 36 COMMIT 168 0 40 12/02/1999 23:26:41 88 40 BEGIN 148 9737 0 12/02/1999 23:26:42 4094 gim2u sr b0 36 UNIQID 148 0 88 80000c 1860674 d4 36 COMMIT 148 0 b0 12/02/1999 23:26:42 1018 40 BEGIN 170 9737 0 12/02/1999 23:26:43 4108 gim2u sr 1040 36 UNIQID 170 0 1018 80000c 1860675 1064 36 COMMIT 170 0 1040 12/02/1999 23:26:43 1088 40 BEGIN 182 9737 0 12/02/1999 23:26:43 4112 gim2u sr 10b0 36 UNIQID 182 0 1088 80000c 1860676 10d4 36 COMMIT 182 0 10b0 12/02/1999 23:26:43 10f8 40 BEGIN 174 9737 0 12/02/1999 23:26:43 4107 gim2u sr 1120 36 UNIQID 174 0 10f8 80000c 1860677 1144 36 COMMIT 174 0 1120 12/02/1999 23:26:43 1168 40 BEGIN 142 9737 0 12/02/1999 23:26:43 4099 gim2u sr 1190 36 UNIQID 142 0 1168 80000c 1860678 11b4 36 COMMIT 142 0 1190 12/02/1999 23:26:43 . . . . . Thanks.... Doug McAllister Fidelity Invetsments
not only update, insert or delete statements create entries in the log-files. also create and drop table are making inserts into the log-file. this category of entries could not be turned off, but the number of entries normaly are reduced to a very small number of entries. for example creating temp-tables permanetly in the database-area are often used. hope i could answer your question roland baumschlager Doug McAllister schrieb in Nachricht <3847F214.293F0424@nospam.fmr.com>... >Hi all.. > >I have a db that is defined as "not logged". When my user executes a >particular job, he fills logical log files with the following entries. >The code he executes is from a third-party vendor and we cannot get a >look at the source, however, the UNIQID entry is for a serial being >assigned to a row. > >My question is how can you have begin/commit entries for a non-logged >db? > >addr len type xid id link >18 40 BEGIN 168 9737 0 12/02/1999 23:26:41 >4102 gim2u >sr >40 36 UNIQID 168 0 18 80000c 1860673 >64 36 COMMIT 168 0 40 12/02/1999 23:26:41 >88 40 BEGIN 148 9737 0 12/02/1999 23:26:42 >4094 gim2u >sr >b0 36 UNIQID 148 0 88 80000c 1860674 >d4 36 COMMIT 148 0 b0 12/02/1999 23:26:42 >1018 40 BEGIN 170 9737 0 12/02/1999 23:26:43 >4108 gim2u >sr >1040 36 UNIQID 170 0 1018 80000c 1860675 >1064 36 COMMIT 170 0 1040 12/02/1999 23:26:43 >1088 40 BEGIN 182 9737 0 12/02/1999 23:26:43 >4112 gim2u >sr >10b0 36 UNIQID 182 0 1088 80000c 1860676 >10d4 36 COMMIT 182 0 10b0 12/02/1999 23:26:43 >10f8 40 BEGIN 174 9737 0 12/02/1999 23:26:43 >4107 gim2u >sr >1120 36 UNIQID 174 0 10f8 80000c 1860677 >1144 36 COMMIT 174 0 1120 12/02/1999 23:26:43 >1168 40 BEGIN 142 9737 0 12/02/1999 23:26:43 >4099 gim2u >sr >1190 36 UNIQID 142 0 1168 80000c 1860678 >11b4 36 COMMIT 142 0 1190 12/02/1999 23:26:43 >. >. >. >. >. > >Thanks.... >Doug McAllister >Fidelity Invetsments > >