I have Oracle 18.104.22.168 run in AIX 5.3, so I mount the file system with cio option.
According to this, I set database parameter as recommended :
1. filesystemio_options -> to be 'SETALL'
2. optimizer_mode -> to be deleted
After that, our backup duration takes 2 longer.
I run database check and optimizer statistic check, there is no error/warning result.
Is there any relation between cio mounting/this database parameter changes and database backup?
Is anyone ever encounter this and find the solution to shorten backup duration like before?
Thank you in advance,
I suggest you go through this note
Check the section
AIX 5.3 or ( AIX 6.1 with Oracle < 22.214.171.124):
Use dd as the copy utility as suggested.
Thank for your suggestion.
I have only limited knowledge about backup.
Currently we do backup to tape with below parameter value:
tape_copy_cmd = cpio
disk_copy_cmd = copy
Is there any significant difference between dd and cpio?
I read that dd command reports an I/O error on UNIX platforms when it reached the physical end of the tape. Is it mean that the backup will be stopped and can't move automatically to the next tape supply?
Thanks and Regards,
I suggest you set the parameters in the init<SID>.sap as mentioned in the SAP note 948294 as below
tape_copy_cmd = dd
disk_copy_cmd = dd
dd_flags = "bs=1024k"
dd_in_flags = "bs=1024k"
compress_cmd = "dd bs=1024k if=$ | ( compress -c > $ ) 2>&1"
uncompress_cmd = "uncompress -c $ | dd bs=1024k of=$ 2>&1"
uncompress_cmd = "uncompress -c $ > $"
For "compress-only" (option "-k only"):
compress_cmd = "dd bs=1024k if=$ | compress -c > $
The dd command is faster as it does not write any file header data. Also you set the value tape_size to less than the actual value and avoid the error of reaching physical end of the tape.
Refer this link for more details and information