Database writing architecture

I'm very curious about comparing the writing architecture of Oracle versus Sybase. This question stems from prior discussions on the difference between databases installed on raw partions and databases installed on filesystems (UNIX). Sybase may have problems with database consistency if filesystem databases are used because the OS buffers the writes. Apparantly, Oracle doesn't have this problem or it isn't as big of an issue. Is this indeed true?

Does anybody know or have theories on how these DBMSs accomplish their writes and/or what would explain the above mentioned behavior? I am not familiar on the internals of either system.

By using filesystem databases you loose some performance, but gain a great deal in the area of administration etc.

Oracle has two writer processes: log-writer and db-writer. Sybase may have something similar but it is done under the covers with threads. Could this be a possible explanation?

Also, what are the various issues you have encountered through the use of write-back caching controllers and power failures, etc.

Thanks,

Jerry. Received on Thu Apr 11 1996 - 00:00:00 CEST