Archive for the ‘Oracle’ Category

« Older Entries

Obsolete Backups Vs RMAN Expired

August 30th, 2026, posted in Oracle EBS Application, Oracle Queries
Share

Obsolete Backups Vs RMAN Expired

Understand and manage expired and obsolete backups in RMAN.

Two terms that are very important when it comes to RMAN backups validation they are

  • Expired Backups
  • Obsolete Backups

Expired backups

Let’s take you trigger an RMAN backup and someone deleted backup set or backup pieces at OS level. The database CONTROFILE has the details of the backup on disk but at OS level the backup file does not exists.
We can run RMAN crosscheck command to check if backup files exists at OS level or not. If the backup files are not found, RMAN will mark it as EXPIRED.

RMAN> crosscheck backup;

DBA Action

The first action a DBA must take is to find out where the backup pieces are. Did a junior DBA move them to different location or different disk due to space issues.
If you can find the backup pieces, put them back into the original location and run crosscheck backup command again via RMAN.
If you are not able to find backup pieces, then you must clear the expired backup entries from RMAN (controlfile). Use below command to delete expired backups

RMAN> delete expired backup;

Obsolete backups

The general meaning of OBSOLETE is no longer used or required.
RMAN considers backups as OBSOLETE when they are no longer required for database recovery. This is done by one of the RMAN CONFIGURATION parameters.
For example, we set RMAN retention policy to redundancy 4. This means that if we have 5 database backups, the first one will be marked as OBSOLETE because we want to keep 4 copies of RMAN backups.
We use below command to list all the obsolete backups inside RMAN

RMAN> report obsolete;

DBA Action

IF the FRA location is full, then do not worry, RMAN is intelligent, it will overwrite the obsolete backups.
If you find obsolete backups, you can simply delete the backups (as they are no longer needed for recovery)

RMAN> delete obsolete;
Share
read more no comments

Oracle EBS Close Payable Period By Query

July 14th, 2026, posted in Oracle EBS Application, Oracle Queries
Share
oracle,oracle ebs suit,

First find the GL Ledger ID : 

select * from Gl_Ledgers_v

Now select and find the period to confirm : 

SELECT * FROM GL_PERIOD_STATUSES GLP
WHERE GLP.APPLICATION_ID = '200'/* PAYABLES */
AND GLP.SET_OF_BOOKS_ID = '2149'
AND GLP.CLOSING_STATUS = 'O'
AND GLP.PERIOD_NAME = 'SEP-22'

Once done update the period : 

UPDATE GL_PERIOD_STATUSES GLP
SET GLP.CLOSING_STATUS = 'C'
WHERE GLP.PERIOD_NAME = 'SEP-22'
AND GLP.APPLICATION_ID = '200'/* PAYABLES */
AND GLP.SET_OF_BOOKS_ID = '2149';
Share
read more no comments

ORA-32001: Write To SPFILE Requested But No SPFILE Is In Use

June 3rd, 2026, posted in Oracle Queries
Share

PROBLEM :

While altering parameter in parameter file got below error :

ALTER SYSTEM SET processes = 800 SCOPE=SPFILE;
ALTER SYSTEM SET processes = 800 SCOPE=SPFILE
*
ERROR at line 1:
ORA-32001: write to SPFILE requested but no SPFILE is in use

SOLUTION :

This error comes, if the database is running with pfile instead of spfile.

1. Check whether DB is running with pfile or spfile:

SQL> show parameter pfile
NAME TYPE VALUE
------ -------- ------------------------------
spfile string

Here value is showing BLANK, Means database is running with pfile. So with pfile , if we are trying to alter any init parameter in database, it will throw error.
To fix it, create an spfile from the pfile and restart the database.

2. Create spfile from pfile ;

create spfile from pfile;

3. Check whether spfile has been created in $ORACLE_HOME/dbs location :

cd $ORACLE_HOME/dbs
ls -ltr spfile*

4. Restart the database :

shutdown immediate;
startup

When we start the database, if both pfile(init$ORACLE_SID.ora) and spfile(spfile$ORACLE_SID.ora) are present at dbs location, Then bydefault spfile will be used for db startup.

5. Check whether spfile is used or not :

show parameter pfile :

NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
spfile string /oracle/app/oracle/product/12chome/spfiledbaclass.ora

6. Now run alter statement :

ALTER SYSTEM SET processes = 800 SCOPE=SPFILE
System altered.
Share
read more no comments

Oracle EBS Reset Oracle Application User Password By Query

May 30th, 2026, posted in Oracle EBS Application, Oracle Queries, Uncategorized
Share

To reset an Oracle EBS application user password, use the FNDCPASS utility via command line to change it instantly, or use the System Administrator responsibility in the GUI for individual users. For APPS/APPLSYS passwords in R12.2, specialized steps involving adstpall.sh and WLS datasource updates are required

Methods to Reset Oracle EBS Passwords :

FNDCPASS Utility (Command Line – Recommended for Admins):
Use this method to change APPS or specific user passwords from the server terminal :

FNDCPASS apps/<apps_pwd> 0 Y SYSTEM/<system_pwd> USER <username> <new_password>
Example to change user “OPERATOR” password: FNDCPASS apps/apps 0 Y system/manager USER OPERATOR welcome1.

System Administrator Responsibility (GUI)
Log in to EBS as a user with System Administrator privileges (e.g., SYSADMIN).

Navigate to Security > User > Define.
Query the user, enter the new password in the Password field, and save.

PL/SQL Method (Back-end):

Use FND_USER_PKG.ChangePassword to change passwords using SQL*Plus, logged in as the APPS user.

R12.2 APPS/APPLSYS Password Change :

– Shut down services using $INST_TOP/admin/scripts/adstpall.sh.
– Run FNDCPASS to change the APPLSYS password.
– Run AutoConfig.
– Update WLS Data Source in WebLogic Console and restart services.

Share
read more no comments

REP-0004: Warning: Unable to open user preference file

May 3rd, 2026, posted in Oracle EBS Application
Share

Metalink id:
===========
R12: Request Logs Contain the Message “REP-0004: Warning: Unable to open user preference file”
[ID 1120529.1]

Symptoms:
============
All concurrent requests that run REPORTS are printing the following warning in the request log.

REP-0004: Warning: Unable to open user preference file.

Cause:
==========

This message occurs when the concurrent process attempts to open the Oracle Reports executable and your local preference file cannot be found or opened. This is just a warning, so the request will continue to run even if this occurs.

Solution:
===========

To resolve the warning, copy the prefs.ora file from your Reports Builder $ORACLE_HOME/tools/admin/ directory into the Applications $HOME directory.

Example :

Copy of the file prefs.ora in the directory /u01/prod/apps/tech_st/10.1.2/tools/admin to the directory  /home/appprod/.

appdev@ctssd $ pwd
/u01/erpapp/10.1.2/tools/admin
appdev@ctssd $ cp prefs.ora /export/home/apptest

Note: Bounce apache service.
After doing above steps issue resolved.

Share
read more no comments
« Older Entries