ANS1126E (RC27) The file space cannot be deleted because this node does not have permission to delete archived or backed up data.

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of delete command on ORA_MAINT_SBT_TAPE_1 channel at 11/13/2014 12:32:22
ORA-19509: failed to delete sequential file, handle="ntpnen1m_1_1", parms=""
ORA-27027: sbtremove2 returned error
ORA-19511: Error received from media manager layer, error text:
   ANS1126E (RC27)   The file space cannot be deleted because this node does not have
permission to delete archived or backed up data.

The above error has happened in the during running delete obsolete command in the rman.

The reason :
=============
We had rman configured to tape in one server(for ex. 192.18.1.1), where the repository holds the backup information that has taken to tape.

but we had moved the database from 192.18.1.1 to 192.18.1.2 server using rman backup, where we tried to clear the rman repository using delete obsolete.

As new node has no delete permission to node filespace of 192.18.1.1 in tsm storage.


resolution:
============
We need to provide the delete permission to the new node.

Enter into tsm server and check the node name of 192.18.1.2 for eg: TsmnewNode

run the below tsm command to provide permission:

tsm>update node TsmnewNode backdel=y

then run the delete obsolete rman command to delete the rman repository catalog info.

Dynamic change of resources in AIX servers generates core dumps Error

Hi,
  
    We are observing core dump errors whenever we are increasing the cores or memory dynamically through HMC.

Example
 
    CORE FILE NAME
/u01/app/grid/log/ecdb1/crfmond/core
PROGRAM NAME
osysmond.bin
STACK EXECUTION DISABLED
           0
COME FROM ADDRESS REGISTER
??
PROCESSOR ID
  hw_fru_id: 0
  hw_cpu_id: 2

Cause

Case I:

AIX perfstat_disk() library call has some known issues and according to this, perfstat_disk() core dumps as per above call stack.


Case II:

The problem is caused by dynamic changing the number of CPUs. Currently it is not supported in osysmond.bin for dynamic change of configuration.
Solution

Case I:

These symptom are reported in Bug 16492284 and has been closed as a duplicate of unpublished base bug 14541391. This base bug has been fixed in version 12.1

Case II:

After changing any configuration like adding/deleting cpus/disks/network cards, restart the ora.crf resource:
1) stop the crf stack

    <GRID_HOME>/bin/crsctl stop res ora.crf -init

2) Start the crf stack

    <GRID_HOME>/bin/crsctl start res ora.crf -init

There is neither CRS nor database downtime required for above ora.crf start/stop operation as recommended by oracle support.

Reference: Oracle Support Knowledge Base

Possibly Best options for generating nmon reports in AIX 6.1

Hi,

  Here are some tips for generating nmon reports.

/usr/bin/topas_nmon -AdfPtV^ -s 30 -c 2880
/usr/bin/topas_nmon -f -t -d -A -O -L -N -P -V -T -^ -s 60 -c 1440


A--Summarizes the Async I/O (AIO server) processes.
d--Displays the I/O information of disks.
f--Specifies that the output is in spreadsheet format
P--Includes the Paging Space section in the recording file.
t--Includes the top processes in the output
V--ncludes disk volume group section.
^--Includes the Fibre Channel (FC) sections.
n--network statistics
c--processor statistics on bar graphs

Adding A LUN from SAN to AIX

Hi Guys,
      Here is an article for you that best describes how you can add a LUN to a AIX machine.
There is no wonder in doing this. As AIX can only be installed on Power Servers and Power Servers are very high cost so small scale companies avoid to have it. But it's power of processing and robustness is remarkable. I am lucky to have an experience on it. In fact I got few training from IBM on AIX administration and Trouble shooting.

1.       Create a  LUN of required size in storage using storage Manager.

2.       Map that LUN to   required hostgroup or host.

3.       Connect to host machine.

4.     run  cfgmgr in root #cfgmgr

5.       #lspv

PVName                PVID             VGName           Status

hdisk0          00f6fed9834f5f14                    rootvg           active

hdisk1          00f6fed9a6e670fa                    datavg          active

hdisk2           none                                          none            none

                                                                                               

6.       #chdev -l hdisk2 -a pv=yes to create a PVID on the disk

     PVName                PVID                VGName        StatuS

     hdisk0          00f6fed9834f5f14              rootvg          active

             hdisk1          00f6fed9a6e670fa             datavg          active

              hdisk2                         id                       none            active

                           

                           or 

 Instead of using above procedure you can also directly go for step-7

7.       We need to assign that harddisk to volumegroup.

If volume group(VG)  is already is there then we can assign that harddisk to that particular VG

#extend  -f  vgname  hdiskn

                                                          (or)

Create a volume group by #smitty  mkvg

o/p:

     hdisk0          00f6fed9834f5f14                    rootvg           active

             hdisk1          00f6fed9a6e670fa                    datavg          active

             hdisk2                   id                                   datavg           active

8.   Then we need to create a logical volume.

     We can create through #smitty mklv

         (or)

 We can create a filesystem   with default  lv  by using the following command;

       #crfs    –v  jfs2  –g  datavg  –a  size=298G  -A  yes  –m   /u03

9.   TO assign pp   Smitty chlv

10.   Lsv g  –l  vgname

11.     TO assign pp s to  chfs –a size=+2G  /u03

12.   Mount /u03