Workaround 1: Use a .pf file for Backup parametersRun PROBKUP with a .pf file providing all backup PARAMETERS through a .pf file as follows:
$ probkup online <dbname> backup.01 enableai enableaiarchiver -pf backup.pf < backupfiles.dat > backup.log
Where there is a
Carriage Return after the last line in the .pf,
indicated by <CR> do not include it
# backup.pf
-aiarcdir <directory>
-aiarcinterval <interval>
-bibackup all
-vs <blocks>
-com
-Bp 32
< CR >
Workaround 2: Call the executable directly
PROBKUP uses _mprshut for online and _dbutil for offline backups.
Example: ONLINE PROBKUP:
$ _mprshut <dbname> -C backup online bkupvol\backup.01 enableai enableaiarchiver -aiarcdir <directory> -aiarcinterval <interval> -vs <blocks> -com < backupfiles.dat > backup.log
Example: OFFLINE PROBKUP:
$ _dbutil probkup <dbname> incremental bkupvol\backup.01 -aiarcdir <directory> -aiarcdircreate -vs 1000 -verbose -com -norecover -estimate < backupfiles.dat
Workaround 3: Change the PROBKUP.bat script to accept more parametersModify the PROBKUP script based off the PROUTIL script to accept the required number of parameters. The disadvantage of this workaround is that the modified batch file will need to be included in the deployment routines every time a new version and possibly a Service Pack is installed (although batch files are rarely changed in Service Packs). Refer to the example provided in Article: