![]() ![]() As we observed above, we were able to reduce by a large percentage many of the waits and the time spent waiting by simply using bind variables. A poorly written program may experience a large gain in performance by setting the CURSOR_SHARING=FORCE parameter, but it will still be running slower than it should, and it will still be limited in the degree to which it can scale. There are side effects from cursor sharing that you must aware of as well. This is a step in the right direction, but should not be the final solution to the problem and should not be used long term. Select * from emp where ename = :SYS_B_0 ![]() This feature will take a query such select * from emp where ename = 'KING' It causes the database to rewrite your query using bind variables before parsing it. Cursor sharing is an 'auto binder' of sorts. In Oracle8i, release 2 (version 8.1.6), Oracle introduced a new feature called CURSOR_SHARING. Specifically in chapter 10 I wrote in part: To get the OTHER side of the coin, you can read another book "Expert one on one Oracle" (written by me). Well, you are on 8.0.4 (very old, unsupported) and this was introduced in 816. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |