CiviCRM Community Forums (archive)

I recently completed a 18K contact migration into CiviCRM and I am experiencing a strange issue whereby contacts that are set to take their membership status from their employer are not fully "up to date".

In other words, an employee of a current member is showing as "expired", and only showing last years membership, for example.

Is there any way to set off a batch update of member "by relationship" status?

Unfortunately, we went live before users caught this, so I can't roll back and reimport...

I found something interesting in "scheduled jobs", the "Membership status processor" job, and I ran it, but the job completed in 5 seconds, giving me this in the job log:
-------------------
Summary
Finished execution of Membership status processor with result: Success (Processed 17300 membership records. Updated 0 records. Sent 0 renewal reminders.)
Details

Parameters raw (from db settings):
version=3


Parameters parsed (and passed to API method):
a:1:{s:7:"version";s:1:"3";}

Full message:
Finished execution of Membership status processor with result: Success (Processed 17300 membership records. Updated 0 records. Sent 0 renewal reminders.)

--------------

Update: Even though the script supposedly ran in 5 seconds, my 2GB dedicated server went off and ran wild soon after, fatal errors (out of memory) everywhere! The thing is still so locked up I can't even FTP to it, but it looks like its over the hump. Ouch.

Update 2: Nope, I was wrong, not over the hump...Right back up to 500% util... Now HTTP and SSH sessions are being rejected...

Any help would be much appreciated!

Thanks!

Ugh.

I wrote a quickie "Relationship Touch" module that uses the batch+civicrm API to update each and every relationship in the civicrm_relationship table (10,932 of them). This refreshed all the stale records without any kind of server killing side effects.

So much for the scheduled job.