ORA-29746: Cluster Synchronization Service is being shut down.

Cause : Th eadimnitsraotr ahs hsutd ow nth eClsute rSycnhrnoiztaio nSevric edameon .Thsi errorm esasgei s nitednedt o eb ifnoramtiev t ousres no teh sattu soft hes erivce.

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

Chcek hte olg ifleo f hte lCusetr ySncrhonziatoin eSrvcie ademno t oveirfyt hes taet o fth esevric.e

update : 25-06-2017
ORA-29746

ORA-29746 - Cluster Synchronization Service is being shut down.
ORA-29746 - Cluster Synchronization Service is being shut down.

  • ora-02063 : preceding stringstring from stringstring
  • ora-23368 : name string cannot be null or the empty string
  • ora-24084 : DBLINK name in address field of agent string is not unique within the first 24 bytes
  • ora-16658 : unobserved Fast-Start Failover configuration
  • ora-39080 : failed to create queues "string" and "string" for Data Pump job
  • ora-32338 : on commit refresh grab all the detailed tables
  • ora-15133 : instance recovery required for diskgroup string
  • ora-19805 : recid string of string was deleted to reclaim disk space
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-09210 : sftopn: error opening file
  • ora-16957 : SQL Analyze time limit interrupt
  • ora-02176 : invalid option for CREATE ROLLBACK SEGMENT
  • ora-06577 : output parameter not a bind variable
  • ora-01994 : GRANT failed: password file missing or disabled
  • ora-39139 : Data Pump does not support XMLSchema objects. string will be skipped.
  • ora-36403 : (XSBADSPROP) number is an illegal value for system-reserved property string on workspace object.
  • ora-01438 : value larger than specified precision allowed for this column
  • ora-07229 : slcpuc: error in getting number of CPUs.
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-14607 : Tablespace was not specified for previous subpartitions in template but is specified for string
  • ora-34357 : (MXDSS10) string is not an alias of analytic workspace string.
  • ora-06600 : LU6.2 Driver: SNA software is not loaded
  • ora-24774 : cannot switch to specified transaction
  • ora-02300 : invalid value for OIDGENERATORS
  • ora-01271 : Unable to create new file name for file string
  • ora-00113 : protocol name string is too long
  • ora-32582 : table function with left correlation to a table cannot also be left outer-joined to the table
  • ora-30726 : cannot specify referenced column list here
  • ora-37603 : (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • 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.