Monday, January 25, 2010

Optimize I/O and disk utilization in Oracle Databases - Space Manager with LiveReorg.


Managing exploding growth of Oracle databases requires a strategy to optimize I/O and available disk space while still meeting SLAs for application performance.

This is especially useful for business critical ERP applications such as SAP, Siebel, Oracle e-Business and Cerner. Such environments have high transaction volumes which require large database storage capacity and routine archiving of data. Inefficient storage can lead to poor I/O performance.
How do you fix this issue with no downtime to the applications or the database?

Space Manager with LiveReorg offers a simple yet comprehensive solution for space reclamation and reorganization, partitioning and capacity management for Oracle databases. DBAs can visualize and plan space use, detect and resolve space fragmentation, reclaim wasted space and project database growth for future planning.

•Perform online reorganizations to minimize downtime to applications and the database
•Support for Oracle database environments running ERP applications such as SAP, Oracle E-Business, PeopleSoft, Siebel and Cerner Millenium
•Resolve database performance issues due to fragmentation from archiving Oracle data
•Predict disk space growth needs to plan for hardware expenditures
•Eliminate unnecessary disk space purchases by reclaiming wasted space


Know more about Quest's Space Manager with LiveReorg,

http://www.quest.com/space_manager_with_livereorg/

Regards,

Shafiulla Syed

Advanced Performance Management for Critical Oracle Databases - Performance Analysis for Oracle



Most Oracle databases today are managed by Oracle's Enterprise Manager (OEM). This is essentially a basic solution for performance management, but what about those problems that you just can't seem to resolve using Oracle's native technology? This can introduce considerable risk when managing critical databases.

Foglight Performance Analysis, extends OEM's basic management to the next level providing advanced performance management for your busiest, most critical databases. Unleash the performance potential of your Oracle databases with:

Intelligent alerting -- detect unusual behavior with adaptive baselines to uncover deviations to normal activity for immediate attention.

Problem centric workflow -- prioritize problems by severity of impact and provide next steps workflow to determine root cause and resolve the problem.

Common problem recognition -- leverage weeks, months of historical data providing real-time advisories to accelerate resolution

Exposing degrading performance trends --compare the workload from different periods to identify the relative health of overall performance

Eliminating change impacts -- quickly pinpoint elusive changes (planned or unplanned) and realign to maximize performance


StealthCollect® – High-frequency in-memory collection provides deep session-level collection at a fraction of the overhead imposed by tracing or SQL-based collection methods.
Performance Advisories – Built-in analytics and business intelligence is like having an in-house Oracle expert to review performance data and provide customized advice to guide DBAs toward maximizing performance.
IntelliProfile® – Sophisticated baselining algorithm continually tracks database behavior and identifies activity that is outside normal deviation.
Statement-level Wait Event Analysis – Provides wait event data down to the statement level, greatly decreasing the time required to resolve resource-related performance problems.

QuickCompare – the compare utility provides DBAs with a shortcut to identifying the root cause of performance deviations in application environments. By allowing customized comparisons of any aspect of an instance or application workload with full access to baseline data, identifying the cause of performance deviations is simple, and can be automated with scheduled reporting.
ChangeTracker – Automated change tracking enables DBAs to receive notifications of changes to server, instance, database and schema environments as well as application SQL degradations and a facility to define custom change alerts. Integrated alerting allows DBAs to use the analysis history view to correlate performance slowdowns with changes to quickly understand where to focus tuning and troubleshooting initiatives.
Integrated Reporting– Built-in wizard-driven reports allow DBAs to easily define, customize, and schedule reports on system health, performance, trends, changes, and a variety of other data points. Plus, by leveraging the long-term performance repository, detailed custom reports are always just a query away. WebView – Enterprise-level visibility, administrative shortcuts, and robust alerting are available from one easy-to-use web interface. WebView provides DBAs with a centralized, configurable set of dashboards to expose performance anomalies across any monitored Oracle and SQL Server instances.
Long-term Performance Repository – Unlimited performance and environmental data storage and dimensional analysis are provided in a data warehouse. DBAs can feel confident that application trends and the custom reports created on their application workload will be available and accessible using standard SQL query techniques. Dimensional Analysis – Traditional methods of analyzing application and workload trends require DBAs to trace activity and sift through huge amounts of data. Foglight provides a dimensional drill-down that exposes resource bottlenecks from poorly written code, inefficient database accesses or rogue applications or users more efficiently.

You can download a trial version of Quest's Performance Analysis for Oracle, the below link drops you there....

http://www.quest.com/Foglight-Performance-Analysis-for-Oracle/

Regards,

Shafiulla Syed

Sunday, January 24, 2010

The FASTEST way to find and fix performance bottlenecks- SPOTLIGHT on ORACLE

Your hardware budget might not be growing, but your data volume sure is. And today's economic conditions put IT cost savings front and center. What can a DBA do? Save time finding and fixing performance bottlenecks to reduce downtime and IT costs.

Spotlight on Oracle provides real-time diagnostics so you can eliminate bottlenecks in Oracle and Oracle RAC environments. Show your boss the improvements you can make and the corresponding ROI with Spotlight on Oracle.
Key Benefits
Reduce time to resolution
Prevent or minimize unplanned downtime
Improve level of service to users and stakeholders
Increase knowledge of Oracle performance
Increase visibility into database processes—including RAC (node, cluster, interconnect)


Spotlight on Oracle includes a comprehensive home page that displays all critical database components at a glance for easy detection of bottlenecks and quick diagnosis.

Spotlight on Oracle with RAC diagnostics graphically represents your RAC cluster displaying the essential components including: individual nodes, the interconnect, the IO subsystem and the flows between these components.


The below link drops you at Quest's Spotlight on Oracle....

http://www.quest.com/spotlight-on-oracle/

Regards,

Shafiulla Syed

Monday, August 10, 2009

Oracle 11g Installation on Red Hat Linux 5

Dear Friends,

Yesterday, I installed & configured the Oracle 11gR1 (11.1.0) and created the database on Linux (Red Hat Enterprise Linux – 5.0) successfully. I would like to share the steps with my blog viewers what I have followed to install it.

Operating System Details: Linux – (Red Had Enterprise Linux – 5.0)

Database Version Details: Oracle 11g Release 1 (11.1.0)

Download Software: (linux_11gR1_database.zip)http://www.oracle.com/technology/software/products/database/index.html

Pre-Installation Tasks:

* Prepare the stage area for Oracle Software on the Serve

----- Choose the mount point where software needs to be staged.

/u01

----- Create the stage directories and change the ownership and permissions.

Su – rootPassword: xxxxx ( Enter your root password Here)

# mkdir –p /u01/11gStage

# chown –R oracle:dba /u01/11gStage

# chmod –R 755 /u01/11gStage

----- Copy the software in the stage areaftp the downloaded Oracle 11g software in this stage area and change the ownership and permissions.

$ cd /u01/11gStage

$ chown oracle:dba linux_11gR1_database.zip

$ chmod 755 linux_11gR1_database.zip

* Performing the pre-installation tasks

----- Check the size of physical RAM

$ grep MemTotal /proc/meminfo

Note: During the installation it will say failed when it checks the available physical RAM is less than 900 MB , no problem even if you have less than 900MB (if it’s for testing purpose), you can continue with the installation.

----- Check the size of SWAP space

$ grep SwapTotal /proc/meminfo

----- Check the free disk space in “/tmp” directory

$ df -k /tmp

----- Check the free space available on the system

$ df –k

* Checking the Software Requirements

----- The version of Linux is installed

$ uname –a

----- Check the following required packages are installed.

binutils-2.15.92.0.2-18

compat-libstdc++-33.2.3-47.3

elfutils-libelf-0.97-5

elfutils-libelf-devel-0.97-5

glibc-2.3.9.4-2.19

glibc-common-2.3.9.4-2.19

glibc-devel-2.3.9.4-2.19

gcc-3.4.5-2gcc-c++-3.4.5-2

libaio-devel-0.3.105-2

libaio-0.3.105-2

libgcc-3.4.5

libstdc++-3.4.5-2

libstdc++-devel-3.4.5-2

make-3.80-5

sysstat-5.0.5

unixODBC-2.2.11

unixODBC-devel-2.2.11

----- To check RPMS are installed or not.Login as ROOT user

# rpm –q libaio-devel-0.3.105-2

# rpm –q unixODBC-devel-2.2.11

…………………………………………………………Like this check for all the above RPMS.

----- Install the missing packages or rpms.

First download the missing RPMS from the relevant Linux websites, or if you have the CDs with you, used during the Linux Installation, you can use them to find the missing rpms from that.

----- To install or upgrade RPMS are installed or not.Login as the ROOT user

# rpm –ivh unixODBC-devel-2.2.11.3-1.i386.rpm

Or

# rpm –Uvh unixODBC-devel-2.2.11.3-1.i386.rpm

* Creating Required Operating System Groups and Users

----- Check and create DBA groupSu – rootPassword: xxxxx ( Enter your root password Here)

# cat /etc/groupgrep dba# /usr/sbin/groupadd dba

----- Check and create ORACLE user and assign dba group.

# cat /etc/passwdgrep oracle

# /usr/sbin/useradd –d “/home/oracle” –m –g dba –c “Oracle 11g Owner” oracle

----- Set the password of the ORACLE user

# passwd oracle

* Create Required Directories

----- The Oracle Base Directory and Oracle Home Directories

Su – rootPassword: xxxxxx (Enter the password for root here)

# mkdir –p /u01/app/oracle/product/11.0.1

# mkdir –p /u02/oradata

----- Chang the owner and group of the directories

# chown –R oracle:dba /u01/app/oracle/product/11.0.1

# chown –R oracle:dba /u02/oradata

----- Change the permissions of the directories

# chmod –R 755 /u01/app/oracle/product/11.0.1

# chmod –R 755 /u02/oradata

* Configuring Kernel Parameters

----- Check the current parameters and values in /etc/sysctl.conf

# cat /etc/sysctl.conf

Note: Take a back up of this file before changing the values and parameters.

# cp –p /etc/sysctl.conf /etc/sysctl.conf.old

----- Check and add the below parameters in /etc/sysctl.conf

fs.file-max = 76800

kernel.shmall = 2097152

kernel.shmmax = 2147483648

kernel.shmmni = 4096

kernel.sem = 250 32000 100 128

net.ipv4.ip_local_port_range = 1024 65000

net.core.rmem_default = 4194304

net.core.rmem_max = 4194304

net.core.wmem_default = 262144

net.core.wmem_max = 262144

----- To change the current values of the kernel parameters

# /sbin/sysctl -p

----- Make sure that the parameters and values in /etc/system file are set properly

# cat /etc/sysctl.conf

----- Check and set the following lines in the /etc/security/limits.conf file.

Note: Take a back up of this file before changing the values and parameters.

# cp –p /etc/security/limits.conf /etc/security/limits.conf.old

oracle soft nproc 2047

oracle hard nproc 16384

oracle soft nofile 1024

oracle hard nofile 65536

----- Add or edit the following line in the /etc/pam.d/login file, if it does not already exist

Note: Take a back up of this file before changing the values and parameters.

# cp –p /etc/pam.d/login /etc/pam.d/login .old

session required /lib/security/pam_limits.so

session required pam_limits.so

* Configuring the Oracle User’s Environment

----- Check and change the contents of .profile or .lgoin files.

$ vi .bash_profile

----- Remove the oracle environment variables set already.

----- Check the DISPLAY variable is set, if not, then set the variable.

$ echo $DISPLAY$ DISPLAY=:0.0

$ export DISPLAY

Su – rootPassword: xxxx ( Enter the root password here)

# xhost +

----- Make sure that xclock command is running

$ xlcok

*Installation of Oracle Software:

------- Login as oracle on the server

Su – oraclePassword: xxxxx (Oracle user password)

------- Go the directory where Oracle software is staged.

$ cd /u01/11gStage

------------ Unzip the software file

$ unzip linux_11gR1_database.zip

------------- Run/Launch the runinstaller

$ cd /u02/11gStage/database

$./.runInstaller

* Answer to the subsequent wizards or screens options with the proper information

*At the end of Installation you will get two scripts , run this scripts as 'root' user "/u01/app/oracle/product/11.1.0/db_1/root.sh" and

"/u01/app/oraInventory/orainstRoot.sh"

Conclusion:

I have followed the above series of steps for installing on one of Linux boxes. I would request and suggest them to go through the referenced links below, who are willing to do this with other options during the installation and as per their requirement.
References:
Oracle Database Installation Guide 11g Release 1 (11.1) for Linux
http://download.oracle.com/docs/cd/B28359_01/install.111/b32002/pre_install.htm#CHDHFGBJ
Installing Oracle Database 11g on Linux
http://www.oracle.com/technology/obe/11gr1_db/install/dbinst/dbinst.htm
Oracle 11g Documentations
http://www.oracle.com/pls/db111/homepage
Others:
http://www.datasoftech.com/library.html
****** Your suggestions and comments are welcomed. ******

Saturday, July 25, 2009

Cloning an Oracle 10g Database Using RMAN in an ASM Environment

Dear Friends,
Using RMAN I have cloned an Oracle 10g ASM Database successfully. I would like to share the steps that I followed during this process.
For understanding, Suppose that the actual database name is ASMDB and I am going to clone database with a different name like CLNDB.
*If the platform is Windows Operating System then first create a new Oracle Service Instance for clone Database (clndb).

C:\> oradim -new -sid clndb
Instance created
.

*Create Password file for clone database for remote logging purpose
D:\oracle\product\10.2.0\db_1\database>orapwd file=pwdCLNDB.ora password=xxxxxxx
(If the Operating System is Linux then the location for creating password file is /u01/oracle/product/10.2.0/db_1/dbs )

*After creating Oracle Service Instance and Password file you need to configure an Initialization parameter file for cloning database
For this you just copy Initialization parameter file of Actual database and configure accordingly or create an initialization parameter file with similar setting.
d:\oracle\product\10.2.0\db_1\database>copy initASMDB.ora initCLNDB.ora
1 file(s) copied.
d:\oracle\product\10.2.0\db_1\database>notepad initCLNDB.ora

*Create directory for destination files ADUMP, BDUMP , CDUMP ,UDUMP.
d:\oracle\product\10.2.0\db_1\admin>mkdir CLNDB
d:\oracle\product\10.2.0\db_1\admin>cd CLNDB
d:\oracle\product\10.2.0\db_1\admin\CLNDB>mkdir ADUMP BDUMP CDUMP UDUMP

*Configure clone database entries in Listener.ora file which locates in ORACLE_HOME/network/admin/listener.ora
d:\oracle\product\10.2.0\db_1\network\ADMIN>notepad listener.ora

*Configure tnsnames entry on clone database side.
d:\oracle\product\10.2.0\db_1\network\ADMIN>notepad tnsnames.ora

*Check both side for whether the network connection established successfully..
d:\oracle\product\10.2.0\db_1\network\ADMIN>LSNRCTL RELOAD
LSNRCTL for 32-bit Windows: Version 10.2.0.3.0 - Production on 10-JUL-2009 18:44:41
Copyright (c) 1991, 2006, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=alinmabank-PC)(PORT=1521)))
The command completed successfully
d:\oracle\product\10.2.0\db_1\network\ADMIN>LSNRCTL STATUS
LSNRCTL for 32-bit Windows: Version 10.2.0.3.0 - Production on 10-JUL-2009 18:44:49
Copyright (c) 1991, 2006, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=alinmabank-PC)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias LISTENER
Version TNSLSNR for 32-bit Windows: Version 10.2.0.3.0 - Production
Start Date 10-JUL-2009 18:20:07
Uptime 0 days 0 hr. 24 min. 42 sec
Trace Level off
Security ON: Local OS Authentication
SNMP OFF
Listener Parameter File d:\oracle\product\10.2.0\db_1\network\admin\listener.ora
Listener Log File d:\oracle\product\10.2.0\db_1\network\log\listener.log
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=alinmabank-PC)(PORT=1521)))
Services Summary...
Service "ASMDB" has 1 instance(s).
Instance "ASMDB", status UNKNOWN, has 1 handler(s) for this service...
Service "CLNDB" has 1 instance(s).
Instance "CLNDB", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

*Now it’s the time to go with RMAN for cloning the database.
Start the oracle service for Actual database.
d:\oracle\product\10.2.0\admin\CLNDB>net start oracleserviceasmdb
The OracleServiceASMDB service is starting.........
The OracleServiceASMDB service was started successfully.

*Set oracle_sid=asmdb
d:\oracle\product\10.2.0\admin\CLNDB>set oracle_sid=asmdb

*Connect the target database as well as auxiliary database at a time using RMAN
The Auxiliary database is nothing but the clone database

d:\oracle\product\10.2.0\admin\CLNDB>rman target / auxiliary sys/xxxx@clndb
Recovery Manager: Release 10.2.0.3.0 - Production on Fri Jul 10 18:54:07 2009
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: ASMDB (DBID=435026396)
connected to auxiliary database: CLNDB (not mounted)

*Take a complete database level backup of the database. Here I used a different disk group for backup my database , else the backup goes to Flash Recovery Area location (FRA) by default.
RMAN> backup database format '+bkpdisk';
Starting backup at 10-JUL-09
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=132 devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=+DATA/asmdb/datafile/system.256.690827499
input datafile fno=00003 name=+DATA/asmdb/datafile/sysaux.257.690827499
input datafile fno=00005 name=+DATA/asmdb/datafile/example.265.690827669
input datafile fno=00002 name=+DATA/asmdb/datafile/undotbs1.258.690827501
input datafile fno=00006 name=+DATA/asmdb/datafile/data01.dbf
input datafile fno=00004 name=+DATA/asmdb/datafile/users.259.690827501
channel ORA_DISK_1: starting piece 1 at 10-JUL-09
channel ORA_DISK_1: finished piece 1 at 10-JUL-09
piece handle=+BKPDISK/asmdb/backupset/2009_07_10/nnndf0_tag20090710t232555_0.265.691889161 tag=TAG20090710T232555 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:01:55
Finished backup at 10-JUL-09
Starting Control File Autobackup at 10-JUL-09
piece handle=+FRA/asmdb/autobackup/2009_07_10/n_691889270.257.691889273 comment=NONE
Finished Control File Autobackup at 10-JUL-09

*Here I have already configured automatic backup of Controlfile which backups up Controlfile as well as Spfile whenever the modification are done in database.
Now use DUPLICATE TARGET DATABASE command to clone the database, It is the only one command that makes everything for cloning.
Obviously it is really important step that should not forget
.
RMAN> duplicate target database to clndb;
Starting Duplicate Db at 10-JUL-09
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=156 devtype=DISK
contents of Memory Script:
{
set until scn 686765;
set newname for clone datafile 1 to new;
set newname for clone datafile 2 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 4 to new;
set newname for clone datafile 5 to new;
set newname for clone datafile 6 to new;
restore
check readonly
clone database
;
}
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 10-JUL-09
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backupset restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to +DATA
restoring datafile 00002 to +DATA
restoring datafile 00003 to +DATA
restoring datafile 00004 to +DATA
restoring datafile 00005 to +DATA
restoring datafile 00006 to +DATA
channel ORA_AUX_DISK_1: reading from backup piece +BKPDISK/asmdb/backupset/2009_07_07/nnndf0_tag20090707t210710_0.264.691621633
channel ORA_AUX_DISK_1: restored backup piece 1
piece handle=+BKPDISK/asmdb/backupset/2009_07_07/nnndf0_tag20090707t210710_0.264.691621633 tag=TAG20090707T210710
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:06
Finished restore at 10-JUL-09
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CLNDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 SIZE 50 M ,
GROUP 2 SIZE 50 M ,
GROUP 3 SIZE 50 M
DATAFILE
'+DATA/clndb/datafile/system.275.691890537'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
{
switch clone datafile all;
}
executing Memory Script
released channel: ORA_AUX_DISK_1
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=691890658 filename=+DATA/clndb/datafile/undotbs1.283.691890537
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=691890658 filename=+DATA/clndb/datafile/sysaux.276.691890537
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=691890658 filename=+DATA/clndb/datafile/users.286.691890537
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=691890658 filename=+DATA/clndb/datafile/example.280.691890537
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=691890658 filename=+DATA/clndb/datafile/data.287.691890537
contents of Memory Script:
{
set until scn 686765;
recover
clone database
delete archivelog
;
}
executing Memory Script
executing command: SET until clause
Starting recover at 10-JUL-09
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: sid=152 devtype=DISK
starting media recovery
archive log thread 1 sequence 7 is already on disk as file +DATA/asmdb/arc00007_0690827617.001
archive log filename=+DATA/asmdb/arc00007_0690827617.001 thread=1 sequence=7
media recovery complete, elapsed time: 00:00:10
Finished recover at 10-JUL-09
contents of Memory Script:
{
shutdown clone;
startup clone nomount ;
}
executing Memory Script
database dismounted
Oracle instance shut down
connected to auxiliary database (not started)
Oracle instance started
Total System Global Area 612368384 bytes
Fixed Size 1292036 bytes
Variable Size 171968764 bytes
Database Buffers 432013312 bytes
Redo Buffers 7094272 bytes
sql statement: CREATE CONTROLFILE REUSE SET DATABASE "CLNDB" RESETLOGS ARCHIVELOG
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
MAXINSTANCES 8
MAXLOGHISTORY 292
LOGFILE
GROUP 1 SIZE 50 M ,
GROUP 2 SIZE 50 M ,
GROUP 3 SIZE 50 M
DATAFILE
'+DATA/clndb/datafile/system.275.691890537'
CHARACTER SET WE8MSWIN1252
contents of Memory Script:
{
set newname for clone tempfile 1 to new;
switch clone tempfile all;
catalog clone datafilecopy "+DATA/clndb/datafile/undotbs1.283.691890537";
catalog clone datafilecopy "+DATA/clndb/datafile/sysaux.276.691890537";
catalog clone datafilecopy "+DATA/clndb/datafile/users.286.691890537";
catalog clone datafilecopy "+DATA/clndb/datafile/example.280.691890537";
catalog clone datafilecopy "+DATA/clndb/datafile/data.287.691890537";
switch clone datafile all;
}
executing Memory Script
executing command: SET NEWNAME
renamed temporary file 1 to +DATA in control file
cataloged datafile copy
datafile copy filename=+DATA/clndb/datafile/undotbs1.283.691890537 recid=1 stamp=691891216
cataloged datafile copy
datafile copy filename=+DATA/clndb/datafile/sysaux.276.691890537 recid=2 stamp=691891216
cataloged datafile copy
datafile copy filename=+DATA/clndb/datafile/users.286.691890537 recid=3 stamp=691891216
cataloged datafile copy
datafile copy filename=+DATA/clndb/datafile/example.280.691890537 recid=4 stamp=691891216
cataloged datafile copy
datafile copy filename=+DATA/clndb/datafile/data.287.691890537 recid=5 stamp=691891217
datafile 2 switched to datafile copy
input datafile copy recid=1 stamp=691891216 filename=+DATA/clndb/datafile/undotbs1.283.691890537
datafile 3 switched to datafile copy
input datafile copy recid=2 stamp=691891216 filename=+DATA/clndb/datafile/sysaux.276.691890537
datafile 4 switched to datafile copy
input datafile copy recid=3 stamp=691891216 filename=+DATA/clndb/datafile/users.286.691890537
datafile 5 switched to datafile copy
input datafile copy recid=4 stamp=691891216 filename=+DATA/clndb/datafile/example.280.691890537
datafile 6 switched to datafile copy
input datafile copy recid=5 stamp=691891217 filename=+DATA/clndb/datafile/data.287.691890537
contents of Memory Script:
{
Alter clone database open resetlogs;
}
executing Memory Script
database opened
Finished Duplicate Db

Please, feel free to leave a comment on this Post.

Wednesday, June 24, 2009

HOW TO CHANGE DATABASE NAME USING ORACLE NID UTILITY
====================================================


Here are the simple steps
how I changed the name of one our databases from CLNDB to CLNDBNEW
***********************************************************************

1.Set the database in MOUNT state
**********************************


CLNDB@SYS>STARTUP MOUNT

2.Go to OS level , glance on NID options
****************************************

d:\oracle\product\10.2.0\db_1\database>NID

DBNEWID: Release 10.2.0.3.0 - Production on Sun Jun 7 18:00:21 2009

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Keyword Description (Default)
----------------------------------------------------
TARGET Username/Password (NONE)
DBNAME New database name (NONE)
LOGFILE Output Log (NONE)
REVERT Revert failed change NO
SETNAME Set a new database name only NO
APPEND Append to output log NO
HELP Displays these messages NO

d:\oracle\product\10.2.0\db_1\database>NID TARGET=sys/syssys dbname=clndbnew setname=y

DBNEWID: Release 10.2.0.3.0 - Production on Sun Jun 7 18:07:31 2009

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connected to database CLNDB (DBID=770789742)

Connected to server version 10.2.0

Control Files in database:
D:\ORACLE\ORADATA\CLNDB\CONTROL1.CTL
D:\ORACLE\ORADATA\CLNDB\CONTROL2.CTL

Change database name of database CLNDB to CLNDBNEW? (Y/[N]) =>Y
Proceeding with operation
Changing database name from CLNDB to CLNDBNEW
Control File D:\ORACLE\ORADATA\CLNDB\CONTROL1.CTL - modified
Control File D:\ORACLE\ORADATA\CLNDB\CONTROL2.CTL - modified
Datafile D:\ORACLE\ORADATA\CLNDB\SYSTEM1.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\UNDOTBS1.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\SYSAUX1.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\LMTS.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\LMTSU.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\SSMA.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\SSMM.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\BIG.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\USERS01.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\ONE.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\TWO.DBF - wrote new name
Datafile D:\ORACLE\ORADATA\CLNDB\TEMP2.DBF - wrote new name
Control File D:\ORACLE\ORADATA\CLNDB\CONTROL1.CTL - wrote new name
Control File D:\ORACLE\ORADATA\CLNDB\CONTROL2.CTL - wrote new name
Instance shut down

Database name changed to CLNDBNEW.
Succesfully changed database name.
DBNEWID - Completed succesfully.

Modify parameter file name to new name
**************************************

d:\oracle\product\10.2.0\db_1\database>rename initclndb.ora initclndbnew.ora

d:\oracle\product\10.2.0\db_1\database>edit initclndbnew.ora

----- change the parameter db_name='clndb' to 'clndbnew'

generate a new password file before restarting
**********************************************


d:\oracle\product\10.2.0\db_1\database>orapwd file=pwdclndbnew.ora password=syssys

Set New Oracle SID
******************

d:\oracle\product\102~1.0\db_1\database>set oracle_sid=clndbnew

Set New Instance At OS level
****************************


d:\oracle\product\102~1.0\db_1\database>oradim -new -sid clndbnew
Instance created.

Connect to Oracle
*****************


d:\oracle\product\102~1.0\db_1\database>sqlplus / as sysdba

clndbnew@SYS>startup mount
ORACLE instance started.

Total System Global Area 524288000 bytes
Fixed Size 1291576 bytes
Variable Size 268438216 bytes
Database Buffers 247463936 bytes
Redo Buffers 7094272 bytes
Database mounted.

clndbnew@SYS>alter system open resetlogs;

clndbnew@SYS>select name from v$database;

NAME
---------
CLNDBNEW

Please leave your comments, if this post helps you.

Regards,
Shafiulla Syed.

My First Post

Hi,
This is my first post in this blog.

Oracle RAC node unavailable with error: Server unexpectedly closed network connection6]clsc_connect: (0x251c670) no listener at (ADDRESS=(PROTOCOL=ipc)(KEY=OCSSD_LL_node2_))

 Early midnight I received a call from the monitoring team that one of the critical production database node is not available. As I am aware...