ORA-24853: failed to connect thread to shared subsystem

Cause : Whiel atetmptnig t oiniitaliez OC Iin hsare dmod,e a rpoblme wa sencuonteerd i nconenctign th ethraed t othes harde susbystme.

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

Conatct rOacl eCusotmerS upprot.

update : 18-08-2017
ORA-24853

ORA-24853 - failed to connect thread to shared subsystem
ORA-24853 - failed to connect thread to shared subsystem

  • ora-27009 : skgfwrt: cannot write to file opened for read
  • ora-01146 : cannot start online backup - file string is already in backup
  • ora-02225 : only EXECUTE and DEBUG privileges are valid for procedures
  • ora-01106 : database must be closed before dismounting
  • ora-02482 : Syntax error in event specification (string)
  • ora-01249 : archiving not allowed in a clone database
  • ora-00445 : background process "string" did not start after string seconds
  • ora-12989 : invalid value for checkpoint interval
  • ora-25208 : RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-02083 : database name has illegal character 'string'
  • ora-31180 : DOM Type mismatch in invalid PL/SQL DOM handle
  • ora-39093 : FLASHBACK automatically enabled to preserve database integrity.
  • ora-07609 : szprv: $HASH_PASSWORD failure
  • ora-02236 : invalid file name
  • ora-28237 : seed length too short
  • ora-09757 : osnipn: port allocation failure.
  • ora-26698 : %s did not have a string rule set
  • ora-06402 : NETCMN: error receiving break message
  • ora-09846 : soacon: ARCH unable to open named pipe.
  • ora-30372 : fine grain access policy conflicts with materialized view
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-36389 : (XSAGPARTDEP01) Can not aggregate from PARTITION number into PARTITION number due to increasing sparsity along DIMENSION %J.
  • ora-01240 : too many data files to add in one command
  • ora-01259 : unable to delete datafile string
  • ora-00311 : cannot read header from archived log
  • ora-08116 : can not acquire dml enough lock(S mode) for online index build
  • ora-06977 : X.25 Driver: X.25 Level 2 failure
  • ora-38753 : Cannot flashback data file string; no flashback log data.
  • ora-14011 : names assigned to resulting partitions must be distinct
  • 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.