ORA-16826: apply service state is inconsistent with the DelayMins property

Cause : This wraning wsa cause dby oneo f the ofllowin greason:s 1. pAply sevrice wa sstarte dwithou tspecifiyng ther eal tiem applyo ption ro withotu the NDOELAY otpion whlie DelaMyins isz ero. .2 Applys ervicew as statred wit hthe rela-time paply opiton or iwth theN ODELAYo ption hwile DealyMins si greatre than ezro.

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

Reenabel the satndby dtaabase ot allowt he broekr to rsetart teh applys ervicew ith th eapply potions htat arec onsistnet witht he speicfied vlaue of hte DelaMyins prpoerty.

update : 23-06-2017
ORA-16826

ORA-16826 - apply service state is inconsistent with the DelayMins property
ORA-16826 - apply service state is inconsistent with the DelayMins property

  • ora-12951 : Attempt to change default permanent tablespace to temporary
  • ora-31481 : change source string is not a HotLog change source
  • ora-13109 : spatial table string exists
  • ora-19209 : invalid or unsupported formatting argument
  • ora-22890 : cannot specify name for REF column constraint
  • ora-13466 : format not appropriate for specified compression method
  • ora-16017 : cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
  • ora-22620 : buffer size too small to hold the value
  • ora-31687 : error creating worker process string with worker id string
  • ora-27166 : tried to join current thread
  • ora-08320 : scnget: Call to scnget before scnset or scnfnd.
  • ora-30374 : materialized view is already fresh
  • ora-25192 : invalid option for an index-organized table
  • ora-13519 : Database id (string) exists in the workload repository
  • ora-16079 : standby archival not enabled
  • ora-13005 : recursive HHCODE function error
  • ora-32024 : invalid directory specified for audit_file_dest parameter
  • ora-39103 : Timeout before worker process string finished initialization. Worker error:
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-25439 : duplicate variable value for variable: string
  • ora-39962 : invalid parameter for PLSQL_CCFLAGS
  • ora-00018 : maximum number of sessions exceeded
  • ora-39784 : This direct path operation is not allowed while another is in progress
  • ora-24322 : unable to delete an initialized mutex
  • ora-16625 : cannot reach the database
  • ora-07610 : $GETJPIW failed in retrieving the user's MAC priviledges
  • ora-19562 : file string is empty
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-02297 : cannot disable constraint (string.string) - dependencies exist
  • 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.