Oracle 19C Golden Gate Installation step by step on VM

 Hi  All, 

I am sharing in details step by step oracle 19c Golden Gate installation on VM , 

pre-requisites ::  in my lab i have already install oracle 19C database software on both target and source side.

configuring the listeners on both the nodes

unlocked the all locked accounts on both the nodes.

Lab setup :

i have created 2 VM with OEL 7 OS and Oracle 19C Database 

downloaded the 19C Golden Gate software and copied to both the servers and unzipped.

[oracle@ggnode1 Disk1]$ ./runInstaller

Starting Oracle Universal Installer...

Checking Temp space: must be greater than 120 MB.   Actual 10710 MB    Passed

Checking swap space: must be greater than 150 MB.   Actual 5056 MB    Passed

Checking monitor: must be configured to display at least 256 colors.    Actual 16777216    Passed

Preparing to launch Oracle Universal Installer from /tmp/OraInstall2026-05-10_12-54-58AM. Please wait ...[oracle@ggnode1 Disk1]$ You can find the log of this install session at:

 /u01/app/oraInventory/logs/installActions2026-05-10_12-54-58AM.log

[oracle@ggnode1 Disk1]$

Installation start from node1 :

> unzipped the software and starting installation of Oracle 19c Golden Gate software

select 19C option click next

click Install 

Oracle 19c Golden Gate software installation completed successfully.

Install the 19C Golden Gate software in node2

enter the target location 

click on Install 

click on close .

This section completes the Installation of Goldengate Software on Both the target and source nodes .

 we will share continues knowledge on Goldengate.

Thanks,

Srini

How to Troubleshoot Long running SQL In Oracle 19C Database Step by step Lab

 Hi All,

In this post i will show how to Troubleshoot Long running SQL In Oracle 19C Database Step by step Lab, with explanation.

Most of the times we will receive complains from application team,saying that ,  as till yesterday query execution was  right and all of suddenly they started observing lag in execution or and some cases not even giving any result. 

as a DBA when we check from our end, mostly we will see plan change and that is due many reasons. 

Below are few checks DBA can try to find why sql plan got changed. 

Though the Oracle Optimizer, you can just give hint if its a small query and you understand the execution flow as well as you know the data. 

But for many large queries its not possible to fix with hint, you have to live with Oracle Optimizer to decide the SQL plan. 

You can also forcefully map any plan to particular SQL ID, but that option need to consider carefully.

Why Plan got changed? or Why SQL is slow check few option mentioned below.

Course if action as DBA we should check below 11 steps one by one, all steps are not mandatory but as per the issue troubleshoot, we have to check until the issue cause and fix identified.

Check for any stale statistics.

col TABLE_NAME for a30

col PARTITION_NAME for a20

col SUBPARTITION_NAME for a20

select OWNER,TABLE_NAME,PARTITION_NAME,SUBPARTITION_NAME,NUM_ROWS,LAST_ANALYZED from dba_TAB_STATISTICS where STALE_STATS='YES';

Next 

Check any invalid index/Partition : 

col TABLE_NAME for a30

oracle@ggnode1>  select owner,index_name,TABLE_NAME,NUM_ROWS,LAST_ANALYZED,STATUS from dba_indexes where status not in ('VALID','N/A');

oracle@ggnode1>  select INDEX_OWNER,INDEX_NAME,PARTITION_NAME,SUBPARTITION_COUNT,LAST_ANALYZED,STATUS from dba_ind_partitions where status <> 'USABLE';

Check free memory shared pool area. Check too much hard parsing.

oracle@ggnode1> select * from (select SQL_ID,PARSING_SCHEMA_NAME, count(1) from v$sql group by SQL_ID,PARSING_SCHEMA_NAME order by  3 desc,2) where rownum<=10;

Wait/ Blocking analysis.

 Display blocked session and their blocking session details.

SELECT sid, serial#, blocking_session_status, blocking_session FROM   v$session WHERE  blocking_session IS NOT NULL;

Display the resource or event the session is waiting for more than 1 minutes

SELECT sid, serial#, event, (seconds_in_wait/1000000) seconds_in_wait FROM   v$session where (seconds_in_wait/1000000) > 60 ORDER BY sid;

select sid,seq#,event,state,SECONDS_IN_WAIT from v$session_wait where SECONDS_IN_WAIT > 60;

Monitor Top Waiting Event Using Active Session History (ASH)

SELECT h.event, SUM(h.wait_time + h.time_waited) "Total Wait Time (ms)" FROM v$active_session_history h, v$sqlarea SQL, dba_users u, v$event_name e WHERE h.sample_time BETWEEN sysdate - 1/24 AND sysdate --event in the last hour AND h.sql_id = SQL.sql_id AND h.user_id = u.user_id AND h.event# = e.event# GROUP BY h.event ORDER BY SUM(h.wait_time + h.time_waited) DESC;

Tablespace Usage

Monitor Overall Oracle Tablespace

SELECT d.STATUS "Status",

d.tablespace_name "Name",

d.contents "Type",

d.extent_management "Extent Management",

d.initial_extent "Initial Extent",

TO_CHAR(NVL(a.bytes / 1024 / 1024, 0),'99,999,990.900') "Size (M)",

TO_CHAR(NVL(a.bytes - NVL(f.bytes, 0), 0)/1024/1024,'99,999,999.999') "Used (M)",

TO_CHAR(NVL((a.bytes - NVL(f.bytes, 0)) / a.bytes * 100, 0), '990.00') "Used %",

TO_CHAR(NVL(a.maxbytes / 1024 / 1024, 0),'99,999,990.900') "MaxSize (M)",

TO_CHAR(NVL((a.bytes - NVL(f.bytes, 0)) / a.maxbytes * 100, 0), '990.00') "Used % of Max"

FROM sys.dba_tablespaces d,

(SELECT tablespace_name,

SUM(bytes) bytes,

SUM(decode(autoextensible,'NO',bytes,'YES',maxbytes))

maxbytes FROM dba_data_files GROUP BY tablespace_name) a,

(SELECT tablespace_name, SUM(bytes) bytes FROM dba_free_space

GROUP BY tablespace_name) f

WHERE d.tablespace_name = a.tablespace_name(+)

AND d.tablespace_name = f.tablespace_name(+)

ORDER BY 10 DESC;

Check for Memory parameters usage

Estimation Of Shared Memory Pool Size vs. Time Saved 

SELECT shared_pool_size_for_estimate "Pool Size (MB)",

estd_lc_size "Lib Cache Size (MB)",

estd_lc_time_saved/1000000 "Lib Cache Time Saved (Sec)"

FROM v$shared_pool_advice;

Estimation Of Buffer Cache Size vs. Physical Reads

SELECT size_for_estimate "Cache Size (MB)",

buffers_for_estimate "Buffers",

estd_physical_read_factor "Estd Phys|Read Factor",

estd_physical_reads "Estd Phys| Reads"

FROM v$db_cache_advice

WHERE name = 'DEFAULT'

AND block_size = (SELECT VALUE FROM V$PARAMETER WHERE name = 'db_block_size')

AND advice_status = 'ON';

SGA Advisor ::: 

select sga_size,sga_size_factor,estd_db_time from v$sga_target_advice;

PGA Advisor :::: 

select pga_target_for_estimate,pga_target_factor,estd_extra_bytes_rw from v$pga_target_advice;

 SQL Tuning using :::: 

SQL> @?/rdbms/admin/sqltrpt

 AWR various Report.

SQL> @?/rdbms/admin/awrsqrpt.sql --> awr report for only single sql_id

SQL> @?/rdbms/admin/awrrpt.sql   --> Traditional awr report for instance.

SQL> @?/rdbms/admin/awrgrpt.sql -- AWR Global Report (RAC) (global report)

SQL> @?/rdbms/admin/awrgdrpt.sql -- AWR Global Diff Report (RAC)

Other important scripts under $ORACLE_HOME/rdbms/admin

SQL> @?/rdbms/admin/spawrrac.sql -- Server Performance RAC report

SQL> @?/rdbms/admin/awrsqrpt.sql -- Standard SQL statement Report

SQL> @?/rdbms/admin/awrddrpt.sql -- Period diff on current instance

SQL> @?/rdbms/admin/awrrpti.sql -- Workload Repository Report Instance (RAC)

Note :::  To more analysis why plan has changed one can check support.oracle.com.

Thanks,

Srini

How to find the top 10 sql's and Find How much PGA usage in Oracle 19C DB

 Dear All,

In this post i am sharing few useful SQL's and How to find the top 10 sql's and Find How much PGA usage in Oracle 19C DB.

1) To find corrupt Object/Segments using file_id and block_id

select segment_name,block_id,file_id from dba_extents where FILE_ID=&1 and &2 between block_id and block_id+blocks-1

/

 Indexes created on Table_name

set lin 10000

col INDEX_NAME for a30

col TABLE_NAME for a30

col index_type for a25

col status for a10

--col LAST_ANALYZED for a19 wrap

col column_name for a20

col column_expression for a25

select a.INDEX_NAME ,b.column_name, column_expression,a.TABLE_NAME,STATUS,INDEX_TYPE

from user_indexes a,user_ind_columns b, user_ind_expressions c

where a.table_name = upper(trim('&1'))

and a.TABLE_NAME=b.TABLE_NAME

and a.INDEX_NAME=b.INDEX_NAME

and a.INDEX_NAME=c.INDEX_NAME (+)

and a.INDEX_NAME=c.INDEX_NAME (+)

/ 

Current running query

set lin 10000

col sid for 999999999

col serial# for  9999999999

col osuer for a20

col SQL_TEXT for a70 wrap

col osuser for a10

col status for a10

--select sid,serial#, status, osuser,b.EXECUTIONS,b.DISK_READS, b.SQL_TEXT from v$session a,  v$sqlarea b

--where a.SQL_ADDRESS=b.ADDRESS

--and b.HASH_VALUE = a.SQL_HASH_VALUE

select sid,serial#, status, osuser,b.EXECUTIONS,b.DISK_READS, b.SQL_TEXT from v$session a,  v$sql b

where a.SQL_ADDRESS=b.ADDRESS

and b.HASH_VALUE = a.SQL_HASH_VALUE

order by 6 desc,5 desc

/

To find query how much memory (PGA)

SET LINESIZE 145

SET PAGESIZE 9999

COLUMN sid FORMAT 999  HEADING 'SID'

COLUMN oracle_username  FORMAT a12     HEADING 'Oracle User'     JUSTIFY right

COLUMN os_username FORMAT a9  HEADING 'O/S User' JUSTIFY right

COLUMN session_program  FORMAT a18     HEADING 'Session Program' TRUNC

COLUMN session_machine  FORMAT a18      HEADING 'Machine'  JUSTIFY right TRUNC

COLUMN session_pga_memory      FORMAT 9,999,999,999  HEADING 'PGA Memory'

COLUMN session_pga_memory_max  FORMAT 9,999,999,999  HEADING 'PGA Memory Max'

COLUMN session_uga_memory      FORMAT 9,999,999,999  HEADING 'UGA Memory'

COLUMN session_uga_memory_max  FORMAT 9,999,999,999  HEADING 'UGA Memory MAX'

SELECT

    s.sid  sid

  , lpad(s.username,12)  oracle_username

  , lpad(s.osuser,9)     os_username

  , s.program     session_program

  , lpad(s.machine,8)    session_machine

  , (select ss.value from v$sesstat ss, v$statname sn

     where ss.sid = s.sid and

    sn.statistic# = ss.statistic# and

    sn.name = 'session pga memory') session_pga_memory

  , (select ss.value from v$sesstat ss, v$statname sn

     where ss.sid = s.sid and

    sn.statistic# = ss.statistic# and

    sn.name = 'session pga memory max')    session_pga_memory_max

  , (select ss.value from v$sesstat ss, v$statname sn

     where ss.sid = s.sid and

    sn.statistic# = ss.statistic# and

    sn.name = 'session uga memory') session_uga_memory

  , (select ss.value from v$sesstat ss, v$statname sn

     where ss.sid = s.sid and

    sn.statistic# = ss.statistic# and

    sn.name = 'session uga memory max')    session_uga_memory_max

FROM

    v$session  s

ORDER BY session_pga_memory DESC

/

 SID  Oracle User  O/S User Session Program               Machine     PGA Memory PGA Memory Max     UGA Memory UGA Memory MAX

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

  20                 oracle oracle@ggnode1 (M0  ggnode1               32,850,736     59,786,032     23,623,584     29,389,984

  18                 oracle oracle@ggnode1 (MM  ggnode1               23,875,304     26,562,280      4,287,472     21,663,552

 252                 oracle oracle@ggnode1 (TT  ggnode1               20,333,360     20,333,360        367,072        367,072

 274                 oracle oracle@ggnode1 (J0  ggnode1               11,682,608    104,809,264        367,072        367,072

 246                 oracle oracle@ggnode1 (DB  ggnode1                8,953,728     10,478,112        367,072        367,072

  42                 oracle oracle@ggnode1 (M0  ggnode1                5,718,832              0         65,488        628,864

 262                 oracle oracle@ggnode1 (M0  ggnode1                5,522,224      8,274,736      3,650,952      5,102,328

  41          SYS    oracle sqlplus@ggnode1 (T  ggnode1                5,006,336     19,489,792      1,611,368      2,893,104

   9                 oracle oracle@ggnode1 (DI  ggnode1                4,844,408      4,844,408        367,072        367,072

  27                 oracle oracle@ggnode1 (CJ  ggnode1                4,411,112      7,294,696      2,462,592      5,014,824

  28                 oracle oracle@ggnode1 (W0  ggnode1                3,556,144      4,408,112      2,070,120      2,633,496

   7                 oracle oracle@ggnode1 (DB  ggnode1                3,533,688      4,123,512      1,742,320      1,873,296

 275                 oracle oracle@ggnode1 (W0  ggnode1                3,425,072      4,408,112      1,929,584      3,006,712

 251                 oracle oracle@ggnode1 (LR  ggnode1                3,354,136      3,681,816        970,864      1,152,952

 250                 oracle oracle@ggnode1 (RE  ggnode1                2,764,312      3,026,456        970,856      1,280,040

  12                 oracle oracle@ggnode1 (SM  ggnode1                2,698,776      3,419,672        970,864      1,458,232

   6          SYS    oracle oracle@ggnode1 (OF  ggnode1                2,567,704      2,567,704        825,488        890,976

  38                 oracle oracle@ggnode1 (Q0  ggnode1                2,442,032      2,900,784      1,036,344      1,341,656

  10                 oracle oracle@ggnode1 (LG  ggnode1                2,379,496      2,379,496        367,072        367,072

  11                 oracle oracle@ggnode1 (CK  ggnode1                2,282,496      2,282,496        367,072        367,072

   4                 oracle oracle@ggnode1 (W0  ggnode1                2,245,424      2,573,104        839,888      1,210,680

   3                 oracle oracle@ggnode1 (GE  ggnode1                2,174,488      2,174,488        367,072        367,072

 263                 oracle oracle@ggnode1 (Q0  ggnode1                2,114,352      2,114,352        498,048        498,048

 259                 oracle oracle@ggnode1 (W0  ggnode1                2,114,352      6,964,016        498,048        498,048

 256                 oracle oracle@ggnode1 (AQ  ggnode1                2,043,416      2,043,416        367,072        367,072

  13                 oracle oracle@ggnode1 (W0  ggnode1                2,031,760      7,291,696        629,048      1,283,976

  15                 oracle oracle@ggnode1 (W0  ggnode1                1,917,744      2,442,032        498,056      1,152,952

   8                 oracle oracle@ggnode1 (SV  ggnode1                1,912,344      1,912,344        367,072        367,072

 253                 oracle oracle@ggnode1 (MM  ggnode1                1,912,344      1,912,344        367,072        432,560

 245                 oracle oracle@ggnode1 (PM  ggnode1                1,846,808      1,846,808        367,072        367,072

 244                 oracle oracle@ggnode1 (VK  ggnode1                1,846,808      1,846,808        367,072        367,072

 242                 oracle oracle@ggnode1 (DI  ggnode1                1,846,808      1,846,808        367,072        367,072

 241                 oracle oracle@ggnode1 (GE  ggnode1                1,846,808      1,846,808        367,072        367,072

 240                 oracle oracle@ggnode1 (MM  ggnode1                1,846,808      1,846,808        367,072        367,072

  19                 oracle oracle@ggnode1 (TM  ggnode1                1,846,808      1,846,808        367,072        367,072

  17                 oracle oracle@ggnode1 (PX  ggnode1                1,846,808      1,846,808        367,072        367,072

 239                 oracle oracle@ggnode1 (VK  ggnode1                1,846,808      1,846,808        367,072        367,072

   2                 oracle oracle@ggnode1 (PS  ggnode1                1,846,808      1,846,808        367,072        367,072

 249                 oracle oracle@ggnode1 (SM  ggnode1                1,846,808      1,846,808        367,072        367,072

 238                 oracle oracle@ggnode1 (CL  ggnode1                1,797,728      1,797,728        367,072        367,072

   1                 oracle oracle@ggnode1 (PM  ggnode1                1,797,728      1,797,728        367,072        367,072

 255                 oracle oracle@ggnode1 (Q0  ggnode1                1,786,672      1,786,672        432,560        432,560

  24                 oracle oracle@ggnode1 (TT  ggnode1                1,655,600      1,655,600        367,072        367,072

  22                 oracle oracle@ggnode1 (QM  ggnode1                1,655,600      1,655,600        367,072        367,072

   5                 oracle oracle@ggnode1 (SC  ggnode1                1,655,600      1,655,600        367,072        367,072

 269                 oracle oracle@ggnode1 (W0  ggnode1                1,655,600      1,655,600        367,072        367,072

 248                 oracle oracle@ggnode1 (LG  ggnode1                1,655,600      1,655,600        367,072        367,072

 247                 oracle oracle@ggnode1 (LG  ggnode1                1,655,600      1,655,600        367,072        367,072

 237                 oracle oracle@ggnode1 (TT  ggnode1                1,655,600      1,655,600        367,072        367,072

 243                 oracle oracle@ggnode1 (SC  ggnode1                1,655,600      1,655,600        367,072        367,072

  35                 oracle oracle@ggnode1 (W0  ggnode1                1,655,600      1,655,600        367,072        367,072

51 rows selected.

Find  Active SQL old versions ::: 

SELECT nvl(ses.username,'ORACLE PROC')||' ('||ses.sid||')' USERNAME,

    SID,  

    MACHINE,

    REPLACE(SQL.SQL_TEXT,CHR(10),'') STMT,

    ltrim(to_char(floor(SES.LAST_CALL_ET/3600), '09')) || ':'

    || ltrim(to_char(floor(mod(SES.LAST_CALL_ET, 3600)/60), '09')) || ':'

    || ltrim(to_char(mod(SES.LAST_CALL_ET, 60), '09'))    RUNT

FROM    V$SESSION SES,  

    V$SQLtext_with_newlines SQL

where SES.STATUS = 'ACTIVE'

    and SES.USERNAME is not null

    and SES.SQL_ADDRESS    = SQL.ADDRESS

    and SES.SQL_HASH_VALUE = SQL.HASH_VALUE

    and Ses.AUDSID <> userenv('SESSIONID')

order by runt desc, 1,sql.piece;

Thanks,

Srini

Oracle Deep Data Security - lab examples and use cases - 2026

 Hi All,

In this post i am going share about Oracle Deep Data Security .

You will learn how to shift from fragmented, application-based controls to a centralized, declarative model that evaluates identity and context at runtime. 

The brief offers practical guidance for enforcing least-privilege access, protecting AI-driven workflows such as retrieval-augmented generation (RAG), and allowing agents to operate within clearly defined guardrails.

 It also explains how capabilities such as cell-level authorization, secure identity propagation, and controlled privilege elevation can reduce risk without sacrificing flexibility or performance.

 Identity & context-aware access control across workloads :::

Key benefits include: 

 Reduced data exposure risk with database-enforced authorization across all access paths .

 Least-privilege access for users and non-human identities, including AI agents .

 Rapid adaptation to changing security requirements by separating policy from application code. 

 Strengthened governance with centralized, end-user-aware auditing.

 Performance and scale maintained for enterprise workloads.

Why Agentic AI increases the risk  ? 

Agentic AI changes how applications interact with data. Instead of executing predefined logic, agents generate SQL at runtime based on user input and model reasoning. This shift introduces new security risks that traditional controls were not designed to address.

Declarative policy model  :

Deep Data Security enforces access control through declarative SQL policies, referred to as Data Grants. These policies define which operations—such as SELECT, INSERT, UPDATE, and DELETE—are allowed on specific rows, columns, or individual data values. 

Policies use SQL predicates to identify the data they apply to and can incorporate joins, subqueries, and runtime attributes. This enables precise, context-aware decisions based on both user attributes and data relationships.

 Policy for row-level access ::

Cell-level authorization ::

 Cell-level authorization enables control over individual data values within a row. 

This allows organizations to enforce strict least-privilege access without creating complex views or duplicating data structures. 

For example: 

 Employees can view their own records but update only contact details .

 Managers can update salaries for direct reports but not their own.

 Sensitive attributes such as SSNs remain restricted even when other fields are visible

Runtime policy enforcement ::

  At runtime, Deep Data Security evaluates authorization policies and transparently rewrites queries and other SQL operations, independent of application logic, to enforce authorization controls. In effect, Deep Data Security serves as the policy decision point (PDP), while the database SQL engine functions as the policy enforcement point (PEP). This helps ensure end users can access only authorized data, regardless of the SQL executed by an agent or application, which helps mitigate prompt injection and SQL injection attacks.

Authorization APIs ::

  

End-user security context

The Oracle Deep Data Security advantage  ::

Securing AI-driven access requires enforcement at the data layer. 

Oracle Deep Data Security, built into Oracle AI Database 26ai, embeds centralized, declarative authorization policies directly in the database. By separating authorization logic from application code, it helps organizations apply consistent access controls across agentic AI, analytics, and enterprise applications, without depending on how SQL is generated. 

Realizing enterprise benefits :::

 Oracle Deep Data Security helps organizations scale AI adoption while maintaining governance and control: 

Enforce identity- and context-aware access: Evaluate runtime security context for both human users and AI agents to support least-privilege access. 

 Protect data at a granular level: Apply row-, column-, and cell-level authorization without requiring complex application logic or data duplication. 

 Simplify application development: Decouple authorization policies from application code to reduce hardcoded logic and streamline updates. 

 Apply consistent policy enforcement: Extend controls across relational data, vector data used in retrieval augmented generation (RAG), and heterogeneous Lakehouse environments. 

Strengthen governance and auditing: Centralize auditing of database activity with end-user and agent attribution to support security and compliance requirements.

Thanks,

Srini

Oracle 19C DB How to export the dump file using LOGTIME parameter step by step lab 2026

 Dear All,

In this post i am sharing Oracle 19C DB  How to export the dumpfile using LOGTIME parameter step by step lab .

This parameter LOGTIME give us the timestamp for each and every export operation during expdp., therefore its easy to check the diagnise/elapsed time taken for execution.

 default LOGTIME=NONE, If you want to use this feature use this parameter in expdp command.

Types of LOGTIME parameters:

LOGTIME=NONE : Default value which will not display timestamp in both command prompt as well as export log file.

LOGTIME=ALL : Display the timestamp in both command prompt as well as export log file.

LOGTIME=LOGFILE : Display the timestamp in only export log file, not in command prompt.

LOGTIME=STATUS : Display the timestamp in only command prompt and not in export log file.

Check the DB version and status :

create schema and that schema we can use it for this lab

grant the schema and connect to that schema create some objects 

Now take the export of the dump file for his schema 

if schema exist in CDB$ROOT use below command :

expdp directory=DATA_PUMP_DIR dumpfile=racsdev_sch.dmp logfile=racsdev_sch.log schemas=racsdev LOGTIME=ALL

If schema exist in PDB use below command

Logtime parameter for all option ::  

expdp system/****@pdb1 directory=DATA_PUMP_DIR dumpfile=racsdev_sch1.dmp logfile=racsdev_sch1.log schemas=racsdev LOGTIME=ALL

Without logtime parameter output 

Logtime parameter with logfile option : 

Display the timestamp in only export log file, not in command prompt.

Logtime parameter STATUS option 

Display the timestamp in only command prompt and not in export log file

Hope this will help when you are working with real-time tasks, with LOGTIME options.

Thanks,

Srini

Oracle EBS R12.2.9 installation step by step process - Part 2/2

  Hi All,

In this post i am sharing how to install Oracle EBS R12.2.9 on OEL step by step.

In this post will share >> stage creation and EBS application configuration - Part 2/2 ,

Rapid Install - application tier installation

After successful installation of the database tier, the application tier should be installed

Login to applprod user and run the rapidwiz command

Start a VNC server for accessing the application tier node in GUI mode. From a VNC client,

Start rapidwiz , $./rapidwiz

Click next to proceed , select 12.2.0 Install then next 

If you have already database then you need to configure application select first options here we have just before created database for EBS application as part of 1/2 . we will select second option then click next 

validate the system configuration  make sure all success if any error need to fix else it will not proceed further .

Component install status 

Select yes then click on next 

EBs installation is in progress monitor the application configuration log 

validation completed successfully then click next 

Click on Finish , it will close the GUI 

Log files ::::::

[root@StgApp01 rapidwiz]# ./rapidwiz

 

 

Rapid Install Wizard is validating your file system......

CMDDIR=/backup/12.2.9_stage/startCD/Disk1/rapidwiz

Rapid Install Wizard will now launch the Java Interface.....

 

[root@StgApp01 rapidwiz]#

 

Configuration file written to: /ebsprod/app/PROD/fs1/inst/apps/PROD_stgapp01/conf_PROD.txt

Configuration file written to: /ebsprod/app/PROD/fs2/inst/apps/PROD_stgapp01/conf_PROD.txt

Second File System logfile - /ebsprod/app/PROD/fs2/inst/apps/PROD_stgapp01/logs/01072207.log

First File System logfile - /ebsprod/app/PROD/fs1/inst/apps/PROD_stgapp01/logs/01072207.log

Check the login page 

EBS Technology Code level Checker (ETCC)

ETCC can be downloaded via Patch 17537119

New Installation Customers

New Installation customers should also run the codelevel checker utility (checkDBpatch.sh or checkDBpatch.cmd for Microsoft Windows) to identify and apply required patches for Database 12.1.0.2. After the release of the startCD, new required patches may have been discovered.

Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes and apply all technology patches for your database and middle tier versions.

The application tier technology patches you need to apply are listed in 'Section 4: Application Tier Technology Patches and Bug Numbers' of My Oracle Support Knowledge Document 1594274.1, Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes.

Run the ETCC on DB node :  complete log 

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

[oraprod@Oracle ETCC]$ ./checkDBpatch.sh

>> complete log shared in the part 1/2 .. 

Check the Opatch version 

=== === ==== 

~]$./opatch version

OPatch Version: 12.1.0.1.10

 OPatch succeeded.

Opatch commands :::::::: 

export PATH=$PATH:$ORACLE_HOME/OPatch

  export PATH=$PATH:/ebsprod/oracle/PROD/12.1.0/OPatch

 opatch prereq CheckConflictAgainstOHWithDetail -ph ./ >>> Check the conflicts 

 opatch apply

 opatch lsinv –inactive

 opatch lsinventory |grep 29176139

 which opatch

 opatch –version

Check MT Patch >> run ETCC on Application node.

applprod@appsndes ETCC]$ ./checkMTpatch.sh

[applprod@StgApp01 ETCC]$ ./checkMTpatch.sh

 +===============================================================+

 |    Copyright (c) 2005, 2019 Oracle and/or its affiliates.     |

 |                     All rights reserved.                      |

 |             Oracle E-Business Suite Release 12.2              |

 |        Applicatione Tier Technology Codelevel Checker         |

 +===============================================================+

Using context file from currently set applications environment:

/ebsprod/app/PROD/fs1/inst/apps/PROD_stgapp01/appl/admin/PROD_stgapp01.xml

Starting Application Tier Technology Codelevel Checker

Version: 120.0.12026000.38.

Wed Jan  8 10:05:34 IST 2026

Log file for this session: /ebsprod/app/ETCC/log/checkMTpatch_62514.log

Bugfix XML file version: 120.0.12026000.42

This file will be used for identifying missing bugfixes.

Mapping XML file version: 120.0.12026000.26

This file will be used for mapping bugfixes to patches.

Checking for prerequisite bugfixes in File Edition: run

Enter the password for the APPS user:

Connecting to database.

Database connection successful.

The installed AD.C codelevel does not support storing the results in the database.

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

Oracle Forms and Reports

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

Now examining product Oracle Forms and Reports.

Oracle Home = /ebsprod/app/PROD/fs1/EBSapps/10.1.2.

Product version = 10.1.2.3.0.

Checking required bugfixes for Oracle Forms and Reports 10.1.2.3.0.

  Missing Bugfix: 17353142  ->  Patch 26825525

  Missing Bugfix: 20643256  ->  Patch 26825525

  Missing Bugfix: 16041055  ->  Patch 26825525

  Missing Bugfix: 16910762  ->  Patch 26825525

  Missing Bugfix: 20270659  ->  Patch 26825525

  Missing Bugfix: 17372642  ->  Patch 26825525

  Missing Bugfix: 17566694  ->  Patch 26825525

  Missing Bugfix: 20240480  ->  Patch 26825525

  Missing Bugfix: 19304738  ->  Patch 26825525

  Missing Bugfix: 20391574  ->  Patch 26825525

  Missing Bugfix: 22351071  ->  Patch 26825525

  Missing Bugfix: 21024122  ->  Patch 26825525

  Missing Bugfix: 19588847  ->  Patch 26825525

  Missing Bugfix: 19639173  ->  Patch 26825525

  Missing Bugfix: 20545718  ->  Patch 26825525

  Missing Bugfix: 22524329  ->  Patch 26825525

  Missing Bugfix: 23123655  ->  Patch 26825525

  Missing Bugfix: 23728755  ->  Patch 26825525

  Missing Bugfix: 24315226  ->  Patch 26825525

  Missing Bugfix: 24480018  ->  Patch 26825525

  Missing Bugfix: 24808044  ->  Patch 26825525

  Missing Bugfix: 24620875  ->  Patch 26825525

  Missing Bugfix: 25355211  ->  Patch 26825525

  Missing Bugfix: 23538157  ->  Patch 26825525

  Missing Bugfix: 23538170  ->  Patch 26825525

  Missing Bugfix: 13557392  ->  Patch 26825525

  Missing Bugfix: 25506193  ->  Patch 26825525

  Missing Bugfix: 25342269  ->  Patch 25342269

  Missing Bugfix: 26048089  ->  Patch 26825525

  Missing Bugfix: 25990479  ->  Patch 26825525

  Missing Bugfix: 1770039  ->  Patch 26825525

  Missing Bugfix: 27491934  ->  Patch 27491934

The above list shows missing bugfixes for Oracle Forms and Reports.

Checking required bugfixes for RSF within Forms 10.1.0.5.0.

All required bugfixes are present for RSF within Forms.

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

Oracle Fusion Middleware (FMW) - Web Tier

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

Now examining product Oracle Fusion Middleware (FMW) - Web Tier.

Oracle Home = /ebsprod/app/PROD/fs1/FMW_Home/webtier.

Product Version = 11.1.1.9.0

Checking required bugfixes for FMW - Web Tier 11.1.1.9.0.

  Missing Bugfix: 21300463  ->  Patch 22288381

  Missing Bugfix: 21892015  ->  Patch 22288381

  Missing Bugfix: 23266217  ->  Patch 27369643

  Missing Bugfix: 22750215  ->  Patch 27369643

  Missing Bugfix: 23055182  ->  Patch 27369643

  Missing Bugfix: 26318200  ->  Patch 27369643

  Missing Bugfix: 24567879  ->  Patch 27301611

  Missing Bugfix: 20900385  ->  Patch 27301611

  Missing Bugfix: 26837992  ->  Patch 27301611

  Missing Bugfix: 21305938  ->  Patch 27301611

  Missing Bugfix: 20913582  ->  Patch 27301611

  Missing Bugfix: 22218211  ->  Patch 27301611

  Missing Bugfix: 23107407  ->  Patch 27301611

  Missing Bugfix: 19571821  ->  Patch 27301611

  Missing Bugfix: 26929226  ->  Patch 27301611

  Missing Bugfix: 25191174  ->  Patch 27301611

  Missing Bugfix: 26101975  ->  Patch 27301611

  Missing Bugfix: 21520649  ->  Patch 27301611

The above list shows missing bugfixes for FMW - Web Tier.

Checking required bugfixes for RSF within FMW Web tier 11.1.0.7.0.

  Missing Bugfix: 20004021  ->  Patch 22290164

  Missing Bugfix: 20004087  ->  Patch 22290164

  Missing Bugfix: 16872333  ->  Patch 22290164

  Missing Bugfix: 19699191  ->  Patch 22290164

  Missing Bugfix: 20558005  ->  Patch 22290164

  Missing Bugfix: 20331945  ->  Patch 22290164

The above list shows missing bugfixes for RSF within FMW Web tier.

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

Oracle Fusion Middleware (FMW) - oracle_common

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

Now examining product Oracle Fusion Middleware (FMW) - oracle_common.

Oracle Home = /ebsprod/app/PROD/fs1/FMW_Home/oracle_common.

Product Version = 11.1.1.9.0

Checking required bugfixes for FMW - oracle common 11.1.1.9.0.

  Missing Bugfix: 9905685  ->  Patch 9905685

  Missing Bugfix: 17428617  ->  Patch 17428617

  Missing Bugfix: 21366277  ->  Patch 21366277

  Missing Bugfix: 21628307  ->  Patch 21628307

  Missing Bugfix: 24606362  ->  Patch 24606362

  Missing Bugfix: 24843064  ->  Patch 24843064

  Missing Bugfix: 13544814  ->  Patch 13544814

  Missing Bugfix: 16089637  ->  Patch 16089637

  Missing Bugfix: 20141119  ->  Patch 20141119

  Missing Bugfix: 24335626  ->  Patch 27120730

  Missing Bugfix: 22998551  ->  Patch 27120730

  Missing Bugfix: 22660018  ->  Patch 27120730

  Missing Bugfix: 24913281  ->  Patch 27120730

  Missing Bugfix: 20055551  ->  Patch 27120730

  Missing Bugfix: 27212806  ->  Patch 27212806

  Missing Bugfix: 28371189  ->  Patch 28708563

The above list shows missing bugfixes for FMW - oracle common.

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

Oracle WebLogic Server (WLS)

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

Now examining product Oracle WebLogic Server (WLS).

Oracle Home = /ebsprod/app/PROD/fs1/FMW_Home/wlserver_10.3.

Product Version = 10.3.6.0.7

Note that for Oracle WebLogic Server, patches rather than bugfixes are verified.

Checking required patches for Oracle WebLogic Server (WLS) 10.3.6.0.7.

  Missing Patch ID: 27395085

The above list shows missing patches for Oracle WebLogic Server.

If you have applied other Oracle WebLogic Server patches, they may have included the bugfixes needed.

Contact Oracle Support if you require assistance in determining whether this is the case.

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

Generating Patch Recommendation Summary.

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

PATCH RECOMMENDATION SUMMARY

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

One or more products have bugfixes missing.

The default patch recommendations to install these missing bugfixes are:

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

Oracle Forms and Reports 10.1.2.3.0

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

  Patch 26825525

    - Filename: p26825525_101232_LINUX.zip

  Patch 25342269

    - Filename: p25342269_101232_Generic.zip

  Patch 27491934

    - Filename: p27491934_101232_LINUX.zip

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

Oracle Fusion Middleware (FMW) - Web Tier 11.1.1.9.0

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

  Patch 22288381

    - Filename: p22288381_111190_Generic.zip

  Patch 27369643

    - Filename: p27369643_111190_Linux-x86-64.zip

  Patch 27301611

    - Filename: p27301611_111190_Linux-x86-64.zip

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

RSF within FMW Web tier 11.1.0.7.0

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

  Patch 22290164

    - Filename: p22290164_111070_Linux-x86-64.zip

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

Oracle Fusion Middleware (FMW) - oracle_common 11.1.1.9.0

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

  Patch 9905685

    - Filename: p9905685_111190_Generic.zip

  Patch 17428617

    - Filename: p17428617_111190_Generic.zip

  Patch 21366277

    - Filename: p21366277_111190_Generic.zip

  Patch 21628307

    - Filename: p21628307_111190_Generic.zip

  Patch 24606362

    - Filename: p24606362_111190_Generic.zip

  Patch 24843064

    - Filename: p24843064_111190_Generic.zip

  Patch 13544814

    - Filename: p13544814_111190_Generic.zip

  Patch 16089637

    - Filename: p16089637_111190_Generic.zip

  Patch 20141119

    - Filename: p20141119_111190_Generic.zip

  Patch 27120730

    - Filename: p27120730_111190_Generic.zip

  Patch 27212806

    - Filename: p27212806_111190_Generic.zip

  Patch 28708563

    - Filename: p28708563_111190_Generic.zip

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

Oracle WebLogic Server (WLS) 10.3.6.0.7

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

  Patch 27395085 [SU Patch [GFWX]: WLS PSU 10.3.6.0.180417]

    - Filename: p27395085_1036_Generic.zip

Apply the required patches and rerun this script.

+-----------------------------------------------------------------------------+

A consolidated zip file with the required application tier patches is

available on My Oracle Support via:

  Patch 29778100

    - EBS RELEASE 12.2 CONSOLIDATED FMW FIXES FOR JUL 2019

+-----------------------------------------------------------------------------+

[WARNING]  Patch 27395085 [SU Patch [GFWX]: WLS PSU 10.3.6.0.180417] is missing.

This is the current recommended minimum WLS patch set.

As patch sets are not included in the consolidated zip file, you must obtain it

(or a later one, if available) from My Oracle Support and install it by

following its Readme.

After successful installation, rerun this script to check for any further

available fixes.

+-----------------------------------------------------------------------------+

See Doc ID 1594274.1 for any special instructions regarding these patches.

Footnotes in Doc ID 1594274.1 also apply to corresponding overlay patches.

Finished checking prerequisite patches for File Edition: run.

Wed Jan  8 10:06:06 IST 2026

Log file for this session: /ebsprod/app/ETCC/log/checkMTpatch_62514.log

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

[applprod@StgApp01 ETCC]$

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

Oracle Forms and Reports 10.1.2.3.0

[appldev@appsnodes dev]$ . ./fsautoDEV.sh

Running fsauto 1.0 :

 Context Name (<SID_host>) : DEV_appsnodes

 RUN Edition APPL_TOP      : /ebsdev/app/dev/fs1

 PATCH Edition APPL_TOP    : /ebsdev/app/dev/fs2

 Non-Editioned File System : /ebsdev/app/dev/fs_ne/EBSapps/appl

 Instance Top Directory    : /ebsdev/app/dev/fs1/inst/apps/DEV_appsnodes

 APPL_TOP environment file : /ebsdev/app/dev/fs1/EBSapps/appl/APPSDEV_appsnodes.env

 Admin Scripts Home        : /ebsdev/app/dev/fs1/inst/apps/DEV_appsnodes/admin/scripts

Setting RUN Edition APPL_TOP environment for /ebsdev/app/dev/fs1 ...

Done.

[appldev@appsnodes dev]$ which opatch

/ebsdev/app/dev/fs1/EBSapps/10.1.2/OPatch/opatch

/stage/patches/APP_patches/LINUX_X86-64/forms/10.1.2.3.0/26825525

Environment sourcing as below 

run etcc on application node and apply all missed pacthes by source each respective oracle homes.

export ORACLE_HOME=

export PATH=$PATH:$ORACLE_HOME/OPatch

ORACLE_HOME=/Apps/apps/VISR1228/fs1/EBSapps/10.1.2

ORACLE_HOME=/Apps/apps/VISR1228/fs1/FMW_Home/webtier

ORACLE_HOME=/Apps/apps/VISR1228/fs1/FMW_Home/oracle_common

ORACLE_HOME=/Apps/apps/VISR1228/fs1/FMW_Home/wlserver_10.3

Weblogic patch 

./bsu.sh -prod_dir=$FMW_HOME/wlserver_10.3 -status=applied -view 

export ORACLE_HOME=$FMW_HOME

cd $ORACLE_HOME/utils/bsu/

[applvis@osirel1226 bsu]$ pwd

/ebsdev/app/dev/fs1/FMW_Home/utils/bsu

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=CW9T verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=BLTG verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=FCX7 -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=1LRI -verbose

./bsu.sh -remove -prod_dir=/ebsdev/apps/VISR1228/fs1/FMW_Home/wlserver_10.3/ -patchlist=2GYW -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=FCX7 -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=2GYW -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=VKXF -verbose 

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=FCX7 -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=Y5AP -verbos

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=Y5AP -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=VKXF -verbose

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=CIH8 –verbose

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=GFWX -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=S5C9 -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=S5C9 -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=S5C9 -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=HMR4 -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=HMR4 -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=F5QI -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=DI8E -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=DI8E -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=DN1F -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=DN1F -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -remove -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/ -patchlist=CIH8 -verbose

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=DN1F -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=EN8U -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=EN8U -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=XNBA -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=XNBA -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=ETK1T -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

./bsu.sh -install -patch_download_dir=/ebsdev/app/dev/fs1/FMW_Home/utils/bsu/cache_dir -patchlist=TK1T -prod_dir=/ebsdev/app/dev/fs1/FMW_Home/wlserver_10.3/

After patches applied above all  > run ./checkMTpatch.sh one more time .

All required one-offs are confirmed as present.

Apply the consolidated seed table upgrade Patch 26787701:12.2.0 on the run file system using adop hotpatch mode.

1. Stop all application tier services on the run file system.

UNIX:

sh $ADMIN_SCRIPTS_HOME/adstpall.sh

2. Start up only the Oracle Weblogic Admin Server on the run file system.

UNIX:

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

2.2 Apply Consolidated Seed Table Upgrade Patch 26787701:12.2.0

Apply the consolidated seed table upgrade Patch 26787701:12.2.0 on the run file system using adop hotpatch mode.

adop phase=apply patches=26787701 hotpatch=yes

1. Start up only the Oracle Weblogic Admin Server on the run edition application tier file system.

UNIX:

$ sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

2. Unzip patches and run adgrants.

a. Download and unzip the following patches:

 Patch 26834480 (R12.AD.C.Delta.11)

 Patch 28840822 (R12.TXK.C.Delta.11)

Note: You should also download and unzip any additional applicable patches from Section 4: Apply Additional Critical Patches.

b. Execute adgrants by following the instructions in the readme of Patch 26834480, which includes the latest version of adgrants.

3. On the run edition application tier file system, apply Patch 26834480 (R12.AD.C.Delta.11) in hotpatch mode.

Note: Do not merge Patch 26834480 with any other patches.

UNIX:

$ adop phase=apply patches=26834480 hotpatch=yes

Applying the Consolidated Seed Table Upgrade Patch (required)

Apply the consolidated seed table upgrade Patch 26787701:12.2.0 on the run file system using adop hotpatch mode.

adop phase=apply patches=26787701 hotpatch=yes

Applying the Latest AD and TXK Patchsets (required)

-> Source the run edition environment file

-> Start up only the Oracle Weblogic Admin Server on the run edition application tier file system

sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh start

  UNIX:

     $ sqlplus /nolog

     SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql <APPS schema name>

-> Unzip patches and run adgrants.

- Download and unzip the following patches:

Patch 26834480 (R12.AD.C.Delta.11)

Patch 28840822 (R12.TXK.C.Delta.11)

Execute adgrants by following the instructions in the readme of Patch 26834480, which includes the latest version of adgrants.

-> On the run edition application tier file system, apply Patch 26834480 (R12.AD.C.Delta.11) in hotpatch mode.

adop phase=apply patches=26834480 hotpatch=yes

-> On the run edition application tier file system, use hotpatch mode to apply Patch 28840822 (R12.TXK.C.Delta.11) (plus any additional critical patches.

adop phase=apply patches=28840822,29965377,29781255 hotpatch=yes merge=yes

-> Run the Middle Tier EBS Technology Codelevel Checker (MT-ETCC)

-> Stop Oracle WebLogic Server's Admin Server and Node Manager services on run filesystem

sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

-> Update the database tier with the latest patches. 

-> On the application tier EBSapps.env run

- Execute the admkappsutil.pl utility to create the appsutil.zip file in <INST_TOP>/admin/out

perl <AD_TOP>/bin/admkappsutil.pl

-> On the database tier (as the ORACLE user)

- Source the environment for RDBMS ORACLE_HOME.

- Copy or FTP the appsutil.zip file to <RDBMS ORACLE_HOME>.

- Uncompress appsutil.zip, under <RDBMS ORACLE_HOME>.

On the Database Tier

[

[dbtest@erpdev ~]$  unzip -o appsutil.zip

- Run AutoConfig on <RDBMS ORACLE_HOME>.

sh <RDBMS_ORACLE_HOME>/appsutil/scripts/<CONTEXT_NAME>/adautocfg.sh

-> Run AutoConfig on the run file system.

sh <INST_TOP>/admin/scripts/adautocfg.sh

Section 6: Apply the Latest AD and TXK Delta Release Update Packs

SQL > Drop user mobileadmin cascade;

If you have a lower version of the file(s) listed below or you have performed customizations on any of these packages, create a back-up of your file(s) under $APPL_TOP_NE/.

Package Name File Version

FLM_KANBAN_CUSTOM_PKG flmkacps.pls

120.3.12026000.2

flmkacpb.pls

120.3.12026000.2

Applying the Latest Oracle E-Business Suite Release Update Pack for Release 12.2 (required)

-> Source the run edition applications environment.

EBSapps.env run

-> Stop Oracle WebLogic Server's Admin Server and Node Manager services.

sh $ADMIN_SCRIPTS_HOME/adadminsrvctl.sh stop

-> Stop the Oracle WebLogic Server Node Manager service on the run file system

sh $ADMIN_SCRIPTS_HOME/adnodemgrctl.sh stop

Apply Oracle E-Business Suite 12.2.9 Release Update Pack Patch 28840850 on the run edition application environment, using downtime mode.

UNIX:

$ adop phase=apply apply_mode=downtime patches=28840850

Log file 

Applying patch 28840850.

    Log: /ebsprod/app/PROD/fs_ne/EBSapps/log/adop/2/20260109_161011/apply/appsnode/28840850/log/u28840850.log

Running finalize actions for the patches being applied.

    Log: @ADZDSHOWLOG.sql "2026/01/09 23:28:46"

Running cutover actions for the patches being applied.

    Creating workers to process cutover DDL in parallel

    Log: /ebsprod/app/PROD/fs_ne/EBSapps/log/adop/2/20260109_161011/apply/appsnode/log/cutover.log

    Performing database cutover in Quick mode

    [ERROR]     [CUTOVER 8:3 ddl_id=33754] ORA-00942: table or view does not exist SQL: alter materialized view APPS."DDR_SV_SLSR_C_MV" evaluate using current edition

    [ERROR]     [CUTOVER 8:1 ddl_id=33808] ORA-00942: table or view does not exist SQL: alter materialized view APPS."DDR_SV_ORDR_C_MV" evaluate using current edition

    [ERROR]     [CUTOVER 8:1 ddl_id=33816] ORA-00942: table or view does not exist SQL: alter materialized view APPS."DDR_BS_SHIP_ITM_BU_WK_MV" evaluate using current edition

    [WARNING]   [CUTOVER 8:1] There are still 11 failed jobs in CUTOVER phase

    [ERROR]     [CUTOVER 8:2 ddl_id=33809] ORA-00942: table or view does not exist SQL: alter materialized view APPS."DDR_SV_SHIP_C_MV" evaluate using current edition

    [ERROR]     [CUTOVER 8:2 ddl_id=33817] ORA-00942: table or view does not exist SQL: alter materialized view APPS."DDR_SV_INV_INT_C_MV" evaluate using current edition

    [WARNING]   [CUTOVER 8:2] There are still 12 failed jobs in CUTOVER phase

    [WARNING]   [CUTOVER 8:3] There are still 11 failed jobs in CUTOVER phase

    [WARNING]   [CUTOVER 8:7] There are still 10 failed jobs in CUTOVER phase

    [WARNING]   [CUTOVER 8:6] There are still 9 failed jobs in CUTOVER phase

    [WARNING]   [CUTOVER 8:5] There are still 8 failed jobs in CUTOVER phase

    [WARNING]   [CUTOVER 8:8] There are still 7 failed jobs in CUTOVER phase

    [WARNING]   [CUTOVER 8:4] There are still 6 failed jobs in CUTOVER phase

Generating post apply reports. 

Generating log report.

    Output: /ebsprod/app/PROD/fs_ne/EBSapps/log/adop/2/20260109_161011/apply/appsnode/adzdshowlog.out

The apply phase completed successfully.

adop exiting with status = 0 (Success)

[applprod@appsnode scripts]$ 

 

•  Start all application tier services on the run file system.

UNIX:

$ sh $ADMIN_SCRIPTS_HOME/adstrtal.sh

•  Perform adop cleanup action.

UNIX:

$ adop phase=cleanup

•  Synchronize file systems

Synchronize the file systems using the command shown below. This action will copy the new run edition code and configuration to the other file system, to ensure that both file systems are in sync before applying patches using the regular adop cycle on the other file system.

$ adop phase=fs_clone

Post-Update Steps

•  Apply Oracle E-Business Suite Release 12.2.9 Online Help

Apply Oracle E-Business Suite Release 12.2.9 Online Help Patch 28840900 using adop hotpatch mode on the run file system.

$ adop phase=apply patches=28840900 hotpatch=yes

The syntax to run an empty patch cycle is:

adop phase=prepare,finalize,cutover,cleanup

This concludes EBs R12.2.9 installation successfully completed login the ebs and test the basic sanity check and release instance for testing .

Thanks,

Srini