Alter SYSTEM nls_date_format don't woking

HI All,
nl_format_date is DD/MM/YY. I what to change it to DD-MON-RRRR
i'm using this comande alter SYSTEM set nls_date_format='DD-MON-RRRR' scope=BOTH ; but i's not working.
SQL> alter SYSTEM set nls_date_format='DD-MON-RRRR' scope=BOTH ;
alter SYSTEM set nls_date_format='DD-MON-RRRR' scope=BOTH
ERROR at line 1 :
ORA-02096: the initioalisaion parameter indicated is not modified with tis option
Please any one have answer how can i change this format help me.

Hemant K Chitale wrote:
Environment settings and client side specifications can override the server side specification.
Thus, if your init.ora has one definition for NLS_DATE_FORMAT but the .profile of the login environment that is used to run sqlplus has a different definition, it is that different definition that will be active in that sqlplus session.
NLS_DATE_FORMAT may also be set different in windows registry settings.
Furthermore, an application may issue it's own ALTER SESSION command to change NLS_DATE_FORMAT.
Therefore, you must find out where the init.ora value is being overriden.
In the session Unix/Windows environment ?
In a login script that issues ALTER SESSION ?
Hemant K Chitale
http://hemantoracledba.blogspot.com
And the follow-on that I'd recommend to the OP is that apps should never depend on all of these different places to set NLS_DATE_FORMAT. I tell programmers they should either set it themselves at the session level, or (my preference) always use the TO_DATE and TO_CHAR functions to specify the format at the SQL statement level. I call that 'defensive programming'.

Similar Messages

Question about ALTER SYSTEM ARCHIVE LOG START

Good morning,
I'm trying (unsuccessfully) to get my database to be in archive log mode.
These are the steps I followed:
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size                  1375792 bytes
Variable Size             377487824 bytes
Database Buffers          150994944 bytes
Redo Buffers                5804032 bytes
Database mounted.
SQL> select log_mode from v$database;
LOG_MODE
ARCHIVELOG
SQL> show parameter log_archive_start;
NAME                                 TYPE        VALUE
log_archive_start                    boolean     FALSE
SQL> alter system archive log start;
System altered.
SQL> show parameter log_archive_start;
NAME                                 TYPE        VALUE
log_archive_start                    boolean     FALSE
SQL>I've gone thru that process twice but, I don't seem to be able to get the ARCH process to start. (newbie mistake I'm sure...)
Thank you for your help (again!),
John.

The parameter log_archive_start is no more needed John (as suggested already) and the best way to check the archive options is through the archive log list command.
[oracle@edhdr2p0-orcl oui]$ sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Tue Aug 10 10:51:57 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, Automatic Storage Management, OLAP, Data Mining
and Real Application Testing options
SQL> archive log list
Database log mode              No Archive Mode
Automatic archival             Disabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Current log sequence           13
SQL> shut immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 418484224 bytes
Fixed Size                  1336932 bytes
Variable Size             318769564 bytes
Database Buffers           92274688 bytes
Redo Buffers                6103040 bytes
Database mounted.
SQL> select process,status from V$archive_processes;
   PROCESS STATUS
         0 STOPPED
         1 STOPPED
         2 STOPPED
         3 STOPPED
         4 STOPPED
         5 STOPPED
         6 STOPPED
         7 STOPPED
         8 STOPPED
         9 STOPPED
        10 STOPPED
   PROCESS STATUS
        11 STOPPED
        12 STOPPED
        13 STOPPED
        14 STOPPED
        15 STOPPED
        16 STOPPED
        17 STOPPED
        18 STOPPED
        19 STOPPED
        20 STOPPED
        21 STOPPED
   PROCESS STATUS
        22 STOPPED
        23 STOPPED
        24 STOPPED
        25 STOPPED
        26 STOPPED
        27 STOPPED
        28 STOPPED
        29 STOPPED
30 rows selected.
SQL>
SQL> alter database archivelog;
Database altered.
SQL> alter database open;
archive log list;
Database altered.
SQL> Database log mode         Archive Mode
Automatic archival             Enabled
Archive destination            USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence     11
Next log sequence to archive   13
Current log sequence           13
SQL>
SQL> select * from V$archive_processes where status <> 'STOPPED';
   PROCESS STATUS     LOG_SEQUENCE STAT
         0 ACTIVE                0 IDLE
         1 ACTIVE                0 IDLE
         2 ACTIVE                0 IDLE
         3 ACTIVE                0 IDLEHTH
Aman....

Alter system set nls_length_semantics

Hi all,
my question concerns the scope in the change of NLS_LENGTH_SEMANTICS can be performed.
The 10gR2 documentation only the
"Modifiable ALTER SESSION"
But what about altering the system and making your own setting to default for all sessions? With which scope?
I tried
alter system set nls_length_semantics='CHAR';
alter system set nls_length_semantics='CHAR' scope=spfile;
alter system set nls_length_semantics='CHAR' scope=both;
None had really any effect. Do I have to bounce the database?

Hello,
Do I have to bounce the database?Yes, you have to shutdown and startup the database.
Else the NLS_LENGTH_SEMANTICS change won't be effective.
You may have more details on the following thread:
nls_database_parameters->nls_length_semantics Help!
There's also an interesting Note from MOS:
Examples and limits of BYTE and CHAR semantics usage (NLS_LENGTH_SEMANTICS) [ID 144808.1]They give many information about NLS_LENGTH_SEMANTICS and the following Bug:
Bug 1488174
Problem: ALTER SYSTEM does not change the setting of NLS_LENGTH_SEMANTICS for the current and new (!) sessions.
Workaround: Don't use ALTER SYSTEM SET NLS_LENGTH_SEMANTICS scope=both; but set NLS_LENGTH_SEMANTICS as a init.ora parameter or issue ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR scope=spfile; and bounce the database.Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on May 27, 2010 2:06 PM

Kill session permission without alter system permission?

Syntax to kill session is
ALTER SYSTEM KILL SESSION 'session info';
Is there a way to allow a user to kill his/her own session without granting rights to SYSTEM? I don't want anyone to be able to drop the database, but they need to be able to kill their own session. I've looked everywhere...
Thanks in advance!

Yes, assuming you are using standard definer's rights stored procedures. Only if you specify AUTHID CURRENT_USER when creating the stored procedure will you get an invoker's rights stored procedure, which would run with the privileges of the caller, not of the definer.
Justin

Ora-02065:Illegal option for alter system.

Hi Dba's,
I want to setup my database oracle 9i to use "FlashBack".
My database is running in archivelog mode.
First I've shutdown the DB and start it in mount mode.
Then I tried:
SQL> alter system set DB_FLASHBACK_RETENTION_TARGET=1800;
But it doesn't work, I always got the same error:
ora-02065:illegal option for alter system.
I tried to connect as SYS,SYSTEM, everyone, the same error. The users must have FlashBack Privilege and Execute
DBMS_FlashBack privileges. They're OK.
I don't know how to solve this problem?!
If someone could help me. Tks a lot.
Marcello

Marcello:
See this:
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=275083.1
to make sure you have other parameters setup correctly.
Tom Best

Alter system flushed shared pool in RMAN backup

Hi,
I am trying to take RMAN backup of 11.2.0.1 Database in IBM AIX 6.1 server.
The RMAN is hanging .
Though the backup gets completed, The channels allocated doesnt get released and the RMAN gets hanging.
In earlier RMAN backup Scripts,
the DBA was using alter system flush shared pool in RMAN backup script and the backup was getting succesful.
Now my question is , is using ALTER SYSTEM FLUSH SHARED POOL have any performance impact on the database.
Regards,
TEJAS

TEJAS_DBA wrote:
Hi,
I am trying to take RMAN backup of 11.2.0.1 Database in IBM AIX 6.1 server.
The RMAN is hanging .
Though the backup gets completed, The channels allocated doesnt get released and the RMAN gets hanging.Are you setting the large pool? If you don't, then rman uses the shared pool. Read about tuning rman performance in the docs.
>
In earlier RMAN backup Scripts,
the DBA was using alter system flush shared pool in RMAN backup script and the backup was getting succesful.
Now my question is , is using ALTER SYSTEM FLUSH SHARED POOL have any performance impact on the database.Yes, you are allowing the components in there to be loaded in the random order of whatever is called first. This may have a good impact if you had some fragmentation in there, or it could be mildly bad if everything was well sorted, or it could be very bad if you are unlucky or have some pattern of invalidations or should be pinning something or who-knows-what. It generally is considered not a good thing to do as a habit. You wind up with [url http://tkyte.blogspot.com/2012/05/another-debugging-story.html]rainy Monday scenarios.
Edit: I notice there are some bugs, including very slow performance when using a catalog. When you say hang, how long are you waiting? Have you considered current patches?
Edited by: jgarry on Aug 8, 2012 11:09 AM

ALTER SYSTEM

I'm fairly new to Oracle, but i'm enjoying learning these new tips and tricks. When i need to change a parameter which will affect the whole database, what I used to do is to edit the pfile and restart the database. However, lately I got to know that I can do the same thing without restarting the database by using the ALTER SYSTEM technique. Then why we don't all use this technique? Are there some disadvantages? In a particular forum there was also stated that when using this technique on Oracle9i/Oracle10g one must set scope to both. Can someone explain me what this means please? Thanks.
(Ah, my ultimate scope is to be able to set the archive redo log to on, and the 07_DICTIONARY_ACCESSIBILITY parameter to true to be able to use sys - and i want to change these parameters without possibly restarting the database)

There are two types of initialization parameters 1. Dynamic and 2. Static.
Only with the dynamic parameters you don?t have to restart the Database.
For static parameters you have to restart the Database. Moreover the technique of ALTER SYSTEM can be used only with spfile.
Scope = SPFILE: means that the change is effective at the next startup
SCOPE = MEMORY: means that the change is applied in memory only
SCOPE = BOTH: is the default value. The change is applied in both the server parameter file and memory
For static parameters SCOPE = MEMORY and SCOPE = BOTH are not allowed.
Following are the steps to enable archiving.
1. Shut down the database instance.
SHUTDOWN
2. Start the instance and mount, but do not open, the database
STARTUP MOUNT
3. Switch the database's no archiving mode. Then open the database for normal operations.
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
4. Shut down the database.
SHUTDOWN IMMEDIATE
5. Back up the database
To change O7_DICTIONARY_ACCESSIBILITY parameter
ALTER SYSTEM SET O7_DICTIONARY_ACCESSIBILITY = true SCOPE=spfile
Manu

Alter system scope=spfile not taking

This should have been brain-dead simple but something is happening I've never seen and don't understand.
Oracle SE 10.2.0.4 on Windows Serve 2003
I do an ALTER SYSTEM ... SCOPE=SPFILE, but when the database is restarted, values have reverted back.
SQL> show parameter spfile
NAME                                 TYPE        VALUE
spfile                               string      E:\ORACLE\PRODUCT\10.2.0\ROY\D
                                                 ATABASE\SPFILEROYDEV.ORA
SQL> show parameter control
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
control_files                        string      +SAN/roydev/controlfile/curren
                                                 t.261.686792331, +SAN/roydev/c
                                                 ontrolfile/current.260.6867923
                                                 31
SQL> --
SQL> alter system set control_files='x:\oradata\roydev\controlfile\control01.ctl','y:\oradata\roydev\controlfile\control02.ctl' scope=spfile;
System altered.
SQL> --
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 612368384 bytes
Fixed Size                  1298192 bytes
Variable Size             167772400 bytes
Database Buffers          440401920 bytes
Redo Buffers                2895872 bytes
Database mounted.
Database opened.
SQL> show parameter spfile
NAME                                 TYPE        VALUE
spfile                               string      E:\ORACLE\PRODUCT\10.2.0\ROY\D
                                                 ATABASE\SPFILEROYDEV.ORA
SQL> show parameter control
NAME                                 TYPE        VALUE
control_file_record_keep_time        integer     7
control_files                        string      +SAN/roydev/controlfile/curren
                                                 t.261.686792331, +SAN/roydev/c
                                                 ontrolfile/current.260.6867923
                                                 31
SQL> spool off

EdStevens wrote:
Girish Sharma wrote:
EdStevens wrote:
Ok, here's what I figured out (and I don't have any experience with Oracle Managed files either)...
The db was using the default spfile, to a point. When I did my ALTER SYSTEM, the timestamp on the default spfile was changing, and that was part of what threw me off. I finally created a pfile from the spfile, and that pfile reflected my changes, but also included a parameter -- spfile=+ASM/... yada, yada. Looking at the contents of the actual spfile (yes, I know it's a binary, but the parms themselves are clear text, so you can see what's going on .. just don't try to edit it). I saw exactly what was in the created pfile.
Next I renamed my newly created pfile, then did another CREATE PFILE FROM SPFILE, only this time specified the spfile name, pointing to the ASM based file. Sure enough, none of my changes were reflected in that file; further evidence that it was overriding. I did a sanity check on the two pfiles, merging a few things from the first into the one created from the ASM file, the created a new default spfile from that. After that life was good.
This was a first for me. Of course I've been at this long enough to have used pfiles before there were spfiles. I've seen pfiles that had a single line, 'SPFILE= ..' to point to some non-standard spfile. But I've never seen an spfile itself refer to yet another spfile.
Oh well. All's well that ends well, and I learned something new.Sorry Ed, but I am still not able to understand your solution because I am bit confused of below text specially :
only this time specified the spfile namewhat you specified here other than first one's pfile spfile=+ASM/...folder1/folder2 ?
Sure enough, none of my changes were reflected in that file; further evidence that it was overriding.completely failed to understand this line, what happened 2nd time that you did't got changes reflected; while you got in the first one pfile.
The more cause of my confusion may be poor and bad in English, but I know, I don't have poor wish of oracle learning, so I am asking for removing doubts please.
Regards
Girish SharmaOk, let me see if I can clarify.
When first approaching the database, I checked to see if it was using a pfile or spfile. A 'show parameter spfile' indicated it was using an spfile, and it was the default name in the default location (%ORACLE_HOME\database\spfile%ORACLE_SID%.ora).
Next I did a couple of ALTER SYSTEM SET .... SCOPE=SPFILE commands.
Next I bounced the database and rechecked the parameters I had set, and they were back to their original values.
After a couple of more iterations to make sure I wasn't doing something really stupid (after all, this should have been dead simple) I opened this thread, then continued to poke at it. So,
Next I created a default pfile from the default spfile - CREATE PFILE FROM SPFILE. This created %ORACLE_HOME%\database\init%ORACLE_SID%.ora.
On examining the resulting pfile, I saw my changes reflected in it, but also was surprised to see the parameter *.SPFILE=+ASM/...., so was including an addition spfile that was under ASM. (BTW, the entire purpose of this exercise was to migrate the database off of ASM.) At this point, as a sanity check I opened the default spfile - the one pointed to by the SHOW PARAMTER SPFILE command, the one in ORACLE_HOME\database. It did - as it should have - matched perfectly with the newly created pfile. So it was apparent that my ALTER SYSTEM changes were going to this default spfile but - unbeknownst to me at the outset - were being over-ridden by that second, ASM-based spfile.
At this point, I renamed the just-created pfile to something like initORCL.sav. Then created a new pfile from the ASM-based spfile - CREATE PFILE FROM SPFILE='+ASM\spfile.ora'. This new pfile was much more extensive than the first, and there were the parameters that were overriding the ones I was trying to change. I hand-modified this pfile, including some other things I found in the first, then created a new default spfile from it. So at this point I had the default spfile without it pulling in a second one that would override what I did.
Does that clarify?Yes, now its 100% clear to me.
Thank you.
Regards
Girish Sharma

Alter database OR alter system?? what is the logic?

Hi,
this is just a general question not related to any particular issue. I seem to be missing the logic behind when we need to use the "alter system ... " statements and when we need to use the "alter database ..." statements. Is there a logic I can use to guess ? Or we only need to remember them (or look up for them)?
Let's take an example.
alter database archivelog; & alter system checkpoint;
OR
alter database add logfile; & alter system set undo_retention=800;
If you have a key that can be generally applied please let me know as I am not able to find it. Thank you,
enrico

I am not sure if there is a general rule but this is what I use:
alter database is about modifying the database architecture, like data files, archived log files etc.
alter system is about modifying the instance. so, you are modifying the way oracle runs. Remember that all parameters should be done with alter system (like undo_retention)
hope this will help you.

ALTER SYSTEM SET _awr_flush_threshold_metrics=TRUE SCOPE=MEMORY;

Hi,
our DB in 10g R2 on Win 2003 server has suddenly restarted with this message in alertlog :
ALTER SYSTEM SET awrflush_threshold_metrics=TRUE SCOPE=MEMORY;
I looked for this parameter in oracle documentation, I did not find.
1-what is this parameter for ?
2-How can I see which user connection has altered this parameter ?
Thanks.

user522961 wrote:
Hi,
our DB in 10g R2 on Win 2003 server has suddenly restarted with this message in alertlog :
ALTER SYSTEM SET awrflush_threshold_metrics=TRUE SCOPE=MEMORY;
I looked for this parameter in oracle documentation, I did not find.
1-what is this parameter for ?
2-How can I see which user connection has altered this parameter ?
Thanks.I don't think that you should be worried about it as its an undocumented parameter.
http://www.orafaq.com/parms/parm113.htm
Without Auditing, its not possible who changed it(if he really did)?
HTH
Aman....

Executing alter system enable restricted session on RAC nodes

alter system enable restricted session command enables restricted mode only on the node on which it runs. I need that all nodes entering this node after executing this statement.
Please help.

Something like this using ssh and ksh:
export db_name=<your database name as appears in crs_stat>
srvctl status database -d ${db_name} | while read a inst b c d e node
do
ssh -f $node "print $inst | . oraenv; print 'alter system enable restricted session;' | sqlplus / as sysdba"
done
or you using dbms_job (old but easer to tie to instance than dbms_scheduler):
declare
job binary_integer;
begin
for i in (select inst_id from gv$instance)
loop
dbms_job.submit (
job=>job,
what=> 'begin execute immediate ''alter system enable restricted session''; end;',
instance=>i.inst_id
commit;
end loop;
end;
/

Alter system or alter session set events

Can we use interchangeably alter session or alter system set events?
Thank you.

DBA-ES wrote:
For example this statement
alter session set events '8103 trace name errorstack level 3';
Can it be done at the system level? How to check it?Sure it can be,
SQL*Plus: Release 11.2.0.1.0 Production on Fri Oct 21 15:32:54 2011
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> alter session set events '8103 trace name errorstack level 3';
Session altered.
SQL> alter system set events '8103 trace name errorstack level 3';
System altered.
SQL>And to check, for the alter system , the statement would be logged in the alert log,
Fri Oct 21 15:31:46 2011
OS Pid: 4656 executed alter system set events '8103 trace name errorstack level 3'
D:\app\aristadba\diag\rdbms\orcl112\orcl112\trace>sqlplus / as sysdbaHTH
Aman....

ALTER SYSTEM KILL SESSION

Hello Everybody,
1) Is there any difference between “ALTER SYSTEM KILL SESSION & “kill -9”? Which one is the preferred method?
2) When we do alter system kill 'sid, serial#'. Are we killing the user process or the server process?
thanks in advance

Welcome to the forum!
Whenever you post provide your 4 digit Oracle version (result of SELECT * FROM V$VERSION)
>
Hello Everybody,
1) Is there any difference between “ALTER SYSTEM KILL SESSION & “kill -9”? Which one is the preferred method?
2) When we do alter system kill 'sid, serial#'. Are we killing the user process or the server process?
>
You should only use the 'kill' from the OS as a last resort.
There are TWO Oracle options: KILL session and DISCONNECT session. Only rarely, in my experience will DISCONNECT SESSION not get the job done.
See ALTER SYSTEM in the SQL Language doc
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
>
end_session_clauses
The end_session_clauses give you several ways to end the current session.
DISCONNECT SESSION Clause
Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever). To use this clause, your instance must have the database open. You must identify the session with both of the following values from the V$SESSION view:
•For integer1, specify the value of the SID column.
•For integer2, specify the value of the SERIAL# column.
If system parameters are appropriately configured, then application failover will take effect.
•The POST_TRANSACTION setting allows ongoing transactions to complete before the session is disconnected. If the session has no ongoing transactions, then this clause has the same effect described for as KILL SESSION.
•The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
◦If you also specify POST_TRANSACTION and the session has ongoing transactions, then the IMMEDIATE keyword is ignored.
◦If you do not specify POST_TRANSACTION, or you specify POST_TRANSACTION but the session has no ongoing transactions, then this clause has the same effect as described for KILL SESSION IMMEDIATE.
See Also:
"Disconnecting a Session: Example"
KILL SESSION Clause
The KILL SESSION clause lets you mark a session as terminated, roll back ongoing transactions, release all session locks, and partially recover session resources. To use this clause, your instance must have the database open. Your session and the session to be terminated must be on the same instance unless you specify integer3.You must identify the session with the following values from the V$SESSION view:
•For integer1, specify the value of the SID column.
•For integer2, specify the value of the SERIAL# column.
•For the optional integer3, specify the ID of the instance where the target session to be killed exists. You can find the instance ID by querying the GV$ tables.
If the session is performing some activity that must be completed, such as waiting for a reply from a remote database or rolling back a transaction, then Oracle Database waits for this activity to complete, marks the session as terminated, and then returns control to you. If the waiting lasts a minute, then Oracle Database marks the session to be terminated and returns control to you with a message that the session is marked to be terminated. The PMON background process then marks the session as terminated when the activity is complete.
Whether or not the session has an ongoing transaction, Oracle Database does not recover the entire session state until the session user issues a request to the session and receives a message that the session has been terminated.
See Also:
"Terminating a Session: Example"
IMMEDIATE Specify IMMEDIATE to instruct Oracle Database to roll back ongoing transactions, release all session locks, recover the entire session state, and return control to you immediately.

Doubt with alter system

I have the doubt with the statement like :
SQL> alter system set OPTIMIZER_FEATURES_ENABLE=8.1.7 scope=both;
is going to permanently alter the system or for that particular instance or session. I mean is it done once or everytime in a new session. Also, how to see the currect value of this parameter, I mean how to query it?
I hope, my question is clear.
Please, help in solving the doubt.
regards

user574290 wrote:
I have the doubt with the statement like :
SQL> alter system set OPTIMIZER_FEATURES_ENABLE=8.1.7 scope=both;
is going to permanently alter the system or for that particular instance or session. I mean is it done once or everytime in a new session. Also, how to see the currect value of this parameter, I mean how to query it?
I hope, my question is clear. Well, here is what alter system about SPFILE is
http://download.oracle.com/docs/cd/B19306_01/server.102/b14231/create.htm#sthref445
From it,
>
SCOPE = BOTH The change is applied in both the server parameter file and memory. The effect is as follows:
For dynamic parameters, the effect is immediate and persistent.
For static parameters, this specification is not allowed.>
So this setting will persist across the session logon and log off.
Suggestion, its good to check oracle docs, choke full of useful info.
HTH
Aman....

Please help me in this command alter system

I enter to DB as dba from toad and try to execute this command to alter the format mask of the date
ALTER SYSTEM SET NLS_DATE_FORMAT='dd/mm/yyyy' SCOPE =
SPFILE;
but this error come for me
ORA-02096: specified initialization parameter is not modifiable with this option

I am not sure why you got error? Its working fine for me,
SQL> alter system set nls_date_format='dd/mm/yyyy' scope=spfile;
System altered.
SQL> select * from V$version;
BANNER
--------------------------------------------------------------------------------Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL Release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
TNS for Linux: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - ProductionHTH
Aman....

Alter SYSTEM nls_date_format don't woking

Similar Messages

Maybe you are looking for