GRC AC V10 - Deletion of connectors (incl. data from GRAC-Tables)

[Former Member]

Hey,

does anybody have an idea how to delete connector AND relating data (e.g. from risk analysis).

Thanks!

Bianca

[Former Member]

Hi,

In addition to the GRAC_RULE_DELETE tcode you may also want to consider for ARA module SA38 - GRAC_DELETE_ACCESS_RULES_ALL, but that is a rigid one. You would still also need to delete the connector and its tied settings in SPRO though. I couldn't find a similar program that quickly for ARM/EAM/BRM though.

Cheers,

George

[Former Member]

Cleaning up EAM can be done via SA38 - GRAC_SPM_CLEANUP.

[Former Member]

Hi,

You can use GRAC_RULE_DELETE tcode. Select Delete Sync data, Delete Violation data for connector (SM59). Make sure that RFC connection is Valid.

Thanks

Kailash

[Former Member]

Hi Kaushal,

this is clear. The issue is, that those connector related data from risk analysis or repository synch won't be deleted, when I delete the customizing. I am able to delete rules etc. but e.g. those data from tables like GRACROLEORG, etc.

Do you have an idea for those data as well?

Thanks!

[Former Member]

Hello Bianca,

This is and old post

and actually is for grc 5.x. The point is that I guess you can ask SAP for a script. Obviously you have to do it on your own risk.

Cheers,

Diego.

[Former Member]

Hi Bianca,

I think the best thing to do is raise a message to SAP, as I am also unclear on the correct solution to achieve what you are trying to do.

In 5.3, I know there was a delete rule set script etc, and basis could delete the historical risk analysis data, allowing you to have a fresh Management report (thats if they knew where to find the correct data tables etc), but with GRC 10.0 running on ABAP, A clear supported strategy from SAP would probably be the safest method to apply and follow.

[Former Member]

Hi Kauhshal,

I already did open a message to SAP. They gave just the answer, that I have to write a report by myself...

Thanks for your opinon and input!

Bianca

[simon_persin4]

Hi Bianca,

Perhaps this is something for the Ideas Place?

In ABAP, you should be able to truncate the database tables or just remove the entries via direct table maintenance. However, I cannot recommend that in good conscience since it contravenes a lot of the generic SAP best practices and audit controls around data maintenance.

Simon

Edited by: Simon Persin on Jan 16, 2012 2:35 PM

[former_member541582]

Hi Bianca,

Did you go for the solution to develop a report for delete the content from GRACROLEORG?

Somehow the table got filled with 49M entries (48M for one connector alone) and now the sync job is dumping during the delete operation because it is running out of undo space after 50000s.

The question is, increase table space or a direct delete? Any specific relations to consider?

Kind Regards,

Vit

[Former Member]

Hello Vit,

We had the same issue. Try to implement OSS note 1741277. This did the trick

Thanks,

Raghav

[former_member541582]

Thanks for the tip! The issue was however solved a while back by temporary increasing the tablespace for PSAPUNDO.

[rudolf_dums2]

Hi,

a big part of cleaning will be done by the loader jobs itself

if you enter all (4) object types for Exclusion at Batch Risk Analysis

...see SIMGH > GRC AC > Access Risk Analysis > Batch Risk Analysis > Maintain Exclude Obj. ...

PS: maybe to late for original request,
but could help others who also want to 'deactivate' a client in GRC

Kind Regards

  R. Dums

[santosh_krishnan2]

In my case, my client renamed the connectors and are now asking me to delete old Firefighter controllers that still appear in the controllers list, but can't be deleted.  Those controllers have the old connector name associated with them, and that connector has since been deleted.

Do you know how to get rid of those controller entries?

Thanks a lot!

Santosh

[Former Member]

Hi Bianca,

You should be able to do this via SPRO and just work backwards from the initial connector configuration steps.

What you may require to do as the initial step is delete the ruleset rules generated against that connector (if it has been generated against that single system etc).