-
Título
ORA-12523, TNS:listener could not find instance appropriate for the client connection when adding Oracle ASM agent -
Descripción
Following error is found in the Oracle installer log when adding an Oracle ASM agent:
ECHO ERROR [pool-19-thread-1] com.quest.qsi.dbwc.AutoDiscovery.verify.AbstractVerify - Exception:ora_verikey1448441972756failed connect to hostname-+ASM2 status: CONNECTION_STATUS_DB_ERROR{1} com.quest.qsi.fason.framework.connections.common.exceptions.FrameworkException: Failed to establish a Oracle JDBC connection protocol to Host [hostname-+ASM2], user account [quest_fog] . Reason : [Listener refused the connection with the following error: ORA-12523, TNS:listener could not find instance appropriate for the client connection - Profile:OracleProfile{host='hostname', instance='+ASM2', service='+ASM', username='quest_fog', userType=sysasm, ports='3031'}]. . [Oracle Error Code = 12523. SQL state : 66000]
-
Causa
ORA-12523 normally happens if the listener is not running or the connection is not setup properly.
1. On the ASM host, if you run 'lsnrctl status', do you see the ASM service?
2. Are you also able to connect the each of the ASM node via sqlplus as the sysasm user?
3. Are you able to tnsping the ASM instance?If there are issues with the above, consult your Oracle documentation on how to rectify them.
-
Resolución
The remote connection to the ASM with +ASM should be configured unrelated to any monitoring tool.
Attempt the connection using SQLPLUS and follow the instructions in Metalink Doc ID 340277.1 and 738462.1 from the Oracle support website to resolve this issue.
Other options that can be considered which may help this issue include:- USE_SID_AS_SERVICE_LISTENER=on in the listener.ora, or
- Adding a SID_LIST_LISTENER with a +ASM GLOBAL_DBNAME, or
- Adding a ASM entry to the tnsnames.ora on both nodes
-
Adjuntos