So, it's not really the DB link that is the issue, it is the ability to
access your ASM instance over the network?
You can, but since the ASM instance is started nomount, there is very
little you can "see", other than the spfile parameters. The easiest way
to "see what's going on" is to start the OEM database control for the
"real" database (the one(s) using ASM) and then click on the links for
ASM within that tool, from anywhere on your network.
However, if you insist, you can access the ASM instance across the
network using SQL*Plus or the OEM Java console. Add an entry similar to
the following in the SID_LIST section of your listener.ora (and reload
the listener, of course):
(SID_DESC =
(GLOBAL_DBNAME = +asm.lake)
(ORACLE_HOME = /u01/app/oracle/product/10.1.0)
(SID_NAME = +ASM)
)Add an entry similar to this in your tnsnames.ora:
+ASM.LAKE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = lake)(PORT = 1521))
)
(CONNECT_DATA =
(SERVICE_NAME = +asm.lake)
)
)Create the password file on the server:
/u01/app/oracle/product/10.1.0/dbs/orapw+ASM
And then connect away:
% sqlplus sys@+asm.lake as sysdba
-- Mark Bole http://www.bincomputing.com
Christo Kutrovsky wrote:
Actually, i want to create a dblink to the ASM instance, so that I dont have to connect to it everything i want to see what's going on :)
On 9/1/05, Paul Drake <bdbafh@xxxxxxxxx> wrote:
On 9/1/05, Christo Kutrovsky <kutrovsky.oracle@xxxxxxxxx> wrote:
Does anyone know how to create a dblink that connects with sysdba
priviliges ?
[...]
-- //www.freelists.org/webpage/oracle-l
