APP-FND-01630 / APP-FND-01662: Cannot Open FNDCPASS Log File in Oracle E-Business Suite R12 – Complete Troubleshooting Guide

The errors APP-FND-01630 and APP-FND-01662 are commonly encountered while running the FNDCPASS utility in Oracle E-Business Suite. These errors usually occur when FNDCPASS is unable to create, access, or write its log file.

Although administrators often assume there is a problem with the FNDCPASS utility itself, these errors almost always indicate an issue with the Oracle E-Business Suite application environment, filesystem permissions, missing directories, incorrect environment variables, insufficient disk space, or an invalid log file location.

Since FNDCPASS is used to change critical Oracle E-Business Suite passwords—including the APPS schema password, application user passwords, and Oracle Applications product schema passwords—it is essential that the utility runs successfully. Failure to generate its log file normally causes the password change operation to terminate immediately.

This guide explains how FNDCPASS creates log files, why APP-FND-01630 and APP-FND-01662 occur, how to diagnose the real cause, and the production-tested troubleshooting procedures used by experienced Oracle E-Business Suite Application DBAs.

Quick Solution

Verify that the APPLCSF, APPLLOG, and APPLTMP environment variables point to valid directories. Confirm that the directories exist, have sufficient free disk space, and are owned by the Oracle Applications operating system user with appropriate read, write, and execute permissions. If necessary, rerun AutoConfig to regenerate environment settings before executing FNDCPASS again.

Typical Error Messages

Depending on the Oracle E-Business Suite version, you may encounter one or more of the following errors:

APP-FND-01630: Cannot open log file

APP-FND-01662: Cannot open log file

FNDCPASS completed with errors

Unable to create log file

Unable to write to log file

Permission denied

No such file or directory

What is FNDCPASS?

FNDCPASS is an Oracle E-Business Suite command-line utility used to change passwords for Oracle Applications users and database schemas.

Common uses include:

Changing the APPS schema password.
Changing Oracle Applications product schema passwords.
Changing application user passwords.
Synchronizing database and application passwords.
Maintaining Oracle E-Business Suite security.

Because FNDCPASS performs security-sensitive operations, it records detailed execution information in a log file.

How FNDCPASS Creates Log Files

Before performing any password update, FNDCPASS attempts to create a log file in the location defined by the Oracle E-Business Suite environment.

The log location is controlled primarily through the following environment variables:

APPLCSF – Common log and output directory.
APPLLOG – Application log directory.
APPLTMP – Temporary working directory.

If any of these directories are missing, inaccessible, full, or incorrectly configured, FNDCPASS cannot create its log file and immediately terminates with APP-FND-01630 or APP-FND-01662.

Why Do APP-FND-01630 and APP-FND-01662 Occur?

These errors indicate that Oracle E-Business Suite cannot successfully create or access the required log file.

Common root causes include:

Incorrect APPLCSF configuration.
Incorrect APPLLOG directory.
Invalid APPLTMP location.
Missing log directory.
Filesystem is full.
Filesystem mounted read-only.
Incorrect file ownership.
Insufficient directory permissions.
NFS mount unavailable.
Incorrect Oracle Applications environment.
AutoConfig not executed after configuration changes.
Corrupted environment file.

Business Impact

Failure to execute FNDCPASS successfully can interrupt important Oracle E-Business Suite administration activities.

Common impacts include:

APPS password cannot be changed.
Application schema passwords remain unchanged.
Security maintenance delayed.
Cloning activities interrupted.
Post-clone configuration failures.
AutoConfig dependencies affected.
Oracle EBS maintenance windows extended.
Production support delays.

Common Root Causes

APPLCSF points to a nonexistent directory.
APPLLOG directory deleted accidentally.
APPLTMP has insufficient permissions.
Filesystem usage reached 100%.
Oracle Applications file owner changed.
Log directory mounted read-only.
Incorrect symbolic links.
NFS storage unavailable.
Environment file not sourced.
AutoConfig configuration out of date.
Manual filesystem changes after cloning.

Where Should You Start?

Rather than rerunning FNDCPASS repeatedly, Oracle Apps DBAs should first verify that the application environment is configured correctly.

A structured investigation should answer questions such as:

Are APPLCSF, APPLLOG, and APPLTMP defined correctly?
Do the required directories exist?
Is sufficient disk space available?
Are directory permissions correct?
Is the filesystem mounted read-write?
Was AutoConfig executed recently?
Is the Oracle Applications environment sourced correctly?
Has a recent clone or migration modified the filesystem layout?

Answering these questions typically identifies the underlying cause much faster than repeatedly attempting to rerun the utility.

Production Oracle Apps DBA Recommendation

Treat APP-FND-01630 and APP-FND-01662 as environmental configuration errors rather than FNDCPASS failures. Before changing passwords, always verify Oracle E-Business Suite environment variables, confirm directory ownership and permissions, ensure adequate filesystem space, and execute AutoConfig if configuration changes have been made.

Step-by-Step Oracle E-Business Suite Troubleshooting

When APP-FND-01630 or APP-FND-01662 occurs, the objective is to determine why FNDCPASS cannot create or access its log file. In most production environments, the root cause is an incorrect Oracle E-Business Suite environment, missing log directories, insufficient filesystem permissions, or storage-related issues.

Step 1 – Source the Oracle E-Business Suite Environment

Before running FNDCPASS, verify that the correct Oracle E-Business Suite environment has been sourced.

. /u01/install/APPS/EBSapps.env run

For Oracle EBS R12.1, source the appropriate APPS environment file.

Step 2 – Verify Environment Variables

Check the environment variables used by FNDCPASS for log and temporary file creation.

echo $APPLCSF

echo $APPLLOG

echo $APPLTMP

Verify that:

Each variable is defined.
The directory exists.
The path is correct.
The filesystem is mounted.

Step 3 – Verify Directory Existence

Confirm that all required directories exist.

ls -ld $APPLCSF

ls -ld $APPLLOG

ls -ld $APPLTMP

If any directory is missing, recreate it or rerun AutoConfig to regenerate the directory structure.

Step 4 – Check Filesystem Space

A full filesystem prevents Oracle E-Business Suite from creating log files.

df -h

Also verify inode usage:

df -i

Ensure sufficient free space is available.

Step 5 – Verify Permissions

The Oracle Applications operating system user must have permission to create files.

Check permissions:

ls -ld $APPLCSF

ls -ld $APPLLOG

ls -ld $APPLTMP

Verify:

Directory owner.
Group ownership.
Read permission.
Write permission.
Execute permission.

Step 6 – Test Log File Creation

Confirm that the operating system user can manually create a file.

touch $APPLLOG/test.log

If the command fails, resolve the underlying filesystem or permission issue before running FNDCPASS.

Step 7 – Verify Filesystem Mount Status

Ensure that the filesystem containing APPLLOG is mounted in read-write mode.

mount | grep APPL

mount

If the filesystem is mounted read-only, identify and correct the underlying operating system issue.

Step 8 – Review AutoConfig

Incorrect configuration files may result in invalid environment variables.

Run AutoConfig if recent configuration changes have been made.

adautocfg.sh

Review the AutoConfig log for any errors.

Step 9 – Review Recent Clone or Migration Activities

These errors frequently occur after:

Oracle EBS cloning.
Filesystem migration.
Storage migration.
Disaster recovery testing.
Application tier rebuild.
Server migration.

Verify that all directory paths remain valid after these activities.

Step 10 – Execute FNDCPASS Again

After correcting the environment, rerun the utility.

Example:

FNDCPASS apps/apps 0 Y system/manager SYSTEM APPLSYS welcome

Verify that the log file is successfully created.

Real Production Case Study

An Oracle E-Business Suite R12.2 environment generated the following error immediately after a successful clone:

APP-FND-01630:
Cannot open log file

Initial investigation focused on FNDCPASS itself. However, reviewing the environment revealed that APPLLOG referenced a directory that no longer existed because the cloned filesystem had been mounted under a different location.

After updating the filesystem paths and rerunning AutoConfig, the environment variables were regenerated correctly. FNDCPASS created its log file successfully, and the APPS password change completed without errors.

Oracle Apps DBA Investigation Checklist

Verification	Status
Correct EBS Environment Sourced	☐
APPLCSF Verified	☐
APPLLOG Verified	☐
APPLTMP Verified	☐
Directories Exist	☐
Filesystem Space Checked	☐
Filesystem Mounted Read-Write	☐
Permissions Verified	☐
Manual Log File Creation Tested	☐
AutoConfig Reviewed	☐
FNDCPASS Executed Successfully	☐
Issue Resolved	☐

Oracle E-Business Suite Version Considerations

Although APP-FND-01630 and APP-FND-01662 can occur in multiple Oracle E-Business Suite releases, the environment configuration differs slightly between versions.

Oracle EBS Version	Considerations
11i	Traditional APPL_TOP architecture with shared application filesystem.
R12.0 / R12.1	Environment sourced from the APPS environment file; verify APPLCSF, APPLLOG, and APPLTMP.
R12.2	Dual File System architecture (Run and Patch). Always source the correct `EBSapps.env` environment before running FNDCPASS.

Best Practices for Oracle Apps DBAs

Always source the correct Oracle EBS environment before executing administrative utilities.
Verify APPLCSF, APPLLOG, and APPLTMP after every clone or migration.
Keep sufficient free disk space in the filesystem containing application logs.
Run AutoConfig after configuration changes.
Use consistent ownership and permissions across the application filesystem.
Monitor filesystem utilization as part of routine health checks.
Validate NFS mounts before maintenance activities.
Back up context files before making configuration changes.
Test FNDCPASS in a non-production environment before production password changes whenever possible.
Document password change procedures and environment validation steps.

Common Administrator Mistakes

Running FNDCPASS without sourcing the Oracle EBS environment.
Ignoring APPLCSF configuration.
Deleting APPLLOG directories during cleanup.
Changing directory ownership manually.
Running FNDCPASS as the wrong operating system user.
Ignoring filesystem capacity warnings.
Skipping AutoConfig after cloning.
Using outdated environment files.
Ignoring read-only filesystem errors.
Repeatedly rerunning FNDCPASS without investigating the root cause.

Useful Linux Commands

Verify Environment Variables

echo $APPLCSF
echo $APPLLOG
echo $APPLTMP

Check Directory Permissions

ls -ld $APPLCSF
ls -ld $APPLLOG
ls -ld $APPLTMP

Check Disk Space

df -h

Check Inode Usage

df -i

Test File Creation

touch $APPLLOG/test.log

Verify Filesystem Mounts

mount

Review AutoConfig Log

tail -100 $INST_TOP/admin/log/*.log

Troubleshooting Flowchart

APP-FND-01630 /
APP-FND-01662

          │

          ▼

Source EBS Environment

          │

          ▼

Verify APPLCSF

          │

          ▼

Verify APPLLOG

          │

          ▼

Verify APPLTMP

          │

          ▼

Directories Exist?

          │

   ┌──────┴──────┐

   │             │

 No            Yes

   │             │

Create       Check
Directory    Permissions

          │

          ▼

Filesystem Full?

          │

   ┌──────┴──────┐

   │             │

 Yes            No

   │             │

Free Space   Check AutoConfig

          │

          ▼

Run FNDCPASS Again

          │

          ▼

Problem Resolved

Frequently Asked Questions (FAQ)

What causes APP-FND-01630?

The error usually occurs because FNDCPASS cannot create or access its log file due to invalid environment variables, missing directories, incorrect permissions, or insufficient filesystem space.

What is the difference between APP-FND-01630 and APP-FND-01662?

Both errors relate to log file access problems. The exact wording varies depending on the Oracle E-Business Suite release and the point at which the logging failure occurs, but the underlying troubleshooting approach is generally the same.

Can AutoConfig resolve these errors?

Yes. If the issue is caused by incorrect environment configuration or invalid directory paths, rerunning AutoConfig often regenerates the correct settings and resolves the problem.

Should I recreate APPLLOG manually?

If the directory has been accidentally removed, it can be recreated with the correct ownership and permissions. However, if the directory structure is managed by AutoConfig, it is generally preferable to rerun AutoConfig so that Oracle regenerates the required configuration consistently.

Does this issue affect Oracle Database?

No. APP-FND-01630 and APP-FND-01662 are Oracle E-Business Suite application-tier errors associated with FNDCPASS logging rather than Oracle Database engine failures.

About the Author

Rana Abdul Wahid is an Oracle Database and Oracle E-Business Suite Consultant with more than 15 years of experience in Oracle Database Administration, Oracle E-Business Suite Application DBA, Oracle Cloud Infrastructure (OCI), Oracle RAC, Oracle Data Guard, RMAN Backup & Recovery, Linux/Unix Administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise database management.

He specializes in Oracle E-Business Suite administration, AutoConfig, Rapid Clone, application tier troubleshooting, Oracle Database performance tuning, backup and recovery, and production support, publishing practical solutions based on real-world enterprise deployments.

Learn more about the author →

Conclusion

APP-FND-01630 and APP-FND-01662 are typically environmental configuration issues rather than problems with the FNDCPASS utility itself. In most production environments, the errors are caused by invalid log directory settings, missing directories, incorrect permissions, insufficient disk space, or improperly configured Oracle E-Business Suite environment variables.

By systematically verifying APPLCSF, APPLLOG, APPLTMP, filesystem availability, directory permissions, AutoConfig configuration, and the Oracle EBS environment, administrators can identify the true root cause and restore normal FNDCPASS operation with minimal downtime.

Final Oracle Apps DBA Recommendation

Before every FNDCPASS execution, verify the application environment, ensure the logging directories exist and are writable, confirm adequate filesystem capacity, and validate the configuration after cloning or migration. A structured pre-check significantly reduces the likelihood of password management failures and helps maintain a stable Oracle E-Business Suite environment.

Found this guide helpful? Explore the Oracle Error Codes Guide for more production-tested Oracle Database and Oracle E-Business Suite troubleshooting articles covering AutoConfig, Rapid Clone, Oracle RAC, Data Guard, RMAN, Linux administration, and enterprise Apps DBA best practices.

Oracle Database Error Solutions & DBA Knowledge Base