
Utilities
301
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
13.5.2 Prerequisites
There are several prerequisites for running the Clean_Database script.
The user running the script must have permission to execute the cleanup script.
The user running the script must have permission to access/execute all of the database tools/
utilities. On Linux systems, this may involve making the esecadm user a member of the
"oinstall" group. For example:
usermode -G esec,dialout,video,oinstall esecadm)
[Identity Cleanup only] The database must be in a healthy state and in good running condition
as the Identity cleanup stored procedure will disable/enable foreign key constraints.
[Identity Cleanup only] All Identity/Account loaders and collectors, such as the Identity Vault
Collector, should be stopped.
[Identity Cleanup only] Reports that are running queries against the Identity tables should be
stopped.
The Identity cleanup DDL operations are NOT atomic so if one DDL statement execution fails, the
script will exit with errors written to the specified log file. There is no recovery for this scenario and
a DBA would be required to run the DDL again.
WARNING:
If identity information is cleaned out of the database and then reloaded, the new
identity information will not be synchronized with any past events that had identity information
injected. Therefore, attempts to perform identity lookups on past events (received before the
cleanup) or run reports on past events with identity information will not be successful.
Use this option with extreme caution.
To run Clean_Database.sh on Linux:
1
Open a console, go to $ESEC_HOME/bin and enter
Clean_Database.sh
to start the script.
NOTE:
At any time you can abort the execution of the cleanup script by entering "q" at any
prompt.
2
At the prompt, indicate which objects you want to remove from the database:
Which objects would you like to cleanup?
(1) Incidents
(2) Identities
(3) Assets
(4) Advisor
(5) Vulnerabilities
(6) Incidents and Identities
(7) All
3
At the prompts, enter the following information to connect to the Oracle database:
Database name (Example: ESEC) => Ansping will be performed to verify the
existing of the specified database instance.
Database username (Press ENTER for default esecdba)
<username> password =>
The connection to the database will be verified.
The database connection is verified before proceeding to the next step.
Summary of Contents for SENTINEL 6.1 SP2
Page 4: ...4 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 20: ...20 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 34: ...34 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 116: ...116 Sentinel 6 1 User Guide novdocx en 7 January 2010 Integer Variable String Variable ...
Page 146: ...146 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 172: ...172 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 178: ...178 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 280: ...280 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 306: ...306 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 329: ...Quick Start 329 novdocx en 7 January 2010 ...
Page 330: ...330 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 412: ...412 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 430: ...430 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...
Page 440: ...440 Sentinel 6 1 User Guide novdocx en 7 January 2010 Figure 18 3 Reports ...
Page 528: ...528 Sentinel 6 1 User Guide novdocx en 7 January 2010 ...