Unsolved
This post is more than 5 years old
24 Posts
1
1855
February 3rd, 2010 10:00
DFS and CENTERA store
DFS: 6.5 SP2
Content Server: 6.0 SP1
WORM Store: Centera
Our system is currently integrated with a .NET DFS service creating both normal filestore objects and CENTERA store. Currently, we've noticed recently that there has been a high degree of CENTERA objects failing via DFS with the following error message. This is not consistant as some CENTERA objects do get created. Any thoughts or links to discussions that may help would be greatly appreciated.
Caused by: com.emc.documentum.fs.services.core.impl.execution.proto.dfc.DfcOperationException: Create contentful action with identity: "[Online Tax forms eReview_Round-2.4.pdf] [id =null] PROPERTIES [object_name=Online Tax forms eReview_Round-2.4.pdf|title=Online Tax forms eReview_Round-2.4.pdf|a_content_type=pdf|piece_id=529292.4.0|created_by=|legacy_created_date=02/03/2010 09:17:00|retention_policy_date=1/9/2014 12:00:00 AM|attach_type=Final|doc_type=Final|rp_signoff_info=]" failed.
...
Caused by: com.emc.documentum.fs.services.core.CoreServiceException: Failed to execute DFC operation: Could not check in document 'dfs-303972.tmp'
DfException:: THREAD: WebContainer : 14; MSG: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_WRITE]error: "Plugin ID: 0000000000000000 returned error: (null) : (null), error code:-11,003"; ERRORCODE: 100; NEXT: DfException:: THREAD: WebContainer : 14; MSG: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_WRITE]error: "Plugin ID: 0000000000000000 returned error: (null) : (null), error code:-11,003"; ERRORCODE: 100; NEXT: null
at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)
at com.documentum.fc.client.impl.connection.docbase.MessageEntry.getException(MessageEntry.java:39)
...
Followed by: DfException:: THREAD: WebContainer : 14; MSG: [DM_STORAGE_E_CA_STORE_PLUGIN_ERROR_DURING_WRITE]error: "Plugin ID: 0000000000000000 returned error: (null) : (null), error code:-11,003"; ERRORCODE: 100; NEXT: null
at com.documentum.fc.client.impl.docbase.DocbaseExceptionMapper.newException(DocbaseExceptionMapper.java:57)
ndegroff
24 Posts
0
February 3rd, 2010 12:00
holgerjakob_c0722c
2 Intern
•
337 Posts
1
February 3rd, 2010 13:00
Hi
Your log does not list any Centera errors that would be starting with -10000 and higher numbers.
Is there anything common to the objects not stored on Centera? Size of them over a certain size?
Is the directory where your tmp files are stored big enough resp. enough free capacity?
Concurrency issue in the database? Numer of connection issues?
Check the Centera and Documentum Server IP Settings. I have had issues when some were on HD instead of FD or automatic having negotiated something silly. Sporadic errors were always the result depending on size of the object transferred; large ones were failing while small ones went well.
On the Centera side there seems nothing to be wrong, the profile has the capability to write (apparently) and the connection itself is possible. Not a lot more to check other than that.
Best regards, Holger
FabianLee-EMC
124 Posts
0
February 3rd, 2010 13:00
Enable tracing of the storage plugin when you startup the Content Server, then check the docbase logs for more information.
-oca_store_trace
holgerjakob_c0722c
2 Intern
•
337 Posts
1
February 4th, 2010 06:00
Hi
The SDK Error Messages go from -10000 to -10215 or something in this region. Your error message does not seem to come from the SDK or an SDK error might result in the message you see.
If you are performing a Migration on your system you might have a lot of load pending on how it is performed. If it's via store then a lot of the usual bandwidth might be used for it. If it is C2C it will depend on the number of threads configured.
Best regards, Holger
ndegroff
24 Posts
0
February 4th, 2010 06:00
Thanks Jakob for your response. If you actually check the dump, the error code # is -11,003. I'll work with our infrastructure team to start setting up trace and write up an EMC ticket to get their POV on it.
On a possibly related/unrelated note, EMC is currently running a CENTERA migration to move the centera stores from one physical location to a store a few states away.
ndegroff
24 Posts
0
February 4th, 2010 13:00
I broached the subject during a migration meeting to discover that multiple CENTERA clusters in our environment were also experiencing similar issues. We opened a ticket and because EMC was on site they were able to identify an issue with the CENTERA store. They implemented a corrective action overnight and since that time, we haven't seen the issue.
What the corrective action was or what was going on with the clusters, I have no idea. I'm still pushing to get a better understanding so if this happens again, I can have more information for reference. Thanks to both of you who responded to this thread. If I find out any more information, I'll post it to this thread for others who get similar issues.