ORA-30182: invalid precision specifier

Cause : Period in format specification not followed by valid format.

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

Replace the invalid precision specifier with a valid one.

update : 24-05-2017
ORA-30182

ORA-30182 - invalid precision specifier
ORA-30182 - invalid precision specifier

  • ora-06110 : NETTCP: message send failure
  • ora-13212 : failed to compare tile with the window object
  • ora-16795 : database resource guard detects that database re-creation is required
  • ora-01696 : control file is not a clone control file
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-25469 : data not specified for alias: string column name: string
  • ora-30726 : cannot specify referenced column list here
  • ora-03206 : maximum file size of (string) blocks in AUTOEXTEND clause is out of range
  • ora-29903 : error in executing ODCIIndexFetch() routine
  • ora-22150 : variable-length array has not been initialized
  • ora-13799 : threshold not found
  • ora-25194 : invalid COMPRESS prefix length value
  • ora-22808 : REF dereferencing not allowed
  • ora-01676 : standby file name convert of 'string' exceeds maximum length of string
  • ora-25109 : standby lock name space has illegal character 'string'
  • ora-30757 : cannot access type information
  • ora-26033 : column string.string encryption properties differ for source or target table
  • ora-13146 : could not find table substitution variable string
  • ora-00310 : archived log contains sequence string; sequence string required
  • ora-13753 : "SQL Tuning Set" "string" already exists for user "string".
  • ora-38763 : flashback not started; enabled threads have changed
  • ora-12087 : online redefinition not allowed on tables owned by "string"
  • ora-12350 : database link being dropped is still mounted
  • ora-31104 : Cannot find lock with token "string" on "string" for unlock
  • ora-22333 : cannot reset type "string"."string" due to invalid dependent types and tables
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-29862 : cannot specify FORCE option for dropping non-domain index
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-31044 : Top-level prefix length string exceeds maximum 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.