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

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

May 2nd, 2026, posted in Oracle EBS Application
Share
Error :


Enter Password:
REP-0004: Warning: Unable to open user preference file.
REP-0069: Internal error
REP-57054: In-process job terminated:Finished successfully but output is voided
Cause :

Your local (customized) Oracle Reports preference file could not be opened.
This is just a warning, so the product will continue to run even if this occurs.
The possible causes of this error include the following:

Case 1: The file was not found under the specified name in the specified location.
Case 2: You lacked the necessary privileges to open the file.
Case 3: A system error made it impossible to open the file.

Action :

You can take the following actions to rectify this error:

Case 1: Make sure the file prefs.ora is located in your “home” directory.
Case 2: Make sure that you have the privileges necessary to access the file. If you don’t, change your privileges accordingly.
Case 3: Consult your operating system documentation or contact your system administrator.

The preferences file referred to above is:

Windows
ORACLE_HOME\CAUPREFS.ORA (user preferences)
ORACLE_HOME\CAGPREFS.ORA (global preferences)
UNIX
your_home_directory/prefs.ora (user preferences)
$ORACLE_HOME/tools/admin/prefs.ora (global preferences)

Simple Way :

Check whether u have prefs.ora file in your application user’s home
eg: prefs file should be in /home/applmg/prefs.ora
if not please copy prefs.ora file from  $ORACLE_HOME/tools/admin/prefs.ora  to /home/applmg/prefs.ora location.
Run your concurrent request/program.

Share
read more no comments

RMAN SCRIPT TO MAKE BACKUP WITH DATES

April 12th, 2026, posted in Oracle
Share

*******************************************************************************************
************* Set Date, Log, Folders with Variable Names *****************************
*******************************************************************************************

#!/bin/bash
DD=(date +%d%m%Y)
BACKUP_BASE_DIR=”/backup_immam/RMAN_DB_BACKUP”
BACKUP_DIR=”$BACKUP_BASE_DIR/DB_$DD”
mkdir -p $BACKUP_DIR
date > $BACKUP_DIR/RmanStarttime.txt
LOG_FILE=”$BACKUP_DIR/RMAN_DB_BACKUP_$(date +%d%m%Y).log”

*******************************************************************************************
**************************** Starting Log File ******************************************
*******************************************************************************************

echo ==== started on date ==== >> $LOG_FILE”

*******************************************************************************************
**************************** Starting RMAN BACKUP ***********************************
*******************************************************************************************

rman target / msglog $LOG_FILE << EOF
RUN {
ALLOCATE CHANNEL ch1 DEVICE TYPE disk FORMAT ‘$BACKUP_DIR/backup_%u_%s_%p_%T’;
BACKUP AS COMPRESSED BACKUPSET DATABASE PLUS ARCHIVELOG;
RELEASE CHANNEL ch1;
BACKUP AS COPY CURRENT CONTROLFILE FORMAT ‘$BACKUP_DIR/controlfile_%u_%s_%p_%T’;
}
exit;
EOF

*******************************************************************************************
**************************** Ending RMAN BACKUP ***********************************
*******************************************************************************************

echo ==== Online Backup Ends on date ==== >> $LOG_FILE
date > $BACKUP_DIR/RmanStoptime.txt

*******************************************************************************************
**************************** Ending Log File ********************************************
*******************************************************************************************

exit

Share
read more no comments
« Older Entries