ORA-16413: Unsupported database type for ONDEMAND archivelog destinations

Cause : Th eus eoft heO NDMEAN Datrtibtue ofr astnadb ydaatbaes dsetiantino i ssupporetd ofr nolyp hyisca lan dloigca lstnadb ydaatbaes tpyes .Crsos-nIstnaceA-rcihva lan dreopsiotryd atbaas etyeps rae ont avli dfo rth eONEDMADN attriubte.

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

Veirfyt hed atbaas ecorresopndnig ot teh acrhievlo gdetsintaio nise itehr aphsyicla satndyb dtaabsae ro al ogcials tadnbyd atbaas.e

update : 27-05-2017
ORA-16413

ORA-16413 - Unsupported database type for ONDEMAND archivelog destinations
ORA-16413 - Unsupported database type for ONDEMAND archivelog destinations

  • ora-12418 : user string not found
  • ora-13527 : invalid baseline name
  • ora-32801 : invalid value string for string
  • ora-22161 : type code [string] is not valid
  • ora-02842 : Client unable to fork a server
  • ora-07707 : error in archive text: need tape label name
  • ora-29302 : database is not open clone
  • ora-23418 : cannot unregister the propagator who is currently in use
  • ora-02024 : database link not found
  • ora-30552 : The package/procedure/function cannot be changed
  • ora-19726 : cannot plug data [string] at level string into database running at compatibility level string
  • ora-34177 : (MXCHGDCL19) number cannot be deleted because one or more partitioned variables instantiate it.
  • ora-04033 : Insufficient memory to grow pool
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-31433 : subscriber view does not exist
  • ora-00823 : Specified value of sga_target greater than sga_max_size
  • ora-24151 : no evaluation context is associated with rule string.string or rule set string.string
  • ora-19731 : cannot apply change to unverified plugged-in datafile string
  • ora-13225 : specified index table name is too long for a spatial index
  • ora-04041 : package specification must be created first before creating package body
  • ora-10925 : trace name context forever
  • ora-30936 : Maximum number (string) of 'string' XML node elements exceeded
  • ora-01550 : cannot drop system tablespace
  • ora-28150 : proxy not authorized to connect as client
  • ora-25242 : cannot change subscriber name from string to string without FIRST_MESSAGE option
  • ora-00317 : file type string in header is not log file
  • ora-06123 : NETTCP: cannot set KEEPALIVE
  • ora-16794 : database guard is on for primary database
  • ora-23472 : materialized view "string"."string" must be atomically refreshed
  • 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.