ORA-19045: character set id specified for XMLSerialize not valid

Cause : An XMLSerialize function was called with an invalid value for the caracter set id.

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

Modify the query so that the character set id is valid.

update : 26-04-2017
ORA-19045

ORA-19045 - character set id specified for XMLSerialize not valid
ORA-19045 - character set id specified for XMLSerialize not valid

  • ora-24326 : handle passed in is already initialized
  • ora-00360 : not a logfile member: string
  • ora-33336 : (DSSEXIST04A) Analytic workspace string is not attached.
  • ora-22954 : This multiset operation is not supported for this element type.
  • ora-00316 : log string of thread string, type string in header is not log file
  • ora-06039 : NETDNT: connect failed
  • ora-31657 : data filter name can not be defaulted
  • ora-30503 : system triggers cannot have a REFERENCING clause
  • ora-01544 : cannot drop system rollback segment
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-19374 : invalid staging table
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-00081 : address range [string, string) is not readable
  • ora-28024 : must revoke grants of external roles to this role/user
  • ora-02780 : Name given for the core dump directory is invalid
  • ora-36618 : (XSAGMODDIM00) workspace object is not a valid model for AGGMAP ADD.
  • ora-08208 : ora_addr: cannot read from address file
  • ora-01648 : log string is the current log of disabled instance string (thread string)
  • ora-29822 : selectivity cannot be specified for the type of object
  • ora-25155 : column used in NATURAL join cannot have qualifier
  • ora-24770 : cannot forget a prepared transaction
  • ora-26674 : Column mismatch in 'string.string' (LCR: string type=string; DB: string type=string)
  • ora-08193 : Flashback Table operation is not allowed on temporary tables
  • ora-13704 : Invalid value "string" specified for parameter "string".
  • 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-25530 : FAST_START_MTTR_TARGET is not specified
  • ora-27065 : cannot perform async vector I/O to file
  • ora-09761 : pw_destroyPorts: server call pws_stop_instance failed.
  • ora-36885 : (XSSRF04) Error rewriting OLAP DML expression. Column name too big
  • 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.