Sie sind auf Seite 1von 3

1.

a.
b.
c.
d.
1. a.
b.
1. a.
b.
1. a.
b.
c.
1.
1.
2.
Infinidb Bible
Mount:
Always ensure that / filesystem is mounted read/write. Otherwise the database will not start up and cause other issues.
License:
Ensure that LICENSE is valid in every system. Refer to LICENSE ALARM and solution section in this mail.
InfiniDB Logs:
Always ensure that all logs are getting updated in:
/var/log/Calpont/err.log
/var/log/Calpont/warning.log
/var/log/Calpont/snmpd.log
/var/log/Calpont/alarm.log
/var/log/Calpont/crit.log
/var/log/Calpont/debug.log
/var/log/Calpont/info.log
/var/log/Calpont/snmptrapd.log
/var/log/Calpont/uiCommands.log
Query Engine Module:
The QE module consists of two processes:
1. Query Agent - /opt/tms/bin/qe_agent communicates with java backend to provide query support
2. Query Processor - /opt/tms/bin/gnqp communicates with PS (replay mode) and CAE (live mode) to read CAE bins into the database
Monitoring the database
Infinidb database runs following processes when its started (check for command below) : cc getProcessStatus
PrimProc
ExeMgr
DDLProc
DMLProc
/usr/local/Calpont/bin/ProcMon this is the process monitor for the database system
/usr/local/Calpont/bin/ServerMonitor
/usr/local/Calpont/mysql//bin/mysqld_safe
/usr/local/Calpont/mysql/libexec/mysqld
/usr/local/Calpont/sbin/snmptrapd this is optional and can be shutdown
/usr/local/Calpont/bin/controllernode fg
/usr/local/Calpont/bin/workernode DBRM_Worker1 fg
If any of these processes go down, there is probably some issue. Follow the steps mentioned in Restarting Infinidb database.
2. Monitoring BRM state
Execute /usr/local/Calpont/bin/dbrmctl status
Expected output - OK.
If the output is Read Only, do following
/usr/local/Calpont/bin/dbrmctl readwrite
2.
3.
1.
2.
3.
a.
b.
c.
d.
e.
4.
5.
a.
b.
c.
d.
1.
1.
1.
1.
2.
3.
/usr/local/Calpont/bin/dbrmctl reload
Follow the steps mentioned in Restarting Infinidb database
Restarting Infinidb database
cc stopSystem
service infinidb start
If step #2 fails then do following
cd /usr/local/Calpont/bin
./reset_locks
./clearShm
./dbrmctl reload
service infinidb start
cc startSystem
If step #4 fails then do following
service infinidb stop
cc shutdownSystem
/usr/local/Calpont/bin/postConfigure
follow all steps to reconfigure the database (NOTE: This can remove any changes that were made in
/usr/local/Calpont/etc/Calpont.xml)
Once the reconfigure is complete, execute cc startSystem
To check whether infinidb database was successfully restarted, do following
From console execute following
#idbmysql
mysql>create database temp1;
mysql> use temp1;
Create a test table
mysql> CREATE TABLE `test1` (
`f1` char(1) DEFAULT NULL,
`f2` bigint(20) DEFAULT NULL
) ENGINE=InfiniDB;
Query OK, 0 rows affected (1.60 sec)
Drop the test table
mysql> DROP TABLE test1;
Query OK, 0 rows affected (2.93 sec)
Additional information
Whenever Infinidb database is restarted, make sure QE processes (qe_agent and gnqp) are also restarted.
In case Infinidb is not able to recover after following the aforementioned instructions, we may need to re-install the database.
Refer to Release Notes here - for more information http://192.168.0.117/release/N2.5.3/N2.5.3.rc3/rn_2.5.3.rc3.txt
ENSURE THAT ALL PROCESSES ARE ACTIVE
[admin@banda ~]# cc getProcessStatus
getprocessstatus Thu Jun 16 13:59:44 2011
Calpont Process statuses
Process Module Status Last Status Change Process ID
--------------- - - ----- - ----------------- - ------ - - --- - - - -
ProcessMonitor pm1 ACTIVE Fri Apr 29 14:45:34 2011 4022
ProcessManager pm1 ACTIVE Fri Apr 29 14:45:42 2011 4388
SNMPTrapDaemon pm1 ACTIVE Fri Apr 29 14:45:48 2011 4589
DBRMControllerNode pm1 ACTIVE Fri Apr 29 14:45:55 2011 4657
SNMPAgent pm1 ACTIVE Fri Apr 29 14:46:02 2011 4769
ServerMonitor pm1 ACTIVE Fri Apr 29 14:46:06 2011 4780
DBRMWorkerNode pm1 ACTIVE Fri Apr 29 14:46:12 2011 4792
PrimProc pm1 ACTIVE Fri Apr 29 14:46:21 2011 4810
ExeMgr pm1 ACTIVE Fri Apr 29 14:46:23 2011 4937
DDLProc pm1 ACTIVE Fri Apr 29 14:46:28 2011 5312
DMLProc pm1 ACTIVE Fri Apr 29 14:46:32 2011 5481
THIS INDICATES THAT LICENSE IS EXPIRED.

[admin@banda ~]# cc getActiveAlarms


getactivealarms Thu Jun 16 14:00:36 2011
Active Alarm List:
AlarmID = 32
Brief Description = EE_LICENSE_EXPIRED
Alarm Severity = CRITICAL
Time Issued = Sun Mar 6 00:00:00 2011
Reporting Module = pm1
Reporting Process = ProcessManager
Reported Device = calpont-1
To activate the enterprise version you will need to run the following commands on each server once InfiniDB is installed.
1) /usr/local/Calpont/bin/setConfig SystemConfig Flags 75755656
2) cc restartsystem
If there is an issue with the database and you need to run the /usr/local/Calpont/bin/postConfigure command to reinstall the database (on top of
the existing data tables), then you should run the setConfig again and restart db after installation to be doubly sure.

Das könnte Ihnen auch gefallen