Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Truncate command internal behavior
In one of our db's, 9.2.0.4 on solaris 9 db_cache-size 4GB, when we did
a truncate of relative small table < 50M, the truncate command would
hang with the rdbms ipc message (wait event). I gather that this was
due to DBWR doing async writes of the dirty buffers to disk, but was
slow (io subsystem problem ?).
we moved to 9206 and this behaviour disappeared.
could you do a alter system checkpoint before the truncate command and see if this makes any difference. Received on Tue Oct 17 2006 - 20:59:10 CDT
![]() |
![]() |