Products | Versions |
---|---|
TIBCO LogLogic Security Event Manager | all versions |
1. Stop all SEM services:
/etc/init.d/exa_all stop
Make sure MySQL has been stopped. To check if it has been correctly stopped, enter the following command line "ps aux | grep mysql" If MySQL has been stopped, you will not get any result.
Note:
If you work on a dedicated reporting server, you must stop the reporting server before the database server.
2. Open MySQL my.cnf configuration file:
vi /usr/local/exaprotect/mysql/my.cnf
Change
innodb_data_file_path = ibdata1:190734M
to
innodb_data_file_path = ibdata1:190734M;ibdata2:1024M
It will create this file: /var/lib/exaprotect/mysql/ibdata2
Comment 1:
You can have as many ibdata files as you want (separated by ";"), it will always be created in this folder /var/lib/exaprotect/mysql/
Comment 2:
You can fix the size you want in Megabytes (ibdataN:XXXXM)
Comment 3:
Warning : Make sure there is enough space:
- on disk so that you can create additional tablespace
- on /var/lib/exaprotect/ for backup, restoration, rawlog
3. Restart MySQL only:
/etc/init.d/exa_mysql start
Note:
This operation may be time consuming (several minutes to some hours depending on the size chosen for the new table(s)) because MySQL will create the tablespace corresponding to ibdata2.
The following output will be displayed:
[root@exabench3 root]# /etc/init.d/exa_mysql start
Starting SMP DataBase: Wait for mysqld to start............ gave up waiting!
A lot of ".." and an error at the end will be displayed. This error is normal because the startup script wait 2 minutes maximum after MySQL is started.
Note:
If you work on a dedicated reporting server, you must start the reporting server after the database server.
4. You must check the MySQL log file:
/var/lib/exaprotect/logs/esmp_mysql.log
4.1 Example:
070620 11:05:19 mysqld started
070620 11:05:19 InnoDB: Data file /var/lib/exaprotect/mysql/ibdata2 did not
exist: new to be created
070620 11:05:19 InnoDB: Setting file /var/lib/exaprotect/mysql/ibdata2 size
to 1024 MB
InnoDB: Database physically writes the file full: wait...
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000
070620 11:05:33 InnoDB: Started; log sequence number 14 1017457304
070620 11:05:33 [Note] /usr/local/exaprotect/mysql/bin/mysqld: ready for
connections.
Version: '5.0.xx-enterprise-log' socket:
'/var/lib/exaprotect/mysql/mysql.sock' port: 3306 MySQL Enterprise Server (Commercial)
4.2 Example:
The longest part is :
InnoDB: Progress in MB: 100 200 300 400 500 600 700 800 900 1000 (...)
4.3 Example:
070620 11:05:33 [Note] /usr/local/exaprotect/mysql/bin/mysqld: ready for
connections.
Version: '5.0.xx-enterprise-log' socket:
'/var/lib/exaprotect/mysql/mysql.sock' port: 3306 MySQL Enterprise Server
(Commercial)
5. Restart all the SEM services:
/etc/init.d/exa_all start