One of my friend told me that they used to have Oracle Enterprise Manager Grid Control 10g and deployed its agents to some database servers but now they removed Grid Control and want to use Oracle Enterprise Manager Database Console. Usually people ask the opposite question

Anyway, in this blog post, I’ll describe how to manually remove Enterprise Manager Grid/Cloud Control Agent and then enable Enterprise Manager Database Control on the target system. First we need to stop the agent:

If your Cloud Control is up, we need to remove agent. Login as oracle user and run the following commands:

If you have Grid Control 10g/11g, then login to the repository database as SYSMAN and execute the following:

Read More

In case, your target systems have no support for SSH, you can use agentDeploy script to deploy Management Agents. To be able to use this method, you need to create a user for management agent and create required directories and give permission to the Management agent user.

Let’s say we’ll create a group named “oinstall” and a user named “oracle” belongs to this group, and install the agent software to “/u01/agent”. Login as root user and issue the following commands:

Of course, I assume that you don’t have oracle user and oinstall group, and there’s no directory named “/u01/agent”. Instead of creating new user, group and directory, you can use an existing user, group and directory (if the directory is empty). Do not forget to check if OMS and target system can resolve each other’s host name!

Login to the OMS host as oracle user (again I assume you used oracle to install OMS), and log in to OEM using emcli:

Read More

If you prefer RPM package management system to keep tracks of installed software on your systems, you can deploy Oracle Management Agent using RPM File.

First, you need to create “/usr/lib/oracle” on OMS server (if there is no such a directory). Login as root user and run the following commands:

Install the rpm-build package on the OMS host:

Switch to oracle user, and login to OEM using emcli as SYSMAN user:

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

Read More

Some readers commented that, after they add JDBC driver for Microsoft SQL Server to their SQL Developer, the “New Connection” window (of SQL Developer) doesn’t open at all. I have downloaded the latest Java (1.6), SQL Developer and added jTDS driver then I have the same problem. I tried to debug the problem with my limited Java knowledge and I think there’s an incompatibility between jTDS and Java 1.6.

Oracle recommends to use Java 1.6 for SQL Developer so instead of trying Java 1.7, I tried to find the latest compatible version of jTDS and luckily I found it on my first try. So to fix the problem, all you need is to download and use 1.2.7 version of jTDS: jtds-1.2.7-dist.zip

Then you’ll be able to connect to Ms SQL Server or Sybase with your Oracle SQL Developer. For more information about using SQL Developer with Ms SQL Server and MySQL, please read my related blog post.

One of my blog readers asked me how we can change the ports of Grid Control after install. Yes it’s possible to change the ports after installing EM Grid Control and it’s well documented for Enterprise Manager Cloud control. I tested if these steps are valid for Grid Control and it worked. I think no one uses insecure ports so I’ll show how I will set Oracle Enterprise Manager (secure) web site port to 8000 and “secure/https upload port” to 2000 on Oracle Enterprise Manager Grid Control 11g:

First we need to stop OMS:

Then modify the port information in repository:

Read More