Αποτελέσματα Αναζήτησης
16 Δεκ 2012 · Looking at BiPin's answer I modified it a bit to suit my needs. I needed to figure out what parameters users were using when running a report in real time. Here's my solution which adds the childnumber to the query from v$sql_bind_capture.
V$SQL_BIND_CAPTURE displays information on bind variables used by SQL cursors. Each row in the view contains information for one bind variable defined in a cursor. This includes:
a NUMBER := 4; b NUMBER := 7; BEGIN plsql_block := 'BEGIN calc_stats(:x, :x, :y, :x); END;' EXECUTE IMMEDIATE plsql_block USING a, b;... END; " So, when should one give how many using parameters?
2 Ιουν 2023 · Bind variables, often called bind parameters or query parameters, are often used in WHERE clauses to filter data. Instead of putting the required value into the query, or writing separate queries for each different value, or concatenating strings, you can use bind variables. Here’s how it works.
1 Νοε 2017 · How can I find out if a SQL used bind variable or not? I know you can check v$sql and get a list of distinct SQLs after translating the constants in the predicates. But if it's using bind variable, shouldn't V$SQL_BIND_CAPTURE have that SQL_ID and also the values really used for the variables?
V$SQL_BIND_DATA describes, for each distinct bind variable in each cursor owned by the session querying this view: Actual bind data, if the bind variable is user defined. The underlying literal, if the CURSOR_SHARING parameter is set to FORCE and the bind variable is system generated.
V$SQL lists statistics on shared SQL areas without the GROUP BY clause and contains one row for each child of the original SQL text entered. Statistics displayed in V$SQL are normally updated at the end of query execution. However, for long running queries, they are updated every 5 seconds.
