Skip navigation.


Syndicate content DBASolved
Helping Oracle DBAs solve problems
Updated: 7 hours 26 min ago

Error referenced ‘irman ioracle’ during binary installation

Thu, 2015-07-16 19:27

This week I decided to redo a few of my virtual box machines and build a few new ones for testing. Getting the Oracle Linux 6.6 installed was a breeze; however, when I started to install the Oracle Database 12c binaries I was hitting errors during the linking phase. This had me puzzled for a bit to say the least. I kept getting this error:

After driving myself nuts, I decided to look closer to what is going on. The file listed in the error message contained a reference to ‘irman ioracle’. The actual message was:

So how did I get past this issue? The message is referring to a linking issue of the Oracle binaries. The issue is due to the libjavavm12.a file not being placed in the $ORACLE_HOME/lib. In order to fix this, I had to run:

cp /opt/app/oracle/product/ /opt/app/oracle/product/

Once this was ran, the installation completed without error and other configuration assistants within the binaries were able to complet successfully.


Filed under: Database
Categories: DBA Blogs

Possible Truncation Attack? logged in #em12c nodemanager.log file

Mon, 2015-07-06 08:38

Recently I’ve come across issues with restarting Oracle Enterprise Manager and seeing messages in the nodemanager.log. The message that I’m referring to is (followed by a java trace stack):

<Jul 2, 2015 11:46:11 PM> <WARNING> Uncaught exception in server 
Inbound closed before receiving peer's close_notify: possible truncation attack? 
Inbound closed before receiving peer's close_notify: possible truncation attack?

What is interesting about this message is the panic that may come over a person when they see the word “attack”. The first time I saw this message, I was working on a client site and I was distressed because I was worried about an “attack” on EM. After some investigation, this message is a bit misleading. So, what was the cause of the message?

The “possible truncation attack” is due to the IP address of the host where the OMS runs changed. Here in my test environment, I recently upgraded my wireless router which effected my whole network. The router upgrade changed all the addresses on the network. When OEM was initially installed, the host had an address of after the upgraded the addressed changed to Not a big deal; how to fix though?

In the case of my test lab, I needed to change the /etc/hosts files to ensure that the correct IP address was picked up. In the enterprise, what needs to happen is your local DNS needs to be updated along as the /etc/hosts file. OEM upon start up will look at DNS then /etc/hosts when trying to resolve host to IP resolution. The order of preference can be changed in the /etc/resolv.conf as well.


Filed under: OEM
Categories: DBA Blogs

Create #em12c users fast and easy!

Thu, 2015-06-18 11:57

Over the last few months, I’ve been working a project where I’ve started to dive into EM CLI and the value that EM CLI brings to cutting down on doing things like creating Enterprise Manager users. Hence the reason for this post.

Note: If you haven’t looked into EM CLI yet, I encourage you to do so. A good starting point is here. Plus there is a whole book written on the topic by some friends and guru’s of mine, here.

Creating users in Enterprise Manager 12c is pretty simple as it is. Simply go to Setup -> Security -> Administrators. When you get this screen, then click on either the Create or Create Like buttons.

After clicking Create or Create Like, Enterprise Manger takes you to a five (5) step wizard for creating a user. This wizard allows you to provide details about the user, assign roles, assign target privileges, assign resource privileges and then review what you have done.

Depending on how many users you have to create, this wizard is either an great way of creating user or a slow way for creating users. Using EM CLI, users can be created from the command line very quickly and easily and no need to use the GUI wizard either.. :)

The syntax to create a user from the command line is as follows:

emcli create_user

The beautiful part of EM CLI is that is can be used with any scripting language. Since I like to use PERL, I decided to write a simple script that can be used to create a user from the command line using EM CLI.

#!/usr/bin/perl -w
use strict;
use warnings;

my $oem_home_bin = “$OMS_HOME/bin";
my ($username, $passwd, $email) = @ARGV;
my $pwdchange = ‘false';

if (not defined $username or not defined $passwd or not defined $email)
    print "\nUsage: perl ./ username password email_address\n\n";    

system($oem_home_bin.'/emcli login -username=sysman);
system($oem_home_bin.'/emcli sync');
my $cmd = 'emcli create_user -name='.$username.' -password='.$passwd.' -email='.$email.' -prevent_change_password='.$pwdchange;
#print $cmd."\n";
system($oem_home_bin.'/emcli logout');

Now using this bit of code, I’m able to create users very rapidly using EM CLI with a command like this:

perl ./ <username> <password for user> <email address>

Well, I hope this helps other look at and start using EM CLI when managing their EM environments.


Filed under: EMCLI, OEM
Categories: DBA Blogs

Adding internal targets to #em12c agents manually

Wed, 2015-05-27 09:23

This post is meant to be more of a note for me to refer to later, but it is also good to share knowledge so here you go.

Note: Hostnames are blacked out for a reason. Commands are the same though.

Recently, I just installed an em agent using the silent install method I blogged about earlier (here). After installing the agent, everything was working fine and the agent could upload to the OMS. As I started to look around, within EM, I noticed that the host was not being monitored. I confirmed this by using “emctl config agent listtargets” in $EM_AGENT_HOME/bin.

In most cases, the agent installation, silent or otherwise, will pick up the host and turn the host from unmanaged host to manage host. Not in this case. So how can the host be discovered now?

In order to re-discover the host target on the machine, I needed to run “emctl config agent addInternalTargets”. This forced the agent to go out and rediscover the host and any potential targets on the host. Once it returns to the command prompt, then I ran “emctl config agent listtargets” again to verify that the host is now discovered.


Filed under: OEM
Categories: DBA Blogs

Finding the Oracle Database Appliance Plug-in within #em12c

Wed, 2015-05-06 08:26

The Oracle Database Appliance (ODA) has been around for a few years now. It is a great, compact, and powerful machine for running at two-node Oracle Real Application Cluster (RAC). The adoption of the ODA has been mostly seen in medium sized organizations that need a work horse but cannot afford the sticker price of an Oracle Exadata.

Just like all the appliances that Oracle puts out, there is a need to monitor these appliances from top to bottom. This is achived by using Oracle Enterprise Manager 12c Plug-ins. Recently, Oracle let it be known that the ODA Plug-in has been released; however, from searching online it is not easily found. Hence the reason for this blog post…. :)

To find the ODA Plug-in, you need to basically download it from within the Self-Update area inside of Oracle Enterprise Manager 12c. In order to do this, you need to set you MOS credientials to access MOS.

Using Setup -> My Oracle Support -> Set Credentials

Once your MOS credentials are set, then you can got to the Self-Update page and update the plug-ins for your Oracle Enterprise Manager (Setup -> Extensibility -> Self-Update).

From the Self-Update page, select the Check Update.

After clicking the Check Update button, Oracle Enterprise Manager will kick off a job to update all the plug-ins in the software library. Once the job completes, you can look at the status of the job and see that the Oracle Database Appliance plug-in was downloaded successfully.

Now that the plug-in has been downloaded, you can go back to the Plug-in Page and deploy the plug-in to the agents that are running on the ODA targets (Setup -> Extensibility -> Plug-ins).

Listed under the Engineered Systems plug-ins, you will not see version of the Oracle Database Appliance plug-in.

Now that the plug-in has been downloaded, it can be deployed to the required targets and configured (more on this later, hopefully).


Filed under: OEM
Categories: DBA Blogs

IOUG Collaborate 2015 – #C15LV

Wed, 2015-04-01 19:31

Like many other Oracle professionals and speakers I will be attending IOUG Collaborate 2015 this year in Las Vegas.  I’m not a big fan of Las Vegas, but hey cannot turn down an opportunity to speak, especially when IOUG asked me to do more than one session.  

This year my schedule is going to keep me busy; yet full of good topics that cover both EM12c and GoldenGate.  If you are going to be a Collaborate, come check out my sessions and many others.

My sessions this year:

09:00 am – 03:00 pm – RAC SIG Function (RAC Attack)

10:30 am – Writing to Lead Panel discussion
12:00 pm – Exadata Exachk and EM12c: Keeping up with Exadata                 
17:30 pm – IOUG Data Integration SIG Meeting

11:00 am – Enable Oracle GoldenGate Monitoring for the Masses with EM12c                     

08:00 am – Examine Oracle GoldenGate Trail Files: How and When to use Logdump Utility
10:45 am – Extreme Replication: Performance Tuning Oracle GoldenGate for the Real World

If you are going to be a Collaborate, I look forward to see you there and hopefully in one of my sessions.


Filed under: Database, Golden Gate, OEM
Categories: DBA Blogs