This content has been marked as final. Show 8 replies
Could you explain in more details what exactly you mean by "it deletes the source file upon replication"?
If you are referring the fact that files might still be located in the "Vault" (physical hard drive) though being deleted, this is not a question about the Archiver - if you delete the revisions (e.g. via Repository Manager) it might show the same result. The Archiver just calls a DELETE service, and cannot be responsible for what this service does.
Therefore, pls. explain what you meant.
My requirement is to set up auto replication so that the contents when expired would be transferred to another UCM.When getting transferred using auto replication,the contents in the source UCM should be deleted.
But I can see the source contents when I access Content Server -->Content Management-->Expired Content.
Am I missing something?
It seems that your data were not archived. Can you come back to the Archiver, open the relevant batch file (that should delete them) and verify that the desired content items are present in the archive? I guess, they won't be.
Also note that the "DELETE" service does not immediately remove the items from your system. It just flags the content item for deletion. The indexer is ultimately responsible for actually deleting the items flagged for deletion.
This time I'm almost certain that the cause is elsewhere - items flagged for deletion would not display in the Expired content (service GET_EXPIRED). I think they are displayed only in the Repository Manager, with 'Deleted' status.
In fact, I came across a similar issue when I tried to replicate it - I created two items, one to be expired today and one to be expired yesterday (requires to adjust Release date to be prior to Expired date); both are displayed in the GET_EXPIRED output. Then, I create a job that archives both the items, but have not noticed that it uses AND to bind conditions (the resulting query was something like dDocName equals X AND dDocName equals Y). Of course, the batch job succeeded, but no item disappeared (and the job result was empty). When I fixed the query items disappeared.
I got confirmation from oracle support that Delete file after Export does not work in auto replication in UCM,they might release future patch to resolve this.
Oracle confirmed this to be a bug in in Archive module in UCM
Hi Ashwin ,
I would say that it is not a BUG , but a desirable feature which is not available .
Bug would indicate existing feature not working correctly .