An S-TAP that was installed by shell can be converted to a GIM-managed S-TAP.
Before you begin
Verify that:
- S-TAP is up and running.
- K-TAP is loaded.
- Database activities are captured.
- Download the BUNDLE-GIM and save it on the database server.
About this task
If you use the BUNDLE-GIM and BUNDLE-STAP that have the exact same version and revision
number as the S-TAP, you do not need to reboot the database server. You can upgrade the S-TAP by
installing a higher version or revision of the BUNDLE-STAP, but you need to reboot the database
server.
Procedure
-
Copy the GIM client installer on the database server in any folder.
- Install the GIM client on database server where S-TAP is running by using the downloaded
GIM client shell installer script.
For example:
If the GIM client reports to
the same collector as the S-TAP:
./guard-bundle-GIM-X.X.X_rXXXX_v1X_1-rhel-8-linux-x86_64.gim.sh --
-q
If the GIM client reports to the central manager:
./ guard-bundle-GIM-X.X.X_rXXXX_v1X_1-rhel-8-linux-x86_64.gim.sh --
--sqlguardip <CM_IP> –q
The database responds:
Installing modules ....
Installation completed successfully
- Verify that the GIM and SUPERVISOR processes are running by entering the command:
ps -ef|grep modules
-
Log in to the Guardium system that this S-TAP reports to. Go to .
-
In the Choose clients section, select the clients using check boxes in
the table. Click Next to continue.
-
In the Choose bundle section, use the Select a
bundle menu to select the bundle that is installed on the database.
- Click Next, the click Install, and then
click nowor OK
Allow about 5 minutes for installation to finish.
- Verify the installation status in the GIM Events List
report.
If you used the exact same version and revision number of BUNDLE-GIM and
BUNDLE-STAP as the currently running S-TAP on the daabase server, then S-TAP and K-TAP continue to
monitor database activities but are managed by GIM. The Event description
column in the GIM Events List report should show Status: OK
- If you upgraded the S-TAP by installing a higher version or revision of BUNDLE-STAP,
verify that the Event description column in the GIM Events
List report is IP-PR. Reboot the database server as follows, depending on the operating
system.
- AIX: reboot
- Linux® shutdown -r
- SuSe: reboot
- HP-UX: shutdown -r
- Solaris: shutdown -i [6|0] (Note: '0' can be used only if shutdown is done from the terminal
server)