How to delete System / System Connector in VIRSA CC ??

[former_member69568]

We have implemented VIRSA with 1 System Landscape. i.e for VIRSA we have only one system.

Our VIRSA version is 5.1.

Currently our VIRSA is configured with 2 DEV + 2 QTY + 2 PRD ABAP systems.

i.e VIRSA is having now 6 ABAP Systems for analysis.

As we aware in 5.1 Batch Risk Analysis can not be run for 1 system.

we have to run Batch Risks Analysis for all systems - it is taking everytime 72 Hours to compete the same.

During 72 Hours any system has any problem / connection / restart / any thing happens. The batch risk analysis goes into "ERROR".

In this corner - we want to remove DEV & QA Systems from VIRSA.

How we can do that??

When we are trying to delte the Connectors of respective Systems.

we are getting the following message

" com.virsa.cc.rulearchitect.dao.DAOException: Cannot delete connector as there are entries related to this connector in the system. "

How can we delete the Connectors in a standard way. if it can not be delted in stnadard way , what is the work around ??

Rgds

Edited by: B Jyothi on May 11, 2009 5:50 AM

[Former Member · Accepted solution]

Hi Jyothi,

To delete connector, you have to delete all data related to that connector.

You can delete using standard SAP script.You have to create message in GRC Component and get the script.

Thanks,

Joseph

.

[Former Member · Accepted solution]

Hello Jyoti,

You did not mentioned which components of GRC you are using, but I will assume it is CC (RAR).

If you want to delete connector from GRC screen then it might give you error given below,

Error:Cannot delete connector as there are entries related to this connector in the system

So for that you have to delete associated data against this connector first.

But for a work around it will give you one oracle command to delete CC (RAR) connector,

delete from VIRSA_CC_SYSTEMC where VSYSKEY= 'your System Name';

This command will delete that connector from GRC 100%, but SAP is not recommending to delete anything from backend oracle.

Thanks,

Sudip...

[pr_srinivas · Accepted solution]

We have done the same.

but we execute Batch Risk Anlysis again we get problem like below

++++++++++++++++++

May 15, 2009 11:49:48 AM com.virsa.cc.xsys.bg.BgJob setStatus

INFO: Job ID: 480 Status: Error

May 15, 2009 11:49:48 AM com.virsa.cc.xsys.bg.BgJob updateJobHistory

FINEST: --- @@@@@@@@@@@ Updating the Job History -

---

2@@Msg is Error while executing the Job:Cannot get Data Extractor for B10CLNT010, reason:System Connector not defined

May 15, 2009 11:49:48 AM com.virsa.cc.xsys.bg.dao.BgJobHistoryDAO insert

INFO: -

---

Background Job History: job id=480, status=2, message=Error while executing the Job:Cannot get Data Extractor for B10CLNT010, reason:System Connector not defined

May 15, 2009 11:59:25 AM com.virsa.cc.common.RiskAnalysisReport addHeader

INFO: showOrgRule. Rule Analysis - Add header - after false

++++++++++

where B10CLNT010

+++++++++++++++

under connectors - it is not avaialble.

but when execute Batch Riks Analysis .. it fails with above message,.

is any restart is required ??

Rgds

[Former Member · Accepted solution]

We only have GRC 5.3 here so that perhaps it is not apple to apple.

I did a test as follows: I removed a JCO for a backend system and I did not see any batch failed.

Is my scenario equavelent to yours?

Thanks!

[former_member69568]

Hi.. Experts

If we would like to delete the connectors,

we can do it manually from database.

You can use attached deletion script which needs to be run at database level.

and restart the instance which very much mandatory

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Note : SAP never recommends to use deletion script on Production Server.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

IMPORTANT Note 1 -

+++++++++++++++++++

This script will delete EVERYTHING related to a connector

including rules, mitigations, management reports, etc.

Therefore, Customer are doing this on their own accord.

In order to delete the (CC) data, you would have to run a

deletion script against the database tables.

However, this is not the recommended best practice especially

in a production environment.

In doing so this may cause data inconsistencies and may render your

application unstable. Therefore, please be advised that by using the

script you are doing this at your own accord and SAP Support will not

be responsible for any loss of data consequent to the application of the

script and SAP cannot support an unstable application.

The script will be provided only upon request. Again, please be aware that

execution of this script is recommended only in a non productive environment.

It is also recommended that you take a backup of the database prior to

executing the script.

IMPORTANT Note 2 -

+++++++++++++++++++

Please involve your DBA to run the attached scripts on the Java Database

where you have the CC 5.x Installed. Since you want to delete the data

for a particular connector,

kindly replace the '&1' in the script

for VSYSKEY with the SID of the Connector.

Note:

+++++++++++++++++++

The Management reports will also be removed after you run the script

andyou will have to re-run the Management Update Jobs for the exisiting

connectors, to make sure that you have the accurate results in the

graphs.

PLEASE USE THIS SCRIPT ONLY ON YOUR OWN RISK. STILL WE HAVE A COMPLETE BACKUP

WE HAVE NO RISK; TAKE BACKUP & TAKE A CHANCE RUNNING THIS SCRIPT.

[former_member69568]

Continue to above

=============

Script can be downloade from below link & You can download replace with SID and use

http://www.4shared.com/file/109426131/cfd4b648/CC51_DELETE_CONNECTOR_DATA__SQL_SCRIPT.html

Rgds

Edited by: B Jyothi on Jun 2, 2009 5:39 PM

[Former Member]

Hi Jyothi,

Can you please provide me the script. I required it badly.

Thanks & Regards,

Satyabrat

[Former Member]

Hi Jyothi,

Can you please provide me the script. I required it badly.

Thanks & Regards,

Satyabrat

[Former Member]

My apologize for re posting. it is due to my network problemr.

Thanks,

Satyabrat

Edited by: Satyabrat Mohanty on Nov 21, 2009 12:39 AM

Edited by: Satyabrat Mohanty on Nov 21, 2009 12:40 AM

[pr_srinivas]

I think it is not !!

Because 5.3 gives more luxuries compare to 5.1.

i beleive in 5.3 , we can schedule Batch Risk Analysis for a specific system.

in 5.1 - we do not have option to run Batch Risk Analysis for a specific system.

if we had option, Deltion of systems is not at all requirement.

Rgds

[Former Member]

So I recommend you remove all systems and then re-define the connector with only selected systems in order to improve the performance.

[pr_srinivas]

As we aware, we can not delete Connectors directly fron VIRSA, if any objects are already alable with that SID. as it is not direct solution is not avaialble , we were trying to delte with SQL commands which directly delting entries for thise data connectors from the database.

But still, Batch Risk Analysis is failing with a reason referrring to Connector which is already delted.

Rgds