Grouper Developers Forum

[Shilen Patel <>]

I think you can either:

1.  Comment out the PSP change log consumer and run the changeLogTempToChangeLog job.  (You could have let the daemon run like this while the import was happening to save time in the overall load.)

2.  Or you can delete the temp change log and run the PIT Sync.  The audit would end up not being 100% accurate but maybe you're okay with that.  For instance, if memberships were added and deleted, then they wouldn't be reflected in the point in time audit.  Also, timestamps for when objects were created and deleted would be off.

gsh 0% new edu.internet2.middleware.grouper.misc.SyncPITTables().syncAllPITTables()

 

Thanks!

-- Shilen

From: Gagné Sébastien <>
Date: Wed, 24 Oct 2012 08:38:16 -0400
To: <>
Subject: [grouper-dev] Scrapping Changelog_TEMP table ?

Hi,

In my big data import in Grouper, I shut down the Daemon so I can bulkSync the data instead of having the PSP Changelog do it. After the big import I’m left with a huge CHANGELOG_TEMP table that will probably take hours to process with loaderRunOneJob("CHANGE_LOG_changeLogTempToChangeLog");

 

Is it safe to simply delete the content in CHANGELOG_TEMP or am I going to run into troubles with audits and point in time (or something else?)?

 

Thanks

 

 

Sébastien Gagné,     | Analyste en informatique

514-343-6111 x33844  | Université de Montréal,

                     | Pavillon Roger-Gaudry, local X-100-11