Shulou(Shulou.com)05/31 Report--

This article is about how to carry out ASM configuration monitoring and TNS, the editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

Find information on the Internet, toss about for a long time, successful, the record is as follows.

The reason for toss: the password provided is wrong, and you are successful after creating your own user! Tragic time!

Add listener under grid users:

SID_LIST_LISTENER =

(SID_LIST =

(SID_DESC =

(ORACLE_HOME = / oracle/crs)

(SID_NAME = + ASM)

)

)

Oracle user tnsnames.ora

Asm =

(DESCRIPTION =

(ADDRESS = (PROTOCOL = TCP) (HOST = ciq-db1) (PORT = 1521))

(ADDRESS = (PROTOCOL = TCP) (HOST = ciq-db2) (PORT = 1521))

(CONNECT_DATA =

(SERVER = DEDICATED)

(SERVICE_NAME = + ASM)

(UR=A)

)

)

Oracle user testing

Tnsping asm

Sqlplus asmcj/asmcj@asm as sysasm

SQL > conn sys/asmdba@asm as sysdba

Connected.

Goldengate extract is written:

TRANLOGOPTIONS ASMUSER SYS@asm,ASMPASSWORD password

=

Http://www.itpub.net/thread-1865683-1-1.html

To understand how to access an ASM instance, you must first understand the ASM system permissions.

[@ more@]

1. ASM permission

Because the ASM instance does not have data dictionary information, it is impossible to use ASM authentication to verify the validity of users logging in to the instance, so operating system verification can only be used to verify the legitimacy of users connected to the ASM instance.

A) SYSASM system permissions, which belong to the group OSASM created by the system, such as asmadmin, and fully manage the permissions of ASM

B) SYSDBA system permission, belongs to the group OSDBA created by the system, (belongs to ASM), such as asmdba, can access data on ASM, create and delete ASM files, grant and withdraw access to ASM files, and cannot create and RESIZE disk groups.

C) SYSOPER system permission, which belongs to the group OSOPER created by the system (belongs to ASM), such as asmoper, can STARTUP,SHUTDOWN instances and MOUNT,DISMOUNT disk groups, cannot access the view of CREATE,DROP,RESIZE,ADD ASM groups, and cannot CREATE,DROP,RESIZE,ADD disk groups.

two。 Access ASM instance

A) use the operating system to verify local access to the ASM instance

Users with OSASM, OSDBA for ASM and or OSOPER for ASM groups log in to the ASM instance using OS authentication.

In fact, the operating system verification accesses the ASM instance. When the instance is not up, users with SYSASM/SYSOPER can enter the interface to launch the ASM instance and perform startup operations on the instance. This is the role of operating system verification. The same is true of database verification.

[grid@dbhouse disks] $sqlplus "/ as sysasm"

SQL*Plus: Release 11.2.0.3.0 Production on Sat Nov 17 16:40:34 2012

Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to an idle instance.

SQL > startup

B) use password files to access ASM instances locally

B.1) set the parameter remote_login_passwordfile:

SQL > show parameter login

NAME TYPE VALUE

-

Remote_login_passwordfile string EXCLUSIVE

B.2) password file is required: / u01/app/11.2.0/grid/dbs/orapw+ASM

B. 3) the user and password log in to the ASM instance locally.

[grid@dbhouse disks] $sqlplus sys/grid as sysasm # username and password

SQL*Plus: Release 11.2.0.3.0 Production on Sat Nov 17 16:47:36 2012

Copyright (c) 1982, 2011, Oracle. All rights reserved.

Connected to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0-Production

With the Automatic Storage Management option

Using a password to log in locally to the ASM instance, in my opinion, is the second set of scenarios to prevent the operating system authentication from failing to enable login to the ASM instance.

C) remote access to ASM instances using Net Services and password files

C:Users123 > sqlplus sys/grid@asm11g as sysasm

SQL*Plus: Release 11.2.0.2.0 Production on Saturday November 17 18:01:48 2012

Copyright (c) 1982, 2010, Oracle. All rights reserved.

Connect to:

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0-Production

With the Automatic Storage Management option

SQL >

This way of logging in to ASM instances is purely set to facilitate remote maintenance of ASM instances. If the ASM instance is not started, this login to the ASM instance will fail because the connection string asm11g cannot get the services name of the ASM instance.

In my opinion, the purpose of using operating system authentication to access ASM instances is to start ASM instances, and the role of using password file authentication to access ASM instances is to facilitate remote maintenance, and the same is true of accessing database instances.

The above is how to carry out ASM configuration monitoring and TNS, the editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

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.