The Automatic Memory Management (AMM) and HugePages are not compatible. With AMM the entire SGA memory is allocated by creating files under /dev/shm. When Oracle Database allocates SGA that way HugePages are not reserved. You must disable AMM on Oracle Database 11g to use HugePages.

From: http://docs.oracle.com/cd/B28359_01/server.111/b32009/appi_vlm.htm

Getting Real About Distributed System Reliability – Jay Kreps.

Hadoop Users Could Get Their First Taste of Real Encryption.

5 low-profile startups that could change the face of big data — Cloud Computing News.

We are currently using Oracle Grid Control 11g to monitor and manage most of our production and development Oracle database and application servers.  When posed with the task of doing some tablespace reorganizations, I opted to embrace the GUI and click my way to what is usually a tedious task.  Unfortunately I hit a brick wall when I needed to enter my user credentials for the host system to do some of the OS level tasks.

In an “ideal” world, there is no such thing as identity management and all of your logins are local to the box that you are interested in working on.  Oh, and you have root access.  In reality, most organizations use some sort of tool like Centrify to allow users a single sign-on for Unix/Linux hosts in their mixed environments.  Unfortunately Oracle Enterprise Manager needs a little help to work with non-local logins.

So how do I make my LDAP login work with OEM when administering remote hosts?  Here is a quick and dirty solution (for Centrify)

Oracle Enterprise Manager does support PAM authentication. To enable PAM authentication, create a file called /etc/pam.d/emagent and include the following lines so the authentication for AD users passes through Centrify PAM modules:
#Centrify mod
auth       sufficient     pam_centrifydc.so
auth       requisite      pam_centrifydc.so deny
account    sufficient     pam_centrifydc.so
account    requisite      pam_centrifydc.so deny
session    required       pam_centrifydc.so homedir
password   sufficient     pam_centrifydc.so try_first_pass
password   requisite      pam_centrifydc.so deny

Note: it is important that these lines be at the beginning of the file – before other lines.

Then restart the Oracle EM agent(s) to reload these directives.

References:

Oracle also has a KB article on this, please check their website for the following article:

How to Configure the Grid Control Agent for PAM and LDAP? [ID 422073.1]

Note the metalink (support.oracle.com) note number (422073.1) above.  Log in over there and get the full run down of making this work.  I don’t want to anger the Oracle gods and post all of the details here, so pay your sales rep and get support if you don’t have it.

Where Will You Find Hadoop Talent? | Blogs | ITBusinessEdge.com.

SQL> SELECT segment_name tbl, sum(bytes)/(1024*1024) size_MB
     from dba_extents where segment_type='TABLE'
     and segment_name LIKE 'your big tables'
     GROUP BY segment_name;

SELECT sum(bytes)/1024/1024 FROM dba_segments WHERE owner=’YOURMOM’;

Back story: having some problems with BI Publisher in a legacy install of OBIEE 10g.  did some port configuration in the Enterprise Manager Console and did some bouncing with opmnctl.  I had some port conflicts (d’oh, fat fingers) and had to force iAS to come up on a non-default port to back out/adjust some of the port changes.  No big whoop.  Then, I tried bringing everything up and saw no errors, EM came up just fine, the apps all had green arrows…but nothing would load.  The browser would just say “waiting” while trying to hit the OBIEE application.  I brought everything down again, and back up again and the same thing happened.  I started digging through the config screens to make sure that I didn’t miss anything.

Then I decided to bring everything down and issue a ps -ef | grep [username] and saw that I had an old sawserver (OBIEE web server) process hanging around.  Killed it…brought everything back up, and we were back in business.

Moral of the story: If you bring everything down to fix a bigger problem, make sure everything is indeed down before bringing the stack back up.

Oracle has partnered with Cloudera to bring Apache Hadoop to its Oracle Big Data Appliance, which the company officially released Tuesday.

The newly released appliance comes with Cloudera’s Distribution Including Apache Hadoop (CDH), along with the Cloudera Manager software. The rack also comes with a copy of the Oracle NoSQL Database. Oracle announcedthe Big Data Appliance, along with the Oracle NoSQL database, at OpenWorld last September.

Full story here