Log cannot be written (existence? authorization?)
Message no. TG153
Diagnosis
A log file could not be written to.
System Response
The upgrade stops in phase BATCHCHK.
Procedure
Check the following causes and correct the error:
- No write authorization to the subdirectories of the upgrade directory (subdirectories bin, log, tmp, …)
- No freespace in the upgrade directory
- The upgrade directory cannot be reached from the batch host specified
- Create a mount to the directory. If the batch host was entered incorrectly, correct it by calling R3up set stdpar.
Resolution is also shared as in SAP Note 2495818 – RDD* jobs cancelled with error Log cannot be “written (existence? authorization?)” in upgrade phase BATCHCHK_GEN.
- SUM folder has authorization issue.
- Please ensure SAP administration users at OS level can access the SUM folder properly.
- The RDD jobs were started in application servers which didn’t have access to SUM folder.
- In an earlier phase PREP_CONFIGURATION/INITSUBST, you decided in which application server background jobs would be started.
- If you chose “Automated batch job distribution” or a specific application server in which SUM folder is not available. Then the SUM folder must be mounted on the relevant background job host.
- If the instance with SUM running was selected in the phase INITSUBST, but the background job still started in other instances. Please go to the transaction SM61 and press the button “Job Server Group”. If a job server group is there, please add the instance selected in the phase INITSUBST to the group. If no job server group is there, please create a job server group named SAP_DEFAULT_BTC, and add the relevant instance to the group.
