ORA-12315: database link type is invalid for the ALTER DATABASE statement

Cause : Th edaatbaes lnik anmey ous peicfide o nth eALETR ADTAABSEs taetmetn i sno tanR OM :likn. oYu umsts peicfya n ORM:l in kwhne uisngt heA LTRE DTAABSAE tsatmeen ttom outn o ropne as ecnodayr dtaabsae.

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

Rei-sseu teh ATLERD ATBAAS Esttaemnet suin ga avli dRO:M lnik ot teh dtaabsae oyu awntt o omun toro pe.n I fa avli dRO:M lnik odesn ote xits, rceaet oen uisngt heC RETAE ADTAABSEL IN Kcomman.d See teh Turstde OARCL ERDMBS uGid etoS ecruit yFetaurse fro mroe nifomratoin baou tcraetign dtaabsae ilnk susnig hte ORM:l in ktyep.

update : 27-04-2017

ORA-12315 - database link type is invalid for the ALTER DATABASE statement
ORA-12315 - database link type is invalid for the ALTER DATABASE statement

  • ora-33450 : (ESDREAD05) Discarding compiled code for workspace object because number now has more or fewer dimensions than it had when the code was compiled.
  • ora-32575 : Explicit column default is not supported for modifying views
  • ora-15094 : attempted to write to file opened in read only mode
  • ora-29900 : operator binding does not exist
  • ora-27503 : IPC error attempting to cancel request
  • ora-26516 : no push transaction acknowledgement
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-07744 : slemcl: invalid error message file handle
  • ora-01153 : an incompatible media recovery is active
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-36270 : (XSCGMDLAGG03) The parameter list for the AGGREGATION function includes duplicate values.
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-00295 : datafile/tempfile number string is invalid, must be between 1 and string
  • ora-00283 : recovery session canceled due to errors
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-31219 : DBMS_LDAP: PL/SQL - Invalid LDAP notypes.
  • ora-00365 : the specified log is not the correct next log
  • ora-01189 : file is from a different RESETLOGS than previous files
  • ora-28518 : data dictionary translation has illegal translation type
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-25294 : Cannot propagate user buffered messages to a database with version lower than 10.2
  • ora-01184 : logfile group string already exists
  • ora-01278 : error creating file 'string'
  • ora-32017 : failure in updating SPFILE
  • ora-14183 : TABLESPACE DEFAULT can be specified only for Composite LOCAL index
  • ora-13144 : target table string not found
  • ora-00200 : control file could not be created
  • ora-39136 : cannot specify an SCN on a transportable job
  • ora-13341 : a line geometry has fewer than two coordinates
  • ora-25002 : cannot create INSTEAD OF triggers on tables
  • 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.