Don't Start Up Oracle Instance as Root User in Unix

It's been a while since I stopped blogging. That is because I've been quite busy this semester with school and work. Right now, I'm taking some classes at the Houston Community College in order to get a MSA (Marketable Skills Achievement Certificate) in Oracle Database Administration as well as a MSA in Java Development.

About 1 months ago, when I was doing one of my Oracle Administration practices, I started up the Oracle Database instance as a root user. After having started up the instance, I started up the Enterprise Management Console (Web-based Oracle Configuration Management Tool), but it didn't get up because the oracle process couldn't log information about the initialization of the EM Console.

I called my instructor to help me out with this problem, and after checking out, we realized that some of the $ORACLE_HOME directories had different permissions because I had started up the instance with a user that doesn't belong to the DBA users.

When you install Oracle Database, you need to set up the OS Environment and create OS users that will perform Oracle Installation. I couldn't get the EM Console up because I previously started up the Oracle Database instance with OS root user, which didn't have written permissions in $ORACLE_HOME directories. In other words

"DO NOT START UP THE ORACLE DATABASE INSTANCE LOGGING IN AS ROOT USER AT LEAST THE ROOT USER BELONGS TO THE OS DB USER GROUP"

Problems running GWT after Upgrading to Mac OS Snow Leopard 10.6.2?

This morning, I tried to show one of my classmates all the work that I've been doing with GWT concerning the GWT Adempiere project. Once I started up the project on Eclipse, I realized that an exception was thrown up and the project didn't launch up.

Invalid memory access of location 00000010 eip=931cf77b

After searching on the Internet about this issue, I found an useful article that tells about what the problem is and also explains how to work around on this problem. All that you have to do is to download the Webkit.app and to follow the steps explained on this post.

http://code.google.com/p/google-web-toolkit/issues/detail?id=4220#c22

That worked for me and now I'm able to work with GWT on my Mac by using Snow Leopard 10.6.2 and Safari 4.0.4.

Twelve Principles of Agile Software

I've been asked to read some information about a software company and its leaders. While I was reading this information, I found an article that talks about Twelve Principles of Agile Software development. I found this article interesting and I think you might be interested too. Reading this article won't take you a lot of time, and I think you can read it in about 5 minutes.

I invite you to read this article and take deeply consideration in these practices. These practices have made the authors successful in building software. If you want to be successful in developing software, these practices can help you build software effectively and efficiently. Click on Twelve Principles of Agile Software to take a look at it.

GWT & Java 6 are Now Working under Snow Leopard

On my previous article GWT does not Work with Snow Leopard, I wrote about some issues that I faced with the new version of Mac OS X, Snow Leopard, and GWT framework. To refresh your memory, GWT framework does not work with Mac OS Snow Leopard because Mac OS Snow Leopard cames up with a 64-bit Java version by default, which is not compatible with GWT 1.7.0 and even any version of GWT.

With the new official release of GWT 1.7.1, now you can run GWT and Java 6 by using Java command line argument -d32 when you start GWT in hosted mode. For example, if you're using Google Plugin for Eclipse, you can add this argument on its settings, and GWT will be launched in hosted mode by using a 32-bit Java Virtual Machine.

Source: GWT 1.7.1 release fixes Mac OS X Snow Leopard issues by Andrew Bowers

GWT does not Work with Snow Leopard

About two weeks ago with the new release of Snow Leopard, I was so excited about upgrading my Macbook Pro OS X to this new operating system. Things came well until I got a message when I was starting up GWT hosted mode application. GWT hosted mode was not launched because Snow Leopard comes with the 64-bit Java 6 version as its default Java Virtual Machine. As you may probably know, GWT is not compatible with any 64-bit Java versions. I initially thought that GWT, specifically 1.7.0 version, was not compatible with Java 6 because of its System Requirements. But after having read Snow Leopard, Java 6 and GWT article, I realized that GWT works with any 32-bit Java versions, even Java 6. All that you need to do is to read Snow Leopard, Java 6 and GWT article and follow the instructions that Alex Moffat posted in it.

A quickly fix was posted in OS X 10.6 Snow Leopard article few hours after Snow Leopard had been released in order to downgrade the JVM from Java 6 to Java 5. I downgraded the JVM version on my Mac OS X because I needed to keep working on my GWT project. But if you need to use Java 6 feautures and work with GWT, I highly recommend you to follow the steps posted in Snow Leopard, Java 6 and GWT.

Just to Remain me- Profile file on Mac OS X

I have been spending a certain amount of time working on a project that includes Google technologies. Due to the quick release of the GWT library, I constantly have to update the environment variable to which this library is located. Due to the fact that I don't upgrade this path so often, I always forget where the Profile file is located on my Mac. The Profile file in your Unix home directory is a collection of Korn shell commands that are executed whenever you login. So, this file is supposed to be in my home directory, but I've never found it there. On my Mac, the file is located in ~/etc/ directory. If you don't find this file in your home directory, look for it in ~/etc/ directory. You'll probably find it there.

Moving to Houston

Dear readers,

It's been long time without writing on my blog. The thing is that I've been quite busy because I moved to Houston, TX last February. I moved to Texas for two reasons. The first one is because my girlfriend is living here, and as you know, it's better if you live close to the girl you love. The second reason is because Houston is cheaper than Atlanta. I looked for an apartment to rent while I was in Atlanta, and it's very expensive to rent an apartment in Atlanta. Before I decided to move to Houston, I studied carefully what the best option could be for me. Right now I'm a student, and I'm living on my own. So, I need to save some money in order to stay in the US for a long time. I have many goals that I want to achieve in the US, so I need to save money for that.


Well dear readers, I'm not gonna promise you that I'm gonna write frequently. Sometimes I don't have enough time to write about me and something else, like my blog says. Have really fun, and enjoy everyday of your life like it was your last day to live for.