My Oracle Support Banner

Troubleshooting: High Version Count Issues (Doc ID 296377.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.

Purpose

This Troubleshooting Guide is provided to assist in debugging SQL sharing issues. When possible, diagnostic tools are included in the document to assist in troubleshooting problems. This document does not contain bugs/patches as these topics are addressed in the articles referenced at the bottom of this document.

Ask Questions, Get Help, And Share Your Experiences With This Article

Would you like to explore this topic further with other Oracle Customers, Oracle Employees, and Industry Experts?

Click here to join the discussion where you can ask questions, get help from others, and share your experiences with this specific article.
Discover discussions about other articles and helpful subjects by clicking here to access the main My Oracle Support Community page for Database Tuning.

Troubleshooting Steps

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
 Ask Questions, Get Help, And Share Your Experiences With This Article
Troubleshooting Steps
 What is a 'High' Version Count?
 What is shared SQL ?
 What is 'SQL Metadata'?
 Why should I be concerned about 'High' Versions?
 How do I see the versions and why they are not shared ?
 What do the reasons given in v$SQL_SHARED_CURSOR mean?
 UNBOUND_CURSOR
 SQL_TYPE_MISMATCH
 **OPTIMIZER_MISMATCH
 OUTLINE_MISMATCH
 STATS_ROW_MISMATCH
 LITERAL_MISMATCH
 SEC_DEPTH_MISMATCH
 EXPLAIN_PLAN_CURSOR
 BUFFERED_DML_MISMATCH
 PDML_ENV_MISMATCH
 INST_DRTLD_MISMATCH
 SLAVE_QC_MISMATCH
 TYPECHECK_MISMATCH
 AUTH_CHECK_MISMATCH
 **BIND_MISMATCH
 DESCRIBE_MISMATCH
 LANGUAGE_MISMATCH
 TRANSLATION_MISMATCH
 ROW_LEVEL_SEC_MISMATCH
 INSUFF_PRIVS
 INSUFF_PRIVS_REM
 REMOTE_TRANS_MISMATCH
 LOGMINER_SESSION_MISMATCH
 INCOMP_LTRL_MISMATCH
 OVERLAP_TIME_MISMATCH
 SQL_REDIRECT_MISMATCH
 MV_QUERY_GEN_MISMATCH
 USER_BIND_PEEK_MISMATCH
 TYPCHK_DEP_MISMATCH
 NO_TRIGGER_MISMATCH
 FLASHBACK_CURSOR
 ANYDATA_TRANSFORMATION
 INCOMPLETE_CURSOR
 TOP_LEVEL_RPI_CURSOR
 DIFFERENT_LONG_LENGTH
 LOGICAL_STANDBY_APPLY
 DIFF_CALL_DURN
 BIND_UACS_DIFF
 PLSQL_CMP_SWITCHS_DIFF
 CURSOR_PARTS_MISMATCH
 STB_OBJECT_MISMATCH
 ROW_SHIP_MISMATCH
 PQ_SLAVE_MISMATCH
 TOP_LEVEL_DDL_MISMATCH
 MULTI_PX_MISMATCH
 BIND_PEEKED_PQ_MISMATCH
 MV_REWRITE_MISMATCH
 ROLL_INVALID_MISMATCH
 OPTIMIZER_MODE_MISMATCH
 PX_MISMATCH
 MV_STALEOBJ_MISMATCH
 FLASHBACK_TABLE_MISMATCH
 LITREP_COMP_MISMATCH
 PLSQL_DEBUG
 LOAD_OPTIMIZER_STATS
 ACL_MISMATCH
 FLASHBACK_ARCHIVE_MISMATCH
 LOCK_USER_SCHEMA_FAILED
 REMOTE_MAPPING_MISMATCH
 LOAD_RUNTIME_HEAP_FAILED
 HASH_MATCH_FAILED
 PURGED_CURSOR
 BIND_LENGTH_UPGRADEABLE
 USE_FEEDBACK_STATS
 BIND_EQUIV_FAILURE
 Version_rpt script:
 What further tracing is available.
 Are there any times when a high version count is expected even though BINDS are being used?
 Explanation:
 Enhancement to obsolete parent cursors if Version Count exceeds a threshold
 High Version Count with Adaptive Cursor Sharing
 Known Issues
 Troubleshooting Other Issues
 Discuss High Version Count Issues
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.