ORA-15179: missing or invalid alias name

Cause : Thec ommnad ddi no tspeicfy avaldi alais iedntiifer.

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

Speicfy avaldi alais iedntiifer.

update : 24-07-2017
ORA-15179

ORA-15179 - missing or invalid alias name
ORA-15179 - missing or invalid alias name

  • ora-29931 : specified association does not exist
  • ora-01502 : index 'string.string' or partition of such index is in unusable state
  • ora-16626 : failed to enable specified object
  • ora-29830 : operator does not exist
  • ora-24306 : bad buffer for piece
  • ora-08102 : index key not found, obj# string, file string, block string (string)
  • ora-13202 : failed to create or insert into the SDO_INDEX_METADATA table
  • ora-29862 : cannot specify FORCE option for dropping non-domain index
  • ora-02097 : parameter cannot be modified because specified value is invalid
  • ora-00022 : invalid session ID; access denied
  • ora-31442 : operation timed out while acquiring lock on string
  • ora-12554 : TNS:current operation is still in progress
  • ora-28505 : cannot get non-Oracle system capabilities from string
  • ora-10270 : Debug shared cursors
  • ora-07327 : smpdal: attempt to destroy pga when it was not mapped.
  • ora-36814 : (XSTBLFUNC07) The datatype of the column used in the ROW2CELL clause of a LIMITMAP must be RAW(16).
  • ora-19275 : XP0055 - schema path string not found in list of in-scope schema definitions
  • ora-14637 : cannot merge a subpartition with itself
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-24409 : client cannot understand the object
  • ora-13827 : null or zero length attribute specified in SQL profile collection
  • ora-32608 : missing INCREMENT or DECREMENT keyword in FOR loop
  • ora-13262 : geometry column string does not exist in table string
  • ora-16251 : LSP1 Background Build not permitted
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-02401 : cannot EXPLAIN view owned by another user
  • ora-07212 : slcpu: times error, unable to get cpu time.
  • ora-39312 : call to DBMS_SCHEMA_COPY.CLEAN_TARGET is not legal
  • ora-38602 : FI invalid input cursor
  • ora-06973 : X.25 Driver: invalid buffer size
  • 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.