Home > database >  View about hint in oracle syntax error has been in a state of the query
View about hint in oracle syntax error has been in a state of the query

Time:09-24

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- the first -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
SQL> The select SQL_TEXT
2 the from v $sqltext where SQL_ID='& amp; Sql_id 'order by piece;
Enter a value for sql_id: 01 grdaq0u7gkg
Old 2: the from v $sqltext where SQL_ID='& amp; Sql_id 'order by piece
New 2: the from v $sqltext where SQL_ID='01 grdaq0u7gkg' order by piece

SQL_TEXT
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
The SELECT/* + FULL (P) + */* FROM "V_JF_KUANXIANG P
"
SQL>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- the second -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
SQL> The select SQL_TEXT
2 the from v $sqltext where SQL_ID='& amp; Sql_id 'order by piece;
Enter a value for sql_id: bzr6zhk94ashb
Old 2: the from v $sqltext where SQL_ID='& amp; Sql_id 'order by piece
New 2: the from v $sqltext where SQL_ID='bzr6zhk94ashb' order by piece

SQL_TEXT
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
The SELECT/* + FULL (P) + */* FROM "V_JF_ERROR P
"
SQL>


-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- the following is the operational analysis of -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
This hint syntax errors,
It should be
The SELECT/* + FULL (P) */* FROM "V_JF_KUANXIANG P
"Not behind the number +,

The SELECT/* + FULL (P) */* FROM "V_JF_ERROR P this is the right way,"


Please locate the application code, modify the SQL statement,

CodePudding user response:

I checked my repository SQL statements, did not find operations said the query statements,
Both view is Shared by DBLINK to intermediate repository, and then by the middle business system access by DBLINK library, query we provide these two views,
Is often the two view in a day or so, the next day at the time of use has been on a query condition, library doesn't DROP off in the middle of these two views, cannot see also create statements,
You can great god to analyse what reason?

CodePudding user response:

Everyone a great god online urgently

CodePudding user response:

Hint syntax error is equivalent to a hint is not effective,
Hint is to influence the optimizer manually draw the execution of the plan;
But behind this while you do more than a +, but actually hint is to take effect, you see how the execution plan,/* + FULL (P) */this hint is to watch a FULL table scan, P
Have been dealing with query condition, slow performance and may have a look the execution plan is go wrong,

CodePudding user response:

Also through dblink query is consumption performance, with network relation also is very big, you even can't see the view is what contents can't analysis,

CodePudding user response:

Dblink handling end hint driving_site (table_name)
This hint used in the business of processing data via dblink connection, its role is to push the surface to the remote database connection and then return the result, is often used in the surface is small, remote table is larger, the effect is very good,

The effectiveness, can use this hints try/* + driving_site (P) */

The SELECT/* + driving_site (P) */* FROM "V_JF_ERROR P
"

CodePudding user response:

I found the reason is because the oracle through DBLINK to query the database at the source end automatically when stitching HINT on grammar,
Details can see down below this link
http://www.oracleplus.net/arch/830.html

CodePudding user response:

It is good to solve the,

CodePudding user response:

But this can only say that to find out why promise this/* + FULL (P) + */, as for has been in the query condition performance didn't solve the problem
  • Related