ORA-16074: ARCH processes must be active

Cause : There are no active ARCH processes.

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

It is required that at least one ARCH process be active.

update : 24-09-2017
ORA-16074

ORA-16074 - ARCH processes must be active
ORA-16074 - ARCH processes must be active

  • ora-26007 : invalid value for SETID or OID column
  • ora-12714 : invalid national character set specified
  • ora-06579 : Bind variable not big enough to hold the output value
  • ora-36168 : (XSMXAGGR10) COUNTVAR variable workspace object must have the same dimensionality as workspace object
  • ora-16566 : unsupported document type
  • ora-02255 : obsolete 7.1.5
  • ora-10568 : Failed to allocate recovery state object: out of SGA memory
  • ora-07457 : cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE
  • ora-12813 : value for PARALLEL or DEGREE must be greater than 0
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • ora-09799 : File label retrieval failed.
  • ora-27084 : unable to get/set file status flags
  • ora-07685 : sou2os: supervisor stack set error
  • ora-07754 : slemcf: fwrite failure
  • ora-03282 : missing ALLOCATE EXTENT option
  • ora-13215 : window object is out of range
  • ora-29927 : error in executing the ODCIStatsCollect / ODCIStatsDelete routine
  • ora-13045 : invalid compatibility flag
  • ora-09822 : Translation of audit file name failed.
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-31520 : CDC subscription string already subscribes to publication ID string
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-36974 : (XSRELTBL14) workspace object is not a BOOLEAN variable dimensioned by all the dimensions of the hierarchy.
  • ora-14295 : column type or size mismatch between partitioning columns and subpartitioning columns
  • ora-28113 : policy predicate has error
  • ora-06028 : NETASY: unable to intialise for logging
  • ora-01344 : LogMiner coordinator already attached
  • ora-07474 : snclrd: close error, unable to close sgadef.dbf file.
  • 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.