Random Picks- Kernel Compilation

A good link for beginners is:
http://bobpeers.com/linux/kernel_compiling.php

How to remove kernel module!!

The two major commands we would need are lsmod and rmmod.
lsmod lists all the kernel module.

and that rmmod directly deletes the kernel module. But more often the system gets stuck.. The best way is to grep for modules and rm -rf it.

find / -name   -print 

I got trouble with sk98lin ..network driver...

As I play more around modules.. the post will be updated.

Good Link for Linux open source books

Good Link for Linux open source books
http://www.dailyart isan.com/ news/open- source-e- books-for- linux/

Agent Upload problem in version 10.2.0.5 (EM Related)

The pending files to get uploaded when you fire
/bin/emctl status Agent shows that the files are pending.. to get uploaded to the OMS.
And it doesnt uploaded even if you give an hour to this..

The problem can be traced as follows:
goto /sysman/log . Open file emagent.trc . Go down find out which xml file is creating the problem.
Goto /emd/upload and remove that xml file. 
Hint here is clearing that file and uploading the rest to the OMS. at least the block is removed.
now do an agent reload
/bin/emctl reload agent
Things should be better now
and agent must show no pending files..

ORA-01031: insufficient privileges upon instance startup

Very good link: http://it.toolbox.com/blogs/david/ora01031-insufficient-privileges-upon-instance-startup-13759

He then proceeded to creating his instance using the following command:

oradim -new -sid InstanceSID -startmode m -pfile C:\location_to_pfile\init.ora -intpwd password

After which, the instance was created. He proceeded to creating the database itself. Since he was all keen about doing this manually he opened up a Windows CMD and did the following steps:

C:> SET ORACLE_SID=InstanceSID
C:> sqlplus /nolog

SQL*Plus: Release 9.2.0.1.0 - Production on Wed Dec 13 10:18:27 2006

Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.

SQL> conn sys/password as sysdba

Connected to an idle instance.

SQL> startup nomount pfile=C:\location_to_file\init.ora;

ORA-01031: insufficient privileges

SQL>

As you see, he got an ORA-01031. He didn't understand what is causing this. His O/S user was a member of the ORA_DBA group. He tried logging off windows and then logging backup in. Nothing.

The Concept of RAC/CRS and Database !!!!

This Concept should have come somewhere in my earlier posts. But ok.. it is never 2 late!!!!

There are 3 most important things to RAC/CRS setup. RAC is Real Application Cluster which is build on CRS (Cluster Ready Service).

We take a 2 node cluster.We try understanding the setup. Both the nodes will have a separate CRS setup. The version of CRS should be greater than or equal to that of RAC. So whenever we go for an upgrade to a newer version, we go for CRS upgrade first and then the RAC.
The reverse will make things unuseable. Reverting back the changes in the version is not possible.(as far as I have known).

Now the two nodes will have a shared location. This shared location contains the ORADATA. this oradata is what helps storing information , our data.
RAC is a normal DB installation except that the other db files are stored in the separate nodes but the oradata which manages the data is stored in the shared location. The two nodes are hence gateway to the same data. This is what increases the availability of the RAC and hence defines its use.

Now, the shared location defines the size of database.

And lets take the case of upgrading the RAC db. We first upgrade the db instance files on both nodes , and then the procedure to upgrade the oradata is not the same and is done by running a specific sql script. We can note that the script is run only from one node. This is because the oradata is accessible from both nodes.

ORA-01031: insufficient privileges ON WINDOWS!

In most cases, the user receiving this error lacks a previlage to create an object (such as a table, view, procedure and the like).

Grant the required privilege like so:

grant create table to user_lacking_privilege;

Startup

If someone receives this error while trying to startup the instance, the logged on user must belong to the ora_dba group on Windows or dba group on Unix.

To add a user to the ora_dba group on Windows, net localgroup should help:

C:\> net localgroup ora_dba rene /add