DBAsupport.com Forums - Powered by vBulletin
Results 1 to 5 of 5

Thread: Ora-2096 Setting Hash_join_enabled scope=SPFILE

  1. #1
    Join Date
    Dec 2005
    Posts
    5

    Ora-2096 Setting Hash_join_enabled scope=SPFILE

    Hi,

    I can change the setting for hash_join_enabled in Oracle 9.2.0.5 (Windows 2003)

    Server ORA_SERVER con Oracle Version 9.2.0.5.0
    SQL> alter system set hash_join_enabled=true scope=spfile ;
    System altered.
    SQL> select NAME, VALUE, ISSES_MODIFIABLE, ISSYS_MODIFIABLE from v$parameter where name = 'hash_join_enabled';
    NAME=hash_join_enabled
    VALUE=TRUE
    ISSES_MODIFIABLE=TRUE
    ISSYS_MODIFIABLE=FALSE
    In my Db 9.2.0.5 hash_join_enabled is already TRUE


    But I've tried in two Oracle 9.2.0.1 (windows 2000) one with hash_join_enabled=true the other with hash_join_enabled=false. In both cases I received the error:

    alter system set hash_join_enabled=true scope=spfile
    *
    ERROR at line 1:
    ORA-02096: specified initialization parameter is not modifiable with this option

    Can it be a Bug or am I doing something wrongly?



    Thanks in advance

  2. #2
    Join Date
    Mar 2002
    Posts
    534

  3. #3
    Join Date
    Mar 2004
    Location
    DC,USA
    Posts
    650
    Quote Originally Posted by mike9

    https://metalink.oracle.com/metalink/plsql/f?p=200:27:4465837078511398338

    HTML Code:
    MetaLink V2 - Note 
     Invalid Document ID
    Can you copy here directly
    "What is past is PROLOGUE"

  4. #4
    Join Date
    Mar 2002
    Posts
    534
    Sorry for the invalid link.

    The bug seems to be fixed in 9.2.0.3. It is documented in the Metalink Note: 2662838.8.
    https://metalink.oracle.com/metalink...p_id=2662838.8

    PS: I don't like the new metalink URL, they are too long (e.g.https://metalink.oracle.com/metalink...,1,1,helvetica)
    Last edited by mike9; 12-21-2005 at 04:03 PM.

  5. #5
    Join Date
    Dec 2005
    Posts
    5
    Mike9, dBasan

    Thank you very much!

    I had found something similar in metalink with parameter nls_date_format, but I couldn't find the generic bug.

    I'm going to explain this, to my client, and maybe I going to do the workaround.

    Thanks very much again.

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