Compress fails with errno 22: Invalid argument

[Former Member]

Hi all,

we have a problem with our compress run on ECC 6.0. Database Version is 10.2.0.2.0, brtools Patchlevel is 40. Everytime we try to compress the database it fails with the following error message:

BR0278E Command output of 'C:\usr\sap\AKE\SYS\exe\uc\NTI386\brtools.exe -f compronly file G:\ORACLE\AKE\SAPDATA4\SR3_3\SR3.DATA3 13254008832 0':

BR0252E Function fread() failed for 'G:\ORACLE\AKE\SAPDATA4\SR3_3\SR3.DATA3' at location only_compress-4

BR0253E errno 22: Invalid argument

Any help is greatly aprreciated!

Regards,

Michael

[Former Member]

Hi Michael,

How do you make your backups (which options for brbackup? Using RMAN or 3rd party software via backint?). The "compress only" run is useful only if you use the O/S level storage utilities (cpio or dd) for the backup, so it might not even be necessary.

Running the compress-only with BR tracing enabled might also shed some light on the error (SET BR_TRACE=15, see note 29321).

Also, just in case, please do check the "Maximize Throughput for Network Applications" setting as per note 171085.

Regards,

Mark

[Former Member]

Hi Mark,

I have checked the settings as described in note 171085, the settings are correct. Can the size of the file be a problem? The size is about 13 GB (don't ask me why, I just have to get compress running...)

We are backing up our database rather traditional with a local attached tape drive using the standard SAP tools. tape_copy_cmd is dd, backup device is tape, compression on backup devive is also turned on. I'll set the tracing option this afternoon and the we'll see what happens.

regards,

Michael

[Former Member]

Michael,

First thing to look at is a possible issue with the Windows file cache. Please have a look at note 171085 and check whether any of the recommendations apply.

Regards,

Mark

[Former Member]

Hi Mark,

thank you for the answer, the problem is though, that the online and offline backups including the archive backup are working correctly. My conclusion at the moment is that it can't be a permission problem on the file system or a cache problem, since the backups are working. Maybe we should try a offline compress of the database?

Regards,

Michael

[Former Member]

Additional Info:

In our Dev Environment we have exactly the same Patchlevels etc, but the problem does not show up in DEV!