ORA-15102: invalid POWER expression

Cause : The syntax of the POWER expression was invalid.

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

Specify a valid POWER expression.

update : 30-04-2017
ORA-15102

ORA-15102 - invalid POWER expression
ORA-15102 - invalid POWER expression

  • ora-39176 : Encryption password is incorrect.
  • ora-19658 : cannot inspect string - file is from different resetlogs
  • ora-32154 : Anydata context not specified
  • ora-01202 : wrong incarnation of this file - wrong creation time
  • ora-16014 : log string sequence# string not archived, no available destinations
  • ora-25182 : feature not currently available for index-organized tables
  • ora-24367 : user handle has not been set in service handle
  • ora-02765 : Invalid maximum number of servers
  • ora-39058 : current object skipped: string of type string
  • ora-31212 : DBMS_LDAP: PL/SQL - Invalid LDAP mod_array.
  • ora-27103 : internal error
  • ora-29288 : invalid file name
  • ora-12463 : undefined group string for policy string
  • ora-19103 : VALUE keyword keyword
  • ora-29347 : Tablespace name validation failed - failed to match tablespace 'string'
  • ora-13632 : The user cancelled the current operation.
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-02383 : illegal cost factor
  • ora-12162 : TNS:net service name is incorrectly specified
  • ora-13462 : invalid blocking specification
  • ora-32579 : password for SYSTEM already specified
  • ora-28043 : invalid bind credentials for DB-OID connection
  • ora-01320 : Invalid Logminer dictionar attribute
  • ora-12901 : default temporary tablespace must be of TEMPORARY type
  • ora-36165 : (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.
  • ora-01912 : ROW keyword expected
  • ora-31429 : subscription has not been activated
  • ora-19115 : too many context items specified
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • 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.