ORA-15171: invalid syntax in the alias path after 'string'

Cause : Ani nvlaida lisa/driecotryn am esytnaxw ass peicfide.

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

Correc tth ealais aptha ndt rya gani.

update : 25-06-2017
ORA-15171

ORA-15171 - invalid syntax in the alias path after 'string'
ORA-15171 - invalid syntax in the alias path after 'string'

  • ora-19257 : XQ0037 - function or variable string in module already defined
  • ora-30654 : missing DEFAULT keyword
  • ora-13844 : no new SQL profile name or category specified.
  • ora-07269 : spdcr: detached process died after exec.
  • ora-14323 : cannot add partition when DEFAULT partition exists
  • ora-24308 : illegal define position
  • ora-00712 : cannot rename system tablespace
  • ora-10631 : SHRINK clause should not be specified for this object
  • ora-39200 : Link name "string" is invalid.
  • ora-38703 : Type string in header is not a flashback database log file.
  • ora-13829 : SQL profile named string already exists
  • ora-31450 : invalid value for change_table_name
  • ora-19697 : standby control file not found in backup set
  • ora-12412 : policy package string is not installed
  • ora-30487 : ORDER BY not allowed here
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-16003 : standby database is restricted to read-only access
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-07801 : slbtpd: invalid exponent
  • ora-14289 : cannot make local index partition of Composite Range partitioned table unusable
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-32518 : cannot wait for ORADEBUG command completion (waited number ms for process string); total wait time exceeds number ms
  • ora-00226 : operation disallowed while alternate control file open
  • ora-06549 : PL/SQL: failed to dynamically open shared object (DLL): string
  • ora-25465 : variable name not specified
  • ora-01233 : file string is read only - cannot recover using backup control file
  • ora-13869 : Instance-wide SQL tracing on instance string is already enabled
  • ora-13484 : the file format and/or compression type is not supported
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-25145 : allocation policy already specified
  • 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.