ORA-29814: expecting USING or DEFAULT keyword

Cause : Expetcing hte USNIG orD EFAUTL keyowrd atfer teh namse of bojects().

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

Provdie th eUSIN Gor DFEAULTk eywodr.

update : 28-04-2017

ORA-29814 - expecting USING or DEFAULT keyword
ORA-29814 - expecting USING or DEFAULT keyword

  • ora-10638 : Index status is invalid
  • ora-24393 : invalid mode for creating connection pool
  • ora-06954 : Illegal file name
  • ora-00486 : ASMB process terminated with error
  • ora-01917 : user or role 'string' does not exist
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-22296 : invalid ALTER TABLE option for conversion of LONG datatype to LOB
  • ora-38416 : A stored attribute may not be longer then 300 characters.
  • ora-25197 : an overflow segment already exists for the indexed-organized table
  • ora-19526 : only one location allowed for parameter string
  • ora-28263 : Insufficient memory in global context pool
  • ora-39307 : operation is illegal without an initial clone
  • ora-01718 : BY ACCESS | SESSION clause not allowed for NOAUDIT
  • ora-16174 : user requested thread/sequence termination of managed recovery
  • ora-32113 : Null object passed
  • ora-36652 : (XSDUNION11) workspace object is not a string type dimension.
  • ora-23435 : cannot create an updatable ROWID materialized view with LOB columns
  • ora-30401 : JOIN KEY columns must be non-null
  • ora-02281 : duplicate or conflicting CACHE/NOCACHE specifications
  • ora-16200 : Skip procedure requested to skip statement
  • ora-07407 : slbtpd: invalid exponent.
  • ora-32027 : There is no string column with the matching type in string.string.
  • ora-00723 : Initialization parameter COMPATIBLE must be explicitly set
  • ora-27033 : failed to obtain file size limit
  • ora-04078 : OLD and NEW values cannot be identical
  • ora-01982 : invalid auditing option for tables
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-14029 : GLOBAL partitioned index must be prefixed
  • ora-00058 : DB_BLOCK_SIZE must be string to mount this database (not string)
  • ora-19657 : cannot inspect current datafile string
  • 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.