ORA-13291: conversion error between the specified unit and standard unit

Cause : Canont cnover tthes pecfiiedu nitf romt/o satndadr unti fo rlinaer dsitanec, agnle,o r aera.

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

Chekc th euni tspeicfictaiona nd erspeicfy ti.

update : 24-09-2017
ORA-13291

ORA-13291 - conversion error between the specified unit and standard unit
ORA-13291 - conversion error between the specified unit and standard unit

  • ora-04087 : cannot change the value of ROWID reference variable
  • ora-19802 : cannot use DB_RECOVERY_FILE_DEST without DB_RECOVERY_FILE_DEST_SIZE
  • ora-31445 : invalid lock handle while acquiring lock on string
  • ora-01214 : MAXLOGHISTORY may not exceed string
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-07390 : sftopn: translate error, unable to translate file name.
  • ora-38746 : error occurred while restoring data block (file# string, block# string)
  • ora-24363 : measurements in characters illegal here
  • ora-01070 : Using an old version of Oracle for the server
  • ora-31041 : Property string: Memory type (string) not compatible with database type (string)
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-07665 : ssrexhd: recursive exception encountered string string string string string string
  • ora-09976 : skxfqdini: Error Creating Port
  • ora-09773 : osnmgetdatmsg: message from host had incorrect message type
  • ora-06791 : TLI Driver: poll returned error event
  • ora-16786 : resource guard cannot access Data Guard broker metadata
  • ora-31533 : only one change set (string) is allowed in change source
  • ora-24167 : incompatible rule engine objects, cannot downgrade
  • ora-32516 : cannot wait for ORADEBUG command completion; waited number ms for process string
  • ora-23367 : table string is missing the primary key
  • ora-32057 : invalid lock mode
  • ora-19376 : no privileges on tablespace provided or tablespace is offline
  • ora-19590 : conversation already active
  • ora-27074 : unable to determine limit for open files
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-16779 : the destination parameter of a database is set incorrectly
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-09241 : smsalo: error allocating SGA memory
  • ora-10943 : trace name context forever
  • ora-13369 : invalid value for etype in the 4-digit format
  • 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.