Oracle Apps DBA Quick Win: Fixing Workflow Down Issue in Minutes Learn how an Oracle Apps DBA resolved a Workflow down issue in Oracle E-Business Suite (EBS) within minutes. A simple restart brought the system back online 🚨 Introduction As DBAs, we’re often seen as firefighters — when systems go down, everyone looks to us to bring them back up. Recently, I handled a quick but critical Oracle E-Business Suite (EBS) Workflow down issue in a non-production environment . What looked alarming at first turned out to be a simple fix. This post explains what happened, how I approached it, and what you can learn from it. 🔎 The Scenario Environment: Non-Production Oracle EBS Issue: Workflow was down in the client’s front-end application Alert: Generated from monitoring tools / user escalation When the Workflow component in Oracle EBS stops functioning, users immediately face disruptions in their day-to-day tasks. 🛠️ Troubleshooting Steps Verified the backend Checke...
Posts
Concurrent Manager (CM) Overview and Real-Time Handling – Oracle EBS Overview of Concurrent Manager (CM): Concurrent Manager is an important part of Oracle E-Business Suite. It is responsible for running background jobs and tasks submitted by users. These tasks are called concurrent requests and can be reports, PL/SQL programs, or system-related jobs. CM makes sure these jobs are handled properly without overloading the system. There are different types of managers like Standard Manager, Inventory CM, and Internal Manager, each handling different kinds of jobs. How a User Request Becomes a CM Job: When a user submits a job from the front-end (like Payroll or a report), Oracle creates a concurrent request for it. This gets stored in a table ( FND_CONCURRENT_REQUESTS ). The request includes details like program name, parameters, and status. The Internal Manager assigns the job to the right CM based on setup. Some programs also trigger multiple sub-requests or child requests. The ac...
How to Upgrade the Oracle Database: A Complete Guide When Should You Upgrade Your Oracle Database? If you're using older Oracle database versions like 10g or 11g, it's time to consider upgrading. Oracle has officially stopped supporting these versions, meaning they no longer receive security updates, bug fixes, or performance enhancements. To ensure better security, improved performance, and compliance with Oracle's latest features, upgrading to a newer version such as Oracle 19c or 21c is recommended. Does Upgrading Always Improve Performance? While upgrading provides many benefits, it doesn't always guarantee improved performance. In some cases, you may encounter issues if the upgrade is not properly planned. One critical factor to consider is server compatibility. Example: If your database is running on Oracle Linux 7.9, upgrading to Oracle 19c should work fine. However, Oracle 21c is not compatible with this OS version. This means you cannot directly upgrade to Orac...
Complete Guide to Oracle Database Patching: CPU, PSU, and Bug Fix Patches What is Oracle Patching? Patching is a crucial process in Oracle Database Management , where software updates are applied to fix bugs, security vulnerabilities, and performance issues . Oracle releases patches regularly to enhance the database's stability and security. Why is Patching Important? Fixes known bugs that affect database performance. Addresses security vulnerabilities to protect against cyber threats. Ensures better stability and database uptime. Required for Oracle Support compliance . How Oracle Database Patching Works Oracle Database is written in Java and is used to store and manage large amounts of data. Patching is performed at the Oracle Software level rather than the database level. For example, after upgrading Oracle Database from 12c to 19c , a job that used to run for 2 hours started taking 8 hours . Upon contacting Oracle Support, it was identified as a bug, and they recommended ...
How to Perform Point-in-Time Recovery in Oracle Database Introduction Point-in-Time Recovery (PITR) in Oracle Database is a crucial process that allows administrators to restore data to a specific moment, preventing data loss in case of accidental deletions or corruption. This guide will walk you through restoring an Oracle database using RMAN (Recovery Manager) with incremental backups and archive logs . Step 1: Taking a Level-0 Backup Before performing PITR, we first take a Level-0 (Full) Backup of the database using RMAN. Checking the Initial Row Count We start by checking the total number of records in the U1.T3 table: SELECT COUNT(*) FROM U1.T3; Total records: 6 Executing Level-0 Backup The following RMAN script performs the Level-0 backup: RUN { ALLOCATE CHANNEL ch11 TYPE DISK MAXPIECESIZE 20G; ALLOCATE CHANNEL ch12 TYPE DISK MAXPIECESIZE 20G; ALLOCATE CHANNEL ch13 TYPE DISK MAXPIECESIZE 20G; BACKUP FORMAT '/data/rman/%d_D_%T_%u_s%s_p%p' INCREMENTAL ...
Oracle Database Restoration Process: Step-by-Step Guide Restoring an Oracle database is a crucial skill for Database Administrators (DBAs). This step-by-step guide will show you how to restore an Oracle database using RMAN (Recovery Manager), covering SPFILE, Control File, Data Files, and Archive Logs. What is Oracle Database Restoration? Database restoration is the process of recovering lost, corrupted, or dropped database components from a backup. This is essential for disaster recovery, ensuring minimal downtime and data integrity. Essential Files Required for Restoration Before starting, ensure you have a backup of these critical files: ✅ SP File (Server Parameter File) ✅ Control File ✅ Data Files ✅ Archive Log Files ⚠️ Pro Tip: Before taking a backup, always check the available free space in the backup location. If needed, manually delete old backups instead of using the DELETE BACKUP command, as it might remove all backups, including recent ones. Step 1: Taking a Backup Using R...
🛠️ Understanding Obsolete Backups in Oracle RMAN In Oracle RMAN (Recovery Manager) , managing obsolete backups is crucial for storage optimization and database performance . In this post, we'll explore: ✅ What are obsolete backups ? ✅ The difference between recovery window and redundancy . ✅ How to identify and delete obsolete backups efficiently. 📌 What Are Obsolete Backups in RMAN? An obsolete backup is any backup older than the defined retention policy . These backups are no longer needed for recovery and can be deleted to free up space. 🔍 How Are Backups Marked as Obsolete? RMAN classifies backups as obsolete based on: 1️ ⃣ Recovery Window Policy (Time-Based) 2️ ⃣ Redundancy Policy (Count-Based) Let’s break them down: ⏳ Recovery Window in RMAN A recovery window specifies how many days of backups should be retained. Any backups older than this window are marked as obsolete . 📌 Example : If the recovery window is set to 7 days , RMAN keeps...