Today I'm going to complete the installation procedure of Oracle 11.2.0.2
Due to problems with the web site that is hosting the blog, I can't attach the images of the runInstaller process.
However, following you'll find all the necessary steps and what's more lots of comments.
1) As Grid user start the runInstaller command.
2) From the graphycal interface choose to install a single instance.
3) Then choose the language, If I were you I would choose English !!
4) Now you have to create at least two diskgroups (ORADATA & ORAFRA). The diskgroup ORADATA is going to be used for the data instead the diskgroup ORAFRA for the Flash Recovery Area.
5) The graphycal interface now is asking to set the password of the ASM instance.
6) You have to assign the role of the ASM instance (ASM dba, ASM operator) with the groups of the linux server. Afterward choose the ORACLE_HOME and ORACLE_BASE path.
7) The runInstaller process is now asking to execute the "orainstRoot.sh" plus "root.sh" files as root user.
[root@OracleVm05 oraInventory]# ./orainstRoot.sh
Changing permissions of /u01/app/oraInventory.
Adding read,write permissions for group.
Removing read,write,execute permissions for world.
Changing groupname of /u01/app/oraInventory to oinstall.
The execution of the script is complete.
[root@OracleVm05 grid]# ./root.sh
Running Oracle 11g root script...
The following environment variables are set as:
ORACLE_OWNER= grid
ORACLE_HOME= /u01/app/grid/product/11.2.0/grid
Enter the full pathname of the local bin directory: [/usr/local/bin]:
Copying dbhome to /usr/local/bin ...
Copying oraenv to /usr/local/bin ...
Copying coraenv to /usr/local/bin ...
Creating /etc/oratab file...
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Using configuration parameter file: /u01/app/grid/product/11.2.0/grid/crs/install/crsconfig_params
Creating trace directory
LOCAL ADD MODE
Creating OCR keys for user 'grid', privgrp 'oinstall'..
Operation successful.
LOCAL ONLY MODE
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
CRS-4664: Node oraclevm05 successfully pinned.
Adding daemon to inittab
ACFS-9300: ADVM/ACFS distribution files found.
ACFS-9307: Installing requested ADVM/ACFS software.
ACFS-9308: Loading installed ADVM/ACFS drivers.
ACFS-9321: Creating udev for ADVM/ACFS.
ACFS-9323: Creating module dependencies - this may take some time.
ACFS-9327: Verifying ADVM/ACFS devices.
ACFS-9309: ADVM/ACFS installation correctness verified.
oraclevm05 2013/12/18 11:31:21 /u01/app/grid/product/11.2.0/grid/cdata/oraclevm05/backup_20131218_113121.olr
Successfully configured Oracle Grid Infrastructure for a Standalone Server
We have just completed the installation process of the ASM instance.
Let's start to install the Oracle binary, shall we ?
1) As Oracle user start the runInstaller command.
2) From the graphycal interface choose to install only the binary.
3) Then choose the version and the language of the database binary and what's more assign the ORACLE_HOME and ORACLE_BASE directory path.
4) You have to assign the role of the database instance (dba,oper) with the group of the linux server.
5) The runInstaller process is now asking to execute the "root.sh" script:
[root@OracleVm05 dbhome_1]# ./root.sh
Running Oracle 11g root script...
The following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /u01/app/oracle/product/11.2.0/dbhome_1
Enter the full pathname of the local bin directory: [/usr/local/bin]:
The contents of "dbhome" have not changed. No need to overwrite.
The contents of "oraenv" have not changed. No need to overwrite.
The contents of "coraenv" have not changed. No need to overwrite.
Entries will be added to the /etc/oratab file as needed by
Database Configuration Assistant when a database is created
Finished running generic part of root script.
Now product-specific root actions will be performed.
Finished product-specific root actions.
We have just completed the installation process of the database binary.
Let's start to create a sample database, shall we ?
1) As Oracle user start the "dbca" command.
2) Choose "create a database" with the general purpose template plus an instance name and a password.
3) Select the ASM instance as a common location for all datafiles (ORADATA diskgroup).
4) Select the ASM instance ( ORAFRA diskgroup) for the archive log files.
5) Lunch the installer process.
We have just completed the installation process of the database.
See you soon.
Byeeee
Friday, 20 December 2013
Wednesday, 18 December 2013
How to Install Oracle 11.2.0.2 on Linux - Part 1
Today I 'm going to look into the steps that are necessary to complete the installation of Oracle 11.2.0.2 database on a Virtual envirnment Vmware ESX.
I decided to split this procedure in two posts.
In the first post you'll find the steps necessary to configure the linux host.
In the next post you are going to find the steps necessary to complete the procedure.
SERVER : RedHat 5.4
Oracle: 11.2.0.2
1) Minimum Hardware Requirements
Memory requirements:
– 1 GB for the database instance with Oracle Enterprise
Manager Database Control
– 1.5 GB for the ASM instance and Oracle Restart
• Disk space requirements:
– 3 GB of swap space (based on 2 GB RAM)
– 1 GB of disk space in the /tmp directory
– 3.8 GB for the Oracle Database software
– 4.5 GB for the Grid Infrastructure software
– 1.7 GB for the preconfigured database (optional)
– 3.4 gb for the fast recovery area (optional)
2) Required Rpms
As root :
cd /mnt/Rh54
cp -r packages /download/
Install createrepo :
rpm -ivh createrepo-0.9.9-17.el6.noarch.rpm
and run
createrepo /download
chmod -R o-w+r /download
Create a repository configuration file, e.g. /etc/yum.repos.d/myrepo.repo containing :
[local]
name=My Repo
baseurl=file:///download
enabled=1
gpgcheck=0
NB: Be sure to remove all file file.repo from the directory /etc/yum.repos.d.
Install packages :
yum install compat-libstdc*
yum install elfutils-libelf*
yum install elfutils-libelf-devel*
yum install gcc*
yum install glibc*
yum install glibc-common*
yum install glibc-devel*
yum install glibc-headersglibc-headers*
yum install ksh*
yum install libaio*
yum install libgcc*
yum install libstdc*
yum install libstdc++-deve*
yum install make*
yum install sysstat*
yum install unixodbc*
yum install unixODBC-devel*
Install ASMLIb rpm
As root :
[root@oraclevm05 asmlibrh5.4]# rpm -ivh oracleasm-support-2.1.8-1.el5.x86_64.rpm
[root@oraclevm05 asmlibrh5.4]# rpm -ivh oracleasm-2.6.18-164.el5-2.0.5-1.el5.x86_64.rpm
[root@OracleVm05 AsmLibRH5.4]# rpm -ivh oracleasmlib-2.0.4-1.el5.x86_64.rpm
3) Modify the kernel adding the following lines :
As root :
modify your kernel settings in /etc/sysctl.conf
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
kernel.shmmni = 4096
kernel.shmmax = 68719476736
kernel.sem = 250 32000 100 128
fs.file-max = 6815744
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
Reload kernel parameter : sysctl –p
4) Modify file /etc/pam.d/login file
As root :
Comments :
#session required pam_selinux.so close
by default, rhel 5 x86_64 linux is installed with selinux as "enforcing".
This is fine for the 11gR2 installation process. However, to subsequently run "sqlplus",
switch SELinux to the "Permissive" mode. See NOTE 454196.1, "./sqlplus: error on libnnz11.so: c
annot restore segment prot after reloc" for more details.
Add the following :
session required pam_limits.so
5) Create groups and users
As root :
groupadd -g 1000 oinstall
groupadd -g 1200 dba
useradd -u 1100 -g oinstall -G dba grid
useradd -u 1101 -g oinstall -G dba oracle
mkdir -p /u01/app/grid
chown -R grid:oinstall /u01
mkdir /u01/app/oracle
chown oracle:oinstall /u01/app/oracle
chmod -R 775 /u01/
6) Change the password of oracle & grid
Come root :
passwd oracle
passwd grid
7) Modify the file .bash_profile
Oracle
ulimit -u 16384 -n 65536
export ORACLE_BASE=/u01/app/oracle
#export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH:$HOME/bin
Grid
ulimit -u 16384 -n 65536
export ORACLE_BASE=/u01/app/grid
#export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH:$HOME/bin
export ORACLE_SID=+ASM
8) Configure asmlib
As root :
/etc/init.d/oracleasm configure
[root@OracleVm03 /]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: grid
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
initializing the oracle asmlib driver: [ ok ]
Scanning the system for Oracle ASMLib disks: [ OK ]
9 ) From the ESX console add the following disks (ORADATA e ORAFRA).
11) From the linux server execute the following commands:
[root@OracleVm05 ~]# fdisk -l
Disk /dev/sda: 85.8 GB, 85899345920 bytes
255 heads, 63 sectors/track, 10443 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 10443 83778975 8e Linux LVM
Disk /dev/sdb: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdc doesn't contain a valid partition table
[root@OracleVm05 ~]# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabelBuilding a new DOS disklabel. Changes will remain in memory only,until you decide to write them. After that, of course, the previous content won't be recoverable.
The number of cylinders for this disk is set to 6527.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-6527, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-6527, default 6527):
Using default value 6527
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
[root@OracleVm05 ~]# fdisk /dev/sdc
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 6527.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-6527, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-6527, default 6527):
Using default value 6527
Command (m for help): w
The partition table has been altered!
calling ioctl() to re-read partition table.
12) Create ASMlib disk :
As root :
/etc/init.d/oracleasm createdisk ORADATA1 /dev/sdb1
/etc/init.d/oracleasm createdisk ORAFRA1 /dev/sdc1
[root@oraclevm05 ~]# /etc/init.d/oracleasm listdisks
ORADATA1
ORAFRA1
We have just completed the first part of the procedure. Now we are ready to start the installation of oracle and grid binary but for now that's all !
See you in my next blog.
Byeeee
I decided to split this procedure in two posts.
In the first post you'll find the steps necessary to configure the linux host.
In the next post you are going to find the steps necessary to complete the procedure.
SERVER : RedHat 5.4
Oracle: 11.2.0.2
1) Minimum Hardware Requirements
Memory requirements:
– 1 GB for the database instance with Oracle Enterprise
Manager Database Control
– 1.5 GB for the ASM instance and Oracle Restart
• Disk space requirements:
– 3 GB of swap space (based on 2 GB RAM)
– 1 GB of disk space in the /tmp directory
– 3.8 GB for the Oracle Database software
– 4.5 GB for the Grid Infrastructure software
– 1.7 GB for the preconfigured database (optional)
– 3.4 gb for the fast recovery area (optional)
2) Required Rpms
As root :
cd /mnt/Rh54
cp -r packages /download/
Install createrepo :
rpm -ivh createrepo-0.9.9-17.el6.noarch.rpm
and run
createrepo /download
chmod -R o-w+r /download
Create a repository configuration file, e.g. /etc/yum.repos.d/myrepo.repo containing :
[local]
name=My Repo
baseurl=file:///download
enabled=1
gpgcheck=0
NB: Be sure to remove all file file.repo from the directory /etc/yum.repos.d.
Install packages :
yum install compat-libstdc*
yum install elfutils-libelf*
yum install elfutils-libelf-devel*
yum install gcc*
yum install glibc*
yum install glibc-common*
yum install glibc-devel*
yum install glibc-headersglibc-headers*
yum install ksh*
yum install libaio*
yum install libgcc*
yum install libstdc*
yum install libstdc++-deve*
yum install make*
yum install sysstat*
yum install unixodbc*
yum install unixODBC-devel*
Install ASMLIb rpm
As root :
[root@oraclevm05 asmlibrh5.4]# rpm -ivh oracleasm-support-2.1.8-1.el5.x86_64.rpm
[root@oraclevm05 asmlibrh5.4]# rpm -ivh oracleasm-2.6.18-164.el5-2.0.5-1.el5.x86_64.rpm
[root@OracleVm05 AsmLibRH5.4]# rpm -ivh oracleasmlib-2.0.4-1.el5.x86_64.rpm
3) Modify the kernel adding the following lines :
As root :
modify your kernel settings in /etc/sysctl.conf
kernel.shmall = 4294967296
kernel.shmmax = 68719476736
kernel.shmmni = 4096
kernel.shmmax = 68719476736
kernel.sem = 250 32000 100 128
fs.file-max = 6815744
fs.aio-max-nr = 1048576
net.ipv4.ip_local_port_range = 9000 65500
net.core.rmem_default = 262144
net.core.rmem_max = 4194304
net.core.wmem_default = 262144
net.core.wmem_max = 1048576
Reload kernel parameter : sysctl –p
4) Modify file /etc/pam.d/login file
As root :
Comments :
#session required pam_selinux.so close
by default, rhel 5 x86_64 linux is installed with selinux as "enforcing".
This is fine for the 11gR2 installation process. However, to subsequently run "sqlplus",
switch SELinux to the "Permissive" mode. See NOTE 454196.1, "./sqlplus: error on libnnz11.so: c
annot restore segment prot after reloc" for more details.
Add the following :
session required pam_limits.so
5) Create groups and users
As root :
groupadd -g 1000 oinstall
groupadd -g 1200 dba
useradd -u 1100 -g oinstall -G dba grid
useradd -u 1101 -g oinstall -G dba oracle
mkdir -p /u01/app/grid
chown -R grid:oinstall /u01
mkdir /u01/app/oracle
chown oracle:oinstall /u01/app/oracle
chmod -R 775 /u01/
6) Change the password of oracle & grid
Come root :
passwd oracle
passwd grid
7) Modify the file .bash_profile
Oracle
ulimit -u 16384 -n 65536
export ORACLE_BASE=/u01/app/oracle
#export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH:$HOME/bin
Grid
ulimit -u 16384 -n 65536
export ORACLE_BASE=/u01/app/grid
#export ORACLE_HOME=$ORACLE_BASE/product/11.2.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH:$HOME/bin
export ORACLE_SID=+ASM
8) Configure asmlib
As root :
/etc/init.d/oracleasm configure
[root@OracleVm03 /]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting <ENTER> without typing an
answer will keep that current value. Ctrl-C will abort.
Default user to own the driver interface []: grid
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Scan for Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: done
initializing the oracle asmlib driver: [ ok ]
Scanning the system for Oracle ASMLib disks: [ OK ]
9 ) From the ESX console add the following disks (ORADATA e ORAFRA).
11) From the linux server execute the following commands:
[root@OracleVm05 ~]# fdisk -l
Disk /dev/sda: 85.8 GB, 85899345920 bytes
255 heads, 63 sectors/track, 10443 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104391 83 Linux
/dev/sda2 14 10443 83778975 8e Linux LVM
Disk /dev/sdb: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdb doesn't contain a valid partition table
Disk /dev/sdc: 53.6 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sdc doesn't contain a valid partition table
[root@OracleVm05 ~]# fdisk /dev/sdb
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabelBuilding a new DOS disklabel. Changes will remain in memory only,until you decide to write them. After that, of course, the previous content won't be recoverable.
The number of cylinders for this disk is set to 6527.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-6527, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-6527, default 6527):
Using default value 6527
Command (m for help): w
The partition table has been altered!
Calling ioctl() to re-read partition table.
Syncing disks.
[root@OracleVm05 ~]# fdisk /dev/sdc
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel. Changes will remain in memory only,
until you decide to write them. After that, of course, the previous
content won't be recoverable.
The number of cylinders for this disk is set to 6527.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Partition number (1-4): 1
First cylinder (1-6527, default 1):
Using default value 1
Last cylinder or +size or +sizeM or +sizeK (1-6527, default 6527):
Using default value 6527
Command (m for help): w
The partition table has been altered!
calling ioctl() to re-read partition table.
12) Create ASMlib disk :
As root :
/etc/init.d/oracleasm createdisk ORADATA1 /dev/sdb1
/etc/init.d/oracleasm createdisk ORAFRA1 /dev/sdc1
[root@oraclevm05 ~]# /etc/init.d/oracleasm listdisks
ORADATA1
ORAFRA1
We have just completed the first part of the procedure. Now we are ready to start the installation of oracle and grid binary but for now that's all !
See you in my next blog.
Byeeee
Friday, 6 December 2013
MySQL Enterprise Service Manager
Since Oracle bought MySQL lots of new products have been released and "MySQL Enterprise Service Manager" is one of these.
There is a license to pay if you decide to use in a production environment. However, there is also a trial period of 30 days too.
Let's try it out, shall we ?
The binary that is necessary to install is : mysqlmonitor-2.3.13.2193-linux-x86_64-installer.bin and is available on the following link "http://dev.mysql.com/downloads/"
A completed MySQL database installation is also necessary before installing the "Enterprise Service Manager", see the November's blog at "http://alessiodba.blogspot.it/2013/11/mysql-56-e-oracle-linux-64.html" for further information.
Keep in mind that "MySQL Enterprise Database" also requires a license but a trial period exists too.
Let's start, shall we ?
1) Create the em_agent user in the MySQL database. This user is going to be used during the installation of the "MySQL Enterprise Service Manager"
MSQL>grant all on *.* to 'em_agent'@'127.0.0.1' identified by 'pwd';
MSQL>grant all on *.* to 'em_agent'@'localhost' identified by 'pwd';
Be careful ! Since I haven't got time right now I won't look the correct grant up in the reference manual but don't do so in a production environment !
2) Execute the command : mysqlmonitor-2.3.13.2193-linux-x86_64-installer.bin
Following you'll find the output of the command and what's more all the answers of the prompt.
[root@SERVER_TEST] > ./mysqlmonitor-2.3.13.2193-linux-x86_64-installer.bin
Language Selection
Please select the installation language
[1] English - English
[2] Japanese - æ¥æ¬èª
Please choose an option [1] : 1
Info: During the installation process you will be asked to enter usernames and
passwords for various pieces of the Enterprise Monitor. Please be sure to make
note of these in a secure location so you can recover them in case they are
forgotten.
Press [Enter] to continue :
----------------------------------------------------------------------------
Welcome to the setup wizard for the MySQL Enterprise Monitor
----------------------------------------------------------------------------
Please specify the directory where the MySQL Enterprise Monitor will be
installed
Installation directory [/opt/mysql/enterprise/monitor]:
----------------------------------------------------------------------------
Tomcat Server Options
Please specify the following parameters for the bundled Tomcat Server
Tomcat Server Port [18080]:
Tomcat Shutdown Port [18005]:
Tomcat SSL Port [18443]:
Is SSL support required? [y/N]: N
----------------------------------------------------------------------------
Database Installation
Please select which database configuration you wish to use
[1] I wish to use the bundled MySQL database
[2] I wish to use an existing MySQL database *
Please choose an option [1] : 2
* Please note that the Enterprise Monitor requires a specific version of the
MySQL server for its own data repository in order to operate correctly. We will
validate the version of your existing server during the installation. See the
documentation for details based on the version of the Enterprise Monitor you are
installing.
Visit the following URL for more information:
http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-server-install-generic.html
----------------------------------------------------------------------------
Repository Configuration
Please specify the following parameters for the existing MySQL server
Repository Username [service_manager]: em_agent
Password :xxxx
Re-enter :xxxx
MySQL Hostname or IP address [127.0.0.1]:
MySQL Database Port [3306]:
Use SSL when connecting to the database [y/N]: N----------------------------------------------------------------------------
Configuration Report
You have not installed the MySQL Enterprise Monitor as the root user. Therefore
it could not be configured to auto-start on reboot. See the Installation section
of the MySQL Enterprise Monitor documentation for instructions on how to do this
manually.
Press [Enter] to continue :
----------------------------------------------------------------------------
Setup is now ready to install MySQL Enterprise Monitor on your computer.
Do you want to continue? [Y/n]: Y
----------------------------------------------------------------------------
Please wait while Setup installs MySQL Enterprise Monitor on your computer.
Installing
0% ______________ 50% ______________ 100%
#########################################
----------------------------------------------------------------------------
Completed installing files
Setup has completed installing the MySQL Enterprise Monitor files on your
computer.
Uninstalling the MySQL Enterprise Monitor files can be done by invoking:
/opt/mysql/enterprise/monitor/uninstall
To complete the installation, launch the MySQL Enterprise Dashboard and complete
the initial setup. Refer to the readme file for additional information and a
list of known issues.
Press [Enter] to continue :
----------------------------------------------------------------------------
Setup has finished installing MySQL Enterprise Monitor on your computer.
View Readme File [Y/n]: n
Info: To configure the MySQL Enterprise Monitor please visit the following page:
http://localhost:18080
Press [Enter] to continue :
3) A web service will be started and it'll be available at the following link :"http://localhost:18080"
4) Using the web page of the previous link create a new user "em_dba". This user will be used to access the EM console.
That's all.
Following you'll find other handy commands :
1) To start and stop EM console : /opt/mysql/enterprise/monitor/mysqlmonitorctl.sh [stop|start]
2) To obtain the status of the EM console : /opt/mysql/enterprise/monitor/mysqlmonitorctl.sh status
MySQL Enterprise MySQL is running
MySQL Enterprise Tomcat is running
3) To debug the EM console :
/opt/mysql/enterprise/monitor/apache-tomcat/logs/mysql-monitor.log
/opt/mysql/enterprise/monitor/configuration_report.txt
Pretty soon I'll tell you how to install the MySQL agent so keep in touch with the blog.
See you soon !
Byee
There is a license to pay if you decide to use in a production environment. However, there is also a trial period of 30 days too.
Let's try it out, shall we ?
The binary that is necessary to install is : mysqlmonitor-2.3.13.2193-linux-x86_64-installer.bin and is available on the following link "http://dev.mysql.com/downloads/"
A completed MySQL database installation is also necessary before installing the "Enterprise Service Manager", see the November's blog at "http://alessiodba.blogspot.it/2013/11/mysql-56-e-oracle-linux-64.html" for further information.
Keep in mind that "MySQL Enterprise Database" also requires a license but a trial period exists too.
Let's start, shall we ?
1) Create the em_agent user in the MySQL database. This user is going to be used during the installation of the "MySQL Enterprise Service Manager"
MSQL>grant all on *.* to 'em_agent'@'127.0.0.1' identified by 'pwd';
MSQL>grant all on *.* to 'em_agent'@'localhost' identified by 'pwd';
Be careful ! Since I haven't got time right now I won't look the correct grant up in the reference manual but don't do so in a production environment !
2) Execute the command : mysqlmonitor-2.3.13.2193-linux-x86_64-installer.bin
Following you'll find the output of the command and what's more all the answers of the prompt.
[root@SERVER_TEST] > ./mysqlmonitor-2.3.13.2193-linux-x86_64-installer.bin
Language Selection
Please select the installation language
[1] English - English
[2] Japanese - æ¥æ¬èª
Please choose an option [1] : 1
Info: During the installation process you will be asked to enter usernames and
passwords for various pieces of the Enterprise Monitor. Please be sure to make
note of these in a secure location so you can recover them in case they are
forgotten.
Press [Enter] to continue :
----------------------------------------------------------------------------
Welcome to the setup wizard for the MySQL Enterprise Monitor
----------------------------------------------------------------------------
Please specify the directory where the MySQL Enterprise Monitor will be
installed
Installation directory [/opt/mysql/enterprise/monitor]:
----------------------------------------------------------------------------
Tomcat Server Options
Please specify the following parameters for the bundled Tomcat Server
Tomcat Server Port [18080]:
Tomcat Shutdown Port [18005]:
Tomcat SSL Port [18443]:
Is SSL support required? [y/N]: N
----------------------------------------------------------------------------
Database Installation
Please select which database configuration you wish to use
[1] I wish to use the bundled MySQL database
[2] I wish to use an existing MySQL database *
Please choose an option [1] : 2
* Please note that the Enterprise Monitor requires a specific version of the
MySQL server for its own data repository in order to operate correctly. We will
validate the version of your existing server during the installation. See the
documentation for details based on the version of the Enterprise Monitor you are
installing.
Visit the following URL for more information:
http://dev.mysql.com/doc/mysql-monitor/2.3/en/mem-server-install-generic.html
----------------------------------------------------------------------------
Repository Configuration
Please specify the following parameters for the existing MySQL server
Repository Username [service_manager]: em_agent
Password :xxxx
Re-enter :xxxx
MySQL Hostname or IP address [127.0.0.1]:
MySQL Database Port [3306]:
Use SSL when connecting to the database [y/N]: N----------------------------------------------------------------------------
Configuration Report
You have not installed the MySQL Enterprise Monitor as the root user. Therefore
it could not be configured to auto-start on reboot. See the Installation section
of the MySQL Enterprise Monitor documentation for instructions on how to do this
manually.
Press [Enter] to continue :
----------------------------------------------------------------------------
Setup is now ready to install MySQL Enterprise Monitor on your computer.
Do you want to continue? [Y/n]: Y
----------------------------------------------------------------------------
Please wait while Setup installs MySQL Enterprise Monitor on your computer.
Installing
0% ______________ 50% ______________ 100%
#########################################
----------------------------------------------------------------------------
Completed installing files
Setup has completed installing the MySQL Enterprise Monitor files on your
computer.
Uninstalling the MySQL Enterprise Monitor files can be done by invoking:
/opt/mysql/enterprise/monitor/uninstall
To complete the installation, launch the MySQL Enterprise Dashboard and complete
the initial setup. Refer to the readme file for additional information and a
list of known issues.
Press [Enter] to continue :
----------------------------------------------------------------------------
Setup has finished installing MySQL Enterprise Monitor on your computer.
View Readme File [Y/n]: n
Info: To configure the MySQL Enterprise Monitor please visit the following page:
http://localhost:18080
Press [Enter] to continue :
3) A web service will be started and it'll be available at the following link :"http://localhost:18080"
4) Using the web page of the previous link create a new user "em_dba". This user will be used to access the EM console.
That's all.
Following you'll find other handy commands :
1) To start and stop EM console : /opt/mysql/enterprise/monitor/mysqlmonitorctl.sh [stop|start]
2) To obtain the status of the EM console : /opt/mysql/enterprise/monitor/mysqlmonitorctl.sh status
MySQL Enterprise MySQL is running
MySQL Enterprise Tomcat is running
3) To debug the EM console :
/opt/mysql/enterprise/monitor/apache-tomcat/logs/mysql-monitor.log
/opt/mysql/enterprise/monitor/configuration_report.txt
Pretty soon I'll tell you how to install the MySQL agent so keep in touch with the blog.
See you soon !
Byee
Subscribe to:
Comments (Atom)