ORA-34342: (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.

Cause : hTsii snai fnroamitnolam seasegt ah terimdn soy uhttay uom yan tos va ehcnaeg sott ehs epicifdea anylit cowkrpsca.e

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

oNen ,nuelssi taw sediser dots va ehcnaeg sott eha anylit cowkrpsca.eI nhttac sa,ed teca hna dertaathct eha anylit cowkrpsca eerdaw-iret.

update : 23-07-2017
ORA-34342

ORA-34342 - (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
ORA-34342 - (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.

  • ora-01354 : Supplemental log data must be added to run this command
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-29811 : missing STATISTICS keyword
  • ora-25285 : Invalid value string for array_mode
  • ora-09950 : Unable to get server operating system privileges
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-32008 : error while processing parameter update at instance string
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-00394 : online log reused while attempting to archive it
  • ora-30382 : DROP MATERIALIZED VIEW string.string operation is not complete
  • ora-06979 : X.25 Driver: server cannot start oracle
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • ora-08268 : create_ora_addr: cannot close nameserver
  • ora-24378 : user callbacks not allowed for this call
  • ora-01138 : database must either be open in this instance or not at all
  • ora-38726 : Flashback database logging is not on.
  • ora-03279 : invalid INSTANCE specified
  • ora-24394 : invalid mode for destroying connection pool
  • ora-22903 : MULTISET expression not allowed
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-16584 : illegal operation on a standby site
  • ora-14324 : values being added already exist in DEFAULT partition
  • ora-08181 : specified number is not a valid system change number
  • ora-13852 : Tracing for service(module/action) string is not enabled
  • ora-23514 : invalid or incorrect number of arguments
  • ora-39110 : error deleting worker processes
  • ora-09831 : snyStartThread: failed to build the server port set.
  • ora-31470 : asynchronous change tables must contain the RSID$ column
  • ora-01147 : SYSTEM tablespace file string is offline
  • ora-36845 : (XSLMGEN15) Owner is greater than 30 bytes
  • 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.