tag:blogger.com,1999:blog-21122514.post1877855512290641353..comments2024-03-23T11:05:13.046+01:00Comments on Dimitri Gielis Blog (Oracle Application Express - APEX): My Top 15 Oracle DB 11g NF for APEX Developers: 14Dimitri Gielishttp://www.blogger.com/profile/16295721159626839167noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-21122514.post-25510558529026501842009-08-26T16:56:27.699+02:002009-08-26T16:56:27.699+02:00Just leaving a note, as I came across this page wh...Just leaving a note, as I came across this page whilst researching a received ORA-13644 when using dbms_sqltune on 10.2.0.4. This was bug 605525.<br /><br />I worked around by flushing the shared pool to obtain a cursor re-parse which left parsing_schema_name populated. This approach was satisfactory as I was using a test system.<br /><br />It looks like a single cursor may be flushed using the information in Doc ID: 457309.1 which may also result in the population of parsing_schema_name. Although I haven't tried/tested this.<br /><br />Bug 605525 is stated as fixed in 10.2.0.5.<br /><br />Regards,<br /><br />M.mathewbutlerhttps://www.blogger.com/profile/04733010552235144796noreply@blogger.comtag:blogger.com,1999:blog-21122514.post-86774349932953502872008-01-18T20:08:00.000+01:002008-01-18T20:08:00.000+01:00Thanks Todd.Thanks Todd.Dimitri Gielishttps://www.blogger.com/profile/16295721159626839167noreply@blogger.comtag:blogger.com,1999:blog-21122514.post-8645929278612302972008-01-18T19:58:00.000+01:002008-01-18T19:58:00.000+01:00Dimitri,Thanks for the nice post! I did run into ...Dimitri,<BR/><BR/>Thanks for the nice post! I did run into bug 6005525 (V$SQL PARSING_SCHEMA_NAME is not populated for schema owners) when running the SQL Tuning Advisor on a statement that was run by an APEX session. <BR/><BR/>The error I saw in OEM is as follows. <BR/>There was a problem creating a SQL tuning task. ORA-13644: The user "" is invalid. ORA-06512: at "SYS.DBMS_SQLTUNE", line 791 ORA-06512: at line 1 <BR/><BR/>See Metalink Note:6005525.8 for the full explanation of that error. In summary the v$sql view does not have the parsing_schema_name column populated when running queries from APEX sessions. The following query showed this was true for my query.<BR/>select parsing_schema_name<BR/>from v$sql<BR/>where sql_id = 'cdjy1aspj45xa';<BR/><BR/>My work around was to run the same statement from SQL Developer, then run the SQL Tuning Advisor on my statement.<BR/><BR/>ToddAnonymousnoreply@blogger.com