Puppet Certificate Store.

If you are using Puppet, and in particular if you are using it to install modules from the main Puppet repository, you may run into an issue.

Specifically this is when the puppet module complains that the puppet server certificate is not valid.


Symptom : Redhat 6.4

Puppet latest version.

After a lot of messing around with openssl ( which turned out not to be the problem )  we went back to concentrating on Puppet.

Puppet expects to see the list of trusted server certificates in

/etc/pki/tls/cert.pem ( we only found this via strace -f )

if it cannot find it then you will get the error.

In a default setup this cert.pem file doesn't exist and needs to be linked in.

The list of certs is happily available in the certs/ca-bundle.crt file.

So :

ln -s cert.pem certs/ca-bundle.crt

and now Puppet module install works just fine.

Regards

Chris.

VMWARE tools on OEL6

Problem : VMWARE tools installing on Oracle Enterprise Linux 6

Problem :  vmware-config-tools cannot find the Kernel headers, even though yum sttes they are installed.

Solution :   yum -y install kernel-uek-devel.x86_64

then re-run vmware-config-tools. 

All done

Regards

Chris. 

Cloud Control 12c MIscellaneous issues

Cloud Control Refused to start at boot ( OMS not started, and agent not started).  This was an upgraded Cloud control with several restarts of the process, but it completed successfully.

After much shell script tracing the issue turned out to be a messed up oragchomelist file in /etc

there were several wrong entries in it.

For a non-oms machine the config of this file should be a single line

$AGENT_HOME:$AGENT_INSTANCE_HOME

see ML 1386113.1 note for more details..

 Further, if this is actually an OMS  machine there will be a 2nd line 

$AGENT_HOME:$AGENT_INSTANCE_HOME
$OMS_HOME

where $OMS_HOME=$MIDDLEWARE_HOME/oms , usually.

Once you set this up properly, OMS And agents will all start up nicely.

Regards

Chris.

Upgrading to EM Cloud Control 12c

It looks like Linux 6.3 targets aren't supported... but they are, there is a bug fix on Metalink

get what you need ( a .sql file ) from PUC: Linux 6.x Agents are shown as Unsupported in the Enterprise Manager 12c Upgrade Console [ID 1545450.1]

Connecting to Work Repository in ODI

One problem I had run into when connecting to ODI was being unable to connect to a work repository remotely.  After debugging this problem it came down to the fact that the hostname resolution was not what was expected; I was using an IP address to connect and this was what was causing the issue.


When ODI Studio has a connection created,  for the master repository it uses the JDBC Url you type in , which is OK as :port:sid

However when it comes to connecting to the Work repository, the studio goes back to the server, and downloads the JDBC URL connection information for it from the Master Repository.   This URL has the hostname for the database server embedded, NOT the IP address, and if you cannot resolve the hostname , you won't be able to connect to the database server; thus Work Repository Connections will fail.

There are two resolutions

1: Enable NS resolution of the db server, either via hosts file or DNS
2:  Edit the Repository definition of the URL via clicking into the Work Repository Definition from the Master, clicking the plug icon, then JDBC , then editing the host= to be host=IP ADDRESS. 


Once either of these are done, then it will work like a top !

The symptom of this issue is ODI-10182

Oracle Business Intelligence Blog: OBIEE 11.1.1.7.0 Available

Hi Folks -  OBIEE 11.1.1.7 Now out !   See the bloglink below for more details and some greatest hits.
Oracle Business Intelligence Blog: OBIEE 11.1.1.7.0 Available

Endeca 3.0 and Endeca Server 7.5 released today

https://blogs.oracle.com/emeapartnerbiepm/entry/endeca_information_discovery_version_release