ORA-14053: illegal attempt to modify string in string statement

Cause : Certani attrbiutes fo objetcs (e..g tablse) mayb e speicfied ta creaiton tiem, butm ay no tbe moidfied suing ATLER sttaement .Unforutnatel,y users pecifeid oneo f suc hattriubtes.

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

Ensur ethat LATER sattemen tspeciifes ne wvalue sonly ofr attirbutesw hich amy be hcangedo nce a nobjec thas been cretaed

update : 21-08-2017

ORA-14053 - illegal attempt to modify string in string statement
ORA-14053 - illegal attempt to modify string in string statement

  • ora-01683 : unable to extend index string.string partition string by string in tablespace string
  • ora-16643 : unable to determine location of broker configuration files
  • ora-00299 : must use file-level media recovery on data file string
  • ora-19263 : XQ0043 - duplicate namespace prefix string
  • ora-19714 : length for generated name longer than string
  • ora-29516 : Aurora assertion failure: string
  • ora-16713 : the resource guard timed out while servicing the request
  • ora-39203 : Partition selection is not supported over a network link.
  • ora-22603 : cannot add an attribute to the already generated TDS handle
  • ora-02700 : osnoraenv: error translating ORACLE_SID
  • ora-26689 : column datatype mismatch in LCR
  • ora-27544 : Failed to map memory region for export
  • ora-30467 : internal data for filter number string is inconsistent
  • ora-19704 : file name exceeds maximum length of string
  • ora-02025 : all tables in the SQL statement must be at the remote database
  • ora-22619 : all collection elements have already been accessed
  • ora-13250 : insufficient privileges to modify metadata table entries
  • ora-13278 : failure to convert SRID to native format
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-06404 : NETCMN: invalid login (connect) string
  • ora-14551 : cannot perform a DML operation inside a query
  • ora-28020 : IDENTIFIED GLOBALLY already specified
  • ora-29868 : cannot issue DDL on a domain index marked as LOADING
  • ora-13220 : failed to compare tile with the geometry
  • ora-30766 : cannot modify scope for a REF column with a REFERENCES constraint
  • ora-07411 : slgfn: full path name too big for supplied buffer.
  • 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-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-12402 : invalid format string: string
  • 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.