Skip to main content

Install MySQL Enterprise Monitor (MEM)

Install MEM (MySQL Enterprise Monitor) for Linux :
01. Download older version of MEM (3.3,3.4,4.0 etc.) from Metallink patchset.
02. Download latest version of MEM (8.0) from e-delivery.
03. Files for MEM 3.3.0
Start | Stop | Check Status MEM agent on node:
#/mysql/MEM8.0.3/agent/etc/init.d/mysql-monitor-agent start
#/mysql/MEM8.0.3/agent/etc/init.d/mysql-monitor-agent stop
#/mysql/MEM8.0.3/agent/etc/init.d/mysql-monitor-agent status

Install MySQL Service manager on MEM host:
Make sure to install MySQL service manager as a root so that it can start automatically while you re-boot server.

Installation files:
    Install Service Manager - mysqlmonitor-3.3.0.1098-linux-x86_64-installer.bin
    Upgrade Service Manager - mysqlmonitor-3.3.0.1098-linux-x86_64-update-installer.bin

MySQL service manager will install
  • Apache Tomcat: mandatory component. Servlet container and web server which hosts the MySQL Enterprise Service Manager.
  • Java Runtime Environment (JRE): mandatory component. Required by Tomcat.
  • MySQL Server: optional component. Used to store the data from the monitored hosts and instances.
There are two modes available to install MEM service manager:

01. Graphical and
02. Text - shell>./mysqlmonitor-4.0.3.5191-linux-x86-64bit-installer.bin --mode text

There is no text mode available for Windows. Text mode is available for Linux env.

    Default location of installation - /opt/mysql/enterprise/monitor/apache-tomcat
    Default port no. is 18443 for Tomcat .
    To see the host name and port to use, check the configuration_report.txt file.   

Control mysql, tomcat, mysql Service manager:

shell>./mysqlmonitorctl.sh help
./mysqlmonitorctl.sh (start|stop|status|restart)
./mysqlmonitorctl.sh (start|stop|status|restart) mysql
./mysqlmonitorctl.sh (start|stop|status|restart) tomcat

Install MEM agent:
Installation files:

Install MEM Agent - mysqlmonitoragent-3.3.0.1098-linux-x86-64bit-installer.bin
Update MEM Agent - mysqlmonitoragent-3.3.0.1098-linux-x86-64bit-update-installer.bin

Agent use three users :
Admin, General (optional), and Limited (optional). These users are created manually or by the installation and configuration process.
One Agent is installed per host, and the Agent monitors the host and all MySQL instances on it. An Agent may also monitor remote MySQL instances.
Agents automatically detect MySQL instances on a host.
New MySQL instance is added using MySQL Enterprise Monitor UI or from the command line.

Control MEM agent on Linux:

shell> /opt/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent help
shell> ./mysql-monitor-agent {start|stop|restart|status}
shell> /opt/mysql/enterprise/agent/etc/init.d/mysql-monitor-agent start
shell> ./mysql-monitor-agent stop
shell> ./mysql-monitor-agent status
shell> tail /opt/mysql/enterprise/agent/logs/mysql-monitor-agent.log

On startup, the agent sets sql_mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION,NO_AUTO_CREATE_USER on the monitored MySQL instance.
If sql_mode=ONLY_FULL_GROUP_BY, agent queries can fail. The local agent of MySQL Enterprise Service Manager also sets sql_mode=STRICT_TRANS_TABLES,NO_ENGINE_SUBSTITUTION
on the repository.

Troubleshooting agent:
Refer https://dev.mysql.com/doc/mysql-monitor/4.0/en/mem-troubleshooting-agent-start.html

Service Manager Configuration Utility:
/opt/mysql/enterprise/monitor/bin/config.sh
Ref.: https://dev.mysql.com/doc/mysql-monitor/4.0/en/mem-program-reference-server-script-config.html

Agent Configuration utility:
/opt/mysql/enterprise/agent/bin/agent.sh
Ref.: https://dev.mysql.com/doc/mysql-monitor/4.0/en/mem-deployment-config-agent-options.html

Ref.: https://dev.mysql.com/doc/mysql-monitor/4.0/en/mem-introduction-installation-types.html

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

MySQL InnoDB cluster troubleshooting | commands

Cluster Validation: select * from performance_schema.replication_group_members; All members should be online. select instance_name, mysql_server_uuid, addresses from  mysql_innodb_cluster_metadata.instances; All instances should return same value for mysql_server_uuid SELECT @@GTID_EXECUTED; All nodes should return same value Frequently use commands: mysql> SET SQL_LOG_BIN = 0;  mysql> stop group_replication; mysql> set global super_read_only=0; mysql> drop database mysql_innodb_cluster_metadata; mysql> RESET MASTER; mysql> RESET SLAVE ALL; JS > var cluster = dba.getCluster() JS > var cluster = dba.getCluster("<Cluster_name>") JS > var cluster = dba.createCluster('name') JS > cluster.removeInstance('root@<IP_Address>:<Port_No>',{force: true}) JS > cluster.addInstance('root@<IP add>,:<port>') JS > cluster.addInstance('root@ <IP add>,:<port> ') JS > dba.getC...
Post a Comment
Read more

InnoDB cluster Remove Instance Force | Add InnoDB instance

InnoDB cluster environment UUID is different on node: To fix it stop group replication, remove instance (use force if require), add instance back Identify the node which is not in sync: Execute following SQL statement on each node and identify the node has different UUID on all nodes. mysql> select * from mysql_innodb_cluster_metadata.instances; Stop group replication: Stop group replication on the node which does not have same UUID on all nodes. mysql > stop GROUP_REPLICATION; Remove instances from cluster: Remove all secondary node from the cluster and add them back if require. $mysqlsh JS >\c root@<IP_Address>:<Port_No> JS > dba.getCluster().status() JS > dba.getCluster () <Cluster:cluster_name> JS > var cluster = dba.getCluster("cluster_name"); JS >  cluster.removeInstance('root@<IP_Address>:<Port_No>'); If you get "Cluster.removeInstance: Timeout reached waiting......" JS > cluster.removeInstance(...
2 comments
Read more

Oracle E-Business Suite Online Patch Phases executing adop

Following description about Oracle E-Business Suite is high level and from documentation https://docs.oracle.com/cd/E26401_01/doc.122/e22954/T202991T531062.htm#5281339 for in depth and detail description refer it. The online patching cycle phases: Prepare Apply Finalize Cutover Cleanup Prepare phase: Start a new online patching cycle, Prepares the environment for patching. $ adop phase=prepare Apply phase: Applies the specified patches to the environment. Apply one or more patches to the patch edition. $ adop phase=apply patches=123456,789101 workers=8 Finalize phase: Performs any final steps required to make the system ready for cutover. Perform the final patching operations that can be executed while the application is still online. $ adop phase=finalize Cutover phase: Shuts down application tier services, makes the patch edition the new run edition, and then restarts application tier services. This is the only phase that involves a brief ...
Post a Comment
Read more