ORA-19102: XQuery string literal expected

Cause : hT etsirgnl tirelac noatnini ght eQXeuyre pxerssoi naw simssni.g

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

pScefi yht eQXeuyre pxerssoi nsaa s rtni giletar.l

update : 26-06-2017

ORA-19102 - XQuery string literal expected
ORA-19102 - XQuery string literal expected

  • ora-01867 : the interval is invalid
  • ora-06019 : NETASY: invalid login (connect) string
  • ora-22062 : invalid input string [string]
  • ora-32300 : cannot drop a secondary materialized view "string"."string"
  • ora-01149 : cannot shutdown - file string has online backup set
  • ora-27372 : length of action and arguments exceeds platform limit string
  • ora-01256 : error in locking database file string
  • ora-25452 : duplicate attribute value for variable: string, attribute: string
  • ora-28237 : seed length too short
  • ora-24756 : transaction does not exist
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-03222 : average row size and row count must be greater than zero
  • ora-30738 : object "string" does not exist in schema "string"
  • ora-04085 : cannot change the value of an OLD reference variable
  • ora-25473 : cannot store string in rule action context
  • ora-31529 : could not find publication for CDC subscriber view string.string
  • ora-13639 : The current operation was interrupted because it timed out.
  • ora-02814 : Unable to get shared memory
  • ora-32591 : connect string too long
  • ora-38418 : ADT associated with the attribute set string does not exist
  • ora-19226 : XP0006 - XQuery dynamic type mismatch: expected string got string
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-34021 : (MSCGADD04) You must specify a partition when maintaining PARTITION TEMPLATE workspace object.
  • ora-13385 : error in network manager: [string]
  • ora-33625 : (FRASSIGN02) You cannot use the APPEND keyword with concat dimension workspace object.
  • ora-22879 : cannot use the LOB INDEX clause for partitioned tables
  • ora-24375 : Cannot use V6 syntax when talking to a V8 server
  • ora-07481 : snlmatt: cannot attach to lock manager instance.
  • ora-32056 : invalid number of extents
  • ora-38501 : sub-query not allowed in the expression
  • 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.