Impact of Oracle Database Switch "force_logging" on JD Edwards EnterpriseOne?

-


  • In Oracle9i release 2, the FORCE LOGGING option was introduced. 
  • If force logging is enabled, all the database changes will be logged in redo log files, even for nologging operations.
  • The above means that if FORCE LOGGING is enabled at a higher level, the NOLOGGING at a lower level has no effect. 
  • The FORCE LOGGING option can be set at the database level or the tablespace level. 
  • The precedence is from database to tablespace. 
  • If a tablespace is created or altered to have FORCE LOGGING enabled, any change in that tablespace will go into the redo log and be usable for recovery. 
  • Similarly, if a database is created or altered to have the FORCE LOGGING enabled, any change across the database, with exception of temporary segments and temporary tablespace, will be available in redo logs for recovery. 
  • The FORCE LOGGING option can be set at database creation time or later using the alter database command. 
  • To set FORCE LOGGING during the database creation, specify the following:
                 CREATE DATABASE <dbname>…..FORCE LOGGING… 
  • To enable FORCE LOGGING after the database is created, use the following command:                     
                 ALTER DATABASE FORCE LOGGING;
  • The following statement will put a tablespace in FORCE LOGGING mode:

                  ALTER TABLESPACE <tablespace name> FORCE LOGGING;
  • The FORCE LOGGING option is the safest method to ensure that all the changes made in the database will be captured and available for recovery in the redo logs. 
  • Logically changing FORCE LOGGING=yes should not cause a problem of data inconsistency or related issues, but could cause a minor performance impact on E1. 
  • Please note that currently, no official testing or performance measuring has been done with changing the default value of NO to YES for "force_logging" in the Oracle DB against JD Edwards EnterpriseOne Software.
Note: Force logging option is by default there for undo tablespace.
          Force logging is not applicable for TEMP tablespace.

Reference: 2478775.1  

Comments

Post a Comment

Popular posts from this blog

Deployment Server Recovery When There Is NO Backup

-
1. Install Deployment Server 2. Install the latest Planner ESU (DO NOT apply - just double click on the setup.exe to expand only the planner ESU or download and install from change assistant, but do not go into E1 Software Updates application P96470 to apply it to pathcodes. Also, be sure to run the setup.exe using the 'Run as Administrator' option.) 3. Install the Service Pack / Tools Release - the one which matches the Service Pack / Tools Release level on the enterprise server 4. Manually create System- XX Data source in Planner Data Source before running R9840C report as this report requires System -XX data source in Processing Option. Define the Data Source in Work With Data Sources (P986115) Application. 5. Copy the CNC System information from the DB server to JDEPLAN (R9840C).  Run UBE R9840C XJDE0001 from the Deployment Server - JDEPLAN Environment to Copy System Information as following: == Fast path to ‘BV’ for batch versions. Type as the Batch Application R9...
Read more

Oracle Cloud Infrastructure(OCI) - Part2

-
Image
In my earlier post (OCI -Part1 ), we have gone through OCI basic details, let's dive deep more into it. Before that, we need to u nderstand the following concepts and terminology to help you get started with Oracle Cloud Infrastructure.  Note: OCI is re-branding of Bare Metal Cloud Service (BMCS) BARE METAL HOST Oracle Cloud Infrastructure provides you control of the physical host (“bare metal”) machine. Bare metal compute instances run directly on bare metal servers without a hypervisor. When you provision a bare metal compute instance, you maintain sole control of the physical CPU, memory, and network interface card (NIC). You can configure and utilize the full capabilities of each physical machine as if it were hardware running in your own data center. You do not share the physical machine with any other tenants. REGIONS AND AVAILABILITY DOMAINS  Oracle Cloud Infrastructure is physically hosted in regions and availability domains. A region is a localized geographic area, an...
Read more

How to Change Your EnterpriseOne Environment Color

-
Image
Sometimes users start working and then forget which EnterpriseOne environment they are logged into. Can you tell which environment you are logged into? Luckily, there is a new UDC that allows you to change your EnterpriseOne environment color. You can now set up environments to be color-coded for when you need a clear visual distinction as to which environment you are logged into. This enables you to quickly identify the non-production environments by color. The new UDC is 98/CO and is available in EnterpriseOne Tools Release 9.2.4 with Applications Release 9.1 and 9.2. The image below shows the default EnterpriseOne environment color. However, you can easily change the color to reflect different environments. For example, DV could be red, PY could be green, and PD could be yellow, as shown below. To do so, just add a new row in the User Defined Codes section, enter the EnterpriseOne environment name and the HEX value of the color you want the environment to be, and ...
Read more