How to drop Old Database edition in R12.2

By -

 Dropping old database editions:

As online patching cycles are completed, the system will build up several old database editions. When the number of old database editions reach about 25, you should consider running a special maintenance operation to drop old database editions.

Use below script to find DB edition details

Cd $AD_TOP/sql/ADZDSHOWED.sql

Output:

SQL> @ADZDSHOWED.sql

=========================================================================

= Editions

=========================================================================

Edition Name Type Status Current?

--------------- -------- -------- -------- ---------

V_20210318_1313 ACTIVE

V_20210323_0209 ACTIVE

V_20210421_0706 ACTIVE

V_20210428_1036 ACTIVE

V_20210505_0620 OLD ACTIVE

V_20210507_2006 RUN ACTIVE CURRENT

Disconnected from Oracle Database 19c EE Extreme Perf Release 19.0.0.0.0 - Production

Actualize_All and Full Cleanup will clear the old database

Example

adop phase=prepare

adop phase=actualize_all

adop phase=finalize

adop phase=cutover

On the new run file system:

adop phase=cleanup cleanup_mode=full

$sqlplus apps/<apps password> @$AD_TOP/sql/ADZDRUNCLEANUNUSE.sql

Note:

The script ADZDRUNCLEANUNUSE.sql forces the database to run edition cleanup immediately, an operation that is normally performed in the background because of the performance overhead. After the run of this script is complete, there should only be one edition in the database.

This maintenance operation will take much longer than a typical online patching cycle and should only be performed when there is no immediate need to start a new online patching cycle.

We can execute Actualize_All and Full Cleanup combined with part of patching

Example:

adop phase=prepare

adop phase=apply patches=123456,765101,11121314

adop phase=actualize_all

adop phase=finalize

adop phase=cutover

adop phase=cleanup cleanup_mode=full

$sqlplus apps/<apps password> @$AD_TOP/sql/ADZDRUNCLEANUNUSE.sql


Comments

Post a Comment

Popular posts from this blog

How to troubleshoot long running concurrent request in R12.2

By -
We frequently encounter issues with concurrent programs running long and concurrent requests not picking up jobs. These problems are often expected from the development and functional team we need to address this issue To solve this, we should take the following steps: Collect below basis level of information to development team 1 Oracle seeded program/Custom program? 2 How much time it used earlier? 3 Is there any recent code change done in concurrent program? 4 Is this program fetching higher data compare to last run? 5 Does this job running any specific time/ It can be run any time? 6 Does this job fetching data using DB link? 7 Does the problem happen on both the test and production instance?   Troubleshooting Steps for Concurrent Requests Check for Locks and Blocking sessions Identify if the request is running but blocked by database locks/Blocking sessions. Use DBA tools or queries to identify and release locks if necessary. Review Parameters and Data ...
Read more

How to run Gather Schema Statistics in R12.2

By -
Image
What is Gather Schema Statistics? Gather Schema Statistics program generates statistics that quantify the data distribution and storage characteristics of tables, columns, indexes, and partitions. The cost-based optimization (CBO)  uses these statistics to calculate the selectivity of prediction and to estimate the cost of each execution plan. Why Run the Gather Schema Statistics? When Data is update, insert, delete in table of user end Like (Technical User ,Finance User ,Ect) It become necessary to run the Gather Schema Statistics It’s recommended to Run GSS in Weekly Once or twice. How to run Gather Schema Statistics? Login application with sysadmin user Submit Request Window Navigate to: Concurrent > Requests Enter the parameters This can be run for specific schemas by specifying the schema name or enter ‘ALL’ to gather statistics for every schema in the database Submit the Gather Schema Statistics program Parameters: S...
Read more

How to clear weblogic stuck threads in R12.2

By -
Web logic stuck threads Overview   What is stuck threads in weblogic server? Stuck threads are  long running threads and It means thread has been running longer predefined timeout.   What stuck threads will do? A thread might get stuck for various reasons.   Example :  When an SQL query is running and the time it takes to complete is say 800 seconds, then, as the default stuck thread timing is 600 seconds in WebLogic Server, the thread allocated for that query waits for 600 seconds and goes to stuck state. Then managed server status showing waning state   How to troubleshoot the stuck threads in EBS instance? Stuck threads will reduce the ebs performance and it’s very important activity to DBA’s Step 1: Go to the weblogic console and check for managed server status like oacore Step 2: if It will show the oacore server in “warning state” then we need to check   Scenario 1: Every alert we need to check the log file and investigate based on the log ...
Read more