[askdba] Re: LOGGING Feature in database
- From: Rajesh Puneyani <rajpuneyani@xxxxxxxxx>
- To: askdba@xxxxxxxxxxxxx
- Date: Thu, 11 Nov 2004 11:34:56 -0500
Thanks Justin,
But if any object has been created with NOLOGGING Option (before
Standby was created) then what will be the impact of this table level
setting on DMLs on that table and ultimately on Standby ?
I assume that DB Level LOGGING takes the precedence again...Right ?
Regards
Rajesh
On Thu, 11 Nov 2004 09:13:29 -0700, Justin Cave (DDBC)
<jcave@xxxxxxxxxxx> wrote:
> A database-level FORCE LOGGING setting will override any NOLOGGING
> command. FORCE LOGGING is designed to ensure, for example, that a
> developer cannot compromise a standby database by doing a NOLOGGING
> operation.
>
> Justin Cave <jcave@xxxxxxxxxxx>
> Distributed Database Consulting, Inc.
> http://www.ddbcinc.com/askDDBC
>
>
>
> -----Original Message-----
> From: askdba-bounce@xxxxxxxxxxxxx [mailto:askdba-bounce@xxxxxxxxxxxxx]
> On Behalf Of Rajesh Puneyani
> Sent: Thursday, November 11, 2004 10:55 AM
> To: askdba@xxxxxxxxxxxxx
> Subject: [askdba] LOGGING Feature in database
>
> Hi guys,
>
> This is just to confirm -=20
>
> If I have FORCE LOGGING enabled at the database level then every DDL
> command I execute (without specifying LOGGING/NOLOGGING option) would
> be executed using LOGGING option.
>
> IF I specifically say NOLOGGING in ALTER TABLE ...MODIFY (for example)
> then NOLOGGING has the priority.
>
> Pls confirm or clarify.
> Thanks
> Rajesh
>
>
Other related posts:
