Recently started seeing this error on few of the Exadata environments. ORA–00600: internal error code, arguments:[qosdExpStatRead: expcnt mismatch] Cause This is due to sys.exp_obj$. EXP_CNT mismatch rows of sys.exp_stat$ Following SQL is used to check issue data of some objects. if there are some rows return, that means data issue. With b as ( select count(*) cnt,objn,snapshot_id from sys.exp_stat$ […]
Recently started seeing this error on few of the Exadata environments. ORA–00600: internal error code, arguments:[KUTYXTTE_TRANSFORM:FAILED] As per metalink this is a known Bug 28194173 Patch 28194173: SQL ON 12.2 QUARANTINED AND CELL THROWING ORA-00600 [KUTYXTTE_TRANSFORM:FAILED] I’ve seen this in 12.2.
Recently started seeing this error on few of the RAC environments. ORA–00600: internal error code, arguments:[ORA-600[KCLANTILOCK_17] After upgrade to 12.2, Due to this Instance got crashed. As per metalink this is a known Bug 27162390 Patch 27162390: LNX64-181-RAC: LMS HIT ORA-600[KCLANTILOCK_17], INST CRASH I’ve seen this in 12.2. As per Oracle it’s fixed in version 18.1
Recently started seeing this error on few of the RAC environments. ORA–00600: internal error code, arguments:[KDZA_CHECK_EQ NOT IN DICTIONARY] As per metalink this is a known Bug 24818566 Patch 24818566: SQLLOAD FAILED WITH ORA-600 [KDZA_CHECK_EQ NOT IN DICTIONARY] I’ve seen this in 11204 ,12102,12.2 both. As per Oracle it’s fixed in version 18.1
Being DBA we all are aware that we must have knowledge of OS level too because Database not just runs over the only one OS. In a different organization, we have a different OS. Being a part if IT we understand that different OS environment has a different parameter. We have to set them. Today […]
We are continuing with the same series of listener errors. Let’s have looked over the new error. Let’s go for the steps
[oracle@hostname]$ sqlplus sys@test_1as sysdba
SQL*Plus: Release 126.96.36.199.0 Production on Tue Jul 7 15:01:04 2017
Copyright (c) 1982, 2011, Oracle. All rights reserved.
ORA-12154: TNS:could not resolve the connect identifier specified
Condition for error When Database is on in restricted on no mount status and you will see service handler for this instance is on BLOCKED or RESTRICTED state.
[oracle@hostname]$ lsnrctl status
LSNRCTL for Linux: Version 188.8.131.52.0 – Production on 07-JUL-2017 15:20:35
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
STATUS of the LISTENER
Version TNSLSNR for Linux: Version 184.108.40.206.0 – Production
Start Date 07-JUL-2015 14:18:31
Uptime 0 days 1 hr. 2 min. 3 sec
Trace Level off
Security ON: Local OS Authentication
Listener Parameter File /opt/oracle/product/220.127.116.11/network/admin/listener.ora
Listener Log File /opt/oracle/diag/tnslsnr/stagedevdb2/listener/alert/log.xml
Listening Endpoints Summary…
Service “+ASM” has 1 instance(s).
Instance “+ASM”, status READY, has 1 handler(s) for this service…
Service “teston” has 1 instance(s).
Instance “teston“, status BLOCKED, has 1 handler(s) for this service…
The command completed successfully
Solution: Add (UR=A) […]
Let’s start the series of Oracle listener. Now are going to focus over the issue for the following errors. Let’s have looked over the steps and solve the issues.
TNS-12516 TNS: listener could not find an instance with the matching protocol stack
ORA-12516 TNS: listener could not find available handler with the matching protocol stack
TNS-12519 TNS: no appropriate service handler found
ORA-12519 TNS: no appropriate service handler found
ORA-12520 TNS: listener could not find available handler for requested type of server
Cause: None of the known and available service handlers for the given SERVICE_NAME support the client’s protocol stack: transport, session, and presentation protocols. Solution: check […]
Being human being we have a lot of unlimited qualities. Listening is one of them. Normally we ignore it but it is most important for all. Good listing keeps us away from 99% problems away and life makes us simple but if we don’t listen properly we invite unlimited problem in our life. In same […]
Let’s have look on some listener issues in the database. Cause: The connect descriptor corresponding to the net service name in TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly specified. Action: If using local naming make sure there are no syntax errors in the corresponding connect descriptor in the TNSNAMES.ORA file. If […]
As we are working on the series of listener errors. Now we are going to work on “ORA-12514“. Let’a have look on the steps which we use to resolve this issue. Cause: “The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a SID […]