VERIFY that the database is DAOS enabled and the status is Read/Write. This is done by entering the command 'tell daosmgr dbsummary dbname' 

It is also possible that the attachment does not meet the minimum DAOS size requirement. Remember that the size of the object is compared to the DAOS Minimum after it is compressed. 

The attachment already exists. Attachments are WRITTEN to a temporary NLO file so that the MD5sum can be calculated. If that checksum matches an existing NLO, the temporary file is deleted. In this case the refcount for the object is INCREMENTED.

A problem was encountered when creating an NLO file. In this case the fallback is to immediately create a standard, inline NSF attachment. If anything goes wrong along the way (can't create NLO file due to out of disk space, write error, PERMISSION, etc.), the DAOS operation returns control to the normal NSF attachment handling code. Worst case, it'll get in-lined in the database. 

Verify that the database is DAOS enabled and the status is Read/Write. This is done by entering the command 'tell daosmgr dbsummary dbname' 

It is also possible that the attachment does not meet the minimum DAOS size requirement. Remember that the size of the object is compared to the DAOS Minimum after it is compressed. 

The attachment already exists. Attachments are written to a temporary NLO file so that the MD5sum can be calculated. If that checksum matches an existing NLO, the temporary file is deleted. In this case the refcount for the object is incremented.

A problem was encountered when creating an NLO file. In this case the fallback is to immediately create a standard, inline NSF attachment. If anything goes wrong along the way (can't create NLO file due to out of disk space, write error, permission, etc.), the DAOS operation returns control to the normal NSF attachment handling code. Worst case, it'll get in-lined in the database.