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-08-2017

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

  • ora-16036 : invalid MANAGED recovery CANCEL option
  • ora-08317 : sllfsk: Error seeking in file.
  • ora-25215 : user_data type and queue type do not match
  • ora-01902 : SEGMENT keyword expected
  • ora-24001 : cannot create QUEUE_TABLE, string already exists
  • ora-19332 : Invalid column in the CREATE_DBURI operator
  • ora-24307 : invalid length for piece
  • ora-28544 : connect to agent failed, probable Net8 administration error
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-27151 : buffer not large enough to hold process ID string
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-12839 : cannot modify an object in parallel after modifying it
  • ora-01223 : RESETLOGS must be specified to set a new database name
  • ora-08499 : Warning: picture mask options 'string' ignored by UTL_PG
  • ora-01935 : missing user or role name
  • ora-24776 : cannot start a new transaction
  • ora-30179 : invalid argument index used in a format code
  • ora-22803 : object type contains zero attributes
  • ora-07745 : slemcl: $CLOSE failure
  • ora-29511 : could not resolve Java class
  • ora-14508 : specified VALIDATE INTO table not found
  • ora-34164 : (MXCGVAR01) A dimension used to define a local string variable cannot be located. Execution cannot continue.
  • ora-24019 : identifier for string too long, should not be greater than string characters
  • ora-12722 : regular expression internal error
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-22928 : invalid privilege on directories
  • ora-28121 : driving context does not exist
  • ora-02242 : no options specified for ALTER INDEX
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • 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.