Oracle 12c Cloud Control Implementationunionsystechnologies.com/downloads/casestudies/Cloud...

UNIONSYS TECHNOLOGIES

Oracle 12c Cloud Control Implementation

Install Oracle Enterprise Manager Cloud Control 12c on Linux

This article describes how-to install Oracle Enterprise Manager Cloud Control 12c (OEM12c) on Linux


Contents

1. OS And Memory Requirements:..................................................................................................... 2

2. Host File Requirements ................................................................................................................... 3

3. Install Oracle 11gR2 RDBMS software .......................................................................................... 3

4. Create OEM Repository database ................................................................................................. ..20

5. Listener and Local Net Service Name configuration ..................................................................... .35

6. Database requirements ................................................................................................................. ...55

7. Install Enterprise Manager Cloud Control 12c ........................................................................... ....58

8. How to Install agents .......................................................................................................................71

9. How to manage 12c Cloud Control..................................................................................................79


1. OS And Memory Requirements:

There are some requirements to meet when preparing OEL 5.7 to run the database and OEM software

correctly.

The installation will take place on Linux with 8GB of memory. Based on the documentation and

experience this is the bare minimum.

Minimum 150 GB Disk is required for implementing 12c Cloud Control

Check the existence of the following lines in file /etc/sysctl.conf:

/etc/sysctl.conf:

kernel.shmmni = 4096

kernel.sem = 250 32000 100 142

fs.file-max = 6815744

fs.aio-max-nr = 3145728

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

Check the existence of the following lines in file /etc/security/limits.conf:

/etc/security/limits.conf:

oracle soft nofile 131072

oracle hard nofile 131072

oracle soft nproc 131072

oracle hard nproc 131072

oracle soft core unlimited

oracle hard core unlimited

oracle soft memlock 50000000

oracle hard memlock 50000000

2. Host File Requirements

Ensure that the host name specified in the /etc/hosts file is unique, and ensure that it maps to the correct

IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page.

The following is the recommended format of the /etc/hosts file:

<ip> <fully_qualified_host_name> <short_host_name>

For example,

192.168.0.205 oem12c.example.com oem12c


3. Install Oracle 11gR2 RDBMS software

We are now ready to continue with the installation of the Oracle 11gR2 RDBMS software so we can

create a repository database. We will use Oracle RDBMS version 11.2.0.3

To install the RDBMS software login as user oracle. Oracle will be the software owner

[oracle@oem12c::/home/oracle]# cd /software/Database/11.2.0.3/database

[oracle@oem12c::/home/oracle]# ./runInstaller

Action:

Deselect I wish to receive security updates via My Oracle Support and click Next.


Action: Confirm by clicking Yes.

Action:

Select Skip software updates and click Next.


Action:

Select Install database software only and click Next.


Action:

Select Single instance database installation and click Next.


Action:

Select the language of your choice and click Next.


Action:

Click button Select Options …


Action:

Only select component Oracle Partitioning and click OK.


Action:

Enterprise Edition and its components are now selected. Click Next.


Action:

Specify the Oracle Base and Software Location. I use the following locations:

Oracle Base /u01/app/oracle

Software Location /u01/app/oracle/product/11.2.0.3/db_000

Click Next.


Action:

Specify the Inventory Directory and oraInventory Group Name.

Click Next.


Action: Specify the Priviliged Operating System Groups for OSDBA and OSOPER.

I use group dba as OS group for both.


Action:

Wait until the Prerequisite Checks are performed.


Action:

Check if all settings are correct. I you are satisfied click Install to start installing the RDBMS software.


Action:

Wait a while until the installation is completed.


Action:

Follow the instructions on the screen by executing the 2 scripts as user root.

root@oem12c::/root

$ /u01/app/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 dba.

The execution of the script is complete.

root@oem12c::/root

$ /u01/app/oracle/product/11.2.0.3/db_000/root.sh

Performing root user operation for Oracle 11g

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /u01/app/oracle/product/11.2.0.3/db_000

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.

Finished product-specific root actions.

After executing the scripts click OK.

Action:

Click Close.


4. Create OEM Repository database

Now we can create a database for the OEM repository. To create the OEM repository database we will

use DBCA utility.

Set the DISPLAY variable and then start DBCA:

[oracle@oem12c::/home/oracle]# export DISPLAY=192.168.0.111:0.0

[oracle@oem12c::/home/oracle]# cd /u01/app/oracle/product/11.2.0.3/db_000/bin

[oracle@oem12c::/home/oracle]# ./dbca

Action:

Click Next.


Action:

Select Create a Database and click Next.


Action:

Select the template General Purpose or Transaction Processing and click Next.


Action:

Specify the Global Database Name and SID for the OEM repository database.

Click Next.


Action:

Because this will be our OEM repository database we don’t need dbconsole. Unfortunately this doesn't

prevent the installation of even just a small part of some sysman objects. I a later step we will remove

these object.

Deselect Configure Enterprise Manager and click Next.


Action:

Set the Database Credentials. In this guide I use the same password for the SYS and SYSTEM accounts.

Click Next.


Action:

If you recall I have specified multiple disks in the kickstart file and the virt-install command. One of these

files is used to create a /u02 filesystem. On this filesystem I want to store my database files.

To store the files on this filesystem select Use Oracle-Managed Files.

Specify the Database Area as /u02/oradata.

Click Next.


Action:

Specify the Fast Recovery Area as /u02/fast_recovery_area.

Select Enable Archiving if you want to enable archiving (useful if you want to create online backups).

Click Next.


Action:

No sample schemas or custom scripts are needed.

Click Next.


Action:

Specify the following memory settings:

Select Custom:

Memory Management: Automatic Shared Memory Management

SGA Size: 2048M

PGA Size: 1024M

It is not recommended to use Automatic Memory Management (by setting parameters memory_target and

memory_max_target).

Click tab Character Sets.


Action:

As Database Character Set select Use Unicode (AL32UTF8).

As National Character Set select UTF8.

Click Next.


Action:

To prevent a warning during installation of OEM12c create Redo Log Groups with a size of at least

300M.

Click Next.


Action:

To start creating the database click Finish.


Action:

View the Database Configuration Summary.

If the configuration is correct click OK.


Action:

Wait a while the database is being created.


Action:

The repository database is now created.

Click Exit


5. Listener and Local Net Service Name configuration

To be able to connect to the repository database using SQL*Net a listener and the local name resolving

must be configured. The easiest way to do this is by using net NETCA utility.

Set the DISPLAY variable and then start NETCA:

[oracle@oem12c::/home/oracle]# export DISPLAY=192.168.0.111:0.0


[oracle@oem12c::/home/oracle]# ./netca

Action:

Select Listener configuration and click Next.


Action:

Click Next.


Action:

Specify the Listener name. I use the default name LISTENER. Click Next.


Action:

Select TCP as protocol for the listener and click Next.


Action:

I use the standard port number of 1521 for the listener.

Click Next.


Action:

Select No and click Next.


Action:

Click Next.


Action:

Select Local Net Service Name configuration and click Next.


Action:

Click Next.


Action:

Specify the Service Name as OEMREP.

Click Next.


Action: Specify TCP as network protocol.

Click Next.


Action:

Specify the Host name where the database is running. I this case it is a local database running on the host

oem12c. Use the standard port number of 1521 for the TCP/IP communication.

Click Next.


Action:

To perform a quick test to check if the net service if configured correctly select Yes, perform a test.

Click Next.


Action:

If the test succeeded click Next. If not, the change the credentials and try again.

Click Next.


Action:

Specify OEMREP ad the Net Service Name and click Next.


Action:

Select No and click Next.


Action:

The net service name configuration is now finished.

Click Next.


Action:

Click Finish.

The previous actions resulted in the creation of 2 files in the $TNS_ADMIN directory, the listener.ora and

tnsnames.ora:

Check is the listener is created successfully and that the databases is registered at the listener:

[oracle@platypus::/home/oracle]# . oraenv

ORACLE_SID = [oracle] ? OEMREP

The Oracle base remains unchanged with value /u01/app/oracle

[oracle@platypus:OEMREP:/home/oracle]# lsnrctl status

LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 16-NOV-2011 20:52:44

Copyright (c) 1991, 2011, Oracle. All rights reserved.

Connecting to

(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=platypus.camoraict.com)(PORT=1521)))

STATUS of the LISTENER

------------------------

Alias LISTENER

Version TNSLSNR for Linux: Version 11.2.0.3.0 - Production

Start Date 16-NOV-2011 20:36:15


Uptime 0 days 0 hr. 16 min. 29 sec

Trace Level off

Security ON: Local OS Authentication

SNMP OFF

Listener Parameter File /u01/app/oracle/admin/network/admin/listener.ora

Listener Log File /u01/app/oracle/diag/tnslsnr/platypus/listener/alert/log.xml

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=platypus.camoraict.com)(PORT=1521)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=EXTPROC1521)))

Services Summary...

Service "OEMREP" has 1 instance(s).

Instance "OEMREP", status READY, has 1 handler(s) for this service...

Service "OEMREPXDB" has 1 instance(s).

Instance "OEMREP", status READY, has 1 handler(s) for this service...

The command completed successfully

Let's try to connect to the database using the Net Service name we have just created:

[oracle@platypus:OEMREP:/home/oracle]# . oraenv

ORACLE_SID = [OEMREP] ? OEMREP

The Oracle base remains unchanged with value /u01/app/oracle

[oracle@platypus:OEMREP:/home/oracle]# sqlplus system@oemrep

SQL*Plus: Release 11.2.0.3.0 Production on Wed Nov 16 20:53:33 2011


Enter password:

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning option

SQL> exit

Disconnected from Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

With the Partitioning option

This looks great! We can now continue with installing Oracle Enterprise Manager Grid Control and its

components.


6. Database requirements

Now that the database is created there are still some requirements to meet for the database before we can

use this database to create the OEM repository in it.

Check that the UNDO- and TEMP tablespaces are autoextensible in the database.

It is recommended to start with a UNDO tablespace of at least 256MB.

SQL> set lines 200

SQL> col tablespace_name form a15

SQL> col file_name form a60

SQL> select tablespace_name, file_name, bytes/1024/1024 as SIZE_MB, autoextensible from

dba_data_files

union

select tablespace_name, file_name, bytes/1024/1024 as SIZE_MB, autoextensible from dba_temp_files;

TABLESPACE_NAME FILE_NAME SIZE_MB AUTOEXTEN

--------------- --------------------------------------------------------- ---------- ---------

SYSAUX /u02/oradata/OEMREP/datafile/o1_mf_sysaux_7d839tmh_.dbf 520 YES

SYSTEM /u02/oradata/OEMREP/datafile/o1_mf_system_7d839tlo_.dbf 710 YES

TEMP /u02/oradata/OEMREP/datafile/o1_mf_temp_7d83dnmd_.tmp 29 YES

UNDOTBS1 /u02/oradata/OEMREP/datafile/o1_mf_undotbs1_7d839tnl_.dbf 75 YES

USERS /u02/oradata/OEMREP/datafile/o1_mf_users_7d839toj_.dbf 5 YES

All datafiles are autoextensible but the datafile of the undo tablespace is too small. Resize this datafile:

SQL> alter database datafile '/u02/oradata/OEMREP/datafile/o1_mf_undotbs1_7d839tnl_.dbf' resize

256M;

There are also some database parameters to be set:

SQL> alter system set sga_target=2G scope=spfile;

SQL> alter system set pga_aggregate_target=1G scope=spfile;

SQL> alter system set shared_pool_size=600m scope=spfile;

SQL> alter system set processes=300 scope=spfile;

SQL> alter system set session_cached_cursors=200 scope=spfile;

SQL> alter system set job_queue_processes=20 scope=spfile;

The databases must now be restarted to activate the modified parameters:

SQL> shutdown immediate

Database closed.

Database dismounted.

ORACLE instance shut down.


SQL> startup

ORACLE instance started.

Total System Global Area 2137886720 bytes

Fixed Size 2230072 bytes

Variable Size 721422536 bytes

Database Buffers 1409286144 bytes

Redo Buffers 4947968 bytes

Database mounted.

Database opened.

Although we explicitly specified NOT to configure the database with Enterprise Manager (which results

in the installation of dbconsole) this doesn't prevent the installation of even just a small part of some

sysman object. Before we can use this databases as a OEM repository database we have to remove these

objects.


[oracle@oem12c::/home/oracle]# ./emca -deconfig dbcontrol db -repos drop

STARTED EMCA at Nov 16, 2011 8:30:01 PM

EM Configuration Assistant, Version 11.2.0.3.0 Production


Enter the following information:

Database SID: OEMREP

Listener port number: 1521

Password for SYS user: xxxxx

Password for SYSMAN user: xxxxx

----------------------------------------------------------------------

WARNING : While repository is dropped the database will be put in quiesce mode.

----------------------------------------------------------------------

Do you wish to continue? [yes(Y)/no(N)]: y

Nov 16, 2011 8:30:15 PM oracle.sysman.emcp.EMConfig perform

INFO: This operation is being logged at

/u01/app/oracle/cfgtoollogs/emca/OEMREP/emca_2011_11_16_20_30_01.log.

Nov 16, 2011 8:30:15 PM oracle.sysman.emcp.util.GeneralUtil initSQLEngineLoacly

WARNING: ORA-28000: the account is locked

Nov 16, 2011 8:30:15 PM oracle.sysman.emcp.ParamsManager checkListenerStatusForDBControl

WARNING: Error initializing SQL connection. SQL operations cannot be performed

Nov 16, 2011 8:30:15 PM oracle.sysman.emcp.EMDBPreConfig performDeconfiguration

WARNING: EM is not configured for this database. No EM-specific actions can be performed. Some of

the possible reasons may be:

1) EM is configured with different hostname then physical host. Set environment variable

ORACLE_HOSTNAME=<hostname> and re-run EMCA script

2) ORACLE_HOSTNAME is set. Unset it and re-run EMCA script

Nov 16, 2011 8:30:15 PM oracle.sysman.emcp.EMReposConfig invoke


INFO: Dropping the EM repository (this may take a while) ...

Nov 16, 2011 8:31:17 PM oracle.sysman.emcp.EMReposConfig invoke

INFO: Repository successfully dropped

Enterprise Manager configuration completed successfully

FINISHED EMCA at Nov 16, 2011 8:31:17 PM


7. Install Enterprise Manager Cloud Control 12c

Now that de repository database is created we can continue with installing the Oracle Enterprise Manager

Cloud Control 12c components.

Enterprise Manager Cloud Control includes the following components:

Oracle Management Agent

Oracle Management Service

Oracle Management Repository

Oracle Management Plug-Ins

Enterprise Manager Cloud Control Console

After downloading the software copy the zipfiles to your server. Unzip the files in the staging area:

[root@oraovs01::/software/EM12]# unzip em12_linux64_disk1of2.zip

[root@oraovs01::/software/EM12]# unzip em12_linux64_disk2of2.zip

Set the DISPLAY variable and then start the installer as the OS user oracle:

[oracle@oem12c::/home/oracle]# export DISPLAY=192.168.0.111:0.0 [oracle@oem12c::/home/oracle]#

cd /software/EM12

[oracle@oem12c::/software/EM12]# ./runInstaller


Action: Optional you can provide your My Oracle Support (MOS) credentials to enable Oracle

Configuration Manager (OCM). If you do not want to enable OCM, then uncheck this option and click

Next.

Action: If you have disable OCM in the previous step click Yes.


Action: If you do not want to apply patched now, select Skip and click Next.


Action: Check the status of the prerequisite checks run by the installation wizard, and verify whether

your environment meets all the minimum requirements for a successful installation.

If some checks result in Warning or Failed status, then investigate and correct the problems before you

proceed with the installation. The screen provides details on why the prerequisites failed and how

you can resolve them. After you correct the problems, return to this screen and click Rerun to check the

prerequisites again.

When all prerequisites are met click Next.


Action:

Select Create a New Enterprise Manager System, and then, select Simple.

Enter the middleware home: /u01/app/oracle/product/12.1.0/middleware.

Click Next.


Action:

Enter an administrator password, which will be used as a common password for configuring OEM12c.

Enter the Database Host Name of the host where the existing database resides, the database's listener

port, its service name, and the SYS user account's password, all created in previous steps.


Action:

The automatic stats gathering job must be disabled. Click Yes and the installer will take care of this.

Action:

Tablespaces will be created by the installer, so what to fix now?

Looks like a unnecessary warning which can be ignored. Click OK.


Action:

After you verify the details, if you are satisfied, click Install to begin the installation process.


Action:

Wait patiently while OEM12c is being installed. This will take more than an hour.


Action:

Follow the instructions on the screen by executing the script as user root.

root@oem12c::/root

$ /u01/app/oracle/product/12.1.0/middleware/oms/allroot.sh

Starting to execute allroot.sh .........

Starting to execute /u01/app/oracle/product/12.1.0/middleware/oms/root.sh ......

Running Oracle 11g root.sh script...

The following environment variables are set as:

ORACLE_OWNER= oracle

ORACLE_HOME= /u01/app/oracle/product/12.1.0/middleware/oms

Enter the full pathname of the local bin directory: [/usr/local/bin]:

The file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying dbhome to /usr/local/bin ...

The file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n)

[n]: y

Copying oraenv to /usr/local/bin ...

The file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n)


[n]: y

Copying coraenv to /usr/local/bin ...

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.sh script.

Now product-specific root actions will be performed.

/etc exist

/u01/app/oracle/product/12.1.0/middleware/oms

Finished execution of /u01/app/oracle/product/12.1.0/middleware/oms/root.sh ......

Starting to execute /u01/app/oracle/product/12.1.0/middleware/agent/core/12.1.0.1.0/root.sh ......


/etc exist

Finished execution of /u01/app/oracle/product/12.1.0/middleware/agent/core/12.1.0.1.0/root.sh ......

Action:

Review the information and click Close to exit the installation wizard.


By default, the following targets get automatically discovered and monitored in the Enterprise Manager

Cloud Control console:

Oracle WebLogic Domain (for example, GCDomain)

Oracle WebLogic AdminServer

Oracle WebLogic Server

Oracle Web Tier

Application deployments, one for the Enterprise Manager Cloud Control console and one for the

platform background services.

Oracle Management Service

Oracle Management Repository

Oracle Management Agent

The host on which you installed Enterprise Manager Cloud Control

Action: The OEM12c login screen is available using a browser with the URL provided in the last screen

from the installation (in this case https://oem12c.example.com:7801/em). Use the credentials of the

sysman user you specified during the installation.

Action:

To continue you must agree with the License Agreement. Click I Agree.


Action:

You are now on the homepage selector screen. Select the desired homepage (I chose Summary) and click

the "Preview" button.

And finally the homepage of OEM12c is presented.


8. Install Cloud Control 12c Agent

Outlined here is the process used to deploy the 12c management agent on a target Linux x86_64 server

using the silent installation method with an agent response file.

In this case the 12c OMS host server is called "Server.Unionsys.com" and the target host where we are

deploying the agent is "Cloud.Oracle.Com"

In the next post we will see how we can deploy or push the 12c management agents to target hosts from

12c Cloud Control itself.

On the OMS host launch the EMCLI client

[oracel@Unionsys Middleware]$ cd oms

[oracle@ Unionsys oms]$ cd bin

[oracle@ Unionsys bin]$ ./emcli login -username=sysman -password=xxx

(./emcli login -username=sysman -password=Weblogic123)

Login successful

Synchronize EMCLI

[oracle@ Unionsys bin]$ ./emcli sync

Synchronized successfully

Check the platforms for which the Management Agent software is available on the OMS host

[oracle@ Unionsys bin]$ ./emcli get_supported_platforms

Getting list of platforms …

Check the logs at /u01/app/oracle/Middleware/oms/bin/agent.log

About to access self-update code path to retrieve the platforms list..

Getting Platforms list …

———————————————–

Version = 12.1.0.1.0

Platform = Linux x86-64

———————————————–

Platforms list displayed successfully.


Download the Management Agent software from Oracle Software Library to a temporary directory

on the OMS host

[oracle@ Unionsys bin]$ ./emcli get_agentimage -destination=/u01/app/oracle/agent_software -

platform=”Linux x86-64″ -version=”12.1.0.1.0″

Platform:Linux x86-64

Destination:/u01/app/oracle/agent_software

=== Partition Detail ===

Space free : 14 GB

Space required : 1 GB

Check the logs at /u01/app/oracle/agent_software/get_agentimage_2012-04-15_22-50-00-PM.log

Setting property ORACLE_HOME to:/u01/app/oracle/Middleware/oms

calling pulloneoffs with

arguments:/u01/app/oracle/Middleware/oms/u01/app/oracle/Middleware/oms/sysman/agent/12.1.0.1.0_A

gentCore_226.zip12.1.0.1.0linux_x64

Check this logs for more information: /u01/app/oracle/Middleware/oms/sysman/prov/agentpush/logs

[oracle@ Unionsys bin]$ cd /u01/app/oracle/agent_software

[oracle@ Unionsys agent_software]$ ls -l

total 230400

-rw-r—– 1 oracle oinstall 235679029 Apr 15 22:50 12.1.0.1.0_AgentCore_226.zip

-rw-r–r– 1 oracle oinstall 1805 Apr 15 22:50 get_agentimage_2012-04-15_22-50-00-PM.log

Transfer the downloaded zip file to the host where we would like to install the 12c management

agent

[oracle@ Unionsys agent_software]$ scp -rp

12.1.0.1.0_AgentCore_226.zip [email protected]:/u01/app/oracle/agent_software

Unzip the file on the target host

Check the directory contents

[oracle@cloud agent_software]$ ls -l

mailto:[email protected]:/u01/app/oracle/agent_software


total 460420

-rw-r—– 1 oracle oinstall 235679029 Apr 16 10:50 12.1.0.1.0_AgentCore_226.zip

-rwxr-xr-x 1 oracle oinstall 4979329 Apr 16 10:50 12.1.0.1.0_PluginsOneoffs_226.zip

-rw-rw-r– 1 oracle oinstall 230621327 Sep 23 2011 agentcoreimage.zip

-rwxrwxr-x 1 oracle oinstall 17150 Sep 23 2011 agentDeploy.sh

-rw-rw-r– 1 oracle oinstall 91 Sep 23 2011 agentimage.properties

-rw-rw-r– 1 oracle oinstall 3856 Sep 23 2011 agent.rsp

drwxr-xr-x 7 oracle oinstall 4096 Apr 16 10:50 plugins

-rwxr-xr-x 1 oracle oinstall 223 Apr 16 10:50 plugins.txt

-rwxr-xr-x 1 oracle oinstall 145976 Sep 23 2011 unzip

Edit the response file agent.rsp

OMS_HOST=”linux-oem-prod.dev.domain”

EM_UPLOAD_PORT=”4902″

AGENT_REGISTRATION_PASSWORD=”xxx”

AGENT_INSTANCE_HOME=”/u01/app/oracle/agent12g/agent_inst”

AGENT_PORT=”3872″

ORACLE_HOSTNAME=”linux-orasql-001-dev.dev.domain”

Run the agent deployment script

[oracle@cloud ~]$ cd /u02/obiee2

[oracle@cloud obiee2]$ mkdir ins_agent

(Create a directory where you want to install agent)

[oracle@ oracle@cloud agent_software]$ ./agentDeploy.sh

AGENT_BASE_DIR=/u02/obiee2/ins_agent

RESPONSE_FILE=/u01/app/oracle/agent_software/agent.rsp

(Instead of giving "agent.rsp" file you can manually specified the path

with agentDeploy.sh utility)


e.g

(./agentDeploy.sh AGENT_BASE_DIR=/u02/obiee2/ins_agent OMS_HOST=cloud.oracle.com

EM_UPLOAD_PORT=4901 AGENT_REGISTRATION_PASSWORD=Weblogic123 -

ignorePrereqs)

Validating the OMS_HOST & EM_UPLOAD_PORT

Executing command : /u01/app/oracle/agent12g/core/12.1.0.1.0/jdk/bin/java -classpath

/u01/app/oracle/agent12g/core/12.1.0.1.0/jlib/agentInstaller.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/

oui/jlib/OraInstaller.jar oracle.sysman.agent.installer.AgentInstaller

/u01/app/oracle/agent12g/core/12.1.0.1.0 /u01/app/oracle/agent_software /u01/app/oracle/agent12g -

prereq

Validating oms host & port with url: http://linux-oem-prod.dev.domain:4902/empbs/genwallet

Validating oms host & port with url: https://linux-oem-prod.dev.domain:4902/empbs/genwallet

Return status:3

Unzipping the agentcoreimage.zip to /u01/app/oracle/agent12g ….

12.1.0.1.0_PluginsOneoffs_226.zip

Executing command : /u01/app/oracle/agent_software/unzip -o

/u01/app/oracle/agent_software/12.1.0.1.0_PluginsOneoffs_226.zip -d /u01/app/oracle/agent12g

Checking the ownership of agent base directory:/u01/app/oracle/agent12g

Checking for proper ownership on the agent base directory.

Checks whether the agent base directory is owned by the agent user oracle and that its parent directory is

owned by either the agent user or root.

….Login name is : oracle & file owner is : oracle

…………Agent Base directory verification completed Successfully.

Ownership check completed.

Executing command : /u01/app/oracle/agent12g/core/12.1.0.1.0/jdk/bin/java -classpath

/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/OraInstaller.jar:/u01/app/oracle/agent12g/core/12.1.0.1.

0/oui/jlib/xmlparserv2.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/srvm.jar:/u01/app/oracle/agen

t12g/core/12.1.0.1.0/oui/jlib/emCfg.jar:/u01/app/oracle/agent12g/core/12.1.0.1.0/jlib/agentInstaller.jar:/u0

1/app/oracle/agent12g/core/12.1.0.1.0/oui/jlib/share.jar oracle.sysman.agent.installer.AgentInstaller

/u01/app/oracle/agent12g/core/12.1.0.1.0 /u01/app/oracle/agent_software /u01/app/oracle/agent12g

AGENT_BASE_DIR=/u01/app/oracle/agent12g AGENT_BASE_DIR=/u01/app/oracle/agent12g

RESPONSE_FILE=/u01/app/oracle/agent_software/agent.rsp

Executing agent install prereqs…


Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runInstaller -ignoreSysPrereqs -

prereqchecker -silent -ignoreSysPrereqs -waitForCompletion -prereqlogloc

/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy -entryPoint

oracle.sysman.top.agent_Complete -detailedExitCodes

PREREQ_CONFIG_LOCATION=/u01/app/oracle/agent12g/core/12.1.0.1.0/prereqs -J-

DORACLE_HOSTNAME=linux-orasql-001-dev.dev.domain

Prereq Logs

Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/prereq<timestamp>.log

Agent install prereqs completed successfully

Cloning the agent home…


clone -forceClone -silent -waitForCompletion -nowait

ORACLE_HOME=/u01/app/oracle/agent12g/core/12.1.0.1.0 -responseFile

/u01/app/oracle/agent_software/agent.rsp AGENT_BASE_DIR=/u01/app/oracle/agent12g

AGENT_BASE_DIR=/u01/app/oracle/agent12g

RESPONSE_FILE=/u01/app/oracle/agent_software/agent.rsp -noconfig

ORACLE_HOME_NAME=agent12g1 -force

Clone Action Logs Location:/u01/app/oraInventory/logs/cloneActions<timestamp>.log

Cloning of agent home completed successfully

Attaching sbin home…


attachHome -waitForCompletion -nowait ORACLE_HOME=/u01/app/oracle/agent12g/sbin

ORACLE_HOME_NAME=sbin12g1 -force

Attach Home Logs

Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/AttachHome<timestamp>.lo

g

Attach home for sbin home completed successfully.

Updating home dependencies…


updateHomeDeps -waitForCompletion

HOME_DEPENDENCY_LIST=”/u01/app/oracle/agent12g/sbin:/u01/app/oracle/agent12g/core/12.1.0.1.

0″ -invPtrLoc /u01/app/oracle/agent12g/core/12.1.0.1.0/oraInst.loc -force

Update Home Dependencies

Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/UpdateHomeDeps<timestam

p>.log

Update home dependency completed successfully.


Performing the agent configuration…

Executing command: /u01/app/oracle/agent12g/core/12.1.0.1.0/oui/bin/runConfig.sh

ORACLE_HOME=/u01/app/oracle/agent12g/core/12.1.0.1.0

RESPONSE_FILE=/u01/app/oracle/agent12g/core/12.1.0.1.0/agent.rsp ACTION=configure

MODE=perform COMPONENT_XML={oracle.sysman.top.agent.11_1_0_1_0.xml} RERUN=true

Configuration Log

Location:/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/cfgfw/CfmLogger<timestamp>.log

Agent Configuration completed successfully

The following configuration scripts need to be executed as the “root” user.

#!/bin/sh

#Root script to run

/u01/app/oracle/agent12g/core/12.1.0.1.0/root.sh

To execute the configuration scripts:

1. Open a terminal window

2. Log in as “root”

3. Run the scripts

Agent Deployment Successful.

Agent deployment log location:

/u01/app/oracle/agent12g/core/12.1.0.1.0/cfgtoollogs/agentDeploy/agentDeploy_<timestamp>.log

Agent deployment completed successfully.

Run the root.sh script

[root@cloud ~]# /u01/app/oracle/agent12g/core/12.1.0.1.0/root.sh


/etc exist


Check the status of the agent on the target host where it has been deployed

[oracle@ oracle@cloud oracle]$ pwd


/u01/app/oracle

[oracle@ cloud oracle]$ cd agent12g/

[oracle@cloud agent12g]$ cd core

[oracle@cloud core]$ cd 12.1.0.1.0/bin

[oracle@cloud bin]$ ./emctl status agent

Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0

Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.

—————————————————————

Agent Version : 12.1.0.1.0

OMS Version : 12.1.0.1.0

Protocol Version : 12.1.0.1.0

Agent Home : /u01/app/oracle/agent12g/agent_inst

Agent Binaries : /u01/app/oracle/agent12g/core/12.1.0.1.0

Agent Process ID : 2678

Parent Process ID : 2631

Agent URL : https://linux-orasql-001-dev.dev.domain:3872/emd/main/

Repository URL : https://linux-oem-prod.dev.domain:4902/empbs/upload

Started at : 2012-04-16 11:20:59

Started by user : oracle

Last Reload : (none)

Last successful upload : 2012-04-16 11:31:33

Last attempted upload : 2012-04-16 11:31:33

Total Megabytes of XML files uploaded so far : 0.02

Number of XML files pending upload : 0

Size of XML files pending upload(MB) : 0


Available disk space on upload filesystem : 45.31%

Collection Status : Collections enabled

Last attempted heartbeat to OMS : 2012-04-16 11:32:06

Last successful heartbeat to OMS : 2012-04-16 11:32:06

—————————————————————

Agent is Running and Ready


9. How To Manage Cloud Control 12c

After successfully done installation of 12c Cloud Control we will see how to manage and administrate it.

Set The Environment :-

[oracle@cloud ]$vi .bash_profile

export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1

export OMS_HOME=/u01/app/oracle/Middleware/oms

export AGENT_HOME=/u01/app/oracle/Middleware/agent/core/12.1.0.1.0

Start/Stop sequence Of Cloud Control :-

Stop sequence:-

[obiee2@urac2 root]$ cd /u02/obiee2/ins_agent/core/12.1.0.3.0/bin/

[obiee2@urac2 bin]$ ./emctl stop agent

[oracle@cloud bin]$ ./emctl stop oms -all

SQL> shut immediate (Database Stop )

Start Sequence:-

SQL> startup ( Database Start )

[oracle@cloud ]$ cd $OMS_HOME/bin

[oracle@cloud bin]$ ./emctl start oms

[oracle@cloud ]$ cd $AGENT_HOME/bin

[obiee2@urac2 bin]$ ./emctl start agent

Oracle 12c Cloud Control Implementationunionsystechnologies.com/downloads/casestudies/Cloud...

Documents

Transcript of Oracle 12c Cloud Control Implementationunionsystechnologies.com/downloads/casestudies/Cloud...