ORA-16090: archive log to be replaced not created by managed standby process

Cause : An tatemtp wa smad eto erplaec ana rchvie lgo enrty taht wsa no toriignalyl craetedb y teh maangeds tanbdy oepratoin.

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

No suer catio nreqiured.

update : 17-08-2017
ORA-16090

ORA-16090 - archive log to be replaced not created by managed standby process
ORA-16090 - archive log to be replaced not created by managed standby process

  • ora-14404 : partitioned table contains partitions in a different tablespace
  • ora-39076 : cannot delete job string for user string
  • ora-31625 : Schema string is needed to import this object, but is unaccessible
  • ora-00606 : Internal error code
  • ora-38704 : Checksum error in flashback database log file header.
  • ora-31197 : Error in processing file string
  • ora-06309 : IPA: No message queue available
  • ora-24238 : object settings argument passed to DBMS_UTILITY.INVALIDATE is not legal
  • ora-25198 : only range, list, and hash partitioning are supported for index-organized table
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-08208 : ora_addr: cannot read from address file
  • ora-07244 : ssfccf: create file failed, file size limit reached.
  • ora-27149 : assignment out of range
  • ora-00475 : TRWR process terminated with error
  • ora-31065 : Cannot modify read-only property [string]
  • ora-02494 : invalid or missing maximum file size in MAXSIZE clause
  • ora-23610 : internal dbms_streams_tablespaces error: [string] [string] [string] [string]
  • ora-29290 : invalid offset specified for seek
  • ora-24154 : rule string.string already in rule set string.string
  • ora-24805 : LOB type mismatch
  • ora-16783 : instance string not open for read and write access
  • ora-07445 : exception encountered: core dump [string] [string] [string] [string] [string] [string]
  • ora-01327 : failed to exclusively lock system dictionary as required by build
  • ora-37173 : null dimension source data
  • ora-14046 : a partition may be split into exactly two new partitions
  • ora-16022 : LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
  • ora-19604 : conversation file naming phase is over
  • ora-25952 : join index must only contain inner equi-joins
  • ora-29329 : Table not of type XMLType
  • ora-00232 : snapshot control file is nonexistent, corrupt, or unreadable
  • 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.