During migration to shared APPL_TOP, we changed the APPLTMP and APPLPTMP and mount point to a dedicated mount for temporary files. The DBAs not wanting to run autoconfig, just changed the environment variable and bounced the services. While viewing the log or output file of any concurrent request this error occurred:
“The Applications File Server could not create a temporary file.”
Metalink Note 433104.1 describes this issue:
Incorrect setup of the apps.conf configuration file
As per the customer's last update, "we found there were some source instance entries in the $IAS_ORACLE_HOME/Apache/Apache/conf/apps.conf with some customization for temp files."
As per Note 276695.1, "FNDWRR does use APPLTMP as its temp directory, but remember FNDWRR is a CGI program so you must set APPLTMP in your WEBSERVER environment."
To implement the solution, please execute the following steps:
1. Ensure the “apps.conf” file is configured correctly, particularly temporary directory paths like "SetEnv APPLTMP"
2. Relink Applications programs and Generate product JAR files via adadmin.
There was no need to relink programs or generate JAR files. We just changed the SetEnv APPLTMP line to point to the correct directory. This resolved the issue.
Blog dedicated to Oracle Applications (E-Business Suite) Technology; covers Apps Architecture, Administration and third party bolt-ons to Apps