Discovering Exalytics in EM13c

In one of my posts I installed and set up EM13c and installed an agent onto the Exalytics system, we will now discover the system in 13c.

Select targets/Systems


Select Add/Exalytics System

Enter the Machine Name, Agent, Platform, Deployment Type, username, Password, IP Address, ILOM Details

Click Next



Click Add Targets

Log onto the ilom


Select a free alert and click edit

In this screen we will enter the details where the agent is running, so that the ilom can send alerts.

Verify the Compute Node ILOM SNMP

  1. Log onto the host running the agent

Log onto the ilom , and see the event log:

Now check in the EM console if we can see the event id.

Clear in cloud control.

Enabling and Diabling BI Publisher in EM13C

So you have installed EM13C, how do you disable and enable the BI Publisher.

Check OMS Status

Enable BI Publisher

Start BI Publisher

Disable BI Publisher

SOACS Timezone

Setting the SOACS timezone

So we have provisioned servers in the cloud but the time is in UTC.


You wanted to use BST, this is how it can be done.

1) Log onto the SOA Server

2) All the timezones you can use can be found in the following /usr/share/zoneinfo –  As root change the target for localtime as below

3) When we reboot, we want this setting to be permanent , so we do the following :


4) Reboot the server

5) Log into EM.




Monitoring Exalytics (linux 5) with EM13C – Part 1

Fresh Install of EM 13C and the challenges of pushing a agent for linux 5 from EM13C.

Oracle Enterprise Manager is an on premise management platform, we decided to investigate the use of 13c and see what benefits we could get by using this to monitor our exalytics system as well as our other Oracle portfolio including premise and cloud applications. There is many blogs on this but I had some interesting challenges that were difficult to resolve that I wanted to share. During this setup, I did reach out to some well-known EM13C experts that I wanted to say thanks to Kellyn – – @DBAKevlar and Philip – – @pbedba.  When 13c came out they did not allow you to push or extract an agent that was lets say that you would need if you have linux 5 running.  It was OK if you already had an agent already installed and upgraded to 13 on the OMS server.  This is where the fun began, In this post I will cover the basics as what was needed to be done to extract a agent and install.  Oracle released a few patches for this in the last 6 weeks to help with this which I will also cover.

We are installing this on windows 8, First thing we do is download the following:

  • 12c Enterprise database
  • Database templates for EM13.
  • EM13

Ensure your account has administrator privileges.

DB12c Install

Start the installer for Oracle 12c Database.

Click next

Select install database software only.

For this we are selecting single instance database installation.

We are installing Enterprise Edition.

Remember the password.

Enter the paths and click next.

We have installed the database.

Unzip the database templates for EM to (This will be the location where you have installed the database software, ensure you unzip the templates to the templates folder.



Run dbca.bat as administrator

Select next

Select advanced mode click next.

If you have saved the templates to the correct location you will see the templates in the above screen.

Enter your database name and click next.

Ensure nothing is selected in screen above and click next.

For this example we are using the same password, note your password.



Select create a new listener, and give it a name and the port you want to use.


Select filesystem,Click next.


In the above screen select the following file, which should be where you extracted your templates.: shpool_12.

Click Next


Click Next

Click Finish


Database Created.

EM13c Install

Select next

Select skip for now, and click next.

As I am installing this on my laptop, I have ignore this error. Still works OK J, I have 8gb memory.


Click Yes

We are doing simple.

Enter your details as well as your host name.


Enter the password you want for your EM, and provide your database connection details.

Select next.

Click Install.

You will see the installation progress.


Downloading Agent Software

Our Exalytics system we need to install the agent, Log into your EM13C., Select Setup/Extensibility/Self Update,


Drill down into the agent software.

Select version

Click Download

At this point I started hitting problems. 13c did not allow you to push to a agent by default, to be able to do this you will need to patch the EM13C. As when you try to export the agent you get an error as below.

Download Patch 22741755 and install as per Read Me, remember on windows ensure you do this as Administrator. Once done also verify it is Installed !!!

Lets try and export the agent on the host again.

Agent Extracted !!! J

Exalytics Configuration

Log onto your ILOM and ensure the SP system identifier is entered.

Log onto your exalytics system

As Root

Agent Install onto exalytics

Create a directory on the Target:

**This is a known BUG (Heartbeat Status : OMS responded illegally [ERROR- Failed to Update Target Type Metadata])

Download Patch

Patch 22581985: agent & 13.1 OMS returns ERROR- Failed to Update Target Type Metadata

Install it and verify it as per previous patch.

We are now ready to Discover the Exalytics system in EM13C.


TimesTen 778: Log write failed because file system is full

TimesTen 778: Log write failed because file system is full

A problem I recently encountered in TimesTen.  So we decided to delete 150gb of data and reload some new data but after finishing the reload and trying to create an index we see the following message:

We then investigate the tterrors.log file and we can see the following:

So what’s happened here?, we know we had enough capacity on this server when we started the delete.

What has happened is that when we decided to remove large amounts of data and reload, this information was written into tt_aggr_store transaction log files, waiting to be checkpointed. Once TimesTen has finished check pointing, these files will be removed. But we have a situation here, our filesystem is full and we need to release some space for the checkpoint to finish, if we log into TimesTen and do ttckpthistory we can see the checkpoint is in progress and at 43% by looking at the 2nd column in from the end (on the in progress checkpoint). If after a few minutes you do ttckpthistory again, this number should rise.


To allow this checkpoint to finish you will have to delete any unnecessary log files that may exist or move them to another file-system, and in the future when reloading – maybe load in smaller batches and keep monitoring the transaction logs and checkpoints.