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 : 28-06-2017

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

  • ora-16740 : redo transport service for standby database "string" incorrectly set to ALTERNATE
  • ora-13039 : failed to update spatial index for element string.string.string
  • ora-38406 : attribute set string already exists
  • ora-19735 : wrong creation SCN - control file expects initial plugged-in datafile
  • ora-07713 : sksamtd: could not mount archival device (SYS$MOUNT failure)
  • ora-16750 : resource guard encountered errors while activating logical primary database
  • ora-31217 : DBMS_LDAP: PL/SQL - Invalid LDAP newparent.
  • ora-33098 : (APABBR01) A value of 'string' is not valid for the workspace object option.
  • ora-29909 : label for the ancillary operator is not a literal number
  • ora-30195 : reserved for future use
  • ora-07702 : unrecognized device type in archive text
  • ora-01626 : rollback segment number 'string' cannot handle more transactions
  • ora-16744 : the DG_CONFIG list of LOG_ARCHIVE_CONFIG parameter is full
  • ora-28139 : Maximum allowed Fine Grain Audit Policies Exceeded
  • ora-13407 : invalid storage parameter
  • ora-32606 : missing NAV keyword in MODEL clause
  • ora-38906 : insert into DML Error Logging table "string" failed
  • ora-39048 : Unable to start all workers; only string worker(s) available.
  • ora-14159 : duplicate subpartition name
  • ora-38611 : FI input cursor's item type is not supported
  • ora-30689 : improper value for ORA_DEBUG_JDWP
  • ora-26015 : Array column string in table string is not supported by direct path
  • ora-29263 : HTTP protocol error
  • ora-39960 : scope can only be SYSTEM or SESSION
  • ora-14304 : List partitioning method expects a single partitioning column
  • ora-22995 : TABLESPACE DEFAULT option is invalid in this context
  • ora-14166 : missing INTO keyword
  • ora-26027 : unique index string.string partition string initially in unusable state
  • ora-26534 : collision: tranID number ignored and purged
  • ora-01521 : error in adding data files
  • 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.