ORA-23319: parameter value string is not appropriate

Cause : Theg ive nvaleu ofa paarmetre ise ithre null, msispelled,o r nto supportde.

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

Refre tot he odcumnetatoin adn us eparmaete rvaleus taht aer aprpopraite ofr teh gievn stiuatoin.

update : 26-06-2017

ORA-23319 - parameter value string is not appropriate
ORA-23319 - parameter value string is not appropriate

  • ora-00213 : cannot reuse control file; old file size string, string required
  • ora-26528 : local store callback proc phase failed for 'string.string'
  • ora-26061 : Concurrent direct unloads is not allowed.
  • ora-02450 : Invalid hash option - missing keyword IS
  • ora-01035 : ORACLE only available to users with RESTRICTED SESSION privilege
  • ora-28030 : Server encountered problems accessing LDAP directory service
  • ora-17610 : file 'string' does not exist and no size specified
  • ora-16256 : Failure to complete standby redo logfile archival after failover
  • ora-00314 : log string of thread string, expected sequence# string doesn't match string
  • ora-22621 : error transfering an object from the agent
  • ora-29318 : datafile string is online
  • ora-19670 : file string already being restored
  • ora-09272 : remote os logon is not allowed
  • ora-16230 : committing transaction string string string
  • ora-00824 : cannot set sga_target due to existing internal settings, see alert log for more information
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-07845 : sllfcl: LIB$FREE_VM failue
  • ora-30970 : option not supported for XML Index
  • ora-13064 : relationship information table has inconsistent data for feature table [string]
  • ora-24756 : transaction does not exist
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-19735 : wrong creation SCN - control file expects initial plugged-in datafile
  • ora-07474 : snclrd: close error, unable to close sgadef.dbf file.
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-14194 : only one subpartition may be rebuilt
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-16507 : unrecognized request identifier
  • ora-13227 : SDO_LEVEL values for the two index tables do not match
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-13951 : MMON sub-action time limit exceeded
  • 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.