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 : 29-06-2017
ORA-30182

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

  • ora-12620 : TNS:requested characteristic not available
  • ora-02482 : Syntax error in event specification (string)
  • ora-02031 : no ROWID for fixed tables or for external-organized tables
  • ora-19247 : XQ0027 - validation error
  • ora-22064 : invalid NLS parameter string [string]
  • ora-16618 : response document of size "string" bytes is too large
  • ora-36883 : (XSSRF02) The first parameter of an AW single row function cannot be NULL.
  • ora-30339 : illegal dimension attribute name
  • ora-39306 : schema name mismatch expected "string" got "string"
  • ora-00061 : another instance has a different DML_LOCKS setting
  • ora-08115 : can not online create/rebuild this index type
  • ora-29363 : plan directive string, string is mandatory and cannot be modified or deleted
  • ora-07459 : cannot restore the RESOURCE_MANAGER_PLAN parameter
  • ora-08457 : syntax error in SEPARATE CHARACTER option of SIGN clause
  • ora-09705 : spcre: cannot initialize latch semaphore
  • ora-37076 : (XSMCSESS04) workspace object is not the type of dimension that can have session-only values. Valid types are TEXT, NTEXT, ID, NUMBER, and CONCAT with the UNIQUE attribute.
  • ora-31023 : Index size error
  • ora-26102 : relative file # in file header is string rather than string for file string
  • ora-33213 : (CINSERT06) The target position for MAINTAIN ADD or MAINTAIN MOVE cannot fall in the range of session-only values.
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-06443 : ssvpstev: Incorrect parameter passed to function call
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-30381 : REWRITE_TABLE is not compatible with Oracle version
  • ora-15020 : discovered duplicate ASM disk "string"
  • ora-38455 : Expression Filter index should be created by the owner.
  • ora-31155 : attribute string not in XDB namespace
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-12213 : TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
  • ora-19038 : Invalid opertions on query context
  • ora-02230 : invalid ALTER CLUSTER option
  • 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.