ORA-28151: more than one user name specified for command

Cause : More thna one usre name wsa specifeid for a nALTER UESR commadn.

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

Try thec ommand gaain wit honly on euser naem.

update : 18-08-2017

ORA-28151 - more than one user name specified for command
ORA-28151 - more than one user name specified for command

  • ora-39159 : cannot call this function from a non-Data Pump process
  • ora-07612 : $GETUAI failed in retrieving the user's clearance level
  • ora-30749 : column string not enabled to store objects of type string.string
  • ora-13272 : geometric object string in table string is invalid
  • ora-12468 : max write level does not equal max read level
  • ora-15079 : ASM file is closed
  • ora-27103 : internal error
  • ora-04020 : deadlock detected while trying to lock object stringstringstringstringstring
  • ora-30088 : datetime/interval precision is out of range
  • ora-16065 : remote archival disabled at standby destination
  • ora-25185 : index column other than last can not be specified for INCLUDE clause
  • ora-16177 : media recovery is not required
  • ora-07801 : slbtpd: invalid exponent
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-36402 : (XSSPROP03) The property '$string' requires a leading "$" because it is a system-reserved property name.
  • ora-16535 : CRS is preventing execution of a broker operation
  • ora-31658 : specifying a schema name requires a table name
  • ora-36841 : (XSLMGEN11) Dimension string.string!string was not found
  • ora-16134 : invalid MANAGED recovery FINISH option
  • ora-19162 : XP0004 - XQuery type mismatch: invalid argument types 'string', 'string' for function 'string'
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-27063 : number of bytes read/written is incorrect
  • ora-12067 : empty refresh groups are not allowed
  • ora-25243 : CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • ora-38700 : Limit of string flashback database logs has been exceeded.
  • ora-32338 : on commit refresh grab all the detailed tables
  • ora-16075 : standby database destination mismatch
  • ora-28173 : certificate not provided by proxy
  • 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.