![]() ![]() What would be the cause of BIND_MISMATCH? ![]() SQL> select * from v$sql_shared_cursor where KGLHDPAR = '8EE280E8' ĪDDRESS KGLHDPAR U S O O S L S E B P I S T A B D L T R I I R L I O S M U T N FĨC215350 8EE280E8 N N N N N N N N N N N N N N Y N N N N N N N N N N N N N N N N PARSING_USER_ID PARSING_SCHEMA_ID SQL_TEXT ADDRESS VERSION_COUNTĠ 0 update prrecordmst set PRBATCHKEY = :1, RECORDTYPE = :2, 8EE280E8 16 SQL> select parsing_user_id, parsing_schema_id, sql_text, address, version_count from v$sqlarea where address = '8EE280E8' PARSING_USER_ID PARSING_SCHEMA_ID SQL_TEXT ADDRESS CHILD_ADĠ 0 update recordmst set BATCHKEY = :1, RECORDTYPE = :2, 8EE280E8 8E9425DCĠ 0 update recordmst set BATCHKEY = :1, RECORDTYPE = :2, 8EE280E8 9273E6F0Ġ 0 update recordmst set BATCHKEY = :1, RECORDTYPE = :2, 8EE280E8 90377C0Cģ7 34 update recordmst set BATCHKEY = :1, RECORDTYPE = :2,ĮNTITY = :3. SQL> select parsing_user_id, parsing_schema_id, sql_text, address, child_address from v$sql where address = '8EE280E8' What would be the cause of BIND_MISMATCH? If the sql statments are exactly same, will they always have the same ADDRESS? Is the child_adress will be different if one of the v$sql_shared_cursor columns have different value? Is it the cause for 16 occurences of the same sql, in the v$sql? ![]() In the v$sql_shared_cursor I see the only difference is in BIND_MISMATCH. What does it imply when the parsion_shema/user_id is 0 (SYS)?. I got the following statements from v$sql*. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |