Thursday, October 31, 2013

Netbackup Oracle DB backup failing with error 6

Today we have faced a backup failure of a Oracle DB and later was able to fix the issue following the steps below.

Error
--------
RMAN-00554: initialization of internal recovery manager package failed
RMAN-04004: error from recovery catalog database: ORA-12516: =
TNS:listener could not find available handler with matching protocol =
stack
------
ERROR : ORA-12516: TNS:listener could not find available handler with matching protocol stack

CAUSE : One of the most common reasons for the TNS-12516 and/or TNS-12519 errors being reported is the configured maximum number of PROCESSES and/or SESSIONS limitation being reached. When this occurs, the service handlers for the TNS listener become "Blocked" and no new connections can be made.

SOLUTION :
----------------
1.Check maximum value for processes and sessions using below command :
select name, value from v$parameter where name in (‘processes’,'sessions’);

2.Check current process and session and maximum limitation using below command :
select * from v$resource_limit;

3. Increase your process and session, for example to 300 using below command :
alter system set processes=300 scope=spfile;
alter system set sessions=300 scope=spfile;

4. You need to restart database to take effect.

Tuesday, October 29, 2013

Netapp Additional Information from the version 7.3.1.1 onwards

Right from Data ONTAP 7.3.1.1 additional information was added to the sysconfig command for the Storage Configuration.


Possible System Storage Configurations:

Single-Path          All storage in system is single-pathed
Mixed-Path          Some storage is single-pathed, some is multi-pathed
Multi-Path             All storage in system is multi-pathed
Single-Path HA   All storage in this system is single-pathed
Mixed-Path HA    Some storage is single-pathed, some is multi-pathed
Multi-Path HA      All storage is multi-pathed

Ex:-  FAS01> sysconfig
NetApp Release 8.1.1 7-Mode:
System ID: 80093278468 (FAS01); partner ID: 80090494093(FAS02)
System Serial Number: 4000201034 (test1)
System Rev: F6
System Storage Configuration:  Multi-Path HA

Monday, October 28, 2013

Ease your daily work with Netapp's new work flow automation (WFA)

OnCommand Workflow Automation (WFA) is a software solution that helps to automate storage
management tasks such as provisioning, migration, decommissioning, and cloning storage. You can
use WFA to build workflows to complete tasks specified by your processes.
A workflow is a repetitive and procedural task that consists of sequential steps, including the
following types of tasks:

• Provisioning, migrating, or decommissioning storage for databases or file systems
• Setting up a new virtualization environment, including storage switches and datastores
• Setting up storage for an application as part of an end-to-end orchestration process
Storage architects can define workflows to follow best practices and meet organizational
requirements, such as the following:
• Using required naming conventions
• Setting unique options for storage objects
• Selecting resources
• Integrating internal configuration management database (CMDB) and ticketing applications

WFA features

WFA includes the following features:
• Designer portal to build workflows
The designer portal includes several building blocks such as commands, templates, finders,
filters, and functions that are used to create workflows. The designer enables workflows to
include advanced capabilities such as automated resource selection, row repetition (looping), and approval points.
• Execution portal to execute workflows, verify status of workflow execution, and access logs
• Administration portal for tasks such as setting up WFA, connecting to data sources, and
configuring user credentials
• Web services interfaces to invoke workflows from external portals and data center orchestration software.

Also Refer to :- 
https://communities.netapp.com/community/products_and_solutions/storage_management_software/workflow-automation

Netapp Performance Limits to achieve better performance

To Achieve better performance Please make sure your filer was under the below threshold limits               

Filer Threshold                                                                                                                             


Volume Threshold                                                                                                                      

  

      Protocol Latency limits


Exchange Server Thresholds                                                                                                      
                                                                               

SQL Threshold Values                                                                                                                 

                            

      ORACLE Threshold values