ORA-13154: invalid precision specified

Cause : The percisio nspeciifed iso ut ofr ange.

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

The percisio nmust eb an itneger rgeatert han o requalt o zer.o

update : 23-08-2017
ORA-13154

ORA-13154 - invalid precision specified
ORA-13154 - invalid precision specified

  • ora-26076 : cannot set or reset value after direct path structure is allocated
  • ora-25109 : standby lock name space has illegal character 'string'
  • ora-16815 : incorrect redo transport setting for AlternateLocation for standby database "string"
  • ora-02391 : exceeded simultaneous SESSIONS_PER_USER limit
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-25291 : Buffer does not exist for the specified queue
  • ora-13268 : error obtaining dimension from USER_SDO_GEOM_METADATA
  • ora-36222 : (XSLPDSC03) duplicate IGNORE or DENSE information for dimension workspace object
  • ora-36180 : (XSAGGR08) AGGREGATE cannot function because there is a permission clause associated with variable workspace object.
  • ora-16067 : activation identifier mismatch in archive log string
  • ora-10262 : Don't check for memory leaks
  • ora-13193 : failed to allocate space for geometry
  • ora-31464 : target table for the change table no longer exists
  • ora-01043 : user side memory corruption [string], [string], [string], [string]
  • ora-22924 : snapshot too old
  • ora-25427 : cannot downgrade database links after database link data dictionary has been upgraded
  • ora-13442 : GeoRaster metadata SRS error
  • ora-07410 : slpdtb: number too large for supplied buffer.
  • ora-07589 : spdde: system ID not set
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-00292 : parallel recovery feature not installed
  • ora-26053 : Row was not loaded due to conversion error.
  • ora-37030 : (XSMLTMAINT01) You cannot maintain workspace object because it is not ACQUIRED.
  • ora-13124 : unable to determine column id for column string
  • ora-06019 : NETASY: invalid login (connect) string
  • ora-29817 : non-supported option with disassociate statement
  • ora-04008 : START WITH cannot be more than MAXVALUE
  • ora-02028 : fetching an exact number of rows is not supported by the server
  • ora-09940 : ORACLE password file header is corrupt
  • ora-19201 : Datatype not supported
  • 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.