Oracle For Life

ASM on windows

Liakat Hossain — Tue, 10 Nov 2009 07:41:52 +0000

Creating ASM on windows .

step 1: create a windows based service for asm.
c:\oradim -new -asmsid +asm -startmode manual

step 2: create init+asm.ora file in your oracle_home/database directory
with just this lines–

instance_name=’+asm’
instance_type=’asm’
asm_diskstring=’\\.\*:’
#asm_diskgroups=dg1

step 3 : set oracle env for ASM

c:\set oracle_sid=+asm

step 4: connect asm instance with sqlplus as sysdba and start the instance.
C:> sqlplus / as sysdba

SQL> STARTUP
ORA-29701: unable to connect to Cluster Manager
–if u see the error that means your CM is not started so follow this step
C:\>CD F:\oracle\product\10.2.0\db_1\BIN
C:\>localconfig delete
Step 1: stopping local CSS stack
Step 2: deleting OCR repository
failed to open the OCR subkey, err(1060)
failed to cleanup local OCR repository
successfully deleted local CSS setup

C:\>localconfig add
Step 1: creating new OCR repository
Successfully accumulated necessary OCR keys.
Creating OCR keys for user ‘robin’, privgrp ”
Operation successful.
Step 2: creating new CSS service
successfully created local CSS service
successfully added CSS to home

step 5: now try again.

SQL> STARTUP
ASM instance started

Total System Global Area 79691776 bytes
Fixed Size 1247396 bytes
Variable Size 53278556 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
SQL> select path from v$asm_disk ;

no rows selected

a–so you have no asm disk group,for disk group first you need to create asm disk first.
b–go to disk management
c–select unallocated space
d–right click unallocated space and luance a new partition wizard..click next
e–choose extended partition not a primary. click next
f–choose the meximum size click finish.
g–right click the free space in the new partition. select logical drive,click next
h–when prompted for a partition size ,enter your desire size from maximum size.
i–select the redo button to assign a drive letter.and acceep what ever later is suggested.
j–select the redo button Do not format the partition.click next.
k–click finish ,the logical drive ,with no file system.
l–repert step “G” to create additional unformatted drive.

Step 6: go to sqlplus
Sql> select path,total_mb from v$asm_disk;

Path total_mb
——— —————–
\\.\k: 2000
\\.\l: 2000

Step 7 :
Create a disk group ,nominating the two raw volumes.
Sql>create diskgroup dg1 disk ‘\\.\k:’,'\\.\l:’

Step 8 :
Shutdown asm instance
Remove # from asm_diskgroups=dg1 parameter in asm+init.ora file.
Startup
–u see your database is mount , actually asm mount the disk group not controlfile , because asm hasn’t any controlfile.

Step 9: go to RDBMS instance. Run the following command.

Sql> create tablespace new_tabs datafile ‘+dg1’ size 10m;

Sql> select name from v$datafile;

Sql>alter database add logfile group 4 ‘+dg_log1’,’+dg_log2’ size 10m;

Sql> select group#,member from v$logfile.

Note : ASM instance should start first before any rdbms instance start.

ASM on windows

Liakat Hossain — Tue, 10 Nov 2009 07:32:06 +0000

Creating ASM on windows .

step 1: create a windows based service for asm.
c:\oradim -new -asmsid +asm -startmode manual

step 2: create init+asm.ora file in your oracle_home/database directory
with just this lines–

instance_name=’+asm’
instance_type=’asm’
asm_diskstring=’\\.\*:’
#asm_diskgroups=dg1

step 3 : set oracle env for ASM

c:\set oracle_sid=+asm

step 4: connect asm instance with sqlplus as sysdba and start the instance.
C:> sqlplus / as sysdba

step 5: now try again.

SQL> STARTUP
ASM instance started

Total System Global Area 79691776 bytes
Fixed Size 1247396 bytes
Variable Size 53278556 bytes
ASM Cache 25165824 bytes
ORA-15110: no diskgroups mounted
SQL> select path from v$asm_disk ;

no rows selected

Step 6: go to sqlplus
Sql> select path,total_mb from v$asm_disk;

Path total_mb
——— —————–
\\.\k: 2000
\\.\l: 2000

Step 7 :
Create a disk group ,nominating the two raw volumes.
Sql>create diskgroup dg1 disk ‘\\.\k:’,'\\.\l:’

Step 9: go to RDBMS instance. Run the following command.

Sql> create tablespace new_tabs datafile ‘+dg1’ size 10m;

Sql> select name from v$datafile;

Sql>alter database add logfile group 4 ‘+dg_log1’,’+dg_log2’ size 10m;

Sql> select group#,member from v$logfile.

Note : ASM instance should start first before any rdbms instance start.

buffer cache tuning

Liakat Hossain — Sat, 31 Oct 2009 07:26:35 +0000

SELECT name, 1 – (physical_reads /
(db_block_gets + consistent_gets)) “HIT_RATIO”
FROM v$buffer_pool_statistics
WHERE db_block_gets + consistent_gets > 0

Data buffer cache hit ratio should be 90%. otherwise tunig datbase buffer cache .

creating a logical standby database

Liakat Hossain — Wed, 28 Oct 2009 05:06:06 +0000

Step-by-step instructions for creating a logical standby database.

——————————————————————————————–
1. Create a Physiacl standby database.
2.Stop Redo Apply
3.Prepare the primary database to support a logical Standby Database.
4.Transition to a logical standby Database
5.Open the Logical Standby database.
6.verify the logical standby database is performing properly.
———————————————————————————————

Step 1:Create a Physiacl standby database.

It asssume that physical standby database is alredy created.

Step 2:Stop Redo Apply
=====on standby DB
Sql> Alter database recover managed standby database cancel;

Step 3: Prepare the primary database to support a logical Standby Database
=====On primary
sql>alter system set log_archive_dest_3=’location=’C:\oracle\product\10.2.0\admin\TEST\arc2′ valid_for=(standby_logfiles,standby_role) db_unique_name=test’

=====Assume our primary database name is “test”

log_archive_dest_state_3=enable

Build a Ditionary in the redo data

Sql> execute dbms_logstdby.build;

step 4: Transition to logical standby database

===== on standby
sql>alter database recover to logical standby db_name;
— create a new password file for logical standby

c:>

sql>shutdown immediate
sql>startup mount
sql>alter system set log_archive_dest_3=’location=C:\oracle\admin\stest\arc2 valid_for=(standby_logfiles,standby_role) db_unique_name=stest’;

step 5: open logical standby database

sql> alter database open resetlogs;
=====applying redo data to the logical standby database
sql>alter database start logical standby apply immediate;

=====verify logical standby database perform properly
sql> select sequence#,applied from archive_log;

The ORACLE Import/Export Utilities

Liakat Hossain — Fri, 23 Oct 2009 11:18:24 +0000

Import one database user object into another database user.

SQL> show parameter db_name

NAME TYPE VALUE
———————————— ———– ———
db_name string cat
SQL> conn alin/alin
Connected.
SQL> select * from test;
TID
——————–
test import
test import
c:\>exp userid=system/manager@cat file=d:\u.dmp owner=alin

c:\>imp userid=system/manager@cat2 file=d:\u.dmp fromuser=alin touser=robin SQL> show parameter db_name

NAME TYPE VALUE
———————————— ———– ———
db_name string cat2
SQL> conn robin/robin
Connected.
SQL> select * from test;
TID
——————–
test import
test import

catalog database

Liakat Hossain — Sat, 17 Oct 2009 13:33:17 +0000

SQL> create tablespace rman_t
datafile ‘d:\oracle\oradata\rcat\rman_t01.dbf’ size 100m;

SQL>create user rman1
identified by rman1
default tablespace rman_t
temporary tablespace temp;

SQL>grant connect,resource, recovery_catalog_owner to rman1;

rman> connect catalog rman/rman@rcat

rman>create catalog tablespace rman_t;

rman> connect target sys/admin@orcl catalog rman1/rman1@rcat
or
c:\>rman target sys/admin@orcl catalog rman1/rman1@rcat

rman>register database;

RMAN> RUN
{allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3 type disk;
backup database;
}

RESETTING THE RECOVERY CATALOG

rman> connect target sys/admin@orcl catalog rman/rman@rcat
or
c:\>rman target sys/admin@orcl catalog rman/rman@rcat

rman>reset database;

resynchronizing recovery catalog

rman> connect target sys/admin@orcl catalog rman/rman@rcat
or
c:\>rman target sys/admin@orcl catalog rman/rman@rcat

RMAN> report schema;
sql> select name from v$tablespaces;

sql> alter tablespace data
add datafile ‘d:\oracle\oradata\grid\data02.dbf’ size 10m;

rman> connect target sys/admin@orcl catalog rman/rman@rcat
or
c:\>rman target sys/admin@orcl catalog rman/rman@rcat

rman> resync catalog;

RMAN> report schema;

SQL> rman/rman@rcat

SQL> select * from db;

SQL> execute dbms_rcvcat.unregisterdatabase ( db_key, db_id);

SQL> select * from db;

rman script

Liakat Hossain — Sat, 17 Oct 2009 13:29:37 +0000

• Create script

RMAN>create script full_back
{allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3type disk;
allocate channel c4 type disk;
backup database;
}

• Run script
RMAN>run {execute script full_back;}

• Managing script

REPLACE SCRIPT
RMAN> REPLACE SCRIPT full_back
{allocate channel c1 type disk;
allocate channel c2 type disk;
allocate channel c3type disk;
allocate channel c4 type disk;
backup database;
backup (archivelog all);
}

DELETE SCRIPT
RMAN> DELETE SCRIPT FULL_BACK;

• Data dictionary view.

 RC_STORED_SCRIPT
 RC_STORED_SCRIPT_LINE.

Tuning data dictionary cache

Liakat Hossain — Sat, 17 Oct 2009 07:35:42 +0000

SELECT (SUM(GETS-GETMISSES))/SUM(GETS) “Dictionary Cache Hit Ratio”
FROM V$ROWCACHE

Tuning library cache

Liakat Hossain — Sat, 17 Oct 2009 07:33:25 +0000

SELECT SUM(PINS-RELOADS)/SUM(PINS)*100 “Library Cache Hit Ratio”
FROM V$LIBRARYCACHE

rman incomplete recovery

Liakat Hossain — Fri, 16 Oct 2009 10:28:16 +0000

Take Rman whole database backup while database in archive log mode.

C:\>set oracle_sid=orcl

C:\>rman
Recovery Manager: Release 9.2.0.1.0 – Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

RMAN> connect target sys/sys123
connected to target database: ORCL (DBID=1184034377)

RMAN> run
2> {allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> allocate channel c3 type disk;
5> backup database;
6> }

Go to sql*plus session run the following command.

SQL> create table t100
2 (id number);
Table created.

SQL> select to_char(sysdate,’dd-mm-yy:hh24:mi:ss’) from dual;
TO_CHAR(SYSDATE,’
—————–
04-06-08:10:01:27

SQL> drop table t100;

Table dropped.

SQL> create table t200
2 (id number);
Table created.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down

SQL> startup mount
ORACLE instance started.
Total System Global Area 135338868 bytes
Fixed Size 453492 bytes
Variable Size 109051904 bytes
Database Buffers 25165824 bytes
Redo Buffers 667648 bytes
Database mounted.

go to RMAN session for recovering droped table.

C:\>set nls_date_format=yyyy-mm-dd hh24:mi:ss

C:\>set oracle_sid=orcl

C:\>rman
Recovery Manager: Release 9.2.0.1.0 – Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.

RMAN> connect target sys/sys123
connected to target database: ORCL (DBID=1184034377)

RMAN> run
2> {allocate channel c1 type disk;
3> allocate channel c2 type disk;
4> allocate channel c3 type disk;
5> set until time=’2008-06-04 10:01:27′;
6> restore database;
7> recover database;
8> }

Go to sqlplus session you table is there.

SQL> alter database open resetlogs;
Database altered.

SQL> desc t100

SQL> desc t200

Smile !!!!!!!!