Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
Oracle ACE Pro
Oracle Solution Architect
Oracle E-Business Suite
Oracle Cloud Infrastructure
Oracle Fusion Middleware
Oracle Database Administration
Oracle Weblogic Administration
The nologging Oracle database feature is used to enhance performance in certain areas of Oracle E-Business Suite. For example, it may be used during patch installation, and when building summary data for Business Intelligence.
What are the tradeoffs of using nologging?
Use of nologging in an operation means that the database redo logs will contain incomplete information about the changes made, with any data blocks that have been updated during the nologging operation being marked as invalid. As a result, a database restoration to a point in time (whether from a hot backup or a cold backup) may require additional steps in order to bring the affected data blocks up-to-date, and make the restored database usable. These additional steps may involve taking new backups of the associated datafiles, or by dropping and rebuilding the affected objects. The same applies to activation of a standby database.
Can nologging be enabled for EBS 12.2?
Yes. See the following documentation for additional considerations and operational implications of using nologging:
Related Articles
Source: https://blogs.oracle.com/stevenchan/can-nologging-be-enabled-for-ebs-122
First find the Invalid Objects in the Database by below given query.
SELECT COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = ‘INVALID’;
For a more detailed query, use the following script :
SELECT OWNER, OBJECT_TYPE, COUNT(*)
FROM DBA_OBJECTS
WHERE STATUS = ‘INVALID’
GROUP BY OWNER, OBJECT_TYPE;
To recompile an individual object, connect to SQL*PLUS as the owner of the object (generally apps) and use one of the following depending on the object type :
alter package <package_name> compile; (package specification)
alter package <package_name> compile body; (package body)
alter view <view_name> compile; (view)
If the object compiles with warnings, use either of the following to see the errors that caused the warnings :
show errors
OR
select * from user_errors where name = ‘<OBJECT_NAME>’;
1. Login OS with APPS owner.
2. Start the ADADMIN Utility from the Unix prompt with this command :
$adadmin
3. Under the Maintain Applications Database Objects Menu, select Compile APPS schema(s)
SELECT Count(*)
FROM v$backup_async_io
WHERE status = ‘IN PROGRESS’;
All Rights Reserved