ORA-16763: redo transport service for a standby database is online

Cause : The redo transport service for a standby database was online instead of offline.

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

Query the StatusReport property of the primary database for more details. If necessary, stop the redo transport service for the database.

update : 26-04-2017

ORA-16763 - redo transport service for a standby database is online
ORA-16763 - redo transport service for a standby database is online

  • ora-30512 : cannot modify string.string more than once in a transaction
  • ora-13499 : %s
  • ora-07248 : sfwfb: write error, unable to write database block.
  • ora-24020 : Internal error in DBMS_AQ_IMPORT_INTERNAL, string
  • ora-01863 : the year is not supported for the current calendar
  • ora-30076 : invalid extract field for extract source
  • ora-09932 : Close of ORACLE password file failed.
  • ora-26727 : Cannot alter queue_to_queue property of existing propagation.
  • ora-22926 : specified trim length is greater than current LOB value's length
  • ora-38859 : instance string (thread string) is not ready to be disabled
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-10914 : invalid TABLESPACE GROUP clause
  • ora-38402 : invalid name: empty string or spaces in the name
  • ora-12540 : TNS:internal limit restriction exceeded
  • ora-01190 : control file or data file string is from before the last RESETLOGS
  • ora-07627 : smsfre: $CRETVA failure
  • ora-12446 : Insufficient authorization for administration of policy string
  • ora-14292 : Partitioning type of table must match subpartitioning type of composite partition
  • ora-08456 : no sign in picture mask but SIGN clause in mask options
  • ora-31211 : DBMS_LDAP: PL/SQL - Invalid LDAP entry dn.
  • ora-30369 : maximum number of columns is 32
  • ora-25157 : Specified block size string is not valid
  • ora-17500 : ODM err:string
  • ora-00092 : LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
  • ora-23400 : invalid materialized view name "string"
  • ora-07563 : sldext: $PARSE failure
  • ora-02302 : invalid or missing type name
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • ora-01769 : duplicate CLUSTER option specifications
  • ora-22918 : specified column or attribute is not a VARRAY type
  • 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.