Summary
When using DPX in conjunction with SAP's BRBACKUP, BRARCHIVE, BRRESTORE utilities, the job may fail after encountering problems accessing a job definition (.jid) file in the DPX logs directory on the SAP Server.
Symptoms
A message similar to the following will be found in the *.bil log created in the same logs directory during the failed job:
Wed Feb 07 11:16:58 2007 SNBSAP1021E Error opening file C:\BACKEX\logs\AP20410.jid, rc=-1
Wed Feb 07 11:16:58 2007 SNBSAP0032S The process cannot access the file because it is being used by another process.
Wed Feb 07 11:16:58 2007 SNBSAP1031E Error calling fn (sap_get_jobid_and_jobrc) rc (-1)
Wed Feb 07 11:16:58 2007 SNBSAP1031E Error calling fn (sap_backup) rc (-1)
Resolution
This is caused when an attempt is made to access this newly-created job information file before it is available.
To resolve this issue, edit the SAP utility (.utl) configuration file to contain the following line:
BEX_CONN_RETRY 8
This forces up to 8 retries in the attempt to open this job definition file, allowing the job to proceed normally once the file is available.
By default the .utl configuration file is found in the %ORACLE_HOME%/database directory and takes the name initsid.utl, though both name and location can be configured by the SAP administrator.