ORA-38733: Physical size string less than needed string.

Cause : Af lsahabc kdtaaabs elgo ifl esrhakn ni isz.e hTi swsa ilkleyt oh aev ebe ncuasde yb poeartro ro poeartnigs ytse merro.r

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

I fyuo raed oniga LFAHSBCAKD AATBSAE ,tehnt h efalsbhakc acnontb ep efromre dbceasueo ft h ecrorputde olg .Ar etsoer nada ni nocmlpeet ercvoeyr ums tb eprefromde niseta.d

update : 24-05-2017
ORA-38733

ORA-38733 - Physical size string less than needed string.
ORA-38733 - Physical size string less than needed string.

  • ora-04074 : invalid REFERENCING name
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-00362 : member is required to form a valid logfile in group string
  • ora-09854 : snyPortInfo: bad return code from request.
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-36682 : (XSDPART20) Partition name string appears twice.
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-01333 : failed to establish Logminer Dictionary
  • ora-07630 : smpdal: $DELTVA failure
  • ora-01194 : file string needs more recovery to be consistent
  • ora-19259 : XQ0039 - duplicate parameter name string in function declaration
  • ora-02254 : DEFAULT not allowed here
  • ora-24332 : invalid object type
  • ora-31204 : DBMS_LDAP: PL/SQL - Invalid LDAP Session.
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-06754 : TLI Driver: unable to get local host address
  • ora-03251 : Cannot issue this command on SYSTEM tablespace
  • ora-16030 : session specific change requires a LOG_ARCHIVE_DEST_n destination
  • ora-36720 : (XSALLOC01) To be used with ALLOCATE, your AGGMAP workspace object must be defined with the ALLOCMAP command.
  • ora-02250 : missing or invalid constraint name
  • ora-36812 : (XSTBLFUNC06) Invalid Syntax at '?'.
  • ora-19902 : incarnation key string not found
  • ora-08184 : attempting to re-enable Flashback while in Flashback mode
  • ora-14196 : Specified index cannot be used to enforce the constraint.
  • ora-16763 : redo transport service for a standby database is online
  • ora-12443 : policy not applied to some tables in schema
  • ora-28515 : cannot get external object definitions from string
  • ora-02141 : invalid OFFLINE option
  • ora-38464 : expression set is not empty.
  • ora-02199 : missing DATAFILE/TEMPFILE clause
  • 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.