The best of all worlds –> Dell EMC Ready Solution for Oracle (Part III)

In the last two blogs viz. Part I and Part II, I was talking about the oracle solution that was running on the DELLEMC VMAX storage along with many other components. In this blog, I will talk about one more oracle solution that is running on the top of the XtremIO X2 storage, though there are some variations in the use cases here. Before we delve into the details of the solution architecture, I would like to emphasize here that the taxonomy got changed this time from “Ready Bundle” to “Ready Solution”. Now, let’s look into architecture diagram as depicted in Figure 1.


Figure 1: Ready Solutions for Oracle with XtremIO X2 and Data Protection

In this solution, the Oracle databases operated in three different mode. The first is the bare metal 2-node RAC database running on two PowerEdge R940 servers and the second consists of two standalone snapshot databases running on R740 standalone server created from the first category via XtremIO XVC (XtremIO Virtual Copies) while the third one is comprised of two standalone virtualized databases of 11g and 12c versions. The whole architecture depicted in Figure 1 is supported by 2 X-Bricks XtremIO X2 cluster array and backed up by the Data Domain 6300 appliance. The DELLEMC engineers have run a rigorous and diversified testing over this oracle solution (as shown in Figure 1) and generated good results. We will discuss about the results in this blog along with the details of different use cases performed in four tests as depicted in Figure 2. In the first test the objective is to create a simple, standalone 2-node RAC database on a bare metal infrastructure with 2 X-Bricks. This architecture is then enhanced to accommodate 2 snapshot databases (created via XVC from Test 1) and finally two different standalone virtualized databases are created one of 11g Rel 2 version & the other database is of 12c . The complete details of the test case 1, 2, 3 and 4 are depicted in Figure 2.


Figure 2: The details of the test case 1, 2, 3 and 4

Following the best practices of running oracle database on XtremIO platform, DELLEMC engineers generated good performance numbers which are depicted in Figure 3.


Figure 3: The performance numbers for Test 1,3,4

From Figure 3, we have observed that as we increase the workload in terms of OLTP and OLAP and in terms of different virtualized environments of 11g and 12c databases, the databases achieved higher IOPS and transactions per second (TPS) with sub-.85 milliseconds latencies. This is a spectacular performance keeping in view we used only 36 SSDs .


The Dell EMC Ready Solution for Oracle is an awesome solution with greater agility, operational efficiencies and resiliency in a single solution. Ready solutions for Oracle features like scalability, performance, consolidation, automation, centralized management and protection. So far as technical virtues of this solution is concerned, it has been internally tested which delivers fantastic results in terms of higher IOPS, transactions per second (TPS), bandwidth, scalability, consolidation along with consistent sub-millisecond (less than .85 milliseconds) latencies even after adding enhanced OLTP and OLAP workloads in a bare metal and virtualized environments. It helps companies to reduce typical company’s financial costs like its CAPEX and OPEX . Additionally, the Dell EMC R740/R940 Servers can sustain multiple and larger workloads with less CPU and memory utilization. When we talk of Dell EMC XtremIO X2 storage we observed that it has generated 131K+ IOPS (in-house) along with higher throughput and less than .85 millisecond latencies for mixed workloads. Repurposing copies generated by the XtremIO Virtual Copies(XVC) helps in 1.8X storage space savings due to the inline deduplication and compression features of XtremIO X2 arrays. In summary, the Dell EMC Ready solution for Oracle is a winning, integrated, validated, flexible and configurable solution in all aspects as it combines the best of all the worlds of a typical datacenter. In the next blog, we will continue discussing the good features of this solution along with the backup and recovery options.

Follow us on Twitter:


Tweet this document:

Want to learn about DELLEMC’s new oracle solution on XtremIO X2 array ? Click here –>

Click here to learn more:


  • No Related Posts

RMAN recovery throws error :’NSR_CLIENT’ was not specified

Oracle DB:

Networker: v9.2.1.0

RMAN> show channel;

RMAN configuration parameters for database with db_unique_name TEST are:


[oracle@halldbtest ~]$ rman target /

Recovery Manager: Release – Production on Tue Oct 16 10:26:23 2018

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.

connected to target database: TEST (DBID=2264480964)

RMAN> recover table scott.salgrade

until time “to_date(’16/10/2018 10:00:00′,’DD/MM/YYYY hh24:mi:ss’)”

auxiliary destination ‘/u01/temp’

remap table scott.salgrade:salgrade_bkp;

Starting recover at 16-OCT-18

using target database control file instead of recovery catalog current log archived

allocated channel: ORA_SBT_TAPE_1

channel ORA_SBT_TAPE_1: SID=1 device type=SBT_TAPE

channel ORA_SBT_TAPE_1: NMDA Oracle v9.2.1.0

allocated channel: ORA_SBT_TAPE_2

channel ORA_SBT_TAPE_2: SID=505 device type=SBT_TAPE

channel ORA_SBT_TAPE_2: NMDA Oracle v9.2.1.0

allocated channel: ORA_DISK_1

channel ORA_DISK_1: SID=624 device type=DISK

RMAN-05026: warning: presuming following set of tablespaces applies to specified point-in-time

List of tablespaces expected to have UNDO segments

Tablespace SYSTEM

Tablespace UNDOTBS1

Creating automatic instance, with SID=’elCb’

initialization parameters used for automatic instance:












#No auxiliary parameter file used

starting up automatic instance TEST

Oracle instance started

Total System Global Area 10066329600 bytes

Fixed Size 12169992 bytes

Variable Size 1644170488 bytes

Database Buffers 8388608000 bytes

Redo Buffers 21381120 bytes

Automatic instance created

contents of Memory Script:


# set requested point in time

set until time “to_date(’16/10/2018 10:00:00′,’DD/MM/YYYY hh24:mi:ss’)”;

# restore the controlfile

restore clone controlfile;

# mount the controlfile

sql clone ‘alter database mount clone database’;

# archive current online log

sql ‘alter system archive log current’;


executing Memory Script

executing command: SET until clause

Starting restore at 16-OCT-18

allocated channel: ORA_AUX_SBT_TAPE_1

channel ORA_AUX_SBT_TAPE_1: SID=169 device type=SBT_TAPE

channel ORA_AUX_SBT_TAPE_1: NMDA Oracle v9.2.1.0

allocated channel: ORA_AUX_SBT_TAPE_2

channel ORA_AUX_SBT_TAPE_2: SID=211 device type=SBT_TAPE

channel ORA_AUX_SBT_TAPE_2: NMDA Oracle v9.2.1.0

allocated channel: ORA_AUX_DISK_1

channel ORA_AUX_DISK_1: SID=251 device type=DISK

Removing automatic instance

shutting down automatic instance

Oracle instance shut down

Automatic instance removed

RMAN-00571: ===========================================================

RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============

RMAN-00571: ===========================================================

RMAN-03002: failure of recover command at 10/16/2018 10:27:07

RMAN-03015: error occurred in stored script Memory Script

ORA-27191: sbtinfo2 returned error

Additional information: 3620

ORA-19511: non RMAN, but media manager or vendor specific failure, error text:

The value of parameter ‘NSR_CLIENT’ was not specified. (9:13:11)

Any idea ? Thanks


Watch4net | EMC M&R: Procedure for migrating Custom Datastore tables/Fields to ElasticSearch

Article Number: 525584 Article Version: 2 Article Type: How To

Watch4Net Family,Watch4net,Service Assurance Suite

To migrate custom datastore tables and fields added in Watch4net versions 6.6u1 and earlier to Watch4net 6.8uX, the following procedure needs to be followed to migrate those tables to ElasticSearch:

1. Run and complete the upgrade to M&R 6.8u2.

2. Define the custom tables and fields in file event-database-reader.xml by navigating to path /Event-Processing/Event-Database-Migration/generic-traffic-flow/conf/

3. The “flow-database-migrate-V2toV3.ddl” script needs to be executed to convert v2 tables used in 6.6u1 to v3 tables used in M&R 6.8ux (please refer to pg. 479 of the SolutionPack articles for SAS 9.5.1. The section is titled ‘Upgrading Traffic Flows SolutionPack from 6.5u4 and 6.6u1 to 6.8u2’)

4. To finish transferring data, please follow the procedure outlined in knowledge base article #517393