We started the Documentum upgrade in the wintertime and our jobs ran successfully by following the defined schedule. Once we moved to the summertime we hit an issue: A job that was scheduled for instance at 4:00 AM was executed at 4:00 AM, but also started every 2 minutes until 5:00 AM. We had this issue on all our 6.7SP2P009 repositories – on upgraded as well as on new repositories.<\/p>\n
Before opening an SR in powerlink, I first checked the date and time with the following query.<\/p>\n
On the content server using idql:<\/p>\n
The date and time was correct, EMC confirmed a bug and asked us to install the Patch 12 which solved the issue.<\/p>\n Unfortunately the patch 12 introduced a bug on D2EventSenderMailMethod which does not work anymore. The mail could not be sent out. D2EventSenderMailMethod is a requirement for D2. It is used by D2 mails but also for some workflow functionalities. By default, if the event is not managed by D2 (ie : configured) the default Documentum mail method is executed, EMC said.<\/p>\n To test the mail issue, I used the dm_ContentWarning job by setting the -percent_full parameter to 5 (lower than the value displayed by df -k).<\/p>\n In $DOCUMENTUM\/dba\/log\/\/MethodServer\/test67.log thefollowing\u00a0error was displayed:<\/p>\n <\/p>\n Wrong number of arguments (31) passed to entry point ‘Mail’.<\/samp><\/p>\n <\/p>\n And by setting the trace flag for the dm_event_sender method we saw:<\/p>\n It worked when I updated the dm_server_config object:<\/p>\n EMC confirmed that this is a bug and should be fixed with D2 3.1 P05<\/p>\n","protected":false},"excerpt":{"rendered":" We started the Documentum upgrade in the wintertime and our jobs ran successfully by following the defined schedule. Once we moved to the summertime we hit an issue: A job that was scheduled for instance at 4:00 AM was executed at 4:00 AM, but also started every 2 minutes until 5:00 AM. We had this […]<\/p>\n","protected":false},"author":24,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[129,419,155],"type_dbi":[],"class_list":["post-3941","post","type-post","status-publish","format-standard","hentry","category-application-integration-middleware","tag-documentum","tag-emc","tag-patching"],"acf":[],"yoast_head":"\n1> select date(now) as date_now from dm_docbase_config
\n<\/code>2> go
\ndate_now
\n<\/code><\/code>————————
\n4\/9\/2014 17:47:55
\n<\/code>(1 row affected)
\n<\/code><\/code>1><\/p>\n<\/h3>\n
Patch 12 and D2EventSenderMailMethod<\/h3>\n
\n2014-05-08T12:53:45.504165\u00a0\u00a0\u00a0\u00a0\u00a0 7260[7260]\u00a0\u00a0\u00a0\u00a0\u00a0 0100007b8000c978\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TRACE LAUNCH [MethodServer]: .\/dmbasic -f.\/dm_event_sender.ebs -eMail\u00a0 —\u00a0\u00a0 “test67”\u00a0 “xxx May 08 12:53:25 2014”\u00a0 “DM_SYSADMIN”\u00a0 “Take a look at \/dev\/mapper\/vg00-lvpkgs–it’s 81% full!!!”\u00a0 “ContentWarning”\u00a0 “0900007b8000aeb3”\u00a0 “nulldate”\u00a0 “10”\u00a0 “dm_null_id”\u00a0 ” ”\u00a0 “dmsd”\u00a0 “test67”\u00a0 “event”\u00a0 ” ”\u00a0 “test67” “”\u00a0 “undefined”\u00a0 “dmsd”\u00a0 “1b00007b80003110”\u00a0 “5\/8\/2014 12:53:28”\u00a0 “0”\u00a0 “dm_document”\u00a0 “text”\u00a0 “3741”\u00a0 “text”\u00a0 “cs.xxy.org”\u00a0 “80”\u00a0 “”\u00a0 “\/soft\/opt\/documentum\/share\/temp\/3799691ad29ffd73699c0e85b792ea66”\u00a0 “.\/dm_mailwrapper.sh”\u00a0 ” ” dmProcess::Exec() returns: 1<\/samp><\/p>\nupdate dm_server_config objects set mail_method = 'dm_event_template_sender'<\/code><\/p>\n