Archiving to SAP Content Server/MaxDB: TCP/IP errors when deleting in paral
We are struggling to get the optimal setup for archiving to SAP Content Server using MaxDB. After running one or more archiving jobs for a few hours we suddenly loose connection to the Content Server, and we need to restart the content server before continueing. We long thought it was the logspace which was running full, but this was eliminated. Now it seems as the error occurs when 4 or more deletions jobs is running in parallel. (Write->Store->Delete).
The run-times on a typical archiving job for about 3 GB data would be W: 3000sec S:40sec D: 12000sec. In general the delete job takes about 3 times the write-job.
Everything seems fine until one suddenly get the TCP/IP error after some heavy archiving jobs.
Have anyone experienced anything like this, and are there any good ideas on how to avoid this?
Thank you very much for your inputs on this.