FileStore changed-but versioned documents are getting created in old location which is full
Hi,
We had configured 3 filestores and were saving our documents to filestore 1. When filestore 1 got filled up, we changed the default location to Filestore 2. All the newly created documents are going to filestore 2 as expected. But the problem is with the versioned documents.
All the versioned documents are trying to get stored to old filestore which is already full and failing.
Can anything be done to stop this behaviour and make the newly created versioned documents also to save to new FileStore.
Regards,
Rakhi Raveendran
Comments
-
Hi Johnny,
I managed with migrate content API to fix the issue temporarily.
But with the API with DQL predicate whenever I use a DATE() condition, I get the below error.
"Bad datatype or value conversion for attribute "DD/MM/YYYY")."
I tried with single quotes and double quotes but still its throwing the same error.
I finally went for other filtering options, but I would like to find out how to do the date filtering also.
Can you please help.
Regards,
Rakhi Raveendran
0 -
DQL Perdicate-a_storage_type='filestore_01' and r_modify_date>DATE('01/02/2017','dd/mm/yyyy')
Full API used:
apply,c,NULL,MIGRATE_CONTENT,TARGET_STORE,S,filestore_02,LOG_FILE,S,/u01/apps/documentum/dba/log/migration1.txt,MAX_MIGRATE_COUNT,S,100000,SYSOBJECT_QUERY,B,F,TYPE_TO_QUERY,S,myCustomType,QUERY,S,a_storage_type='filestore_01' and r_modify_date>DATE('01/02/2017','dd/mm/yyyy'),REMOVE_ORIGINAL,B,T
I also tried with double quotes. Except date criteria everything else is working fine.
0 -
FYI - I use full date/time format whenever, I use DATE(). It just seems to work better. Try this:
apply,c,NULL,MIGRATE_CONTENT,TARGET_STORE,S,filestore_02,LOG_FILE,S,/u01/apps/documentum/dba/log/migration1.txt,MAX_MIGRATE_COUNT,S,100000,SYSOBJECT_QUERY,B,F,TYPE_TO_QUERY,S,myCustomType,QUERY,S,a_storage_type='filestore_01' and r_modify_date>DATE('01/02/2017 00:00:00','dd/mm/yyyy hh:mi:ss'),REMOVE_ORIGINAL,B,T
0 -
Hi Johny,
I'm still getting the same weird error of Bad Datatype even with time stamp added.
I doubt if its a problem with Samson from where I'm trying to execute.
May I know from where are you executing your api s from iapi- or any third party tool ?
Regards,
Rakhi Raveendran
0
Categories
- All Categories
- 117 Developer Announcements
- 52 Articles
- 145 General Questions
- 133 Services
- 56 OpenText Hackathon
- 35 Developer Tools
- 20.6K Analytics
- 4.2K AppWorks
- 9K Extended ECM
- 912 Cloud Fax and Notifications
- 81 Digital Asset Management
- 9.3K Documentum
- 29 eDOCS
- 167 Exstream
- 39.8K TeamSite
- 1.7K Web Experience Management
- 4 XM Fax