确实是可以的~只是需要配置一下~不过这个如果不操作ASM instacne的话没什么用

Applies to:Oracle Net Services - Version: 10.1.0.4.0 to 10.2.0.4.0

Information in this document applies to any platform.

SymptomsChecking the listener status, ASM instance is shown as BLOCKED.

Remote connections and administration cannot be performed in this case for the ASM instance.

Example :

LSNRCTL for Linux: Version 10.2.0.1.0 - Production on 19-NOV-2007 11:31:18

Copyright (c) 1991, 2005, Oracle. All rights reserved.

Connecting to (ADDRESS=(PROTO =tcp)(HOST=)(PORT=1521))

STATUS of the LISTENER

------------------------

Alias LISTENER_PNYPERMDB01

Version TNSLSNR for Linux: Version 10.2.0.1.0 - Production

Start Date 09-AUG-2007 15:16:58

Uptime 101 days 21 hr. 14 min. 20 sec

Trace Level off

Security ON: Local OS Authentication

SNMP ON

Listener Parameter File /opt/oracle/product/10.2/network/admin/listener.ora

Listener Log File /opt/oracle/product/10.

2/network/log/listener_pnypermdb01.log

Listening Endpoints Summary...

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521)))

(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521)))

Services Summary...

Service "+ASM" has 1 instance(s).

Instance "+ASM1", status BLOCKED, has 1 handler(s) for this service...

Service "+ASM_XPT" has 1 instance(s).

Instance "+ASM1", status BLOCKED, has 1 handler(s) for this service...

Service "PLSExtProc" has 1 instance(s).

Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...

...................

The command completed successfully

CauseThe blocked status is being set by the instance, indicating that the database is not able to accept connections. This can be caused by the instances not being mounted or mounted in a restricted state.

Since an ASM instance never mounts a database, it will always be shown in 'BLOCKED' status.

The administration of an ASM instance is intended to be done on the server itself and not remotely.

This is the default and expected behaviour for 10gR1 and newer databases.

SolutionConnecting to a 'BLOCKED' instance via a listener requires creating an entry in the tnsnames.ora file on the client side with 'UR=A' under CONNECT_DATA.

Also, creating a password file for the ASM instance will be required to connect as SYS.

The steps are shown below :

1) Edit the listener.ora on ASM server to create a static SID_DESC definition for the +ASM instance:

a) Logon to the ASM/Database server

b) Locate your listener.ora (typically located in the $ORACLE_HOME/network/admin)

c) Add an entry under SID_LIST_LISTENER entry for your ASM instance.

Example:

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(GLOBAL_DBNAME= +ASM)

(ORACLE_HOME = c:\oracle\app\product\11.1.0\db_1)

)

)

2. Issue a lsnrctl reload so that these changes take effect.

3. Stop the ASM instance

4. Set the REMOTE_LOGIN_PASSWORDFILE to SHARED or EXCLUSIVE in the ASM instance

5. Create a password file for the ASM instance using the ORAPWD utility

6. Start the ASM instance

7. Edit the tnsnames.ora file on the client side with the entry UR=A under CONNECT_DATA as shown :

ASM =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP)(HOST = myhost)(PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = +ASM)

(UR=A)

)

)

8. Then connect to +ASM instance remotely using the sqlplus client using the command

"conn sys/password@alias as sysdba"

Note :

This behaviour changes in 11gR1, where the status of ASM instances is always 'UNBLOCKED' instead of

'BLOCKED' for listeners.