Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Database Administration (MOSC)

Change the database to archive log mode. There are 1438 tables with status LOGGING=NO.

Feb 13, 2014 9:10AM edited Feb 21, 2014 1:03PM in Database Administration (MOSC) 10 commentsAnswered

I need to change a database to archive log mode. There are 1438 tables with status LOGGING=NO.

Do I need to alter these tables to logging status before changing the database to archive log mode?
There are temp tables that developers want to stay with logging=no. Can I do an "alter database force logging;"?
Do I have to do this (alter database force logging) before or after altering the tables? Before or after change the database to archive log mode?

Regards,

Maritza

1

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month