Reasons Things Went Wrong

Bad Request

If you get errors while downloading saying "Bad Request" this may mean that your client tries to use Byte serving. LOBCDER supports Byte serving if its storage backends do. This means that when a range of bytes is requested (say from 100 to 500) LOBCDER will try to find a storage backend that supports random access files to start reading the requested file from the 100th byte. If the backend doesn't support random access files LOBCDER will return a "Bad Request" .

Physical Data Missing

This is for lobcder admins. If users can't download files you can check if they are physically there with the use of cadaver. By running:

propget file

Look for the custom: data-distribution property. If it looks like this:

custom: data-distribution = []

then somehow the physical data are gone.

If you want to find all files with no physical data you can run this query on the database:

SELECT uid, parentRef, ownerId, ldName, createDate, modifiedDate, accessDate FROM ldata_table LEFT JOIN pdri_table on ldata_table.pdriGroupRef = pdri_table.pdriGroupRef where fileName is NULL and datatype = 'logical.file' order by uid INTO OUTFILE '/tmp/filesWithNoPysicalData.csv' FIELDS TERMINATED BY ',' ENCLOSED BY '"' LINES TERMINATED BY '\n';