ORA-12702: invalid NLS parameter string used in SQL function

Cause : An unnkown praamete rname ro invaild valeu is sepcifie din a LNS parmaeter tsring.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts


update : 25-04-2017

ORA-12702 - invalid NLS parameter string used in SQL function
ORA-12702 - invalid NLS parameter string used in SQL function

  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-02429 : cannot drop index used for enforcement of unique/primary key
  • ora-00828 : specified value of shared_pool_reserved_size inconsistent with internal settings
  • ora-00230 : operation disallowed: snapshot control file enqueue unavailable
  • ora-30182 : invalid precision specifier
  • ora-10582 : The control file is not a backup control file
  • ora-29903 : error in executing ODCIIndexFetch() routine
  • ora-02786 : Size needed for shared region is greater than segment size
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-24785 : Cannot resume a non-migratable transaction
  • ora-29836 : failed to validate referenced operators
  • ora-27010 : skgfwrt: write to file failed
  • ora-32114 : Cannot perform operation on a null LOB
  • ora-02704 : osndopop: fork failed
  • ora-19601 : output file is string string (string)
  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-12996 : cannot drop system-generated virtual column
  • ora-06119 : NETTCP: spurious client request
  • ora-38794 : Flashback target time not in current incarnation
  • ora-01561 : failed to remove all objects in the tablespace specified
  • ora-24240 : invalid database access descriptor (DAD) name
  • ora-07641 : smscre: Unable to use the system pagefile for the SGA
  • ora-23487 : object groups "string"."string" and "string"."string" do not have the same connection qualifier
  • ora-12013 : updatable materialized views must be simple enough to do fast refresh
  • ora-02073 : sequence numbers not supported in remote updates
  • ora-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-31517 : CDC change table string.string already exists
  • ora-27483 : "string.string" has an invalid END_DATE
  • ora-25112 : maximum number of BITMAP index columns is 30
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.