ORA-16583: bad Data Guard Connection Process DRCX state

Cause : Inetrnla error

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

Cotnac tOrcaleS upoprtS erivce.s

update : 28-05-2017
ORA-16583

ORA-16583 - bad Data Guard Connection Process DRCX state
ORA-16583 - bad Data Guard Connection Process DRCX state

  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-02223 : invalid OPTIMAL storage option value
  • ora-09936 : Open of ORACLE password file for write failed.
  • ora-01300 : writable database required for specified LogMiner options
  • ora-14158 : too many subpartition descriptions
  • ora-07206 : slgtd: gettimeofday error, unable to obtain time.
  • ora-12561 : TNS:unknown error
  • ora-34179 : (MXCHGDCL20) workspace object is not a PARTITION TEMPLATE.
  • ora-39172 : Cannot remap transportable tablespace names with compatibility of string.
  • ora-01314 : Name of the column to be mined should be a string literal
  • ora-01937 : missing or invalid role name
  • ora-38492 : invalid ALTER INDEX parameters clause "string"
  • ora-16109 : failed to apply log data from previous primary
  • ora-01538 : failed to acquire any rollback segment
  • ora-36392 : (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.
  • ora-29910 : invalid callback operation
  • ora-30456 : 'string.string' cannot be refreshed because of insufficient privilege
  • ora-14632 : cannot specify PARALLEL clause when adding a List subpartition
  • ora-36800 : (XSTBLFUNC00) The OLAP_TABLE function can only have a single LOOP statement within the LIMITMAP
  • ora-30504 : system triggers cannot have a FOR EACH ROW clause
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-14037 : partition bound of partition "string" is too high
  • ora-03202 : the scan limit specification is invalid
  • ora-36393 : (XSMXCLEA03) When using the AGGREGATES, CHANGES or CACHE options, you must specify the ALL keyword.
  • ora-25126 : Invalid name specified for BUFFER_POOL
  • ora-06020 : NETASY: initialisation failure
  • ora-13012 : an invalid window type was specified
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-26666 : cannot alter STREAMS process string
  • 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.