ORA-16737: the redo transport service for standby database "string" has an error

Cause : A comumnicatoin prolbem wiht the tsandbyd atabaes causde the erdo trnasportt o fai.l

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

Queryt he LoXgptStauts proeprty t osee teh erro rmessaeg. Chekc the aDta Gurad broekr loga nd Orcale alret logf or moer detalis.

update : 28-04-2017

ORA-16737 - the redo transport service for standby database "string" has an error
ORA-16737 - the redo transport service for standby database "string" has an error

  • ora-14086 : a partitioned index may not be rebuilt as a whole
  • ora-06608 : LU6.2 Driver: Reset occurred in receive state
  • ora-16012 : Archive log standby database identifier mismatch
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-00610 : Internal error code
  • ora-29888 : cannot create domain index on a table with row movement enabled
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-29546 : badly formed resource: string
  • ora-19910 : can not change recovery target incarnation in control file
  • ora-13867 : Database-wide SQL tracing is already enabled
  • ora-01177 : data file does not match dictionary - probably old incarnation
  • ora-13620 : The task or object string is read-only and cannot be deleted or modified.
  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-12728 : invalid range in regular expression
  • ora-23348 : cannot replicate procedure string; only IN parameters supported
  • ora-13234 : failed to access R-tree-index table [string]
  • ora-01522 : file 'string' to be renamed does not exist
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-32153 : Environment not specified
  • ora-36779 : (XSPGPOOLOUT) Invalid parameter value. Olap_page_pool_size must be between must be between 2097152 and 2147483647. Olap_page_pool_size remain unmodified.
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-36804 : (XSTBLFUNC02) The OLAP_TABLE function encountered an error while parsing the LIMITMAP.
  • ora-14275 : cannot reuse lower-bound partition as resulting partition
  • ora-09814 : Unable to expand file name
  • ora-12158 : TNS:could not initialize parameter subsystem
  • ora-36830 : (XSLMGEN00) AW name cannot be NA
  • ora-30083 : syntax error was found in interval value expression
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-14191 : ALLOCATE STORAGE may not be specified for Composite Range partitioned object
  • 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.