EDITED: I just found THIS issue, which probably covers this question. Will need to do some testing though to verify it.
http://www.odusergroup.org/forums/index.php?topic=996.0Hi,
This is a long shot, something for all you OnDemand-lovers out there!
We currently have a customer, on OD 8.5.0.9 running on AIX, where we recently experienced something very weird. A PMR is opened, and we are working with IBM on this, but we have been unable to efficiently reproduce the problem on purpose - thus far, at least.
We made a script which had the purpose of doing this (plus a little extra, but we can pinpoint the error to these two steps):
* Export all documents within a named LoadId
* Unload all documents in that same LoadId - although here the two last parts of the LoadId are replaced with "-0-0" for practical reasons.
The result is, somewhat surprisingly, that on step 1, X number of documents are exported.
While in step 2, a number GREATER than X is Unloaded!!!
This shouldn't be possible, no.
The number in step two, for example "34", matches the number reported in the System Log MsgNum 87 (arsload) for the same load. But when we exported that LoadId, we only got 33 documents.
Can you guys please think of any situation where this may come true?
YES: we use Enhanced Retention Management on this system. Between step 1 and step 2, we remove ALL Holds on all documents within the LoadId. Never any problem with this, all documents in the LoadId ALWAYS get deleted. IF there was a problem with this step, the resulting number of deleted documents should be LESS THAN the number that got exported, but it is the other way around.
Here are the exact commands that we used in the script. Let us know if they are incorrect in some way, which may cause the behaviour above.
Also, let us know if you in any other setting have experienced similar problems, please describe when and how.
The exact scripted arsdoc get command looked like this:
${OD_BASE_CATALOG}/arsdoc get -a -d ${WORKDIR} -G ${APPGRP} -X ${LOAD_ID} -g -h ${OD_INSTANCE} -o ${PREFIX} -u ${USERNAME} -p ${PASSWORD} -A 7 -N -c > tmp.txt 2>&1
Which instantiated would translate to something like this (Sensitive information changed for security reasons):
arsdoc get -a -d /opt/ondemand/arsdownload/erm/working -G OURAPPGROUP -X 6099-13-0-2129FAA-16683-16683 -g -h ARCHIVE -o FILE2129 -u ODUSER -p xxxxxxxx -A 7 -N -c -v >> FILE2129.txt 2>&1
The exact scripted arsadmin unload looked like this:
${OD_BASE_CATALOG}/arsadmin unload -h ${OD_INSTANCE} -g ${APPGRP} -u ${USERNAME} -p ${PASSWORD} -Q -L ${LOAD_ID} > tmp.txt 2>&1
Instantiated, something like this:
arsadmin unload -h ARCHIVE -g OURAPPGROUP -u ODUSER -p xxxxxxxx -Q -L 6099-13-0-2129FAA-0-0 > tmp.txt 2>&1
