The last thing you just did was to log onto your new server as the oracle user. If you followed the instructions in the prelimiinary ‘how to build a Kickstart server‘ article, you will already have the necessary software available on your Kickstart server in the form of two large zip files. You get them across to your new Grid Control server, therefore, like so:
cd /osource wget http://192.168.0.70/linux.x64_11gR2_database_1of2.zip wget http://192.168.0.70/linux.x64_11gR2_database_2of2.zip unzip linux.x64_11gR2_database_1of2.zip unzip linux.x64_11gR2_database_2of2.zip rm *.zip
That lot will leave you with a /osource/database directory, and it is from within there that we can launch the Oracle 11g installation by issuing the command:
For the most part, what you now do is click [Next] quite a lot of times! But there are complications (the principal one being that we don’t want Enterprise Manager database control configured by mistake, because that and Grid Control cannot co-exist), so here’s a slideshow putting it all together for you:
The main thing to get right in that lot is to supply a suitable database name and SYS passwords. The database we create here is going to be the Grid Control “repository database” -where it stores the things it needs to work. So a database name of griddb seems appropriate to me, but you can use whatever up-to-8-character name you like (so long as it doesn’t start with a number).
The only trouble with this way of doing things is that you end up with a database being created that actually uses the database control tools. Database control is, if you like, “Grid Control Lite” -it’s meant for managing standalone databases that aren’t part of a wider, enterprise-style collection of databases. As such, database control and grid control are completely incompatible. So we have to remove the database control elements if our new database is to ever serve as a Grid Control repository. Happily, that’s easily done by issuing the following command (in a terminal, with you logged on as the oracle user):
emca -deconfig dbcontrol db -repos drop
You’ll be prompted to supply the database SID (that’s griddb in my case); the Listener port number (nearly always 1521); and the password for the SYS and SYSMAN users (whatever you supplied during the OUI installation):
Once you have a database that has no Database Control aspects to it, you’re ready to move on. (Incidentally, it’s always possible to create a database without Database Control elements from the word go -and if you prefer to do it that way, fine. I just think it’s so easy to remove Database Control that the way I’ve described things is the simplest and most fuss-free way of going about things. But it’s your choice).
Anyway, now you’re ready to install the application server and Java components, so read on!