Will DBMS_SQL.PARSE(DBMS_SQL.V7) suppress index in 9i partitioned table?
DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: Will DBMS_SQL.PARSE(DBMS_SQL.V7) suppress index in 9i partitioned table?

  1. #1
    Join Date
    Jan 2004
    Location
    Bangalore, India
    Posts
    66

    Exclamation Will DBMS_SQL.PARSE(DBMS_SQL.V7) suppress index in 9i partitioned table?

    Oracle Gurus,

    I encountered a strange problem in my production environment today.

    There is a procedure calling a certain SQL with an INDEX hint.
    This SQL is called using DBMS_SQL (not native dynamic SQL, for whatever reason !!). However, Iam in no postition to contest the developers who have coded it right now.

    My concern is:
    The DBMS_SQL.PARSE uses various parameters, including language_flag.
    We can pass 3 parameters viz., v6(0), native(1) and v7(2).
    Oracle supplied PL/SQL packages documentation says =>

    "Determines how Oracle handles the SQL statement. The following
    options are recognized:
     V6 (or 0) specifies version 6 behavior.
     NATIVE (or 1) specifies normal behavior for the database to
    which the program is connected.
     V7 (or 2) specifies Oracle7 behavior."
    What does this mean?

    The SQL I am concerned with, runs on a partitioned table with corresponding partitioned index (global).

    My question is: If I use the "v7" language_flag, will it suppress any INDEX hint that might exist in the SQL statement being run?

    If somebody helps me out fast, I can save a potential production embarassment (and face !)

    Thanks in advance...

    Regards,
    Suhas

  2. #2
    Join Date
    Apr 2004
    Location
    Boston MA
    Posts
    90
    As far as I know the v7 flag is the latest. It won't suppress any optimizations that 9i wants to do. You use native if you want your program to run also on oracle 6. If you want your program to run on oracle 7 and up then v7 is fine. I use native flag when I program because I don't know how it can ever be bad.
    Developers continue using dbms_sql because NDS cannot do everything dbms_sql can. With dbms_sql you have more control and it is possible to write code that runs faster and uses less resources than NDS does. Of course it is possible that your developers do not feel comfortable with NDS yet.
    d

  3. #3
    Join Date
    Jan 2004
    Location
    Bangalore, India
    Posts
    66
    Thanks a million ddrozdov !!
    I guess none of the other members are either interested in replying or do not know the solution...
    But I have something to go on now....
    Again, thanx very much, buddy.

    Regards,
    Suhas

  4. #4
    Join Date
    Aug 2002
    Location
    Colorado Springs
    Posts
    5,253
    Originally posted by suhasd75
    Thanks a million ddrozdov !!
    I guess none of the other members are either interested in replying or do not know the solution...
    But I have something to go on now....
    Again, thanx very much, buddy.

    Regards,
    Suhas
    I guess that a lot of people have just lost any interest in any of your problems you want to get solved for free.
    David Aldridge,
    "The Oracle Sponge"

    Senior Manager, Business Intelligence Development
    XM Satellite Radio
    Washington, DC

    Oracle ACE

  5. #5
    Join Date
    Nov 2002
    Location
    Geneva Switzerland
    Posts
    3,142

    Re: Will DBMS_SQL.PARSE(DBMS_SQL.V7) suppress index in 9i partitioned table?

    Originally posted by suhasd75
    If somebody helps me out fast, I can save a potential production embarassment (and face !)
    This is ensured by an arcane process known the the elite as "testing".

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width