Articles Comments

Headline

11gR2: CVU needs SCAN Listeners’ Manual Startup During Grid-Infrastructure Configuration

February 21st, 2010 | 2 Comments

During configuration phase of Grid Infrastructure for cluster, CVU failed while performing post-checks. Following message is displaced in the Installation Log file: Checking Single Client Access Name (SCAN)... WARNING: PRVF-5056 : Scan Listener "LISTENER" not running Checking name resolution setup for "scan-test.abc.com"... Verification of SCAN VIP and Listener setup failed The LISTENER from Grid Infrastructure home is running fine: $ ps -eaf | grep tns /u01/app/grid_11.2/GridInfra/bin/tnslsnr LISTENER -inherit Same error is observerd by manually runnig CVU as: $ cluvfy comp scan Verifying scan Checking Single Client Access Name (SCAN)... WARNING: PRVF-5056 : Scan Listener "LISTENER" not running Checking name resolution setup for "scan-test.abc.com"... Verification of SCAN VIP and Listener setup failed Verification of scan was unsuccessful on all the specified nodes. Checking the status of SCAN using SRVCTL gives correct results: $ srvctl config scan SCAN name: scan-test.abc.com, Network: 1/165.101.124.0/255.255.254.0/eth0 SCAN VIP name: scan1, IP: /scan-test.abc.com/165.101.125.204 SCAN VIP name: scan2, IP: /scan-test.abc.com/165.101.125.235 SCAN VIP … Read entire article »

Latest

How To Discover Disk Name When LUN Number is Known (OEL5)

I am creating 11gR2 RAC setup for one of my client. Following Oracle documentation for storage, I opted for Oracle ASM and asked storage team for new physical devices. Storage admin thus provided me with a set of LUNs instead of actual physical device names like /dev/sdcxxx. Now the major task is to get the actual device name associated with LUNs. In OEL4 this is easy to get by issuing # iscsi-ls -l This command will give output like: DEVICE DETAILS: --------------- LUN ID : 0 Vendor: DELL Model: MD3000i Rev: 0670 Type: Direct-Access … Read entire article »

Cluvfy Reports CRS not Installed on Nodes

Cluvfy Reports CRS not Installed on Nodes

Before I start my post, I would like to wish all our readers a “Happy New Year”. While reviewing a 10gR2 RAC configuration I faced following errors on invoking cluvfy utility $ ./cluvfy stage -post crsinst -n prod01,prod02 -verbose Performing post-checks for cluster services setup Checking node reachability... Check: Node reachability from node "prod01-fe" Destination Node … Read entire article »

Life Is Changed Now!!!!!

Life Is Changed Now!!!!!

Hi All, This time I am sharing an experience from my personal life, I got Married on 2nd Dec 2009 I was on holidays since last month and just joined back. In this time I visited beautiful Island of Koh-Samui (Thailand). At this time finding hard to concentrate on work Cheers!!! Saurabh Sood … Read entire article »

11gR2: Steps to Rename ASM Diskgroup with DB files

11gR2: Steps to Rename ASM Diskgroup with DB files

11gR2 introduced renamedg utility to rename diskgroups. I would discuss renaming a diskgroup on a Standalone Grid Infrastructure installation with Oracle Restart. Before you use the command, ensure that ASM diskgroup is dismounted. Below is syntax for the command. You can refer to 11gR2 docs for details renamedg [phase={ one|two |both } ] dgname=diskgroup newdgname=newdiskgroup [config=configfile] [ asm_diskstring=discoverystring, discoverystring ... ] [ clean={true|false} ] [ check={true|false} ] [ … Read entire article »

11gR2 – SysAsm vs SysDba

SYSASM role was introduced in 11gR1 and was designed to administer ASM instances. In 11gR1 , if you connected with SYSDBA role , you used to get a warning which was only recorded in alert log (Refer to my earlier post here). But things have changed in 11gR2. While trying to dismount a Diskgroup, I found following errors SQL> alter diskgroup flash_arc mount; alter diskgroup flash_arc mount * ERROR at line 1: ORA-15032: not all alterations performed ORA-15260: permission denied on ASM disk group Above error indicates that I do not have permission on the ASM Diskgroup.  As per 11gR2 documentation, SYSASM privilege is used for carrying out administration tasks on ASM Diskgroups. SYSDBA privilege can be used only for creating/deleting aliases and … Read entire article »

Next Page »