Last updated on FEBRUARY 13, 2017
Applies to:Oracle Pedigree and Serialization Manager - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
Customer has a Oracle 188.8.131.52 database with our product (Oracle Pedigree &
Serialization Manager) installed. A simple query ( SELECT S.SERIAL_ID,
S.UNIQUE_CHECK_STRING, S.COUNTERFEIT_STATUS, S.COUNTERFEIT_DATE,
S.SERIAL_STATE, S.SERIAL_STATUS FROM PAS_S_SERIALS S WHERE
S.UNIQUE_CHECK_STRING = :B1 ) is not using the index with UNIQUE_CHECK_STRING
which exists in the schema.
When the query is executed seperately and explain plan is run, the index is
utilized, however when the same query is run from a procedure, the query does
perform a full access causing performance issue. Issue could not replicate
locally, but is consistent in customer's instance.
Dropped and recreated the index, ran explain plain with the index hint to be
sure the index exist and used by execution, but still fails to use the index
while executing from the procedure.
Checked Doc 67522.1, no specific issues.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms