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 : 23-04-2017
ORA-16413

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

  • ora-19574 : output filename must be specified
  • ora-25255 : incorrect subscription string string
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-12482 : internal MLS error: string Error: string
  • ora-39085 : cannot update job string for user string
  • ora-02775 : Invalid request done signal
  • ora-09293 : sksasmo: unable to send message to console
  • ora-15004 : alias "string" does not exist
  • ora-06018 : NETASY: message send failure
  • ora-14000 : only one LOCAL clause may be specified
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-27432 : step string does not exist for chain string.string
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-13518 : Invalid database id (string)
  • ora-27207 : syntax error in device PARMS - parentheses mismatch or missing
  • ora-01152 : file string was not restored from a sufficiently old backup
  • ora-12035 : could not use materialized view log on "string"."string"
  • ora-01612 : instance string (thread string) is already enabled
  • ora-12725 : unmatched parentheses in regular expression
  • ora-01879 : the hh25 field must be between 0 and 24
  • ora-38707 : Media recovery is not enabled.
  • ora-31403 : change table string already contains a column string
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-01258 : unable to delete temporary file string
  • ora-13031 : Invalid Gtype in the SDO_GEOMETRY object for point object
  • ora-01698 : a clone database may only have SYSTEM rollback segment online
  • ora-07584 : spdcr: invalid value for ORA_sid_(proc_)PQL$_item
  • ora-31208 : DBMS_LDAP: PL/SQL - Invalid LDAP Message.
  • ora-30054 : invalid upper limit snapshot expression
  • ora-09959 : IMON: deletion of a process failed.
  • 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.