Posts

Showing posts from June, 2012

Oracle Database Error Solutions & DBA Knowledge Base

Welcome to Oracle Database Error Solutions, a professional technical knowledge base dedicated to helping Oracle Database Administrators, Oracle E-Business Suite administrators, developers, and IT professionals troubleshoot Oracle Database and Oracle Linux issues with confidence.

This website provides practical, real-world troubleshooting guides based on hands-on Oracle administration experience. You'll find detailed solutions for Oracle Database errors, RMAN backup and recovery, Data Guard, ASM, RAC, Oracle Linux administration, Oracle E-Business Suite (EBS), cloning, performance tuning, patching, installation, and day-to-day DBA tasks.

Whether you're resolving ORA-27101, ORA-28040, ORA-01555, ORA-12154, ORA-01017, or other Oracle errors, our step-by-step articles are designed to save you time and help you solve problems efficiently.

UNDO tablespace increasing and not release space

UNDO tablespace increasing/growing and not release space Applies to:  Oracle Database 10gR2 Description: Undo tablespace start growing abnormally. UNDO_RETENTION parameter is set to 900 seconds, but undo data did not release the space. After doing some research work, I found the following solution: Solution: Set the following hidden parameter in init.ora file and check the free space in undo tablespace after 3-4 Hrs. _smu_debug_mode=33554432 or SQL> Alter system set "_smu_debug_mode" = 33554432; Related Oracle Errors ORA-01194 Error Fix in Oracle ORA-01555 Snapshot Too Old – Solution ORA-01017 Invalid Username Password – Fix ORA-12541 TNS No Listener – Solution 👉 Check our complete guide: Oracle Error Codes Guide Author Box About the Author Rana Abdul Wahid  is an experienced Oracle Database Administrator with expertise in Oracle Database Administration, Oracle Data Guard, RMAN Backup & Recovery, Oracle RAC, Oracle E-Bu...

tmp folder 100 percent full in linux

Image
tmp folder 100 percent full in Linux Description: I recently came across a problem where the /tmp folder was listed as 100% full: [root@prodapps01 ~]# df -h Filesystem            Size  Used Avail Use% Mounted on /dev/cciss/c0d0p2     9.7G  4.2G  5.1G  46% / /dev/cciss/c0d0p8     2.0G  152M  1.7G   9% /home /dev/cciss/c0d0p7     3.9G  3.9G  0M  100% /tmp /dev/cciss/c0d0p6     7.8G  334M  7.1G   5% /var /dev/cciss/c0d0p5      12G  3.2G  7.9G  29% /usr /dev/cciss/c0d0p1     494M   32M  437M   7% /boot Strangely, there were no files in the /tmp folder. This is how it happens. If you delete files from a folder and they still show up when you check a df -h disk status,...

Unable to Stop Apache – adapcctl.sh Exiting With Status 1 in Oracle E-Business Suite (EBS) R12/11i

Image
Unable to Stop Apache – adapcctl.sh Exiting With Status 1 in Oracle E-Business Suite (EBS) R12/11i Oracle E-Business Suite administrators frequently use the adapcctl.sh utility script to start and stop Apache services on the application tier. However, in some environments, attempting to stop Apache may fail with the following error: unable to stop apache adapcctl.sh: exiting with status 1 ERROR: Service cannot be stopped using this script This issue is commonly encountered in Oracle E-Business Suite 11i and R12 environments and is usually related to inconsistencies in the Apache runtime files stored under the Oracle Application Server logs directory. In this guide, we will explain the root cause, troubleshooting methodology, and step-by-step resolution for the adapcctl.sh exiting with status 1 error. Applies To Oracle E-Business Suite 11.5.10.2 Oracle E-Business Suite R12 Oracle Application Server (Apache) Oracle Apps DBA Administration Error Symptoms When ...

All Receiving Transactions Fail with rvtptcontrol Error

Image
All Receiving Transactions Fail with rvtptcontrol Error Description: All Receiving transactions fail with rvtptcontrol. After some research work I found that the error occurs when many transactions fail with same error it is usually because the receiving executables (RVCTP and RCVOLTM) are out of sync. Solution: 1.       Resolve INVALID Objects 1.1   Set environment 1.2   cd $ORACLE_HOME/rdbms/admin 1.3   sqlplus / as sysdba 1.4   SQL>@utlrp.sql 2.       Relink Receiving executables 2.1   cd $AD_TOP/bin 2.2   sh adrelink.sh force=y ranlib=y "PO RCVOLTM" 2.3   sh adrelink.sh force=y ranlib=y "PO RVCTP" 3         Bounce Receiving Transaction Manager: 3.1   (System Administrator > Concurrent > Manager > Administer) 3.2   Deactivate Receiving Transaction Manager 3.3   ps -ef | grep RCVOLTM (repeat until n...

Adcfgclone.pl dbTier Failed: RC-00110

Image
Adcfgclone.pl dbTier Failed: RC-00110 Description: On Applications 11.5.10.2, when attempting to clone using rapidclone the following error occurs: ERROR: -------- Log file located at ORACLE_HOME/appsutil/log/$SID_$HOSTNAME/ApplyDBTechStack_22472575.log RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack \ 40% completed ERROR while running Apply... ERROR: Failed to execute $RDBMS_ORACLE_HOME/appsutil/clone/bin/adclone.pl-- Found the following in Cloning log file: dest : $ORACLE_HOME/oui/bin/runInstaller.sh backup : $ORACLE_HOME/oui/bin/runInstaller.sh to $ORACLE_HOME/appsutil//out/$SID_$HOSTNAME/runInstaller.sh DEBUG : The destination file does not have write permission $ORACLE_HOME/oui/bin/runInstaller.sh DEBUG : Changing the permission of the file failed AC-00444: Unable to write to file: java.io.FileNotFoundException: $ORACLE_HOME/oui/bin/runInstaller.sh (Permission denied) Raised by oracle.apps.ad.autoconfig.InstantiateFile Afte...

ORA-19909: Datafile 1 Belongs to an Orphan Incarnation – Complete Oracle Recovery Guide

Image
ORA-19909: Datafile 1 Belongs to an Orphan Incarnation – Complete Oracle Recovery Guide The ORA-19909: datafile string belongs to an orphan incarnation error is an Oracle Database recovery-related error that occurs when Oracle determines that a datafile is associated with a database incarnation that is not part of the current recovery path, or when Oracle cannot correctly determine the database incarnation to which the datafile belongs. This problem can occur during Oracle Database recovery operations such as RMAN restore and recovery, database duplication, point-in-time recovery, or recovery after database incarnation changes. This guide explains what Oracle database incarnations are, why ORA-19909 occurs, how to diagnose the problem, when RESET DATABASE TO INCARNATION is appropriate, and how to approach the problem safely in different recovery scenarios. What You Will Learn What ORA-19909 means What an Oracle database incarnation is What an orphan incarnation m...

How to Resize Redo Logs on Primary and Standby Database in Oracle Data Guard – Complete DBA Guide

Image
How to Resize Redo Logs on Primary and Standby Database in Oracle Data Guard – Complete DBA Guide Managing redo log file size is one of the most important Oracle DBA tasks for maintaining database performance, archive log efficiency, and Data Guard synchronization. In Oracle Data Guard environments, resizing redo logs requires careful coordination between both the primary database and standby database to maintain proper log shipping and recovery consistency. Improper redo log sizing can lead to: Excessive log switches High archive generation Checkpoint performance issues Standby synchronization delays Database performance degradation Recovery inefficiencies In this complete Oracle DBA guide, you will learn: Why redo log resizing is important How redo logs work in Oracle How to resize redo logs safely How to manage redo logs in Data Guard Step-by-step primary and standby procedures Important Oracle SQL commands Best practices for redo log management What are ...

ORA-00474: SMON Process Terminated with Error – Complete Oracle DBA Recovery Guide

Image
The ORA-00474: SMON process terminated with error message is a serious Oracle Database startup and recovery issue that occurs when the System Monitor (SMON) background process crashes unexpectedly. The SMON process is one of the most critical Oracle background processes responsible for instance recovery, cleanup operations, transaction recovery, and space management. When SMON fails, Oracle may terminate the database instance automatically to protect database consistency. This error is commonly associated with: Corrupted undo tablespaces Corrupted rollback segments Data block corruption Oracle internal errors Storage or I/O failures Improper shutdowns Recovery inconsistencies In this complete Oracle DBA troubleshooting guide, you will learn: What ORA-00474 means Why the SMON process crashes How to analyze Oracle alert logs How to identify undo corruption How to recreate UNDO tablespaces How to recover database startup failures Best practices to prevent S...