8a.) Since we are using Network Time Protocol (NTP) for synchronization of time across all the servers in the cluster, a mandatory requirement with 11gR2 is to enable the slewing option by adding ‘-x’ argument in the ntp configuration file as seen below: -# vi /etc/sysconfig/ntpd# Drop root to id 'ntp:ntp' by default.OPTIONS="-x -u ntp:ntp -p /var/run/ntpd.pid" #add -x in the options string.# Set to 'yes' to sync hw clock after successful ntpdateSYNC_HWCLOCK=no# Additional options for ntpdateNTPDATE_OPTIONS=""

Checking swap space: must be greater than 500 MB. Actual 12287 MB PassedThe inventory pointer is located at /etc/oraInst.locThe inventory is located at /oracle/oraInventory'UpdateNodeList' was successful.

Run the same on node2

[root@node2 11.2]# ./root.shRunning Oracle 11g root.sh script...

The following environment variables are set as: ORACLE_OWNER= oracle ORACLE_HOME= /oragrid/product/11.2

Enter the full pathname of the local bin directory: [/usr/local/bin]: Copying dbhome to /usr/local/bin ... Copying oraenv to /usr/local/bin ... Copying coraenv to /usr/local/bin ...

Creating /etc/oratab file...Entries will be added to the /etc/oratab file as needed byDatabase Configuration Assistant when a database is createdFinished running generic part of root.sh script.Now product-specific root actions will be performed.2010-08-27 23:44:15: Parsing the host name2010-08-27 23:44:15: Checking for super user privileges2010-08-27 23:44:15: User has super user privilegesUsing configuration parameter file: /oragrid/product/11.2/crs/install/crsconfig_paramsCreating trace directoryLOCAL ADD MODECreating OCR keys for user 'root', privgrp 'root'..Operation successful.Adding daemon to inittabCRS-4123: Oracle High Availability Services has been started.ohasd is startingCRS-4402: The CSS daemon was started in exclusive mode but found an active CSS daemon on node node1, number 1, and is terminatingAn active cluster was found during exclusive startup, restarting to join the clusterCRS-2672: Attempting to start 'ora.mdnsd' on 'node2'CRS-2676: Start of 'ora.mdnsd' on 'node2' succeededCRS-2672: Attempting to start 'ora.gipcd' on 'node2'CRS-2676: Start of 'ora.gipcd' on 'node2' succeededCRS-2672: Attempting to start 'ora.gpnpd' on 'node2'CRS-2676: Start of 'ora.gpnpd' on 'node2' succeededCRS-2672: Attempting to start 'ora.cssdmonitor' on 'node2'CRS-2676: Start of 'ora.cssdmonitor' on 'node2' succeededCRS-2672: Attempting to start 'ora.cssd' on 'node2'CRS-2672: Attempting to start 'ora.diskmon' on 'node2'CRS-2676: Start of 'ora.diskmon' on 'node2' succeededCRS-2676: Start of 'ora.cssd' on 'node2' succeededCRS-2672: Attempting to start 'ora.ctssd' on 'node2'CRS-2676: Start of 'ora.ctssd' on 'node2' succeededCRS-2672: Attempting to start 'ora.crsd' on 'node2'CRS-2676: Start of 'ora.crsd' on 'node2' succeededCRS-2672: Attempting to start 'ora.evmd' on 'node2'CRS-2676: Start of 'ora.evmd' on 'node2' succeeded

Checking swap space: must be greater than 500 MB. Actual 12287 MB PassedThe inventory pointer is located at /etc/oraInst.locThe inventory is located at /oracle/oraInventory'UpdateNodeList' was successful.

The issue occurs when we start installation with a wrong ORA_NLS10 environment parameter. Best is to unset the variable before installation or change it to point to $GRID_HOME/nls/data:unset ORA_NLS10or export ORA_NLS10=$GRID_HOME/nls/data

- name of the host, as known to a communications network - name by which the interface is configured in the system - subnet address of the interface - type of the interface { cluster_interconnect | public }

Wednesday, August 18, 2010

Well I had racked my brains a lot to create an mview on a large table across geographies, and it failed a few times.Plus to increase my problem the character set was also different between the two DBs.:Master Site:SQL> select * from nls_database_parameters@link1 where PARAMETER='NLS_CHARACTERSET';PARAMETER VALUE------------------------------ ------------------------------NLS_CHARACTERSET WE8MSWIN1252

This ran for ever and finally failed with ORA-01555, as expected, as it ran for almost a day.To give a background the size of the table is 1G.

Then I finally decided to use the PREBUILT Table option:So I took an export backup of that table in the master site and imported it in mview site.And then tried to recreate the mview with PREBUILT TABLE option:create materialized view user.test1 ON PREBUILT TABLErefresh fast with primary key for updateasselect col1,col2 from user.test1@link1;

Which failed with:Col1,*ERROR at line 6:ORA-12060: shape of prebuilt table does not match definition query

Well I checked the table structure and realized that the col size for char data type had become 2 folds as during import, due to character set conversion this happens.

Then I searched metalink, etc, and found an options called "WITH REDUCED PRECISION", to be used when there is col mis-match.create materialized view user.test1 ON PREBUILT TABLE WITH REDUCED PRECISIONrefresh fast with primary key for updateasselect col1,col2 from user.test1@link1;

But it still failed:

create materialized view user.test1 ON PREBUILT TABLE WITH REDUCED PRECISION *ERROR at line 1:ORA-12060: shape of prebuilt table does not match definition query

What resolved the problem is removing "with primary key for update"create materialized view user.test1 ON PREBUILT TABLE WITH REDUCED PRECISIONrefresh fast on demandasselect col1,col2 from user.test1@link1;