Shulou(Shulou.com)06/01 Report--

The following test comes from an experiment of adding and deleting instances. In 10G RAC, we know that monitoring is managed through netca, which is different from the mechanism of 11G.

When adding nodes, you need to manually execute netca to register the listening service. In fact, we can also register the listening service manually through the crs_profile tool.

Welcome to join the ORACLE Super Group: 17115662 solve all kinds of ORACLE problems for free

Database version information

[oracle@www.htz.pw oracle] $sqlplus / as sysdba

SQL*Plus: Release 10.2.0.4.0-Production on Sun May 11 17:06:26 2014

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Connected to:

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-Production

With the Partitioning, Real Application Clusters, OLAP, Data Mining

And Real Application Testing options

SQL > select * from v$version

BANNER

Oracle Database 10g Enterprise Edition Release 10.2.0.4.0-Prod

PL/SQL Release 10.2.0.4.0-Production

CORE 10.2.0.4.0 Production

TNS for Solaris: Version 10.2.0.4.0-Production

NLSRTL Version 10.2.0.4.0-Production

1. Configure tnsnames.ora and listener.ora files

As follows:

[root@www.htz.pw admin] $cat listener.ora

# listener.ora.sol1 Network Configuration File: / oracle/app/oracle/product/10.2.0/db_1/network/admin/listener.ora.sol1

# Generated by Oracle configuration tools.

LISTENER_SOL1 =

(DESCRIPTION_LIST =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.111.48) (PORT = 1521) (IP = FIRST))

(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.111.46) (PORT = 1521) (IP = FIRST))

)

)

# IP address is recommended here

SID_LIST_LISTENER_SOL1 =

(SID_LIST =

(SID_DESC =

(SID_NAME = PLSExtProc)

(ORACLE_HOME = / oracle/app/oracle/product/10.2.0/db_1)

(PROGRAM = extproc)

)

)

[root@www.htz.pw app] $cd $ORACLE_HOME/network/admin

[root@www.htz.pw admin] $cat tnsnames.ora

# tnsnames.ora.sol1 Network Configuration File: / oracle/app/oracle/product/10.2.0/db_1/network/admin/tnsnames.ora.sol1

# Generated by Oracle configuration tools.

LISTENERS_SOL10G =

(ADDRESS_LIST =

(ADDRESS = (PROTOCOL = TCP) (HOST = sol1-vip) (PORT = 1521))

(ADDRESS = (PROTOCOL = TCP) (HOST = sol2-vip) (PORT = 1521))

)

# it is recommended to use the IP address. When configuring REMOTE_LISTENER in 10G, it will be used by default.

SOL10G2 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = sol2-vip) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = sol10g)

(INSTANCE_NAME = sol10g2)

)

)

SOL10G1 =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = sol1-vip) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = sol10g)

(INSTANCE_NAME = sol10g1)

)

)

SOL10G =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = sol1-vip) (PORT = 1521))

(ADDRESS = (PROTOCOL = TCP) (HOST = sol2-vip) (PORT = 1521))

(LOAD_BALANCE = yes)

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = sol10g)

)

)

2cr crsrecording register registration monitoring service

Note that there are two ways to monitor the service, 1, to take advantage of the current monitoring configuration information. 2, use crs_profile to create

2.1 leverage existing monitoring configuration information

[oracle@www.htz.pw oracle] $crs_stat-p ora.sol2.LISTENER_SOL2.lsnr > / tmp/listener.txt

The monitoring configuration information of the normal node is exported here.

[oracle@www.htz.pw oracle] $cat / tmp/listener.txt

NAME=ora.sol1.LISTENER_SOL1.lsnr

# the name LISTENER_SOL1 that needs to be noted here should be the same as the listener name in listener.ora

TYPE=application

ACTION_SCRIPT=/oracle/app/oracle/product/10.2.0/db_1/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

CHECK_INTERVAL=600

DESCRIPTION=CRS application for listener on node

FAILOVER_DELAY=0

FAILURE_INTERVAL=0

FAILURE_THRESHOLD=0

HOSTING_MEMBERS=sol1

OPTIONAL_RESOURCES=

PLACEMENT=restricted

REQUIRED_RESOURCES=ora.sol1.vip

RESTART_ATTEMPTS=5

SCRIPT_TIMEOUT=600

START_TIMEOUT=0

STOP_TIMEOUT=0

UPTIME_THRESHOLD=7d

USR_ORA_ALERT_NAME=

USR_ORA_CHECK_TIMEOUT=0

USR_ORA_CONNECT_STR=/ as sysdba

USR_ORA_DEBUG=0

USR_ORA_DISCONNECT=false

USR_ORA_FLAGS=

USR_ORA_IF=

USR_ORA_INST_NOT_SHUTDOWN=

USR_ORA_LANG=

USR_ORA_NETMASK=

USR_ORA_OPEN_MODE=

USR_ORA_OPI=false

USR_ORA_PFILE=

USR_ORA_PRECONNECT=none

USR_ORA_SRV=

USR_ORA_START_TIMEOUT=0

USR_ORA_STOP_MODE=immediate

USR_ORA_STOP_TIMEOUT=0

USR_ORA_VIP=

Only three addresses need to be changed.

[oracle@www.htz.pw oracle] $mv / tmp/listener.txt $ORA_CRS_HOME/crs/public/ora.sol1.LISTENER_SOL1.lsnr.cap

[oracle@www.htz.pw oracle] $crs_register ora.sol1.LISTENER_SOL1.lsnr

[oracle@www.htz.pw oracle] $crs_start ora.sol1.LISTENER_SOL1.lsnr

Attempting to start `ora.sol1.LISTENER_ SOL1.lsnr` on member `sol1`

Start of `ora.sol1.LISTENER_ SOL1.lsnr` on member `sol1` succeeded.

The monitor can start normally.

2.2 use crs_profiler to manually create snooping

The following methods are not recommended until it is absolutely necessary.

[oracle@www.htz.pw oracle] $crs_profile-create ora.sol1.LISTENER_SOL1.lsnr-t application-a / oracle/app/oracle/product/10.2.0/db_1/bin/racgwrap-d "CRS application for listener on node"-h sol1-ro ra.sol1.vip-p restricted-o as=1,ci=600,st=600,ra=5

[oracle@www.htz.pw oracle] $cat ora.sol1.LISTENER_SOL1.lsnr.cap

NAME=ora.sol1.LISTENER_SOL1.lsnr

TYPE=application

ACTION_SCRIPT=/oracle/app/oracle/product/10.2.0/db_1/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

CHECK_INTERVAL=600

DESCRIPTION=CRS application for listener on node

FAILOVER_DELAY=0

FAILURE_INTERVAL=0

FAILURE_THRESHOLD=0

HOSTING_MEMBERS=sol1

OPTIONAL_RESOURCES=

PLACEMENT=restricted

REQUIRED_RESOURCES=ora.sol1.vip

RESTART_ATTEMPTS=5

SCRIPT_TIMEOUT=600

START_TIMEOUT=0

STOP_TIMEOUT=0

UPTIME_THRESHOLD=7d

USR_ORA_ALERT_NAME=

USR_ORA_CHECK_TIMEOUT=0

USR_ORA_CONNECT_STR=/ as sysdba

USR_ORA_DEBUG=0

USR_ORA_DISCONNECT=false

USR_ORA_FLAGS=

USR_ORA_IF=

USR_ORA_INST_NOT_SHUTDOWN=

USR_ORA_LANG=

USR_ORA_NETMASK=

USR_ORA_OPEN_MODE=

USR_ORA_OPI=false

USR_ORA_PFILE=

USR_ORA_PRECONNECT=none

USR_ORA_SRV=

USR_ORA_START_TIMEOUT=0

USR_ORA_STOP_MODE=immediate

USR_ORA_STOP_TIMEOUT=0

USR_ORA_VIP=

[oracle@www.htz.pw oracle] $crs_register ora.sol1.LISTENER_SOL1.lsnr

[oracle@www.htz.pw oracle] $crs_start ora.sol1.LISTENER_SOL1.lsnr

Attempting to start `ora.sol1.LISTENER_ SOL1.lsnr` on member `sol1`

Start of `ora.sol1.LISTENER_ SOL1.lsnr` on member `sol1` succeeded

In fact, when it comes to VIP resources, we need to pay attention, because the group of VIP data is root.

[oracle@www.htz.pw oracle] $crs_stat-ls

Name Owner Primary PrivGrp Permission

-

Ora....L1.lsnr oracle oinstall rwxrwxr--

Ora.sol1.gsd oracle oinstall rwxr-xr--

Ora.sol1.ons oracle oinstall rwxr-xr--

Ora.sol1.vip root oinstall rwxr-xr--

Ora.sol10g.db oracle oinstall rwxrwxr--

Ora....g2.inst oracle oinstall rwxrwxr--

Ora....SM2.asm oracle oinstall rwxrwxr--

Ora....L2.lsnr oracle oinstall rwxrwxr--

Ora.sol2.gsd oracle oinstall rwxr-xr--

Ora.sol2.ons oracle oinstall rwxr-xr--

Ora.sol2.vip root oinstall rwxr-xr

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.