Introduction:
Oracle E-Business Suite (EBS) Rapid Clone is a critical tool for creating copies of an EBS environment. However, issues may arise during the cloning process due to system configuration or resource constraints. This blog explores a specific issue encountered while running the dbTechStack command in an Oracle EBS 12.2 environment, where the process failed due to insufficient space in the /tmp directory. We will discuss the problem, its root cause, and how it was resolved.
Issue:
While running the dbTechStack command to set up the database technology stack for a cloned Oracle EBS environment, the following error was encountered:
ERROR
———————–
[APPLY PHASE]AutoConfig could not successfully execute the following scripts:
Directory: /u01/pretest/tech_st/19.3.0/perl/bin/perl -I /u01/pretest/tech_st/19.3.0/perl/lib/5.36.0 -I /u01/pretest/tech_st/19.3.0/perl/lib/site_perl/5.36.0 -I /u01/pretest/tech_st/19.3.0/appsutil/perl /u01/pretest/tech_st/19.3.0/appsutil/clone
ouicli.pl INSTE8_APPLY 1
AutoConfig is exiting with status 1
WARNING: RC-50013: Fatal: Instantiate driver did not complete successfully.
/u01/pretest/tech_st/19.3.0/appsutil/driver/regclone.drv
Root Cause:
Upon further investigation, the issue was traced back to the /tmp directory being full or having less than 1 GB of free space.
The /tmp directory is used by Oracle EBS utilities as a temporary workspace during the cloning process. If there is insufficient space, operations like running AutoConfig or applying the database technology stack (dbTechStack) will fail.
Key observations:
Temporary Space Constraint: The /tmp directory had less than the required 1 GB of free space.
Inactive Cleanup: The directory was cluttered with old temporary files, which caused the space constraint.
Error message indicating the issue:
Value: /tmp tooSmall
TMPDIR lessThan1
Solution:
The issue was resolved by clearing unnecessary files from the /tmp directory to free up space. The dbTechStack command was then rerun successfully. Below are the detailed steps taken:
Clear Temporary Files:
Identify large or unused files in the /tmp directory.
Remove unnecessary files using rm or cleanup scripts:
rm -rf /tmp/*
Verify Available Space:
Ensure that at least 1 GB of free space is available:
df -h /tmp
Rerun the dbTechStack Command:
perl adcfgclone.pl dbTechStack /u01/pretest/19.3.0/appsutil/UATA_pretestuatdb.xml
Monitor the log file for any additional errors or warnings.
Sample output upon successful execution:
Completed Apply…
Running ETCC to check the status of DB technology patches…
…
Completed Successfully!
Recommendations
To prevent similar issues in the future:
Monitor Temporary Space: Regularly monitor the /tmp directory and ensure sufficient free space before running Oracle EBS utilities.
Conclusion:
Issues like insufficient temporary space can disrupt critical operations in Oracle EBS. Identifying and resolving such problems promptly ensures smooth execution of processes like cloning and dbTechStack. By implementing regular monitoring and cleanup measures, you can prevent similar errors and maintain system stability.
