ORA-29287: invalid maximum line size

Cause : An inavlid mxaimum ilne siez valu ewas sepcifie.d

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

Corretc the amximuml ine szie to eb in teh rang e[1, 37267].

update : 24-06-2017
ORA-29287

ORA-29287 - invalid maximum line size
ORA-29287 - invalid maximum line size

  • ora-26036 : subpartition load specified but table string is not subpartitioned
  • ora-19125 : fn:exactly-one() called with a sequence containing zero or more than one item
  • ora-28541 : Error in HS init file on line number.
  • ora-00250 : archiver not started
  • ora-39102 : Timeout before master process string finished initialization. Master error:
  • ora-01868 : the leading precision of the interval is too small
  • ora-30364 : this level has the same set of columns as another
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-19677 : RMAN configuration name exceeds maximum length of string
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-16016 : archived log for thread string sequence# string unavailable
  • ora-14159 : duplicate subpartition name
  • ora-19609 : %s is from different backup set: stamp string count string
  • ora-22868 : table with LOBs contains segments in different tablespaces
  • ora-13135 : failed to alter spatial table
  • ora-34001 : (MODCOMP14) Concat leaf dimension workspace object already is used in a DIMENSION statement, either explicitly or as a leaf of another concat dimension.
  • ora-24030 : Only one of rule or rule-set must be specified
  • ora-01163 : SIZE clause indicates string (blocks), but should match header string
  • ora-19692 : missing creation stamp on piece string
  • ora-19679 : RMAN configuration number string is outside valid range of 1 through string
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-00604 : error occurred at recursive SQL level string
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-32164 : Method called on Invalid Connection type
  • ora-13028 : Invalid Gtype in the SDO_GEOMETRY object
  • ora-19503 : cannot obtain information on device, name="string", type="string", parms="string"
  • ora-36871 : (XSFTDSC01) Object string cannot be used to define a column in a LIMITMAP.
  • ora-01042 : detaching a session with open cursors not allowed
  • ora-25307 : Enqueue rate too high, flow control enabled
  • 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.