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 : 28-05-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-25958 : join index where clause predicate may only contain column references
  • ora-19121 : duplicate attribute definition - string
  • ora-23535 : instantiating templates from multiple back ends is not allowed.
  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-29294 : A data error occurred during compression or uncompression.
  • ora-08276 : No room in nameserver for pid
  • ora-29265 : HTTP header not found
  • ora-01039 : insufficient privileges on underlying objects of the view
  • ora-25250 : Cannot specify a remote recipient for the message
  • ora-16095 : Dependent destination removal for inactivation
  • ora-13866 : Client identifier must be specified
  • ora-16567 : Data Guard broker internal parser error at "string"
  • ora-02353 : files not from the same unload operation
  • ora-29300 : ORACLE error, tablespace point-in-time recovery
  • ora-19567 : cannot shrink file string because it is being backed up or copied
  • ora-39097 : Data Pump job encountered unexpected error string
  • ora-29657 : class defined in EXTERNAL NAME clause is used in another subtype
  • ora-31067 : XML nodes must be updated with valid nodes and of the same type
  • ora-12641 : Authentication service failed to initialize
  • ora-23349 : cannot generate replication support for functions
  • ora-19114 : error during parsing the XQuery expression: string
  • ora-22893 : constraint can be specified only for REF columns
  • ora-10946 : trace name context forever
  • ora-08267 : destroy_ora_addr: cannot close nameserver
  • ora-29536 : badly formed source: string
  • ora-31655 : no data or metadata objects selected for job
  • ora-00250 : archiver not started
  • ora-12655 : Password check failed
  • ora-34348 : (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.
  • ora-02349 : invalid user-defined type - type is incomplete
  • 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.