DBMS_SCHEDULER

This is some task i did for the first time in one of my recent projects.
so just an another attempt to share my learning.
To create a scheduled job the syntax is -

begin
sys.dbms_scheduler.create_job(job_name => 'test_job',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN DBMS_STATS.gather_schema_stats(''ABC''); END;',
repeat_interval => 'FREQ=DAILY;BYHOUR=21;BYMINUTE=45;BYSECOND=0',
start_date => sysdate,
job_class => 'DEFAULT_JOB_CLASS',
comments => 'gather stats job',
auto_drop => TRUE,
enabled => TRUE);
END;

initializing oracle ASMLib driver : FAILED , Loading module "oracleasm": Unable to load module "oracleasm"

I came across this problem recently while installing Oracle RAC on one of the systems.

[root@rac1]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.

This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting without typing an
answer will keep that current value. Ctrl-C will abort.

Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Loading module "oracleasm": Unable to load module "oracleasm"
[FAILED]

The correct place to look for erorr was /var/log/messages.
here i found the error Module oracle ASM not found.

I did a rpm -qa | grep oracleasm on the system and found 3 asm packages installed.
oracleasm-2.6.9-89.EL-2.0.5-1.el4.i686.rpm,
oracleasmlib-2.0.4-1.el4.i386.rpm,
oracleasm-support-2.1.3-1.el4.i386.rpm


The following package was missing -->
oracleasm-2.6.9-89.ELsmp-2.0.5-1.el4.i686.rpm

I installed the above given package with -->

rpm -ivh oracleasm-2.6.9-89.ELsmp-2.0.5-1.el4.i686.rpm
Preparing... ########################################### [100%]
1:oracleasm-2.6.9-89.ELsm########################################### [ 100%]

afterwards again tried to configure Oracle ASM

[root@rac1]# /etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.

This will configure the on-boot properties of the Oracle ASM library
driver. The following questions will determine whether the driver is
loaded on boot and what permissions it will have. The current values
will be shown in brackets ('[]'). Hitting without typing an
answer will keep that current value. Ctrl-C will aborts.

Default user to own the driver interface [oracle]: oracle
Default group to own the driver interface [dba]: dba
Start Oracle ASM library driver on boot (y/n) [y]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration: [ OK ]
Initializing the Oracle ASMLib driver [ OK ]
Scanning the system for Oracle ASMLib disks [OK]

RW-50016 Error: - {0} was not created during rapidinstall

ERROR LOGIN PAGE
-------------------------
checking URL = http://.:8000/OA_HTML/AppsLogin
RW-50016: Error: - {0} was not created

Finally when i thought i have solved all errors, i came across this new error at the end on installation. Now am trying to solve this one, and will post the solution as soon i come across one. Anyhow installation was smooth till now, its just this error i had come across at the end, but it took me a lot of time to complete installation since am also installing vision database for test purpose and am that too on vmware.

I tried one of the solutions that i came across on other sites, and changed the entries in /etc/hosts.
127.0.0.1 localhost

Now i started install again and one of the error that was previously coming - JSP page could not be displayed has stopped coming.

Let's hope the other error also stops coming.

I will update this post soon with some results.

Finally all errors resolved as of now!

Finally i was able to resolve the rw error that was coming, it was actually because of the improper unzip of files that i had downloaded. Now i am going to start the installation once again , and am sure will finish things this time. I will surely paste some more details about the installation in some time

rw-20003 while installing E-business 12i suite on linux

Today i recieved the above error while installing E-Business suite on Linux. anyhow i searched on google and found a link to metalink note No.802195.1
It seems like there is some corruption in the files that i have downloaded for installation. so i have to run the md5 checksum file given in this note with the cds that i have downloaded. Am doing the same.
I downloaded this file and placed it in the directory where i had staged all my components.
then i ran -->

$md5sum --check md5sum_Linux32.txt > md5sum_result.txt

This is going to take some time. so will have to wait for the output.

Oracle Data Pump 10g

Recently i worked on Oracle data pump for second time. Its actually a feature of oracle database that helps to export data in a faster manner, i had earlier worked on this in one of my previous projects, but recently used it to export somewhat bigger table in the database.
This method of exporting data is much faster that simple imp and exp.

I will just outline some simple steps to use this great utility -

First of of all we need to create a Dump directory -

In my case i create this directory at the location /backup/dpump_dir

SQL> Create directory exp_dir as '/backup/dpump_dir';

Then we need to grant read,write access to the users that are exporting data on this directory.

SQL> grant read,write on exp_dir to user1;

Now we are all set to start datapump export , we will use -

$expdp username/password DIRECTORY=exp_dir DUMPFILE=exp1.dmp LOGFILE=exp1l.og FULL=y PARALLEL= 10

Also to export a single table we can use -

$ expdp username/password DIRECTORY=exp_dir DUMPFILE=user1.dmp LOGFILE=user1l.log TABLES=TABLENAME PARALLEL=10

This will export a single table

For more information use EXPDP help=y on dollar prompt

Now to check your jobs you can write-

sql> select * from dba_datapump_jobs

From here you can view the name of your job.

To kill currently running job we can first find session name from above and then use -

expdp username/password attach=JOB_NAME
Afterwards we get a prompt

Export >
Export > Kill_job
Are you sure you wish to stop this job ([y]/n): y

Again we can check with -->

SQL> select * from dba_datapump_jobs
no rows selected