Oracle Database Error Solutions & DBA Knowledge Base

Practical, step-by-step Oracle Database troubleshooting and administration resources for DBAs, developers, Oracle E-Business Suite administrators, and IT professionals.

Explore practical guidance covering Oracle Database errors, RMAN backup and recovery, Data Guard, ASM, RAC, performance tuning, installation, patching, cloning, Oracle Linux administration, and Oracle E-Business Suite.

Our troubleshooting guides explain common causes, diagnostic steps, SQL queries, configuration checks, and recommended solutions to help database professionals understand problems and resolve them systematically.

Start with the Oracle Error Codes Guide or explore the main DBA topic areas to find detailed technical articles and practical administration resources.

ADCFGClone.pl DBTier Failed with RC-00110: ApplyDBTechStack Relinking Error

-

ADCFGClone.pl DBTier Failed with RC-00110: ApplyDBTechStack Relinking Error

The ADCFGClone.pl DBTier Failed with RC-00110 error can occur during Oracle E-Business Suite Rapid Clone configuration when the database technology stack cannot be successfully configured on the target system.

In one real-world troubleshooting scenario, the failure occurred during the ApplyDBTechStack phase of the Oracle E-Business Suite database-tier clone. The high-level error was: 

RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

The underlying cause was identified in the detailed log as a file permission problem involving: 

AC-00444: Unable to write to file

FileNotFoundException:
$ORACLE_HOME/oui/bin/runInstaller.sh
(Permission denied)

The problem was resolved by correcting the permission on the affected file and then rerunning the database-tier configuration using the target context file.

What You Will Learn

  • What RC-00110 means during Oracle EBS Rapid Clone
  • What the ApplyDBTechStack phase does
  • Why RC-00110 should not be treated as a single specific error
  • How to locate the detailed Rapid Clone log
  • How to identify the underlying permission problem
  • How to check file and directory permissions
  • How to verify ownership and filesystem access
  • How to correct the specific permission problem safely
  • How to rerun adcfgclone.pl dbTier
  • How to troubleshoot other possible causes of RC-00110

Quick Solution for the Permission-Denied Scenario

If the detailed ApplyDBTechStack log specifically reports a permission error for: 

$ORACLE_HOME/oui/bin/runInstaller.sh

First check the existing permission: 

ls -l $ORACLE_HOME/oui/bin/runInstaller.sh

If the file does not have the required execute permission, correct the permission: 

chmod 755 $ORACLE_HOME/oui/bin/runInstaller.sh

Verify the result: 

ls -l $ORACLE_HOME/oui/bin/runInstaller.sh

After correcting the specific file permission problem, rerun the database-tier configuration using the appropriate target context file: 

cd $ORACLE_HOME/appsutil/clone/bin

perl adcfgclone.pl dbTier \
$ORACLE_HOME/appsutil/<SID>_<HOSTNAME>.xml

Important: The exact command and context-file location may vary depending on the Oracle E-Business Suite release, environment configuration, operating system, and Rapid Clone setup.

What Does RC-00110 Mean?

The message: 

RC-00110: Fatal: Error occurred while relinking of ApplyDBTechStack

is a high-level Rapid Clone failure message.

It tells you that an error occurred during the ApplyDBTechStack configuration phase, but RC-00110 alone does not identify the actual root cause.

The underlying problem may be related to:

  • File permissions
  • Incorrect file ownership
  • Directory access permissions
  • Insufficient filesystem space
  • Read-only filesystem
  • Missing files
  • Incorrect Oracle software environment
  • Invalid Oracle Home configuration
  • Relinking failures
  • Operating system restrictions
  • Incorrect environment variables

Therefore, the correct troubleshooting approach is:

RC-00110 is the symptom. The detailed ApplyDBTechStack log contains the actual cause.

What Is ApplyDBTechStack?

During the Oracle E-Business Suite database-tier cloning process, Rapid Clone performs a series of configuration operations on the target environment.

The ApplyDBTechStack phase is associated with configuring and applying the Oracle Database technology stack on the target system.

Depending on the Oracle E-Business Suite release and environment, this phase may involve operations related to:

  • Oracle Home configuration
  • Oracle software files
  • Oracle Universal Installer components
  • Database technology stack files
  • Configuration files
  • Relinking operations
  • Permissions and ownership
  • Operating system dependencies

If one of these operations fails, Rapid Clone may report a high-level error such as RC-00110.

The Actual Error in This Case

The important part of this troubleshooting case was not only the RC-00110 message.

The detailed log showed: 

AC-00444: Unable to write to file

FileNotFoundException:
$ORACLE_HOME/oui/bin/runInstaller.sh

Permission denied

This indicated that the process could not access or modify the required file because of a permissions problem.

The correct approach was therefore to investigate the file and its parent directories instead of treating RC-00110 as a generic relinking command problem.

Step-by-Step Troubleshooting

Step 1: Identify the Failed Clone Operation

First determine exactly which operation failed.

In this case, the error indicated: 

Error occurred while relinking of ApplyDBTechStack

This tells us that the failure occurred during the database technology-stack configuration phase.

Step 2: Locate the Detailed ApplyDBTechStack Log

The detailed log is more important than the high-level RC-00110 message.

A typical Oracle EBS Rapid Clone log location may look similar to: 

$ORACLE_HOME/appsutil/log/<SID>_<HOSTNAME>/

The exact location can vary depending on the Oracle E-Business Suite version and environment.

Search the relevant log directory for the failed operation: 

find $ORACLE_HOME/appsutil/log -type f \
-name "*ApplyDBTechStack*" -print

You can also search the logs for important error messages: 

grep -iE "ERROR|FAILED|PERMISSION|AC-00444|RC-00110" \
ApplyDBTechStack_<timestamp>.log

The exact log filename depends on the Oracle E-Business Suite release and Rapid Clone implementation.

Step 3: Check the Affected File

After identifying the file reported in the error, check its permissions: 

ls -l $ORACLE_HOME/oui/bin/runInstaller.sh

Review:

  • File owner
  • File group
  • Read permission
  • Write permission
  • Execute permission

For example, a permission display may look like: 

-rwxr-xr-x  oracle  oinstall  runInstaller.sh

The correct permission depends on the intended Oracle software installation configuration and the user executing the Rapid Clone operation.

Step 4: Check the Current User

Confirm which operating system user is executing the clone process: 

whoami

Also review the user's groups: 

id

The user running the Rapid Clone operation must have appropriate access to the Oracle Home and related directories.

Step 5: Check Parent Directory Permissions

A file may have correct permissions but still be inaccessible if one of its parent directories does not allow the user to traverse it.

Check the relevant directories: 

ls -ld $ORACLE_HOME
ls -ld $ORACLE_HOME/oui
ls -ld $ORACLE_HOME/oui/bin

The user must have appropriate directory access to reach: 

$ORACLE_HOME/oui/bin/runInstaller.sh

Step 6: Check Ownership

Check the ownership of the affected file: 

stat $ORACLE_HOME/oui/bin/runInstaller.sh

Incorrect ownership can cause access problems even when the permission bits appear reasonable.

Do not change ownership blindly. The correct owner and group depend on the Oracle E-Business Suite installation and operating-system configuration.

Step 7: Check Filesystem Space

A failure reported as an inability to write to a file may also occur when the filesystem is full.

Check filesystem usage: 

df -h $ORACLE_HOME

Also check inode usage when appropriate: 

df -i $ORACLE_HOME

If the filesystem has no available space or inodes, the Rapid Clone process may fail even when file permissions are correct.

Step 8: Check Whether the Filesystem Is Read-Only

A read-only filesystem can prevent Rapid Clone from modifying files.

Review the mount configuration: 

mount | grep "$ORACLE_HOME"

If the filesystem is mounted read-only, the underlying filesystem or operating-system issue must be investigated before rerunning the clone process.

Step 9: Correct the Specific Permission Problem

In the original troubleshooting case, the affected file was: 

$ORACLE_HOME/oui/bin/runInstaller.sh

The permission was corrected using: 

chmod 755 $ORACLE_HOME/oui/bin/runInstaller.sh

After making the change, verify the result: 

ls -l $ORACLE_HOME/oui/bin/runInstaller.sh

The important point is to correct the specific problem identified in the log.

Important Permission Warning

Do not blindly execute chmod -R on the entire Oracle Home.

Recursive permission changes can damage the expected permissions of Oracle software files and create additional problems. Correct only the affected file or directory after understanding the cause.

Step 10: Rerun ADCFGClone.pl DBTier

After correcting the underlying problem, rerun the database-tier configuration using the appropriate target context file.

A typical command structure is: 

cd $ORACLE_HOME/appsutil/clone/bin

perl adcfgclone.pl dbTier \
$ORACLE_HOME/appsutil/<SID>_<HOSTNAME>.xml

The actual context-file path and command may vary depending on the Oracle E-Business Suite version and environment.

Oracle's Rapid Clone documentation describes using the database-tier context file during the target database-tier configuration process. Always follow the procedure appropriate for your Oracle E-Business Suite release. ([docs.oracle.com](https://docs.oracle.com/cd/B15436_02/current/acrobat/11iadproc.pdf?utm_source=chatgpt.com))

Why the Target Context File Is Important

During the cloning process, the target environment uses a context file containing configuration information for the target system.

The context file may contain information related to:

  • Database SID
  • Host information
  • Oracle Home
  • Database configuration
  • Port configuration
  • Target environment settings

When rerunning the database-tier configuration, ensure that the correct target context file is used.

Other Possible Causes of RC-00110

The permission problem described in this article is one possible cause of RC-00110. Other environments may fail for different reasons.

Incorrect File Permissions

The Rapid Clone process may not be able to read, write, or execute required files.

Incorrect File Ownership

Files may belong to an unexpected operating-system user or group.

Insufficient Filesystem Space

The database technology stack configuration may require additional disk space.

Read-Only Filesystem

The operating system may prevent modifications to the Oracle Home.

Missing Files

Required Oracle Home or Oracle Universal Installer files may be missing or incomplete.

Incorrect Environment Variables

Variables such as ORACLE_HOME, ORACLE_SID, and PATH should be reviewed when the log indicates an environment-related problem.

For example: 

echo $ORACLE_HOME
echo $ORACLE_SID
echo $PATH
which perl

Oracle Home Inconsistency

An Oracle Home that is incomplete, incorrectly copied, or inconsistent with the target environment may cause Rapid Clone configuration failures.

Common Troubleshooting Mistakes

1. Treating RC-00110 as the Root Cause

RC-00110 is a high-level failure message. Always inspect the detailed ApplyDBTechStack and Rapid Clone logs.

2. Changing Permissions Without Checking the Log

Do not execute chmod commands randomly. First identify the exact file or directory that caused the failure.

3. Running chmod -R on ORACLE_HOME

This can change permissions on a large number of Oracle files and may create additional problems.

4. Ignoring File Ownership

Permission bits alone do not always explain access problems. Verify the owner and group.

5. Ignoring Filesystem Space

A full filesystem can generate errors that appear to be file-access problems.

6. Using the Wrong Context File

When rerunning the database-tier configuration, verify that the context file belongs to the correct target environment.

How to Prevent Similar Rapid Clone Failures

  • Verify Oracle Home ownership and permissions before starting a clone.
  • Confirm that the required Oracle software files exist.
  • Check available filesystem space.
  • Verify that the filesystem is writable.
  • Use the correct Oracle EBS environment and context file.
  • Review the Rapid Clone documentation for the specific Oracle EBS release.
  • Keep detailed records of source and target environment configuration.
  • Review Rapid Clone logs after every major cloning operation.
  • Avoid unnecessary recursive permission changes.
  • Test the cloning procedure in a suitable non-production environment whenever possible.

Frequently Asked Questions

What does RC-00110 mean in Oracle EBS?

RC-00110 is a high-level Rapid Clone failure message indicating that an error occurred during an operation such as ApplyDBTechStack. The detailed log must be reviewed to identify the actual root cause.

What caused RC-00110 in this particular case?

The underlying error indicated a permission problem involving: 

$ORACLE_HOME/oui/bin/runInstaller.sh

The permission was corrected and the database-tier configuration was rerun.

Is chmod 755 a universal fix for RC-00110?

No. The permission change described in this article applies to the specific permission-denied scenario. Other RC-00110 failures may have completely different causes.

How do I find the real cause of RC-00110?

Review the detailed Rapid Clone and ApplyDBTechStack logs. Search for messages such as ERROR, FAILED, PERMISSION, AC-00444, and other underlying operating-system or Oracle errors.

Can incorrect directory permissions cause this error?

Yes. Even if the target file has appropriate permissions, the operating-system user must also be able to traverse the parent directories.

Can a full filesystem cause a file permission-style error?

Yes. If a filesystem has no available space or inodes, operations that require writing files can fail. Check both disk space and inode availability when appropriate.

Should I run chmod -R 755 on the Oracle Home?

No. Avoid blindly changing permissions recursively across the Oracle Home. Identify the specific problem and correct only the affected file or directory after understanding the expected configuration.

Related Oracle E-Business Suite and DBA Topics

You can add additional Oracle E-Business Suite, Rapid Clone, Oracle Database, Linux, and Oracle EBS administration articles here as your content library grows.

Conclusion

The ADCFGClone.pl DBTier Failed with RC-00110 message should not be treated as a single error with one universal solution.

The correct troubleshooting approach is to identify the detailed failure inside the Rapid Clone and ApplyDBTechStack logs. In the specific case discussed in this article, the underlying problem was a permission-denied error involving: 

$ORACLE_HOME/oui/bin/runInstaller.sh

After verifying the problem, the file permission was corrected and the database-tier configuration was rerun using the appropriate target context file.

The most important lesson is:

Do not troubleshoot RC-00110 by the RC code alone. Always identify and resolve the underlying error reported in the detailed Rapid Clone log.

A systematic approach that checks logs, permissions, ownership, directory access, filesystem space, filesystem mount status, Oracle Home integrity, and the target context file can significantly improve the chances of resolving Rapid Clone failures efficiently.

Important Technical Note

Oracle E-Business Suite cloning and Oracle software configuration operations can affect critical enterprise environments. Always verify commands and procedures against the Oracle E-Business Suite release and operating-system configuration in use. Test procedures in a suitable non-production environment whenever possible and follow your organization's backup, change-management, and production-support procedures.

About the Author

Rana Abdul Wahid is a seasoned Database Consultant with more than 15 years of professional experience in Oracle Database Administration, Oracle E-Business Suite Administration, Oracle Cloud Infrastructure (OCI), RMAN Backup & Recovery, Oracle Data Guard, Oracle RAC, Oracle ASM, database performance tuning, Linux administration, MySQL, Microsoft SQL Server, PostgreSQL, and enterprise IT infrastructure.

Through this website, he shares practical Oracle DBA troubleshooting guides, Oracle E-Business Suite administration techniques, database recovery procedures, automation scripts, and real-world technical knowledge to help database professionals solve complex enterprise technology problems.

Learn more about the author and this technical knowledge base.

Article originally published: June 23, 2012
Article substantially updated: July 2026

Comments

Post a Comment