NetApp - Databases

Have a blessed Thanksgiving

 

Hi my friends,

This is neto from Brazil

How are you?

As we go into this Thanksgiving holiday, take the time to reflect on all that we have for which to be thankful; a great company to work for, our families that love us unconditionally, our friends to make and share memories.

I wish you a healthy, happy and blessed Thanksgiving holiday.

All the best

neto

NetApp - I love this company!

Have a blessed Thanksgiving

Hi my friends,

This is neto from Brazil

How are you?

As we go into this Thanksgiving holiday, take the time to reflect on all that we have for which to be thankful; a great company to work for, our families that love us unconditionally, our friends to make and share memories.

I wish you a healthy, happy and blessed Thanksgiving holiday.

All the best

neto

NetApp - I love this company!

NEw Technology for enterprise APPlications - Introduction

 

Hi All,

This is neto from Brazil

How are you?

The purpose of this post is demonstrate and showing real examples from field of flexibility, powerful and robustness of New Technology for enterprise Applications Solutions versus Your Excellency, Mr. Complexity Solutions.

Excuses, Mr. Complexity, but could you please help me to understand which solutions do you have to execute a "remote clone" of an ASM disk group name for  a different host? (without requiring additional storage space) and of course supported by Oracle.

Net(App)O(racle) Solutions - using SnapManager for Oracle

Note: I have been using CLI to show exactly commands and steps for all readers. But the customer can use GUI to execute the same steps.

Production Server: mickey

Remote Server: minnie

 

SnapDrive Install

Production Node

[root@mickey ~]# rpm -ivh netapp.snapdrive.linux_4_0.rpm
Preparing...                ########################################### [100%]
   1:netapp.snapdrive       ########################################### [100%]

[root@mickey ~]# snapdrive config set root pernalonga
Password for root:
Retype password:

Remote Node

[root@minnie ~]# rpm -ivh netapp.snapdrive.linux_4_0.rpm
Preparing...                ########################################### [100%]
   1:netapp.snapdrive       ########################################### [100%]

[root@minnie ~]# snapdrive config set root pernalonga
Password for root:
Retype password:

 

SMO install

Production Node

[root@mickey ~]# ./netapp.smo.linux-x86-2.2.0.bin
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Preparing CONSOLE Mode Installation...

===============================================================================
SnapManager for Oracle            (created with InstallAnywhere by Macrovision)
-------------------------------------------------------------------------------

===============================================================================
Introduction
------------

InstallAnywhere will guide you through the installation of SnapManager for
Oracle, version 2.2.0

Respond to each prompt to proceed to the next step in the installation.  If you
want to change something on a previous step, type 'back'.

You may cancel this installation at any time by typing 'quit'.

PRESS <ENTER> TO CONTINUE:

===============================================================================

Enter Password for SnapManager for Oracle

To start the SnapManager for Oracle server on this host, the server password
must be set.  If you just press <ENTER>, no password will be set at this time.
However, you will need to set a password after installation by entering the
command "smo_server config -password ..." while logged in as root.

Please enter the password:*

Please reenter the same password:*

===============================================================================

Enter Operating System User Name and Group Name

Please enter the operating system user name and group name that should be used
to run SnapManager for Oracle commands.  Press <ENTER> to accept the default
values.

   User Name (DEFAULT: oracle):

   User Group (DEFAULT: dba):

===============================================================================
Configuration Summary
---------------------

Please review the following settings before continuing:

Installation directory (fixed location): /opt/NetApp/smo

User Id: oracle
User Group: dba
Server Password: <password must be set after installation>

PRESS <ENTER> TO CONTINUE:

===============================================================================
Installing...
-------------

[==================|==================|==================|==================]
[------------------|------------------|------------------|------------------]

===============================================================================
SnapManager for Oracle Configured Successfully

To start the server component of SnapManager for Oracle, perform the following
steps while logged in as root:
* Set the server password with command "smo_server config -password ...".
* Enter the command "smo_server start".

[root@mickey ~]# smo_server config -password netapp1
SMO-20021 [INFO ]: Successfully set password for SnapManager server running on "mickey:/opt/NetApp/smo".
SMO-20018 [INFO ]: Set password for host "mickey" in user credentials for "root".

[root@mickey ~]# smo_server start
SMO-17100 [INFO ]: SnapManager Server started on secure port 27214 with PID 26151.

 

Remote Node

[root@minnie ~]# ./netapp.smo.linux-x86-2.2.0.bin
Preparing to install...
Extracting the JRE from the installer archive...
Unpacking the JRE...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Preparing CONSOLE Mode Installation...

===============================================================================
SnapManager for Oracle            (created with InstallAnywhere by Macrovision)
-------------------------------------------------------------------------------

===============================================================================
Introduction
------------

InstallAnywhere will guide you through the installation of SnapManager for
Oracle, version 2.2.0

Respond to each prompt to proceed to the next step in the installation.  If you
want to change something on a previous step, type 'back'.

You may cancel this installation at any time by typing 'quit'.

PRESS <ENTER> TO CONTINUE:

===============================================================================

Enter Password for SnapManager for Oracle

To start the SnapManager for Oracle server on this host, the server password
must be set.  If you just press <ENTER>, no password will be set at this time.
However, you will need to set a password after installation by entering the
command "smo_server config -password ..." while logged in as root.

Please enter the password:*

Please reenter the same password:*

===============================================================================

Enter Operating System User Name and Group Name

Please enter the operating system user name and group name that should be used
to run SnapManager for Oracle commands.  Press <ENTER> to accept the default
values.

   User Name (DEFAULT: oracle):

   User Group (DEFAULT: dba):

===============================================================================
Configuration Summary
---------------------

Please review the following settings before continuing:

Installation directory (fixed location): /opt/NetApp/smo

User Id: oracle
User Group: dba
Server Password: <password must be set after installation>

PRESS <ENTER> TO CONTINUE:

===============================================================================
Installing...
-------------

[==================|==================|==================|==================]
[------------------|------------------|------------------|------------------]

===============================================================================
SnapManager for Oracle Configured Successfully

To start the server component of SnapManager for Oracle, perform the following
steps while logged in as root:
* Set the server password with command "smo_server config -password ...".
* Enter the command "smo_server start".

[root@minnie ~]# smo_server config -password netapp1
SMO-20021 [INFO ]: Successfully set password for SnapManager server running on "minnie:/opt/NetApp/smo".
SMO-20018 [INFO ]: Set password for host "minnie" in user credentials for "root".

[root@minnie ~]# smo_server start
SMO-17100 [INFO ]: SnapManager Server started on secure port 27214 with PID 12546.

 

SMO Credentials

Repository

Production Node

[oracle@mickey][prod][~]$ smo credential list
Credential cache for OS user "oracle":
Repositories:
Profiles:
Hosts:

[oracle@mickey][prod][~]$ smo credential set -repository -dbname repo -host minnie -port 1521 -login -username repo -password repo

[oracle@mickey][prod][~]$ smo credential list
Credential cache for OS user "oracle":
Repositories:
repo@repo/minnie:1521
Profiles:
Hosts:

 

Production Node

[oracle@mickey][prod][~]$ smo repository create -repository -port 1521 -dbname repo -host minnie -login -username repo -verbose
SMO-09202 [INFO ]: Creating new schema as repo on jdbc:oracle:thin:@//minnie:1521/repo.
SMO-09205 [INFO ]: Schema generation complete.
SMO-09209 [INFO ]: Performing repository version INSERT.
SMO-09210 [INFO ]: Repository created with version: 37
SMO-13048 [INFO ]: Repository Create Operation Status: SUCCESS
SMO-13049 [INFO ]: Elapsed Time: 0:00:25.100

Note: The REPO database has been located on the minnie server.

 

Profile

[oracle@mickey][app][~]$ smo credential set -host -name mickey -password netapp1
[oracle@mickey][app][~]$ smo credential list
Credential cache for OS user "oracle":
Repositories:
repo@repo/minnie:1521
Profiles:
Hosts:
mickey

[oracle@mickey][app][~]$ smo profile create -profile app -profile-password netapp1 -repository -dbname repo -host minnie -port 1521 -login -username repo -database -dbname app -host mickey -sid app -login -username sys -password oracle -port 1521 -rman -login -username rman -password rman -tnsname rman -osaccount oracle -osgroup dba -retain 100 -verbose
SMO-20020 [INFO ]: Set password for profile "app" in user credentials for "oracle".
SMO-13036 [INFO ]: Starting operation Profile Create on host mickey
SMO-13048 [INFO ]: Profile Create Operation Status: SUCCESS
SMO-13049 [INFO ]: Elapsed Time: 0:00:23.412
Operation Id [8a9bd4af1a213a03011a213a31a80006] succeeded.

 

Configuring RMAN

[oracle@mickey][app][~]$ $ORACLE_HOME/bin/rman catalog=rman/rman@rman target=sys/oracle@app

Recovery Manager: Release 11.1.0.6.0 - Production on Sun May 25 15:05:55 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.

connected to target database: APP (DBID=3779959199)connected to recovery catalog database

RMAN> register database;
database registered in recovery catalog
starting full resync of recovery catalog
full resync complete

RMAN> exit
Recovery Manager complete.

 

SMO Backup

[oracle@mickey][app][~]$ smo backup create -profile app -online -full -label snap1 -comment "NetApp Snapshots" -verbose
SMO-13046 [INFO ]: Operation GUID 8a9bd4af1a25b3b9011a25b3d8e00001 starting on Profile app
SMO-13505 [INFO ]: Snapdrive verification passed.
SMO-12136 [INFO ]: ORACLE_HOME "/oracle/app/product/11g/db_1" is version 11.1.0.6.0.
SMO-13506 [INFO ]: SQLPlus verification for database SID "app" passed.  Environment: [ORACLE_HOME=/oracle/app/product/11g/db_1]
SMO-12101 [INFO ]: Querying database version.
SMO-13507 [INFO ]: JDBC verification for "sys@app/mickey:1521" passed.
SMO-13509 [INFO ]: RMAN verification using catalog "rman" passed.
SMO-07127 [INFO ]: Locked database for SnapManager operations - created lock file "/oracle/app/product/11g/db_1/dbs/.sm_lock_app".
SMO-07431 [INFO ]: Saving starting state of the local database instance: OPEN.
SMO-07100 [INFO ]: Placing database "app" into online backup mode.
SMO-11104 [INFO ]: Locking Disk Group "+DATA".
SMO-08005 [INFO ]: Beginning snapshot with name smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0 for filesystem(s) [] and device(s) [/dev/sdb1, /dev/sdc1].
SMO-08020 [INFO ]: Querying for snapshot "pernalonga:/vol/asm_data:smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0".
SMO-08022 [INFO ]: Finished querying for snapshot "pernalonga:/vol/asm_data:smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0".
SMO-08006 [INFO ]: Created snapshot with name smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0 for filesystem(s) [] and device(s) [/dev/sdb1, /dev/sdc1].
SMO-07101 [INFO ]: Taking database "app" out of online backup mode.
SMO-07106 [INFO ]: Forcing log archival on database "app".
SMO-07107 [INFO ]: Backing up control file for database "app" to "+LOG/app/SMOBakCtl_1211813408335_0".
SMO-07107 [INFO ]: Backing up control file for database "app" to "+LOG/app/SMOBakCtl_1211813410382_1".
SMO-07107 [INFO ]: Backing up control file for database "app" to "+LOG/app/SMOBakCtl_1211813412401_2".
SMO-11104 [INFO ]: Locking Disk Group "+LOG".
SMO-08005 [INFO ]: Beginning snapshot with name smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0 for filesystem(s) [] and device(s) [/dev/sdd1].
SMO-08020 [INFO ]: Querying for snapshot "pernalonga:/vol/asm_log:smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0".
SMO-08022 [INFO ]: Finished querying for snapshot "pernalonga:/vol/asm_log:smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0".
SMO-08006 [INFO ]: Created snapshot with name smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0 for filesystem(s) [] and device(s) [/dev/sdd1].
SMO-07108 [INFO ]: Deleting backup control file "+LOG/app/SMOBakCtl_1211813408335_0".
SMO-07108 [INFO ]: Deleting backup control file "+LOG/app/SMOBakCtl_1211813410382_1".
SMO-07108 [INFO ]: Deleting backup control file "+LOG/app/SMOBakCtl_1211813412401_2".
SMO-08064 [INFO ]: Beginning to connect device(s) [/dev/sdc1, /dev/sdb1] from snapshot smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-08066 [INFO ]: Finished connecting device(s) [/dev/sdc1, /dev/sdb1] from snapshot smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-11145 [INFO ]: Creating mapping from disk "/dev/sdg1" to ASMLib disk "ORCL:SMO_1211813530962".
SMO-11116 [INFO ]: Changing ASM Disk Group name in header of cloned disk "/dev/sdg1" from "DATA" to "SMO_1_1211813477131".
SMO-11145 [INFO ]: Creating mapping from disk "/dev/sdf1" to ASMLib disk "ORCL:SMO_1211813532345".
SMO-11116 [INFO ]: Changing ASM Disk Group name in header of cloned disk "/dev/sdf1" from "DATA" to "SMO_1_1211813477131".
SMO-11121 [INFO ]: Mounting ASM Disk Group "+SMO_1_1211813477131".
SMO-08064 [INFO ]: Beginning to connect device(s) [/dev/sdd1] from snapshot smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-08066 [INFO ]: Finished connecting device(s) [/dev/sdd1] from snapshot smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-11145 [INFO ]: Creating mapping from disk "/dev/sdh1" to ASMLib disk "ORCL:SMO_1211813590656".
SMO-11116 [INFO ]: Changing ASM Disk Group name in header of cloned disk "/dev/sdh1" from "LOG" to "SMO_2_1211813541454".
SMO-11121 [INFO ]: Mounting ASM Disk Group "+SMO_2_1211813541454".
SMO-12101 [INFO ]: Querying database version.
SMO-07109 [INFO ]: Cataloguing all files in backup set with RMAN, TAG=SMO_snap1_1211813600260, RMAN=rman@rman/catalog.
SMO-11122 [INFO ]: Dropping ASM Disk Group "+SMO_2_1211813541454".
SMO-11146 [INFO ]: Removing mapping from disk "/dev/sdh1" to ASMLib disk "ORCL:SMO_1211813590656".
SMO-11122 [INFO ]: Dropping ASM Disk Group "+SMO_1_1211813477131".
SMO-11146 [INFO ]: Removing mapping from disk "/dev/sdg1" to ASMLib disk "ORCL:SMO_1211813530962".
SMO-11146 [INFO ]: Removing mapping from disk "/dev/sdf1" to ASMLib disk "ORCL:SMO_1211813532345".
SMO-08028 [INFO ]: Beginning to disconnect storage [/dev/sdh1].
SMO-08030 [INFO ]: Done disconnecting storage [/dev/sdh1].
SMO-08028 [INFO ]: Beginning to disconnect storage [/dev/sdg1, /dev/sdf1].
SMO-08030 [INFO ]: Done disconnecting storage [/dev/sdg1, /dev/sdf1].
SMO-11105 [INFO ]: Unlocking Disk Group "+LOG".
SMO-11105 [INFO ]: Unlocking Disk Group "+DATA".
SMO-07433 [INFO ]: Returning the local database instance to its initial state: OPEN.
SMO-07131 [INFO ]: Unlocked database for SnapManager operations - removed lock file "/oracle/app/product/11g/db_1/dbs/.sm_lock_app" on host mickey.
SMO-13048 [INFO ]: Backup Create Operation Status: SUCCESS
Operation Id [8a9bd4af1a25b3b9011a25b3d8e00001] succeeded.

 

SMO Remote Clone

Note: On the minnie server, will be necessary to have the following services:

FCP or iSCSI
SnapDrive
Oracle ASMLib
Oracle ASM instance

Here is the steps, in case the DBA doesn't have configured the services.

Remote Node

[oracle@mickey][app][~]$ smo credential set -host -name minnie -password netapp1
[oracle@mickey][app][~]$ smo credential list
Credential cache for OS user "oracle":
Repositories:
  repo@repo/minnie:1521
Profiles:
  APP (Repository: repo@repo/minnie:1521)
Hosts:
  minnie
  mickey

[root@minnie ~]# service 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 <ENTER> without typing an
answer will keep that current value.  Ctrl-C will abort.

Default user to own the driver interface []: oracle
Default group to own the driver interface []: dba
Start Oracle ASM library driver on boot (y/n) [n]: y
Fix permissions of Oracle ASM disks on boot (y/n) [y]: y
Writing Oracle ASM library driver configuration:           [  OK  ]
Loading module "oracleasm":                                [  OK  ]
Mounting ASMlib driver filesystem:                         [  OK  ]
Scanning system for ASM disks:                             [  OK  ]

[root@minnie~] /oracle/app/product/11g/db_1/bin/localconfig add
/etc/oracle does not exist. Creating it now.
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Configuration for local CSS has been initialized

Cleaning up Network socket directories
Setting up Network socket directories
Adding to inittab
Startup will be queued to init within 30 seconds.
Checking the status of new Oracle init process...
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
        minnie
Cluster Synchronization Services is active on all the nodes.
Oracle CSS service is installed and running under init(1M)

[oracle@minnie][prod][~]$ mkdir -p /oracle/app/admin/+ASM/bdump
[oracle@minnie][prod][~]$ mkdir -p /oracle/app/admin/+ASM/cdump
[oracle@minnie][prod][~]$ mkdir -p /oracle/app/admin/+ASM/udump
[oracle@minnie][prod][~]$ mkdir -p /oracle/app/admin/+ASM/pfile

[oracle@minnie][app][/oracle/app/admin/+ASM/pfile/]$ cat init+ASM.ora
instance_type='asm'
large_pool_size=12M
remote_login_passwordfile=exclusive

[oracle@minnie][app][~]$ orapwd file=$ORACLE_HOME/dbs/orapw+ASM password=oracle
[oracle@minnie][+ASM][~]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Mon May 26 16:34:08 2008

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

Connected to an idle instance.

SQL> startup
ASM instance started

Total System Global Area  284565504 bytes
Fixed Size                  1299428 bytes
Variable Size             258100252 bytes
ASM Cache                  25165824 bytes
ORA-15110: no diskgroups mounted

SQL> create spfile from pfile='/oracle/app/product/11g/db_1/dbs/init+ASM.ora';

File created.

SQL> quit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

[oracle@minnie][+ASM][~]$ cat /etc/oratab
repo:/oracle/app/product/11g/db_1:N
rman:/oracle/app/product/11g/db_1:N
+ASM:/oracle/app/product/11g/db_1:N

 

XML Config File

CLI: One example using XML config file from CLI

[oracle@mickey][app][~]$ cat clone-app.xml
<clone-specification xmlns="http://www.netapp.com">
  <database-specification>
    <controlfiles>
      <file>+CLONE/control01.ctl</file>
    </controlfiles>
    <redologs>
      <redogroup>
        <file>+CLONE/redo_1.log</file>
        <number>1</number>
        <size unit="M">50</size>
      </redogroup>
      <redogroup>
        <file>+CLONE/redo_2.log</file>
        <number>2</number>
        <size unit="M">50</size>
      </redogroup>
      <redogroup>
        <file>+CLONE/redo_3.log</file>
        <number>3</number>
        <size unit="M">50</size>
      </redogroup>
    </redologs>
    <parameters>
      <parameter>
        <name>log_archive_dest_1</name>
        <value>LOCATION=+CLONE/archive_logs</value>
      </parameter>
      <parameter>
        <name>memory_target</name>
        <value>256M</value>
      </parameter>
    </parameters>
    <oracle-home>/oracle/app/product/11g/db_1</oracle-home>
    <sql-statements/>
  </database-specification>
  <storage-specification>
    <storage-mapping>
      <asm-diskgroup>
        <source>+DATA</source>
        <destination>+CLONE</destination>
      </asm-diskgroup>
    </storage-mapping>
  </storage-specification>

GUI: One example generating XML config file from GUI

 

Production Node

[oracle@mickey][app][~]$ smo clone create -profile app -backup-label snap1 -newsid clone -clonespec clone-app.xml -reserve no -host minnie -label clone-snap1 -comment "NetApp FlexClone" -verbose
SMO-13046 [INFO ]: Operation GUID 8a9bd4ac1a26dbc2011a26dbcf420001 starting on Profile app
SMO-04030 [INFO ]: Validating uniqueness of new SID "clone".
SMO-04040 [INFO ]: Using ORACLE_HOME of "/oracle/app/product/11g/db_1" from clonespec for clone.
SMO-04041 [INFO ]: Using Oracle OS account "oracle" from backup for clone.
SMO-04043 [INFO ]: Using Oracle OS group "dba" from backup for clone.
SMO-07127 [INFO ]: Locked database for SnapManager operations - created lock file "/oracle/app/product/11g/db_1/dbs/.sm_lock_clone".
SMO-08064 [INFO ]: Beginning to connect device(s) [/dev/sdb1, /dev/sdc1] from snapshot smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-08066 [INFO ]: Finished connecting device(s) [/dev/sdb1, /dev/sdc1] from snapshot smo_app_app_f_h_1_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-11145 [INFO ]: Creating mapping from disk "/dev/sdc1" to ASMLib disk "ORCL:SMO_1211832818352".
SMO-11116 [INFO ]: Changing ASM Disk Group name in header of cloned disk "/dev/sdc1" from "DATA" to "CLONE".
SMO-11145 [INFO ]: Creating mapping from disk "/dev/sdb1" to ASMLib disk "ORCL:SMO_1211832820398".
SMO-11116 [INFO ]: Changing ASM Disk Group name in header of cloned disk "/dev/sdb1" from "DATA" to "CLONE".
SMO-11121 [INFO ]: Mounting ASM Disk Group "+CLONE".
SMO-08064 [INFO ]: Beginning to connect device(s) [/dev/sdd1] from snapshot smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-08066 [INFO ]: Finished connecting device(s) [/dev/sdd1] from snapshot smo_app_app_f_h_2_8a9bd4af1a25b3b9011a25b3d8e00001_0.
SMO-11145 [INFO ]: Creating mapping from disk "/dev/sdd1" to ASMLib disk "ORCL:SMO_1211832878791".
SMO-11116 [INFO ]: Changing ASM Disk Group name in header of cloned disk "/dev/sdd1" from "LOG" to "SMO_2_1211832828491".
SMO-11121 [INFO ]: Mounting ASM Disk Group "+SMO_2_1211832828491".
SMO-12126 [INFO ]: Adding entry for database "clone".
SMO-07300 [INFO ]: Beginning clone of database "app" to SID "clone" on host "minnie".
SMO-07302 [INFO ]: Generating parameter file for "clone" at "/oracle/app/product/11g/db_1/dbs/initclone.ora".
SMO-07303 [INFO ]: Generating password file for "clone" at "/oracle/app/product/11g/db_1/dbs/orapwclone".
SMO-07304 [INFO ]: Starting up database "clone" in NOMOUNT mode.
SMO-07305 [INFO ]: Generating control files for database "clone".
SMO-07312 [INFO ]: Create Control File - Database: clone.
SMO-07313 [INFO ]: Create Control File - Redolog: +CLONE/redo_2.log.
SMO-07313 [INFO ]: Create Control File - Redolog: +CLONE/redo_3.log.
SMO-07313 [INFO ]: Create Control File - Redolog: +CLONE/redo_1.log.
SMO-07314 [INFO ]: Create Control File - Datafile: +CLONE/app/undotbs01.dbf.
SMO-07314 [INFO ]: Create Control File - Datafile: +CLONE/app/system01.dbf.
SMO-07314 [INFO ]: Create Control File - Datafile: +CLONE/app/sysaux01.dbf.
SMO-07314 [INFO ]: Create Control File - Datafile: +CLONE/app/users01.dbf.
SMO-07306 [INFO ]: Generating server parameter file for database "clone" at Oracle default location.
SMO-07337 [INFO ]: Recovering database clone "clone" to a consistent point using archived logs from the backup.
SMO-07320 [INFO ]: Opening database "clone" with RESETLOGS option.
SMO-07316 [INFO ]: Shutting down database "clone".
SMO-07321 [INFO ]: Starting up database "clone" in MOUNT mode.
SMO-07307 [INFO ]: Generating new Database ID for "clone".
SMO-07308 [INFO ]: Opening database "clone".
SMO-11122 [INFO ]: Dropping ASM Disk Group "+SMO_2_1211832828491".
SMO-11146 [INFO ]: Removing mapping from disk "/dev/sdd1" to ASMLib disk "ORCL:SMO_1211832878791".
SMO-08028 [INFO ]: Beginning to disconnect storage [/dev/sdd1].
SMO-08030 [INFO ]: Done disconnecting storage [/dev/sdd1].
SMO-07131 [INFO ]: Unlocked database for SnapManager operations - removed lock file "/oracle/app/product/11g/db_1/dbs/.sm_lock_clone" on host minnie.
SMO-13048 [INFO ]: Clone Create Operation Status: SUCCESS
Operation Id [8a9bd4ac1a26dbc2011a26dbcf420001] succeeded.

Checking on Remote Node...

[oracle@minnie][+ASM][~]$ sid +ASM

[oracle@minnie][+ASM][~]$ asmcmd -p
ASMCMD [+] > lsdg
State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Name
MOUNTED  EXTERN  N         512   4096  1048576      2046      424                0             424              0  CLONE/
ASMCMD [+] > exit

[oracle@minnie][+ASM][~]$ sqlplus / as sysdba

SQL*Plus: Release 11.1.0.6.0 - Production on Mon May 26 17:20:25 2008

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

Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> set lines 1000
SQL> select GROUP_NUMBER, NAME, STATE, TYPE from v$asm_diskgroup;

GROUP_NUMBER NAME                           STATE       TYPE
------------ ------------------------------ ----------- ------
           1 CLONE                          MOUNTED     EXTERN

SQL> column NAME format a7
SQL> column LABEL format a20
SQL> column PATH format a23
SQL> select GROUP_NUMBER, DISK_NUMBER, NAME, LABEL, PATH from v$asm_disk;

GROUP_NUMBER DISK_NUMBER NAME    LABEL                PATH
------------ ----------- ------- -------------------- -----------------------
           1           1 DATA2   SMO_1211832818352    ORCL:SMO_1211832818352
           1           0 DATA1   SMO_1211832820398    ORCL:SMO_1211832820398

SQL> select * from v$instance;

INSTANCE_NUMBER INSTANCE_NAME    HOST_NAME                                                        VERSION           STARTUP_T STATUS    PAR    THREAD# ARCHIVE LOG_SWITCH_WAIT LOGINS     SHU DATABASE_STATUS   INSTANCE_ROLE      ACTIVE_ST BLO
--------------- ---------------- ---------------------------------------------------------------- ----------------- --------- ------------ --- ---------- ------- --------------- ---------- --- ----------------- ------------------ --------- ---
              1 +ASM             minnie                                                           11.1.0.6.0        26-MAY-08 STARTED           NO           0 STOPPED                 ALLOWED    NO  ACTIVE            UNKNOWN            NORMAL    NO

SQL> exit
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

Really, NetApp is the real New Technology for enterprise Applications Solutions compared with Your Excellency, Mr. Complexity Solutions.

All the best

neto

NetApp - My LIFE!

Populating an Oracle Database for Demo Purposes - Introduction

Hi All,

This is neto from Brazil

How are you?

Here one example how to populate an Oracle Database for Demo Purposes

Host

Oracle 11.1.0.6.0 and ASM

1 - Starting ASM instance

2 - Starting Oracle Database (APP)

3 - Creating a Tablespace (small for demo purposes)

4 - Creating a loader user

5 - Grants to loader user

6 - Creating a table

7 - Creating 1MB image file

8 - Creating configuration file

9 - Adding more lines to configuration file

10 - Checking how many lines in the configuration file

11- Script to check % space of the Tablespace

#!/bin/sh
#
# NetApp
#
# Authors:     Bob Smith, neto from Brazil
#                     Mike Doherty, Silviu Angelescu
#                     Greg Loughmiller, Dan Giannascoli
#
# Purpose:  Checking space on the tablespace
#
# Space disk report - version 0.1

while
true;
do
        clear;
        echo "NetApp";
        echo "Authors:  Bob Smith, neto from Brazil";
        echo "          Mike Doherty, Silviu Angelescu";
        echo "          Greg Loughmiller, Dan Giannascoli";
        echo -e "\n";
        echo "Purpose:  Checking space on the tablespace";
        echo -e "\n";
        echo "NetApp - Space Disk Report - version 0.1";
        echo -e "\n";
        echo "Generating Space Disk Report ...";
        sleep 5;

        sqlplus / as sysdba << EOF

                set pages 1000
                set lines 132
                set trims on
                col tablespace_name format a15            heading "Tablespace"
                col file_name       format a40            heading "Filename"
                col total_size      format 999,999.00     heading "Size MB"
                col free_space      format 999,999.00     heading "Free MB"
                col pct_used        format 999.00         heading "%|Used"

                clear breaks

                select df.tablespace_name
                ,      df.file_name
                ,      df.bytes/1024/1024                        total_size
                ,      nvl(fr.bytes/1024/1024,0)                 free_space
                ,      ((df.bytes-nvl(fr.bytes,0))/df.bytes)*100 pct_used
                from   (select sum(bytes) bytes
                ,      file_id
                from   dba_free_space
                group by file_id)     fr
                ,       dba_data_files        df
                where df.file_id = fr.file_id(+)
                order by 1, df.file_id
                /

EOF
sleep 5;
done

10 - Checking % space of Tablespaces (before running the loader)

11 - Populating ...

12 - Checking % space of Tablespaces (after running the loader)

All the best

neto

NetApp - My LIFE!