Changing v$nls_parameters

Hi,
I need to change the value in v$nls_parameters;I can execute alter session command but the change is for the current session.If i want to change it permanently..what would the command????
I executed :Alter session set nls_date_format='DD.MM.YYYY';But if i use alter system it returns an error.
Please suggest me....

select name,issys_modifiable from v$parameter where upper(name) like '%NLS%';
It will tell you which nls% parameter can be changed by alter system command, FALSE means you can not use alter session....; you have to set in your init<sid>.ora.
Now you wish to change nls_date_format which is FALSE as above query; so you have to :
Alter system set nls_date_format='DD.MM.YYYY' scope=spfile;
shutdown immediate;
startup;
HTH
Girish Sharma

Similar Messages

  • Changing values in v$nls_parameters.

    below is the result of query. Select * from v$nls_parameters.
    i want to change the value of parameter NLS_LANGUAGE FROM AMERICAN TO RUSSIAN. NLS_TERRITORY FROM AMERICA TO RUSSIA AND NLS_CHARACTERSET FROM WE8MSWIN1252 TO UTF8.
    How can i do this.
    Also is the territory russia and language russian is correct.
    if i set the NLS_LANG FROM AMERICAN_AMERICA.WE8MSWIN1252 (which is present in the rgistery) to RUSSIAN_RUSSIA.UTF8, Will this work. and wat will be the values in the view V$NLS_PARAMETER.
    plz help this is very urgent.
    PARAMETER      VALUE
    NLS_LANGUAGE      AMERICAN
    NLS_TERRITORY      AMERICA
    NLS_CURRENCY      $
    NLS_ISO_CURRENCY      AMERICA
    NLS_NUMERIC_CHARACTERS      .,
    NLS_CALENDAR      GREGORIAN
    NLS_DATE_FORMAT      DD-MON-RR
    NLS_DATE_LANGUAGE      AMERICAN
    NLS_CHARACTERSET      WE8MSWIN1252
    NLS_SORT      BINARY
    NLS_TIME_FORMAT      HH.MI.SSXFF AM
    PARAMETER      VALUE
    NLS_TIMESTAMP_FORMAT      DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT      HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT      DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY      $
    NLS_NCHAR_CHARACTERSET      AL16UTF16
    NLS_COMP      BINARY
    NLS_LENGTH_SEMANTICS      BYTE
    NLS_NCHAR_CONV_EXCP      FALSE
    Message was edited by:
    437022
    Message was edited by:
    437022

    First, why do want to do this? What do want to accomplish?
    Setting language and territory parameters can be done
    1) at app level (alter session... or NLS_LANG or maybe app specific settings)
    2) at instance level (alter system... or parameter file), which defaults sessions settings.
    Character set is another matter. You cant just "change" character set of the database. You should read the Globalization Support guide, there's even a chapter about character set migration. Setting NLS_LANG=.<char set> is only used for indicating to which character set oracle should convert to for your specific application. You tell oracle how your app or os locale expects charcter data to be encoded.
    What is you database char set now?
    sql> select * from nls_database_parameters where parameter like '%CHARACTERSET';

  • How change NLS_PARAMETERS

    Hi
    I need change the nls paramaters from my 10g database.
    ..

    you can find how to change nls parameters in the below link
    http://www.oracle.com/technetwork/database/globalization/nls-lang-099431.html?ssSourceSiteId=otncn
    Edited by: user8403888 on Dec 22, 2011 1:25 AM

  • OAF changes Date Format

    Hi
    I need to store a date into a flexfield. We have enabled the Flexfield and there is NO value set attached to it.
    This attribute is already in the VO as a varchar, so we have just added a new column into the page as data type Date and link it to the flexfield column.
    In this page we have a table layout so the user can enter 10 rows before saving them. And this page it just used to punch data into a table, which means, once the user press apply the page saves and clears. The user can not query on that page.
    When entering the first row, we can open the Date picker and we can choose the date and then it populates the column as “DD-MON-YYYY”.
    The problem is:
    When we entering the second row after entering one column the pages changes the format of my date from the previous record to “YYYY-MM-DD”, then after entering any second column the pages clear the date from the previous row.
    Running the page from JDev it shows the following message before clears the flexfield:
    java.text.ParseException: 2011-01-28
    Note we have not extended the VO and not extended the controller.
    My questions are:
    1) Why the Self-Service is change the date format to YYYY-MM-DD even if the profile ICX: Date Format Mask (31-DEC-1999) and my preference is set to DD-MON-YYYY?
    2) How can I avoid this to happen? Is there any way to keep my date as DD-MON-YYYY?
    Thanks,
    Alex

    Alex,
    That was the update from Oracle support, when we raised it,
    But I did the following to handle that, I feel this is not the right way, since we had that issue as SEV1, I did that as a workaround,
    Check this this might help.
    package oracle.apps.xxper.selfservice.appraisals.webui;
    import com.sun.java.util.collections.HashMap;
    import java.io.Serializable;
    import oracle.apps.fnd.common.VersionInfo;
    import oracle.apps.fnd.framework.OAApplicationModule;
    import oracle.apps.fnd.framework.OAException;
    import oracle.apps.fnd.framework.webui.*;
    import oracle.apps.fnd.framework.webui.beans.OAWebBean;
    import oracle.apps.fnd.framework.webui.beans.form.OASubmitButtonBean;
    import oracle.apps.fnd.framework.webui.beans.message.OAMessageCheckBoxBean;
    import oracle.apps.per.selfservice.appraisals.ApprConstants;
    import oracle.apps.per.selfservice.arch.webui.PerOAControllerImpl;
    import oracle.apps.per.selfservice.common.webui.CommonCO;
    import oracle.apps.per.selfservice.compgaps.Constants;
    import oracle.apps.per.selfservice.appraisals.webui.MAFinalRatingsPageCO;
    import oracle.apps.fnd.framework.server.OADBTransaction;
    import oracle.apps.fnd.framework.OAViewObject;
    import java.sql.CallableStatement;
    import java.sql.ResultSet;
    import oracle.jbo.Row;
    import oracle.apps.fnd.framework.webui.beans.message.OAMessageDateFieldBean;
    import oracle.apps.per.selfservice.appraisals.server.AppraisalVORowImpl;
    public class XXPERMAFinalRatingsPageCO extends MAFinalRatingsPageCO
    public void processRequest(OAPageContext pageContext, OAWebBean webBean)
    super.processRequest(pageContext, webBean);
    writeLog("XXPER",pageContext,"Start PR XXPERMAFinalRatingsPageCO ");
    OAMessageDateFieldBean dateBean =(OAMessageDateFieldBean) webBean.findChildRecursive("DeliveryDateTime");
    if(dateBean !=null )
    String dateBeanValue = (String) dateBean.getValue(pageContext) ;
    writeLog("XXPER",pageContext,"dateBean Value "+dateBeanValue);
    if(dateBeanValue !=null)
    if(dateBeanValue.indexOf(".0") !=-1)
    dateBeanValue = dateBeanValue.substring(0,dateBeanValue.length()-2);
    writeLog("XXPER",pageContext,"dateBean Updated Value "+dateBeanValue);
    String dateMaskQry = "SELECT value FROM V$NLS_Parameters WHERE parameter ='NLS_DATE_FORMAT'";
    writeLog("XXPER",pageContext,"dateMaskQry "+dateMaskQry);
    String dateMask = (String) executeSql(dateMaskQry, pageContext, webBean);
    writeLog("XXPER",pageContext,"dateMask : "+dateMask);
    String dateConvertQry = "select to_char(fnd_date.canonical_to_date('"+dateBeanValue+"') ,'"+dateMask+" HH24:MI:SS') from dual";
    writeLog("XXPER",pageContext,"dateConvertQry "+dateConvertQry);
    String convertedDateValue = (String) executeSql(dateConvertQry,pageContext,webBean);
    writeLog("XXPER",pageContext,"convertedDateValue "+convertedDateValue);
    if(convertedDateValue == null )
    convertedDateValue = dateBeanValue;
    dateBean.setValue(pageContext,convertedDateValue);
    writeLog("XXPER",pageContext,"After set the value "+convertedDateValue);
    setAttribute3(pageContext, convertedDateValue);
    writeLog("XXPER",pageContext,"After set the VO value "+convertedDateValue);
    }else
    writeLog("XXPER",pageContext,"dateBean value is null from the bean Get the value from getAttribute3() method");
    dateBeanValue = getAttribute3(pageContext);
    dateBean.setValue(pageContext,dateBeanValue);
    }else
    writeLog("XXPER",pageContext,"dateBean is null ");
    writeLog("XXPER",pageContext,"End PR XXPERMAFinalRatingsPageCO ");
    public void processFormRequest(OAPageContext pageContext, OAWebBean webBean)
    writeLog("XXPER",pageContext,"Start PFR XXPERMAFinalRatingsPageCO ");
    writeLog("XXPER",pageContext,"Event Param "+pageContext.getParameter(EVENT_PARAM));
    OAMessageDateFieldBean dateBean =(OAMessageDateFieldBean) webBean.findChildRecursive("DeliveryDateTime");
    if(dateBean !=null )
    String dateBeanValue = (String) dateBean.getValue(pageContext) ;
    if(dateBeanValue !=null)
    if(dateBeanValue.indexOf(".0") !=-1)
    dateBeanValue = dateBeanValue.substring(0,dateBeanValue.length()-2);
    writeLog("XXPER",pageContext,"dateBean Updated Value "+dateBeanValue);
    String dateMaskQry = "SELECT value FROM V$NLS_Parameters WHERE parameter ='NLS_DATE_FORMAT'";
    writeLog("XXPER",pageContext,"dateMaskQry "+dateMaskQry);
    String dateMask = (String) executeSql(dateMaskQry, pageContext, webBean);
    writeLog("XXPER",pageContext,"dateMask : "+dateMask);
    String dateConvertQry = "select to_char(fnd_date.canonical_to_date('"+dateBeanValue+"') ,'"+dateMask+" HH24:MI:SS') from dual";
    //String dateConvertQry = "select fnd_date.string_to_canonical('"+dateBeanValue+"','"+dateMask+" HH24:MI:SS') from dual";
    writeLog("XXPER",pageContext,"dateConvertQry "+dateConvertQry);
    String convertedDateValue = (String) executeSql(dateConvertQry,pageContext,webBean);
    writeLog("XXPER",pageContext,"convertedDateValue "+convertedDateValue);
    if(convertedDateValue == null )
    convertedDateValue = dateBeanValue;
    dateBean.setValue(pageContext,convertedDateValue);
    writeLog("XXPER",pageContext,"After set the value "+convertedDateValue);
    setAttribute3(pageContext, convertedDateValue);
    writeLog("XXPER",pageContext,"After set the VO value "+convertedDateValue);
    }else
    writeLog("XXPER",pageContext,"dateBean is null ");
    writeLog("XXPER",pageContext,"End PFR XXPERMAFinalRatingsPageCO ");
    super.processFormRequest(pageContext, webBean);
    writeLog("XXPER",pageContext,"End PFR XXPERMAFinalRatingsPageCO (After Super Call )");
    public void writeLog(String moduleName, OAPageContext pageContext, String diagText)
    if(pageContext.isLoggingEnabled(OAWebBeanConstants.STATEMENT))
    System.out.println(moduleName+" : "+diagText);
    pageContext.writeDiagnostics(moduleName,diagText,OAWebBeanConstants.STATEMENT);
    * Method to execute SQL.
    public Object executeSql(String pSqlStmt, OAPageContext pageContext , OAWebBean webBean)
    OADBTransaction tx = pageContext.getApplicationModule(webBean).getOADBTransaction();// (OADBTransaction)getOADBTransaction();
    Object lObject = null;
    // Create the callable statement
    CallableStatement lCstmt = (CallableStatement)tx.createCallableStatement(pSqlStmt, 1);
    ResultSet rs = null;
    try
    rs = lCstmt.executeQuery();
    while(rs.next())
    lObject = rs.getObject(1);
    catch (Exception e)
    //throw OAException.wrapperException(e);
    finally
    try {
    if(rs!=null)
    rs.close();
    if(lCstmt != null)
    lCstmt.close();
    catch(Exception e) {
    throw OAException.wrapperException(e);
    return lObject;
    } // executeSql
    public void setAttribute3(OAPageContext pageContext, String dateValue)
    OAApplicationModule rootAM = pageContext.getRootApplicationModule();
    OAApplicationModule apprAM = (OAApplicationModule)rootAM.findApplicationModule("AppraisalsAM");
    OAViewObject appraisalVO = (OAViewObject)apprAM.findViewObject("AppraisalVO");
    writeLog("XXPER",pageContext,"appraisalVO "+appraisalVO);
    if(appraisalVO !=null)
    AppraisalVORowImpl appraisalVORow = (AppraisalVORowImpl) appraisalVO.getCurrentRow();
    if(appraisalVORow !=null)
    int attrCount = appraisalVO.getAttributeCount();
    writeLog("XXPER",pageContext,"Attrbuute count "+attrCount);
    String[] attributeNames = appraisalVORow.getAttributeNames();
    appraisalVORow.setAttribute3(dateValue);
    public String getAttribute3(OAPageContext pageContext)
    OAApplicationModule rootAM = pageContext.getRootApplicationModule();
    OAApplicationModule apprAM = (OAApplicationModule)rootAM.findApplicationModule("AppraisalsAM");
    String attribute3Value = "N";
    OAViewObject appraisalVO = (OAViewObject)apprAM.findViewObject("AppraisalVO");
    writeLog("XXPER",pageContext,"appraisalVO "+appraisalVO);
    if(appraisalVO !=null)
    AppraisalVORowImpl appraisalVORow = (AppraisalVORowImpl) appraisalVO.getCurrentRow();
    if(appraisalVORow !=null)
    int attrCount = appraisalVO.getAttributeCount();
    writeLog("XXPER",pageContext,"Attrbuute count "+attrCount);
    String[] attributeNames = appraisalVORow.getAttributeNames();
    writeLog("XXPER",pageContext," AppraisalId :- "+ appraisalVORow.getAppraisalId());
    attribute3Value = (String)appraisalVORow.getAttribute3();
    String attribute1Value = (String)appraisalVORow.getAttribute1();//getAttribute2
    String attribute2Value = (String)appraisalVORow.getAttribute2();
    writeLog("XXPER",pageContext," attribute3Value :- "+attribute3Value + " attribute1Value "+ attribute1Value +"attribute2Value "+attribute2Value);
    }else
    writeLog("XXPER",pageContext," appraisalVORow is null ");
    }else
    writeLog("XXPER",pageContext," appraisalVO is null ");
    return attribute3Value;
    }

  • Changing database character set

    Can anyone help with the way to change the database character set.
    I am runn into problem while exporting with error message exp-00091
    Thanks

    You don't need to change the database character set. You have only to set the correct character set at
    OS level before doing the export. Execute the following at Sql prompt as DBA :
    SQL> select * from v$nls_parameters
      2* where parameter in ('NLS_LANGUAGE', 'NLS_TERRITORY', 'NLS_CHARACTERSET')
    SQL> /
    PARAMETER            VALUE
    NLS_LANGUAGE         AMERICAN
    NLS_TERRITORY        AMERICA
    NLS_CHARACTERSET     WE8ISO8859P15
    SQL>then at OS prompt :
    $ export NLS_LANG=AMERICAN_AMERICA.WE8ISO8859P15
    $ exp ..............
    Of course you have to use your values.

  • How to change the database character set on physical standby database?

    Hi,
    We have a database with character set WE8ISO8859P1 and migrated the character set to WE8MSWIN1252 using csscan/csalter scripts. This database has a physical standby database setup also and after the migration, the physical standby database is still showing the character set as WE8ISO8859P1. How can I change the characterset on the physical standby? I raised a Service Request with Oracle, and they said that recreating the standby database is the only supported way of changing the char set on the standby database. Is this true?
    Thanks,
    Sreekanth

    Thank you, Robert, for your reply.
    The standby is in sync with the primary.
    see below
    SYS@sisprod>select * from v$dataguard_stats;
    NAME VALUE UNIT TIME_COMPUTED
    apply finish time +00 00:00:00.0 day(2) to second(1) interval 12-NOV-2009 14:02:46
    apply lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
    estimated startup time 11 second 12-NOV-2009 14:02:46
    standby has been open N 12-NOV-2009 14:02:46
    transport lag +00 00:00:00 day(2) to second(0) interval 12-NOV-2009 14:02:46
    SYS@sisprod>
    I am selecting from v$nls_parameters;
    I don't know how to restore the controlfile from primary. Could you please tell me how to do it?
    Thanks,
    Sreekanth

  • How to change character set

    hi my database character set is non-AL32UTF8 HOW can i change this to be AL32UTF8 am in database 11g
    SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
    PARAMETER
    VALUE
    NLS_CHARACTERSET
    WE8MSWIN1252
    NLS_NCHAR_CHARACTERSET
    AL16UTF16
    there is something in database i cannot drop database

    i did this
    SQL> @C:\app\Tshifhiwa\product\11.2.0\dbhome_1\RDBMS\ADMIN\csalter.plb
    insert into csm$dictusers
    ERROR at line 1:
    ORA-00942: table or view does not exist
    Function created.
    Warning: Function created with compilation errors.
    Warning: Procedure created with compilation errors.
    This script will update the content of the Oracle Data Dictionary.
    Please ensure you have a full backup before initiating this procedure.
    Would you like to proceed (Y/N)?y
    old   6:     if (UPPER('&conf') <> 'Y') then
    new   6:     if (UPPER('y') <> 'Y') then
        csm$main();
    ERROR at line 10:
    ORA-06550: line 10, column 5:
    PLS-00905: object SYS.CSM$MAIN is invalid
    ORA-06550: line 10, column 5:
    PL/SQL: Statement ignored
        select value into svalue from csm$parameters where name='CSALTER_FINISHED';
    ERROR at line 9:
    ORA-06550: line 9, column 35:
    PL/SQL: ORA-00942: table or view does not exist
    ORA-06550: line 9, column 5:
    PL/SQL: SQL Statement ignored
    ORA-06550: line 18, column 35:
    PL/SQL: ORA-00942: table or view does not exist
    ORA-06550: line 18, column 5:
    PL/SQL: SQL Statement ignored
    ORA-06550: line 21, column 38:
    PL/SQL: ORA-00942: table or view does not exist
    ORA-06550: line 21, column 8:
    PL/SQL: SQL Statement ignored
    ORA-06550: line 27, column 35:
    PL/SQL: ORA-00942: table or view does not exist
    ORA-06550: line 27, column 5:
    PL/SQL: SQL Statement ignored
    ORA-06550: line 30, column 38:
    PL/SQL: ORA-00942: table or view does not exist
    ORA-06550: line 30, column 8:
    PL/SQL: SQL Statement ignored
    delete from csm$dictusers where username in ('PM', 'SH', 'HR', 'OE')
    ERROR at line 1:
    ORA-00942: table or view does not exist
    Function dropped.
    Function dropped.
    Procedure dropped.
    SQL> shutdown immediate;
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
    ALTER SYSTEM ENABLE RESTRICTED SESSION
    ERROR at line 1:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
    ERROR:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0
    ERROR at line 1:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
    ERROR:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    ALTER SYSTEM SET AQ_TM_PROCESSES=0
    ERROR at line 1:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
    ERROR:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0
    ERROR at line 1:
    ORA-01034: ORACLE not available
    Process ID: 4360
    Session ID: 139 Serial number: 6
    SQL> connect /as sysdba
    Connected to an idle instance.
    SQL> startup mount;
    ORACLE instance started.
    Total System Global Area  535662592 bytes
    Fixed Size                  1375792 bytes
    Variable Size             373293520 bytes
    Database Buffers          155189248 bytes
    Redo Buffers                5804032 bytes
    Database mounted.
    SQL> ALTER SYSTEM ENABLE RESTRICTED SESSION;
    System altered.
    SQL> ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
    System altered.
    SQL> ALTER SYSTEM SET AQ_TM_PROCESSES=0;
    System altered.
    SQL> ALTER DATABASE OPEN;
    Database altered.
    SQL> ALTER DATABASE CHARACTER SET 'AL32UTF8';
    ALTER DATABASE CHARACTER SET 'AL32UTF8'
    ERROR at line 1:
    ORA-24329: invalid character set identifier
    SQL> ALTER DATABASE CHARACTER SET AL32UTF8;
    ALTER DATABASE CHARACTER SET AL32UTF8
    ERROR at line 1:
    ORA-12712: new character set must be a superset of old character set
    SQL> select * from v$nls_parameters where parameter like '%CHARACTERSET%';
    PARAMETER
    VALUE
    NLS_CHARACTERSET
    WE8MSWIN1252
    NLS_NCHAR_CHARACTERSET

  • Unable to change NLS_LENGTH_SEMANTICS

    I am currently trying to run a UTF8 enabled application on a Oracle 11.2.0.1.0 database, and have been having trouble storing some characters into the DB. I have been advised by the application support that the product can definitely do store them, and that I must set the NLS_LENGTH_SEMANTICS parameter to CHAR using the following statement;
    ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR SCOPE=BOTH;
    However after logging into the target database as the "systems" user and running this statement, which runs successfully, querying the "v$nls_parameters" still shows that it is set to "BYTE". I have tried then creating a new database and setting this value to CHAR in the advanced settings, but still to no avail.
    However after googling this and reading several articles I have began to notice some other strange behaviour. The first thing i noticed was the "SPFILE{dbname}.ORA" file contains the right value i.e;
    *.nls_length_semantics='CHAR'
    The second thing that I noticed was that running the "v$nls_parameters" query in SQL Developer produced a different result to the one produced by SQL Plus (See below) even though exactly the same user in the same database is being used. In SQL developer the following query "select * from v$nls_parameters where Parameter = 'NLS_LENGTH_SEMANTICS';" produces;
    PARAMETER VALUE
    NLS_LENGTH_SEMANTICS BYTE
    1 rows selected
    Where as in SQLPLUS this query produces;
    SQL> select * from v$nls_parameters where Parameter = 'NLS_LENGTH_SEMANTICS';
    PARAMETER
    VALUE
    NLS_LENGTH_SEMANTICS
    CHAR
    Can anyone provide any insight as to what could be the problem with my oracle database setup, as the application developers are adamant that UTF8 chars are supported and the only difference they can see between my setup (which doesnt work) and theirs (which does work) is the value of this parameter. Details of my system are;
    OS: Windows 7 x64
    SQL Developer: 2.1.0.63
    DATABASE: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    PL/SQL Release 11.2.0.1.0 - Production
    CORE     11.2.0.1.0     Production
    TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
    NLSRTL Version 11.2.0.1.0 - Production

    Forum for NLS / Globalization Support discussions:
    Globalization Support
    user10600690 wrote:
    I am currently trying to run a UTF8 enabled application on a Oracle 11.2.0.1.0 database, Is this database created with db charset of AL32UTF8?
    and have been having trouble storing some characters into the DB. What kind of trouble?
    ALTER SYSTEM SET NLS_LENGTH_SEMANTICS=CHAR SCOPE=BOTH;
    However after logging into the target database as the "systems" user and running this statement, which runs successfully, querying the "v$nls_parameters" still shows that it is set to "BYTE". I have tried then creating a new database and setting this value to CHAR in the advanced settings, but still to no avail. You've changed one parameter and looked at another.
    There are different "levels" in what you wrote in the previous quote. Take a look at the dictionary views (http://download.oracle.com/docs/cd/E11882_01/server.112/e10729/ch3globenv.htm#i1006415)
    NLS_SESSION_PARAMETERS (compare to v$nls_parameters, on which the view is based)
    NLS_INSTANCE_PARAMETERS (alter system set nls...)
    NLS_DATABASE_PARAMETERS (creating a new database...)
    You may need to bounce the instance for the setting to have any effect (even with scope=both) for new sessions. At least I think that was the case in some previous release.
    Note that I do not think you can (or, at least, should) create a database with semantics=char. The "advcanced settings" probably referred to instance parameters.
    The first thing i noticed was the "SPFILE{dbname}.ORA" file contains the right value i.e;
    *.nls_length_semantics='CHAR'Yes, the instance level view should agree.
    >
    The second thing that I noticed was that running the "v$nls_parameters" query in SQL Developer produced a different result to the one produced by SQL Plus Could be different client config/environment settings affecting session parameters. Compare with session level view.

  • V$nls_parameters

    Does anyone knows how to change the character set in v$nls_parameters?
    Eg
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET WE8ISO8859P1
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    to
    NLS_LANGUAGE ENGLISH
    NLS_TERRITORY UNITED KINGDOM
    NLS_CURRENCY z
    NLS_ISO_CURRENCY UNITED KINGDOM
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE ENGLISH
    Thanks!

    Hi
    There is table props$ owned from sys. You can change this data in it but be cearful. The knew data is available after shutdown and startup of database but if you set wrong value database cannot be started. If you change characterset and you have old data with national characters you may have problem with them.
    I did this change in my practice and it work.
    Regards
    null

  • Pppd and vpnd changed.....Format String Vulnerability probably cause?

    Looks like I am hit with this pppd problem. Noticed when I ran disk utility that pppd and vpnd (I use Cisco VPN) were changed and could not be repaired.
    I cannot get net access at all, but I can do an ssh using terminal, sftp, and use screen sharing app (which is ssh). I can print to a network printer. Cannot get connected inside my work. When outside my domain, I can reach all, expect my work domain.
    OK, my options seem limited. I must scrape and rebuild, as far as I see it. Is theer another option?
    Thanks to all who respond.

    I actually want the date format of DD-MON-YY. Which, from what I understand, is the default format for both Oracle 8.0.5 and 9.2.03. I'm trying to figure out why it is now displaying as 'yyyy-mm-dd hh24:mi:ss'. I could convince the client that the code needs changing if I had evidence that this version of Oracle (9.2.03) used a different default date format. Or if Cold Fusion pulls the date differently. Ughh.
    Here are the database parameters:
    SQL> show parameter nls_date_format
    NAME TYPE VALUE
    nls_date_format string
    select sysdate from dual;
    SYSDATE
    26-FEB-08
    1 row selected.
    select * from nls_session_parameters
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    17 rows selected.
    select * from v$nls_parameters
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET WE8MSWIN1252
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZR
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZR
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET AL16UTF16
    NLS_COMP BINARY
    NLS_LENGTH_SEMANTICS BYTE
    NLS_NCHAR_CONV_EXCP FALSE
    19 rows selected.

  • Chang Charactor set WE8MSWIN1252 to AL32UTF8 for creating RCU

    Hi
    how can I chang the Charactor set for creating RCU,
    Thanks,
    Sri.

    Balaa wrote:
    Sri,
    Follow the below steps,
    conn / as sysdba
    col parameter format a30
    col value format a30
    SELECT view_name FROM dba_views WHERE view_name LIKE '%NLS%';
    SELECT * FROM v$nls_parameters;
    SHUTDOWN IMMEDIATE;
    STARTUP RESTRICT;
    ALTER SYSTEM SET JOB_QUEUE_PROCESSES=0;
    ALTER SYSTEM SET AQ_TM_PROCESSES=0;
    ALTER DATABASE CHARACTER SET AL32UTF8;
    -- if the above fails:
    ALTER DATABASE CHARACTER SET INTERNAL_USE AL32UTF8;
    SHUTDOWN IMMEDIATE;
    STARTUP;
    SELECT * FROM v$nls_parameters;
    Thanks,
    Balaa...
    Absolutely the INCORRECT thing to do !!
    This will result in corruption of your database that you cannot recover from.
    Review MOS Doc - 260912.1
    Difference between NLS_CHARACTERSETAL32UTF8 & NLS_CHARACTERSET WE8MSWIN125
    Supported methods are documented - Character Set Migration

  • Change session Date/Time

    Hi,
    How could I change the session Date/Time without changing server Date/Time?
    Cheers
    Soheil

    Using the nls parameters it is possible to change to a different calendar type but I believe you will have to run a utility to which you supply the calendar. There is also a parameter to set the sysdate to a fixed value for testing, fixed_date, but I believe that is instance wide.
    Here are the nls parameters from v$nls_parameters. You will need to pull the manuals for more information:
    PARAMETER VALUE
    NLS_LANGUAGE AMERICAN
    NLS_TERRITORY AMERICA
    NLS_CURRENCY $
    NLS_ISO_CURRENCY AMERICA
    NLS_NUMERIC_CHARACTERS .,
    NLS_CALENDAR GREGORIAN
    NLS_DATE_FORMAT DD-MON-RR
    NLS_DATE_LANGUAGE AMERICAN
    NLS_CHARACTERSET US7ASCII
    NLS_SORT BINARY
    NLS_TIME_FORMAT HH.MI.SSXFF AM
    NLS_TIMESTAMP_FORMAT DD-MON-RR HH.MI.SSXFF AM
    NLS_TIME_TZ_FORMAT HH.MI.SSXFF AM TZH:TZM
    NLS_TIMESTAMP_TZ_FORMAT DD-MON-RR HH.MI.SSXFF AM TZH:TZM
    NLS_DUAL_CURRENCY $
    NLS_NCHAR_CHARACTERSET US7ASCII
    NLS_COMP BINARY
    Good luck -- Mark D Powell --

  • BADI for changing fields during Creation of BP in CRM

    Hello to everyone,
      I need to find a BADI (or other way) to default several fields during BP creation in CRM (4.0 SR1 SP9). The fields I will like to set are TAX TYPE, TAX NUMBER, TAX CATEGORY, etc.. I have found the BADI BUPA_TAX_UPDATE but i dont see any suitable parameters (structures) to changes these fields. Please advice and thanks in advance.

    Hi
    If you use function BUPA_NUMBERS_GET then your BP number will already be buffered and you can avoid a DB read. It may also be that the BP is not in the DB yet anyway.
    You can only pass one GUID in at a time - loop through IT_CHANGED_INSTANCES into a variable of type BU_PARTNER_GUID and pass that into the function as input parameter IV_PARTNER_GUID.
    Cheers
    Dom

  • How to restrict manual changing of free goods in sales order

    Hi ,
    Goodmorning ,
    We have some requirement : In sales order free goods quantity determination by system  should not be allowed to change manually , where can we do this ?
    Looking for your inputs
    Thanks and regards
    Venkat

    As per SAP Standard, when the main Item quantity is changed, the Free Goods are redetermined. In this case any manual changes to Free Goods Quantities are lost.
    But your requirement is for restricting the Chages of the Quantity of Free Goods Correct?
    I believe there is no SAP standard solution for this. You will have to apply a User Exit, which will check the Item category of each LIne item & if it is free goods (TANN) then changes are not permitted.
    Hope this helps.
    Thanks,
    Jignesh Mehta

  • Sy-tabix value has changed...

    Hi Gurus,
    I  am using a code like dis...this is not the actual code m using instad m sendin u a sample program so that u can understand the problem
    There is a selecvtion for Customer.
    sort itab by kunnr.
    loop at itab.
    on change of itab-kunnr.
    wkunnr = itab-kunnr.
      read table zitab with key kunnr = itab-kunnr.
    endon.
    if itab-kunnr = wkunnr.
    wdmbtr = wdmbtr + itab-dmbtr.
    endif.
    at end of kunnr.
    ftab-kunnr = wkunnr.
    ftab-dmbtr = wdmbtr.
    append ftab.
    endat.
    endloop.
    Now my problem is that  AT END OF Kunnr is working fine for the first customer or say for single customer but when there are multiple customers  AT END OF kunnr is triggring for each entry.......
    In debug MOdei can see that as soon as read table  syntax is used the tabix value is changed....
    So Can anyone suggest what is the solution....
    Regards,
    Raman

    This is the Declaration
    DATA:  BEGIN OF ITAB OCCURS 0,
                      KUNNR      LIKE BSID-KUNNR,
                      BELNR      LIKE BSID-BELNR,
                      BUKRS      LIKE BSID-BUKRS,
                      GJAHR      LIKE BSID-GJAHR,
                      BUZEI      LIKE BSID-BUZEI,
                      SHKZG      LIKE BSID-SHKZG,
                      VALUT      LIKE BSID-ZFBDT,
                      SGTXT(70)  TYPE  C,
                      ZFBDT      LIKE BSID-ZFBDT,
                      ZBD1T       TYPE BSID-ZBD1T,
           ZBD2T       TYPE BSID-ZBD2T,
           ZBD3T       TYPE BSID-ZBD3T,
           REBZG       TYPE BSID-REBZG,
           NETDT       TYPE BSID-BUDAT,
                      ZUONR      LIKE BSID-ZUONR,
                       BLART      LIKE BSID-BLART,
                      DMBTR      LIKE BSID-DMBTR,
                      SPART       TYPE VBRK-SPART,
                      DAY    TYPE RFPOSX-VERZN,
                      FLAG TYPE C,
                      CITY        TYPE KNA1-ORT01,
           NAME1       TYPE LFA1-NAME1,
                     CR_DR1(4)  TYPE C,
                      PSWSL      LIKE BSID-PSWSL,
                      ZTERM      LIKE BSID-ZTERM,
                      VBELN      LIKE BSID-VBELN,
                      UMSKZ      LIKE BSID-UMSKZ,
                      KLIMK      LIKE KNKK-KLIMK,
                      VTEXT      LIKE TVZBT-VTEXT,
                      ADV        LIKE BSID-DMBTR,
                      REBZT       TYPE BSID-REBZT,
                      XBLNR      LIKE BSID-XBLNR,
                      VTEXT1(70) TYPE  C,
                       FKLIMK    LIKE KNKK-KLIMK,
                      ABC(4)     TYPE C,
                    AGRO(4)        TYPE C,
                      BIO(4)        TYPE C,
                      SKFOR      LIKE KNKK-SKFOR,
                      SSOBL      LIKE KNKK-SSOBL,
                      CTLPC      LIKE KNKK-CTLPC,
                      OEIKW      LIKE S066-OEIKW,
                      OLIKW      LIKE S067-OLIKW,
                      OFAKW      LIKE S067-OFAKW,
                     NAME1      LIKE LFA1-NAME1,
                      BUDAT      LIKE BKPF-BUDAT,
                      D_DMBTR    LIKE BSID-DMBTR,
                      S_DMBTR    LIKE BSID-DMBTR,
                      VORGN      LIKE BSEG-VORGN,
                      WERKS      LIKE BSEG-WERKS,
                      NAMESO     LIKE KNA1-NAME1,
                      NAMEAM     LIKE KNA1-NAME1,
                      NAMERM     LIKE KNA1-NAME1,
                       NAMEDR     LIKE KNA1-NAME1,
       END OF ITAB.

Maybe you are looking for