- yes
- because you have specified that LOBS doesn't have to be logged, so
Oracle doesn't log it regarding of archivelog mode. By changing
database to archivelog mode you simply say to archive redo log, not to
log everything.
- Starting with 9i you can force database to log all changes
regarding of LOGGING/NOLOGGING mode with ALTER DATABASE FORCE LOGGING.
You can read about this mode in documentation
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10739/create.htm#sthref273
On Tue, 14 Dec 2004 10:42:16 +0100, Francesco.Borgoglio_at_cedacri.it
<Francesco.Borgoglio_at_cedacri.it> wrote:
> Hi all.
> This is my problem.
> I have i database in archivelog mode,
> with tables containing lobs.
> After a database recover, the lob data blocks affected by the nologging
> operation are marked corrupted, i know that.
> Here are my questions.
> 1) These data are lost for ever?
> 2) Why after altering database in archivelog mode,
> tables with lobs remain in nologging mode?
> 3) What can i do to have a full archivelog mode,
> i would change the logging mode of all my tables with lobs?
>
> Thank you so much.
--
Edgar
--
http://www.freelists.org/webpage/oracle-l
Received on Tue Dec 14 2004 - 03:57:57 CST
