Introduction:

Effectively managing large log and output files is crucial for maintaining optimal performance in Oracle E-Business Suite 12.2. Despite the availability of purge programs to address both database and file system levels, challenges arise due to the high volume of concurrent programs generated daily. This article explores the hurdles faced and introduces Oracle’s innovative solution – the APPLLDM environmental variable.

Audience: Oracle Application DBA’s, Oracle Architect

Challenges:

1. Custom Program Performance Impact:
– Custom programs utilizing ‘ls’ or ‘find’ commands may cause high CPU usage when searching for files within the log and output directories.

2. NFS-Mounted Storage Performance Impact:
– Storage devices mounted via NFS can experience performance issues when manipulating log and output folders.

To overcome these challenges, Oracle has introduced the APPLLDM environmental variable, allowing users to specify the storage location for log and output files. The variable offers different schemes, each addressing specific needs:

1. SCHEME = product:
– Requests log and output files to be stored in $APPLCSF/log and output.
– Manager logs will be directed to $APPLCSF/system/log directory.
– These directories must exist when starting managers.

2. SCHEME = single:
– Requests log and output files to be stored in $APPLCSF/log and output.
– Manager logs will be directed to $APPLCSF/log directory.
– These directories must exist when starting managers.

3. SCHEME = user:
– Requests log and output files to be stored in $APPLCSF/log and output.
– Manager logs will be directed to $APPLCSF/system/log directory.
– User name directories need not exist when starting managers. The system directory must exist.

4. SCHEME = date:
– Takes a string parameter following the strftime() function format (In C language).
– Valid values must create one level of directory and not include special characters or spaces.
– Requests log and output files to be stored in $APPLCSF/log and output.
– Manager logs will be directed to $APPLCSF/system/log directory.
– Date directories need not exist when starting managers. The system directory must exist.

5. SCHEME = reqidexp:
– Takes an integer parameter for request_id manipulation.
– Requests log and output files to be stored in $APPLCSF/log and output.
– Manager logs will be directed to $APPLCSF/system/log directory.
– Derived directories need not exist when starting managers. The system directory must exist.

6. SCHEME = reqidmod:
– Takes an integer parameter for request_id manipulation.
– Requests log and output files to be stored in $APPLCSF/log and output.
– Manager logs will be directed to $APPLCSF/system/log directory.
– Derived directories need not exist when starting managers. The system directory must exist.

7. SCHEME = mgrproc:
– Requests log and output files to be stored in $APPLCSF/<manager’s process id>/log and output.
– Manager logs will be directed to $APPLCSF/system/log directory.
– Derived directories need not exist when starting managers. The system directory must exist.

Conclusion:

Oracle’s APPLLDM environmental variable provides a flexible and efficient solution for managing log and output files in Oracle E-Business Suite 12.2. By choosing the appropriate scheme, users can optimize performance and overcome the challenges associated with high-volume concurrent programs.

Recent Posts

Start typing and press Enter to search