It looks like Oracle intentionally leaves that column undocumented. So
is v$archived_log.compressed. According to Note:284618.1, 10g Release 1
is not ready for this feature yet. If you're not afraid of damaging
your database, you may try setting _log_archive_compress_enable to
true, which "Bypass database rules for enabling archivelog
compression". Messages such as "Starting block is invalid due to log
compression" are probably related to this feature.
Yong Huang
yong321ATyahoo.com
Received on Fri Apr 22 2005 - 10:53:38 CDT
