Grouper Users - Open Discussion List

[Emilio Recio <>]

Well, I am not sure. The query goes against a DB Link on the database.
It's using the same database that grouper uses internally. So I guess it
was connecting OK. However, there's a db link from grouper's db to the
remote db (SOR) from which loader is pulling in data. If the db link
goes down, does this count as zero rows from the SOR and hence it
deletes the members from the group?


On 09/13/17 09:14, Hyzer, Chris wrote:
> If there is an error running the query, the loader will not remove all 
> members.  Only if the database successfully returns no records.  Are you 
> sure that is what happened?
>
> -----Original Message-----
> From: 
> 
>  
> [mailto:]
>  On Behalf Of Emilio Recio
> Sent: Wednesday, September 13, 2017 7:20 AM
> To: Grouper Users Mailing List 
> <>
> Subject: [grouper-users] grouper-loader fail safe / threshold for failed 
> connections
>
> So we had a network outage, and the connection between grouper-loader
> and our oracle database failed. This caused zero entries to be returned
> when loader ran. When pspng provisioned out to our ldap, it undid the
> attributes for the people we expected from the back end oracle database.
>
> Is there a way I can tell grouper that if grouper-loader experiences a
> *connection* problem with the back end database, do not do anything;
> just exit with an appropriate rc? Is there a way I can kick off a script
> before to check for connectivity that stops the loader process based on
> its rc?
>
> I've seen the threshold value, but don't know if it would make sense. We
> expected only 40 peoples' data elements from the back end database. Say
> I put the threshold to 40, then as far as I've seen in the docs,
> reaching this just drops it into fullsynch mode. How does fullsynch mode
> know to apply a failsafe? Is there a property for that?
>
> --
>
> Thanks,
> E. Recio
> The information contained in this transmission contains privileged and 
> confidential information. It is intended only for the use of the person 
> named above. If you are not the intended recipient, you are hereby notified 
> that any review, dissemination, distribution or duplication of this 
> communication is strictly prohibited. If you are not the intended 
> recipient, please contact the sender by reply email and destroy all copies 
> of the original message.
>
> CAUTION: Intended recipients should NOT use email communication for 
> emergent or urgent health care matters.
>