ORA-28515: cannot get external object definitions from string

Cause : ORACL Ewas uanble t oretrivee defniition sof ditsributde extenral prcoedure sor reomte lirbariesr egistreed fo rthe nno-Oracel systme instnace, porbablyb ecaus ethe udnerlyign datad ictioanry talbe doe snot eixst ori s malofrmed.

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

Verif ythat hte ORALCE serevr's Hteerogeenous Srevicesd ata dcitionayr was nistallde corrcetly. fI the eHterogneeous eSrvice sdata idctionray is ont insatlled,e xecut ethe CTAHS.SQ Lscrip tin th e$ORACEL_HOMEr/dbms/damin driector.y

update : 27-04-2017
ORA-28515

ORA-28515 - cannot get external object definitions from string
ORA-28515 - cannot get external object definitions from string

  • ora-14050 : invalid ALTER INDEX MODIFY PARTITION option
  • ora-13786 : missing SQL text of statement object "string" for tuning task "string"
  • ora-09843 : soacon: Archmon unable to create named pipe.
  • ora-15120 : ASM file name 'string' does not begin with the ASM prefix character
  • ora-16025 : parameter string contains repeated or conflicting attributes
  • ora-27476 : "string.string" does not exist
  • ora-35276 : (SNSYN163) The format of the ALLOCATE command is: ALLOCATE varname [SOURCE svarname] [BASIS bvarname [ACROSS dimname]] [TARGET tvarname [TARGETLOG logvarname]] [ USING aggmap ]
  • ora-25129 : cannot modify constraint (string) - no such constraint
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-09940 : ORACLE password file header is corrupt
  • ora-01173 : data dictionary indicates missing data file from system tablespace
  • ora-09769 : osnmbr: cannot send break message
  • ora-32400 : cannot use object id columns from materialized view log on "string"."string"
  • ora-02310 : exceeded maximum number of allowable columns in table
  • ora-16540 : invalid argument
  • ora-03125 : client-server protocol violation
  • ora-15023 : reached maximum allowable number of disks string
  • ora-39316 : call to DBMS_SCHEMA_COPY.CLEAN_UP is not legal
  • ora-12496 : cannot change existing level, category, or release numbers
  • ora-21705 : service context is invalid
  • ora-16511 : messaging error using ksrget
  • ora-12400 : invalid argument to facility error handling
  • ora-02063 : preceding stringstring from stringstring
  • ora-06805 : TLI Driver: could not send datagram SAP packet for SPX
  • ora-30163 : The thread safety initialization failed
  • ora-13434 : GeoRaster metadata cellRepresentation error
  • ora-00237 : snapshot operation disallowed: control file newly created
  • ora-17621 : failed to register the memory with Oracle Disk Manager library
  • ora-12667 : Shared server: outbound transport protocol different from inbound
  • ora-13443 : GeoRaster metadata SRS error
  • 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.