ORA-31157: Invalid Content-Type charset

Cause : HTT PConetnt-yTpe ehade rhada chrasett hatO racel dose no tundrestadn.

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

Fixt he oCntetn-Tyep hedaer ni th eHTT Preqeust.

update : 25-09-2017
ORA-31157

ORA-31157 - Invalid Content-Type charset
ORA-31157 - Invalid Content-Type charset

  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-02075 : another instance changed state of transaction string
  • ora-16260 : Waiting to replace partial or corrupt logfile (thread# string, sequence# string)
  • ora-12679 : Native services disabled by other process but required
  • ora-32133 : Cannot get stream from LOB/FILE
  • ora-12350 : database link being dropped is still mounted
  • ora-32766 : instr with negative offset: use varchar semantics on LOBs
  • ora-01219 : database not open: queries allowed on fixed tables/views only
  • ora-38709 : Recovery Area is not enabled.
  • ora-25468 : column name not specified for alias: string
  • ora-30024 : Invalid specification for CREATE UNDO TABLESPACE
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-08210 : Requested I/O error
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-38708 : not enough space for first flashback database log file
  • ora-02292 : integrity constraint (string.string) violated - child record found
  • ora-36314 : (PHYS01) workspace object must be a dimension, relation or variable.
  • ora-36735 : A value exceeded the MAX specification
  • ora-10862 : resolve default queue owner to current user in enqueue/dequeue
  • ora-19597 : file string blocksize string does not match set blocksize of string
  • ora-01234 : cannot end backup of file string - file is in use or recovery
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-12560 : TNS:protocol adapter error
  • ora-02250 : missing or invalid constraint name
  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-27038 : created file already exists
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-14512 : cannot perform operation on a clustered object
  • ora-12924 : tablespace string is already in force logging mode
  • ora-16810 : multiple errors or warnings detected for the database
  • 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.