Create a user in Oracle E-Business Suite (EBS) R12 from the backend (database) and assign system responsibilities

 Create a user in Oracle E-Business Suite (EBS) R12 from the backend (database) and assign system responsibilities 

Step 1: Connect to the Database

Log in to the Oracle EBS database using SQL*Plus or any SQL client:

sqlplus apps/apps@EBSDB

---

Step 2: Create the User in FND_USER

Run the following SQL statement to create a new user:

INSERT INTO fnd_user 
    (user_id, user_name, description, password, start_date, end_date, created_by, last_updated_by, last_update_login)
VALUES 
    (fnd_user_id_s.NEXTVAL, 'JOHNDOE', 'Finance User', fnd_web_sec.validate_login('Welcome123'),
     SYSDATE, NULL, 0, 0, 0);

COMMIT;

Explanation:

• user_name = 'JOHNDOE' → Replace with the actual username.
• password → Encrypted using fnd_web_sec.validate_login('password').
• start_date = SYSDATE → User is active from today.
• end_date = NULL → User does not have an expiration date.

---

Step 3: Assign Responsibilities

To assign a responsibility, find the responsibility_id first:

SELECT responsibility_id, responsibility_name 
FROM fnd_responsibility 
WHERE responsibility_name LIKE '%System Administrator%';

Then, use the retrieved responsibility_id (e.g., 20420) to assign it to the user:

INSERT INTO fnd_user_resp_groups_direct 
    (user_id, responsibility_id, responsibility_application_id, security_group_id, start_date, end_date, created_by, last_updated_by, last_update_login)
VALUES 
    ((SELECT user_id FROM fnd_user WHERE user_name = 'JOHNDOE'), 
     20420, 1, 0, SYSDATE, NULL, 0, 0, 0);

COMMIT;

Explanation:

• responsibility_id = 20420 → Replace with the correct responsibility ID.
• responsibility_application_id = 1 → Usually Application Object Library (AOL).
• security_group_id = 0 → Default security group.
• start_date = SYSDATE → Responsibility is active immediately.

---

Step 4: Verify User and Responsibilities

Check if the user has been created:

SELECT user_id, user_name, start_date, end_date 
FROM fnd_user 
WHERE user_name = 'JOHNDOE';

Verify assigned responsibilities:

SELECT fu.user_name, fr.responsibility_name 
FROM fnd_user fu
JOIN fnd_user_resp_groups_direct frg ON fu.user_id = frg.user_id
JOIN fnd_responsibility fr ON frg.responsibility_id = fr.responsibility_id
WHERE fu.user_name = 'JOHNDOE';

---

Step 5: Force Password Reset (Optional)

If you want the user to change their password at the first login, update:

UPDATE fnd_user 
SET password_date = NULL 
WHERE user_name = 'JOHNDOE';

COMMIT;

---

Step 6: Inform the User

• Provide the username (JOHNDOE) and the initial password (Welcome123).
• The user should log in via EBS and change their password.

---

Troubleshooting

1. User Cannot Log In?

   • Ensure the user is not end-dated:

     SELECT user_name, end_date FROM fnd_user WHERE user_name = 'JOHNDOE';

   • Ensure the responsibility is active:

     SELECT * FROM fnd_user_resp_groups_direct 
     WHERE user_id = (SELECT user_id FROM fnd_user WHERE user_name = 'JOHNDOE') 
     AND end_date IS NULL;
     

2. Incorrect Password?

   • Reset the password manually:

     UPDATE fnd_user 
     SET password = fnd_web_sec.validate_login('NewPass123') 
     WHERE user_name = 'JOHNDOE';
     
     COMMIT;
     

---

Summary

✅ Created user in FND_USER
✅ Assigned responsibility in FND_USER_RESP_GROUPS_DIRECT
✅ Verified the user and permissions
✅ Informed the user

creating a user in Oracle E-Business Suite (EBS) R12 and assigning system responsibilities.

 Creating a user in Oracle E-Business Suite (EBS) R12 and assigning system responsibilities.

Step 1: Log in to Oracle EBS

1. Open a web browser and go to the Oracle EBS login page.
2. Enter your Username and Password.
3. Click Login.

---

Step 2: Navigate to User Management

1. Go to System Administrator responsibility.
2. Navigate to:
   Security → User → Define

---

Step 3: Create a New User

1. In the Users form, enter the following details:

   • User Name: (e.g., JOHNDOE)
   • Password: (Enter a temporary password; the user will change it on first login)
   • Description: (Optional, e.g., "Finance Team User")
   • Person: (If linked to an employee, click the LOV to select)
   • Customer/Supplier: (If applicable, choose the respective entity)
   • Email: (For notifications)
   • Effective Dates:
     • From: (Set to today’s date)
     • To: (Leave blank if the account is permanent)

2. Save the record (Ctrl + S or click the disk icon).

---

Step 4: Assign Responsibilities

1. In the same Users form, navigate to the Responsibilities block.
2. Click in the Responsibility Name field and enter the responsibility (use F11 to search if needed).
   • Examples:
     • System Administrator
     • Application Developer
     • General Ledger Super User
3. Save the record.

---

Step 5: Verify the User Account

1. Run the following SQL query in the database to verify the user:

   
   SELECT user_id, user_name, start_date, end_date 
   FROM fnd_user 
   WHERE user_name = 'JOHNDOE';
   

2. Check assigned responsibilities:

   
   SELECT fu.user_name, fr.responsibility_name
   FROM fnd_user fu
   JOIN fnd_user_resp_groups_direct frg ON fu.user_id = frg.user_id
   JOIN fnd_responsibility fr ON frg.responsibility_id = fr.responsibility_id
   WHERE fu.user_name = 'JOHNDOE';
   

---

Step 6: Inform the User

• Share the Username and Temporary Password with the user.
• Instruct them to log in and change the password at first login.

---

Step 7: Optional - Set Profile Options (If Needed)

To set profile options for the user:

1. Navigate to:
   System Administrator → Profile → System
2. Query the user and assign any required profile options (e.g., MO: Operating Unit).

---

Step 8: Validate Login and Responsibility Access

• The user should log in and verify they can access the assigned responsibilities.
• If any access issues arise, recheck responsibility assignments.

---

Troubleshooting

• If a user cannot log in:
  • Check if their account is Active (end_date should be NULL).
  • Reset their password in User Management.
  • Check for security rules restricting access.

Oracle Exadata -The Game Changer

Oracle Exadata -The Game Changer

Oracle Exadata: Revolutionizing Database Technology Since 2008

Since its launch in 2008, Oracle Exadata has been a game-changer in enterprise database systems, offering unmatched performance, scalability, and reliability. From the early versions to the cutting-edge Exadata X11M, Oracle has consistently pushed the boundaries of what’s possible in database technology. This article takes you through the evolution of Exadata, highlighting its innovations and impact on modern data management.

---

A Timeline of Innovation

Exadata V1 (2008): The Beginning

Oracle introduced the first-ever Database Machine, Exadata V1, which revolutionized data processing with:

• SQL Offloading: Offloading query processing to storage for faster results.
• I/O Resource Management: Prioritizing critical workloads to maximize performance.

Exadata V2 (2009): Flash and InfiniBand

Exadata V2 introduced groundbreaking features:

• Flash Cache: Drastically improved I/O speeds.
• Hybrid Columnar Compression: Reduced storage costs.
• InfiniBand Networking: Enabled ultra-fast data transfers.

Exadata X2 (2010): Accessibility for All

Making high-performance databases more accessible, X2 brought:

• 1/8 Rack Configurations: A cost-effective option for smaller enterprises.
• Flash Cache Write-Back: Improved write performance for OLTP workloads.

Exadata X3 (2012): The In-Memory Era

With Exadata X3, Oracle introduced:

• In-Memory Database Technology: Boosting real-time analytics.
• Elastic Configurations: Flexible storage and compute scaling.

Exadata X4 to X6 (2013-2016): Analytics and Efficiency

Oracle enhanced analytics and efficiency with:

• Columnar Flash Cache: Faster analytics on compressed data.
• Hot-Swap Flash Cards: Increased reliability by minimizing downtime.
• In-Memory Analytics: Accelerated query performance.

Exadata X7 to X8M (2017-2019): Performance Boosts

These versions set new performance standards:

• Automatic Indexing: Reduced manual intervention in query optimization.
• Memory Acceleration with RDMA: Delivered 160% performance boosts.
• PCIe Gen4 and RoCE: Further improved I/O throughput.

Exadata X9M (2021): Enterprise-Grade Innovation

The X9M was a step closer to perfection:

• Storage Index Persistence: Reduced query latencies.
• Extended Storage: Accommodated growing data workloads.

Exadata X10M (2023): Towards Autonomy

The X10M introduced:

• RDMA Memory: Near-zero latency for high-frequency applications.
• Capacity-Optimized Flash: Enhanced performance at reduced costs.

Exadata X11M (2025): AI and Sustainability

The latest Exadata X11M focuses on:

• AI Vector Search Accelerators: Optimized for machine learning workloads.
• Exascale Architecture: Unprecedented scalability for enterprise workloads.
• Energy Efficiency: New features for sustainable computing.

---

What Makes Oracle Exadata Unique?

1. Unparalleled Performance:

   • SQL offloading, hybrid columnar compression, and memory acceleration set Exadata apart from traditional systems.

2. Scalability for Any Enterprise:

   • Elastic configurations and exascale architecture accommodate businesses of all sizes.

3. Reliability and Uptime:

   • Features like hot-swappable components and advanced storage tiering ensure minimal downtime.

4. Future-Ready Technology:

   • AI-driven optimizations, PCIe Gen5, and sustainability features prepare enterprises for the future.

---

Why Exadata Matters for Modern Enterprises

As businesses grow increasingly data-driven, the need for high-performance, reliable, and scalable databases has never been greater. Exadata meets these demands, offering:

• Real-Time Analytics: Delivering insights at the speed of business.
• Cost Efficiency: Reducing storage and compute costs with intelligent optimizations.
• Seamless Integration: Compatible with Oracle Cloud and on-premises environments.

---

Conclusion

Oracle Exadata’s journey from V1 to X11M is a testament to Oracle's commitment to innovation and excellence. It has redefined database management by introducing features that address the evolving needs of businesses, from high-speed analytics to AI-ready architecture.

Whether you’re looking to handle massive transactional workloads, analyze petabytes of data, or adopt autonomous databases, Exadata is the trusted solution. With a proven track record and future-focused roadmap, Exadata remains the ultimate choice for enterprises worldwide.

Step By Step Oracle Database 19c Release Update (DB+OJVM) for Single Instance (19.24 to 19.25)

 

Step By Step Oracle Database 19c Release Update   (DB+OJVM) for Single Instance (19.24 to 19.25)

Step by Step Document  how to perform Oracle Database 19c Release Update (DB+OJVM) for Single Instance (19.24 to 19.25). I hope it will be useful for those who need it!

High Level Steps

1-Prerequisites

2-Download Patches

3- Copy Patches to Servers

4- Check & Update OPATCH Utility

5- Verify the Database Current Version

6-Take Necessary Backups

7-Pre Patch Steps

8-Patch Steps

9-Post Patch Steps

10-Patch Deinstallation Steps (If Needed)

Low Level Steps

1-Prerequisites

• You must go throw the README files
  • Patch 36912597 – Database Release Update 19.25.0.0.241015
  • Patch 36878697 – Oracle JavaVM Component Release Update 19.25.0.0.241015
• You must use the OPatch utility version 12.2.0.1.43 or later to apply this patch.

2-Download Patches

• Download Latest OPATCH Version
• Download 19.25 DBRU and OJVM Patches

3-Copy Patches to Servers

I have copied patches to /u01/software/ directory.

4-Check & Update OPATCH Utility

You must use the OPatch utility version 12.2.0.1.43 or later to apply this patch.

Check OPATCH version

Check Version

sudo su -
su - oracle
. oraenv
cd $ORACLE_HOME/OPatch
./opatch version

# Sample Output
[oracle@oraclelinux810-test OPatch]$ ./opatch version
OPatch Version: 12.2.0.1.44
OPatch succeeded.
[oracle@oraclelinux810-test OPatch]$

Backup Current OPatch (Skip if you have the latest version of OPatch)

cd $ORACLE_HOME
mv OPatch OPatch_12.2.0.1.43

Upgrade OPATCH (Skip if you have the latest version of OPatch)

cd /u01/software/
unzip /u01/software/p6880880_190000_Linux-x86-64 -d $ORACLE_HOME/

Check Version

cd $ORACLE_HOME/OPatch
./opatch version

5-Verify the Database Current Version

Using the below command verify the current version details and some other information related to the database.

sqlplus / as sysdba

select BANNER_FULL from v$version;

BANNER_FULL
--------------------------------------------------------------------------------
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.24.0.0.0

col comp_id for a10
col version for a11
col status for a10
col comp_name for a37
select comp_id,comp_name,version,status from dba_registry;

COMP_ID    COMP_NAME                             VERSION     STATUS
---------- ------------------------------------- ----------- ----------
CATALOG    Oracle Database Catalog Views         19.0.0.0.0  VALID
CATPROC    Oracle Database Packages and Types    19.0.0.0.0  VALID
RAC        Oracle Real Application Clusters      19.0.0.0.0  OPTION OFF
JAVAVM     JServer JAVA Virtual Machine          19.0.0.0.0  VALID
XML        Oracle XDK                            19.0.0.0.0  VALID
CATJAVA    Oracle Database Java Packages         19.0.0.0.0  VALID
APS        OLAP Analytic Workspace               19.0.0.0.0  VALID
XDB        Oracle XML Database                   19.0.0.0.0  VALID
OWM        Oracle Workspace Manager              19.0.0.0.0  VALID
CONTEXT    Oracle Text                           19.0.0.0.0  VALID
ORDIM      Oracle Multimedia                     19.0.0.0.0  VALID
SDO        Spatial                               19.0.0.0.0  VALID
XOQ        Oracle OLAP API                       19.0.0.0.0  VALID
OLS        Oracle Label Security                 19.0.0.0.0  VALID
DV         Oracle Database Vault                 19.0.0.0.0  VALID

15 rows selected.

6-Take Necessary Backups

Due to any type of error if patching got failed, then you must have a backup plan.

• Take Oracle Home Backup
• Take Central Inventory Backup
• Create Guaranteed Restore Point

Take Oracle Home Backup (if you have enough disk space)

How to Perform ORACLE_HOME Backup? (Doc ID 565017.1)

# Backup
# (Suggested but not mandatory) Shutdown databases, listeners, or any other processes related to the ORACLE_HOME which you are taking backup.
# Make sure there is enough free disk space before doing the backup.
cd /u01/app/oracle/product/<version>/
tar -pcvf /u01/backup/oracle_home_bkup_DDMMYYYY.tar <dbhomename>


# Restore
# (This step would be mandatory in the case of restore) Shutdown databases, listeners, or any other processes related to the ORACLE_HOME which you are restoring.
cd /u01/app/oracle/product/<version>/
mv <dbhomename> <dbhomename_DDMMYYYY>
tar -pxvf /u01/backup/oracle_home_bkup_DDMMYYYY.tar

Take Central Inventory Backup

# Backup
# (Suggested but not mandatory) Shutdown databases, listeners, or any other processes related to the ORACLE_HOME which you are taking backup.
more /etc/oraInst.loc
cd /u01/app/
tar -pcvf /u01/backup/oraInventoryBackup_DDMMYYYY.tar oraInventory

# Restore
# (This step would be mandatory in the case of restore) Shutdown databases, listeners, or any other processes related to the ORACLE_HOME which you are restoring.
cd /u01/app/
mv oraInventory oraInventory_DDMMYYYY
tar -pxvf /u01/backup/oraInventoryBackup_DDMMYYYY.tar

Create Guaranteed Restore Point

# Create Guaranteed Restore Point
1. $> su – oracle
2. $> sqlplus / as sysdba;
3. Find out if ARCHIVELOG is enabled
   SQL> select log_mode from v$database;
   If step 3 shows that ARCHIVELOG is not enabled then continue else skip to step 8 below.
4. SQL> shutdown immediate;
5. SQL> startup mount;
6. SQL> alter database archivelog;
7. SQL> alter database open;
8. SQL> create restore point before_upgrade guarantee flashback database;
   where CLEAN_DB is the name given to the guaranteed restore point.
9. Viewing the guaranteed restore point
   SQL> select * from v$restore_point;
   Verify the information about the newly created restore point. Also, note down the SCN# for
   reference and we will refer to it as "reference SCN#"

# Flashback to the Guaranteed Restore Point
1. $> su – oracle
2. $> sqlplus / as sysdba;
3. SQL> select current_scn from v$database;
4. SQL> shutdown immediate;
5. SQL> startup mount;
6. SQL> select * from v$restore_point;
7. SQL> flashback database to restore point before_upgrade;
8. SQL> alter database open resetlogs;
9. SQL> select current_scn from v$database;
Compare the SCN# from step 9 above to the reference SCN#.
NOTE: The SCN# from step 9 above may not necessarily be the exact SCN# as the reference SCN# but it will be close enough.

# Drop Guaranteed Restore Point
drop restore point before_upgrade;

7-Pre Patch Steps

Unzip the Patches

cd /u01/software/

unzip /u01/software/p36912597_190000_Linux-x86-64.zip -d /u01/software/

unzip /u01/software/p36878697_190000_Linux-x86-64.zip -d /u01/software/

Check Conflict

cd /u01/software/36912597

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./

cd /u01/software/36878697

$ORACLE_HOME/OPatch/opatch prereq CheckConflictAgainstOHWithDetail -ph ./

Stop All Database Services

Check how many instances & listener is running on the machine.

ps -ef|grep pmon

oracle      2124       1  0 Dec16 ?        00:00:01 ora_pmon_orcl

Check the Listener status.

ps -ef|grep tns

oracle      6524       1  0 00:48 ?        00:00:00 /u01/app/oracle/product/19.3/db_home/bin/tnslsnr LISTENER -inherit

On my machine, one instance and one listener are currently running, letting down both services.

lsnrctl stop LISTENER

Shutdown Database

sqlplus / as sysdba

shut immediate

8-Patch Steps

Make sure 7 GB of disk space is free in your binary location otherwise the patch will be failed.

Execute opatch apply

cd /u01/software/36912597

$ORACLE_HOME/OPatch/opatch apply

cd /u01/software/36878697

$ORACLE_HOME/OPatch/opatch apply

Start All Database Services

Once opatch apply successfully, then start all the database services.

Start Listener

lsnrctl start LISTENER

Start Database

sqlplus / as sysdba

startup

Check Database

select instance_name ||'  '||version||'  '||startup_time||'  '||database_status from gv$instance;

INSTANCE_NAME||''||VERSION||''||STARTUP_TIME||''||DATABASE_STATUS
---------------------------------------------------------------------------
orcl  19.0.0.0.0  2024-12-17:12:51:04  ACTIVE


select name, open_mode, database_role, log_mode from gv$database;

NAME      OPEN_MODE            DATABASE_ROLE    LOG_MODE
--------- -------------------- ---------------- ------------
ORCL      READ WRITE           PRIMARY          NOARCHIVELOG

9-Post Patch Steps

Now it’s time to run datapatch -verbose which updates the patch information at the database binary & dictionary level as well as binary files.

Run datapatch -verbose

Important Note: For each separate database running on the same shared Oracle home being patched, run the datapatch utility

. oraenv

cd $ORACLE_HOME/OPatch

./datapatch -sanity_checks (optional)

./datapatch -verbose

Execute utlrp.sql

Once datapatch -verbose is completed then execute the utlrp script to validate the invalid objects.

sqlplus / as sysdba

@?/rdbms/admin/utlrp.sql

Verify the Patch at OS Level

Check applied patch details using lsinventory command.

cd $ORACLE_HOME/OPatch

./opatch lsinventory | grep 36912597

./opatch lsinventory | grep 36878697

Verify the Patch at DB Level

sqlplus / as sysdba

col action for a8
col status for a10
col action_time for a28
col description for a60
set line 999 pages 999
select patch_uid,patch_id,SOURCE_VERSION, TARGET_VERSION, action, status,action_time,description from dba_registry_sqlpatch order by action_time desc;

Check Invalid Objects

COLUMN object_name FORMAT A30
SELECT owner,object_type,object_name,status FROM dba_objects
WHERE status = 'INVALID'
ORDER BY owner, object_type, object_name;

no rows selected

Check DBA_REGISTRY

col comp_id for a10
col version for a11
col status for a10
col comp_name for a37
select comp_id,comp_name,version,status from dba_registry;

COMP_ID    COMP_NAME                             VERSION     STATUS
---------- ------------------------------------- ----------- ----------
CATALOG    Oracle Database Catalog Views         19.0.0.0.0  VALID
CATPROC    Oracle Database Packages and Types    19.0.0.0.0  VALID
RAC        Oracle Real Application Clusters      19.0.0.0.0  OPTION OFF
JAVAVM     JServer JAVA Virtual Machine          19.0.0.0.0  VALID
XML        Oracle XDK                            19.0.0.0.0  VALID
CATJAVA    Oracle Database Java Packages         19.0.0.0.0  VALID
APS        OLAP Analytic Workspace               19.0.0.0.0  VALID
XDB        Oracle XML Database                   19.0.0.0.0  VALID
OWM        Oracle Workspace Manager              19.0.0.0.0  VALID
CONTEXT    Oracle Text                           19.0.0.0.0  VALID
ORDIM      Oracle Multimedia                     19.0.0.0.0  VALID
SDO        Spatial                               19.0.0.0.0  VALID
XOQ        Oracle OLAP API                       19.0.0.0.0  VALID
OLS        Oracle Label Security                 19.0.0.0.0  VALID
DV         Oracle Database Vault                 19.0.0.0.0  VALID
15 rows selected.

10-Patch Deinstallation Steps (If Needed)

Patch Deinstallation Instructions

Shut down all instances and listeners associated with the Oracle home that you are updating.

sudo su -
su - oracle
. oraenv
lsnrctl stop LISTENER
sqlplus / as sysdba
shut immediate
quit
cd $ORACLE_HOME/OPatch
opatch rollback -id 36912597
opatch rollback -id 36878697
Rollback SQL Changes from the the Database
Datapatch is run to complete the post-deinstall SQL deployment for the patch being deinstalled.
Important Note: For each separate database running on the same shared Oracle home being patched, run the datapatch utility.
lsnrctl start LISTENER
sqlplus / as sysdba
startup
quit
cd $ORACLE_HOME/OPatch
./datapatch -sanity_checks (optional)
./datapatch -verbose

Workflow debugging scripts wfstat.sql

 Understanding the Workflow debugging scripts wfstat.sql

The wfstat.sql script is a valuable tool used in Oracle E-Business Suite (EBS) for debugging and understanding the status and flow of workflows. It helps track, analyze, and debug workflow-related issues by providing detailed insights into the workflow statuses, activities, notifications, and related details.

Here’s how to understand and use the wfstat.sql script for debugging workflows:

---

Purpose of wfstat.sql

• To fetch the status of a specific workflow instance.
• To provide detailed information on the workflow's current state, activities, notifications, and their statuses.
• To debug issues in workflow execution, such as stuck or errored activities.

---

Key Parameters of wfstat.sql

1. ITEM_TYPE: The type of workflow item (e.g., REQAPPR for requisition approval, POAPPRV for purchase order approval).
2. ITEM_KEY: The unique identifier for a specific workflow instance.
3. USER_ID (optional): Used to filter workflow details specific to a user.
4. ACTIVITY_STATUS: Filters activities based on their status (e.g., OPEN, COMPLETED, ERROR).

---

Steps to Use wfstat.sql

1. Locate the script: The wfstat.sql script is typically located in $FND_TOP/sql/ or your database administrator may provide access to the script.
2. Run the script: Execute the script using SQL*Plus or a similar SQL client.

   SQL> @wfstat.sql

3. Provide Input: Enter the required parameters such as ITEM_TYPE and ITEM_KEY when prompted.
4. Analyze the Output:
   • Workflow Instance Information: Details about the workflow, including creation date, status, and current owner.
   • Activity Statuses: Shows activities in the workflow, their status (OPEN, COMPLETED, ERROR), and timestamps.
   • Notifications: Information on notifications sent as part of the workflow, including status (SENT, CANCELED, ERROR).
   • Error Details: If an activity is in error, the output will indicate the error message or stack trace.

---

Debugging Common Issues

1. Stuck Activities:
   • Check for OPEN activities that have not progressed.
   • Identify the ACTIVITY_NAME and trace the issue in the corresponding PL/SQL procedure or function.
2. Errored Activities:
   • Look for activities with the status ERROR.
   • Review the error messages or stack trace in the output.
3. Notification Issues:
   • Check the notification statuses (SENT, CANCELED, ERROR).
   • If notifications are not being sent, verify the workflow mailer service and notification preferences.
4. Workflow Ownership:
   • Ensure that the workflow item has the correct owner (RUNNING or DEFERRED).
   • Reassign ownership if necessary using administrative workflow tools.

---

Proactive Measures

• Schedule regular audits of critical workflows using scripts like wfstat.sql.
• Monitor notifications and activity logs for potential issues.
• Automate repetitive tasks in workflow monitoring using shell scripts or custom reports.

By using the wfstat.sql script effectively, you can identify, troubleshoot, and resolve workflow-related issues, ensuring seamless operation of Oracle E-Business Suite workflows.

While logging a bug in Workflow area, it is always advisable to provide output of some of the diagnostic scripts such as wfstat.sql. This blog provides a detailed description about the usage of and the information this script provide. Output of wfstat.sql script provides workflow activity details for a given workflow process. Output of wfmlrdbg.sql provides details about a particular notification that are used to debug any issues with a Workflow Notification. wfbesdbg.sql is used to debug the event and subscription related issues in Business Event System.

wfstat.sql

This script can be used to debug the workflow activity issues for a given workflow. It can be run using the below command. Use spool command to generate the output of this into a text file.

SQL>spool wfstat.txt
SQL>sqlplus apps/apps @$FND_TOP/sql/wfstat.sql <item type> <item key>
SQL>spool off;

It generates a text file called wfstat.txt that contains output of this script. You can get the following information from this:

1. Workflow item type and itemkey
2. Workflow activities' start time and end time
3. Parent process and child process information
4. Status and result of each activity
5. Start date and End date of each activity
6. Errored Activities and Error Process Activity Statuses
7. Notification details with notification id and notification recipient
8. Performer of each activity.

The following section explains each item from the output file:

WorkFlow Item

It provides item type, item key, start date and end date for the workflow item. It also provides the root activity details for the same.

Activity Statuses

It provides start date, end date, status, result for each of the activities. In addition to that it provides the performer user and notification ID for Notification activities. It also provides the sequence of execution of the activities.

Activity Statuses History

It provides status history of the all the actions performed on the different activities

Notifications

It provides information about a notification such as Notification ID, status, message name, begin date, end date, from-user, to-user, subject.

Errored Activities

It provides all the activities information that are resulted into ERROR status.

EBS 12.2 Certified with Database Release Update 19.25 - All Platforms (October 2024)

 EBS 12.2 Certified with Database Release Update 19.25 - All Platforms (October 2024)

Oracle announced the release of the October 2024 updates to the E-Business Suite (EBS) Technology Codelevel Checker (ETCC) - Part II.  The latest October 2024 updates for ETCC include the certification of Oracle Database Release Update (DBRU) 19.25(19.25.0.0.241015-Oct2024) for all UNIX and Windows platforms with Oracle E-Business Suite Release 12.2 on-premises.

For additional details, refer to Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Database Patches and Technology Bug Fixes (MOS Note 1594274.1)

References

• Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Database Patches and Technology Bug Fixes (MOS Note 1594274.1)
• Previous Oracle Database 19c Release Update Database Patch Lists for Oracle E-Business Suite (MOS Note 2683670.1)
• Oracle Database - Overview of Database Patch Delivery Methods for 12.2.0.1 and greater (MOS Note 2337415.1)
• Oracle E-Business Suite Release 12.2: Consolidated List of Oracle Fusion Middleware Patches and Technology Bug Fixes (Doc ID 2877607.1)
• Information Center: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1 (MOS Note 2655839.2)

Related Articles

• October 2024 Update to EBS Technology Codelevel Checker (ETCC) - Part II
• October 2024 Update to EBS Technology Codelevel Checker (ETCC) - Part I
• July 2024 Update to EBS Technology Codelevel Checker (ETCC) - Part II
• July 2024 Update to EBS Technology Codelevel Checker (ETCC) - Part I
• April 2024 Update to EBS Technology Codelevel Checker (ETCC) - Part II
• April 2024 Update to EBS Technology Codelevel Checker (ETCC) - Part I
• January 2024 Update to EBS Technology Codelevel Checker (ETCC) 
• New Alert for EBS and Oracle Database 12.1.0.2 and 11.2.0.4
• Reminder: End of Error Correction Support for Oracle Database 12.1.0.2
• Updated: Oracle Database 19c Certified with EBS 12.2
• New MOS Note: Oracle Database 19c with Oracle E-Business Suite 12.2 and 12.1
• Oracle E-Business Suite Technology Blog - Database Tier Announcements