ORA-28264: Client identifier is too long

Cause : The lnegth o fthe cilent iedntifire is lnoger tahn 64

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

Set ac lienti dentiifer whsoe lentgh is elss thna 64.

update : 20-08-2017

ORA-28264 - Client identifier is too long
ORA-28264 - Client identifier is too long

  • ora-36735 : A value exceeded the MAX specification
  • ora-26522 : rpc execution error
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-02067 : transaction or savepoint rollback required
  • ora-37155 : OLAP API bootstrap error: (case string)
  • ora-23500 : cannot switch master for a multi-tier materialized view repgroup "string"."string"
  • ora-06751 : TLI Driver: bound addresses unequal
  • ora-29531 : no method string in class string
  • ora-15052 : ASM file name 'string' is not in diskgroup "string"
  • ora-02481 : Too many processes specified for events (max string)
  • ora-24076 : cannot perform operation string for NON_PERSISTENT queue string.string
  • ora-25955 : all tables must be joined in the where clause
  • ora-34896 : (PPMONTHS00) At least 12 month names must be given. Only number were provided.
  • ora-16572 : Data Guard configuration file not found
  • ora-25017 : cannot reference NEW ROWID for movable rows in before triggers
  • ora-30025 : DROP segment 'string' (in undo tablespace) not allowed
  • ora-22313 : cannot use two versions of the same type "string"
  • ora-01671 : control file is a backup, cannot make a standby control file
  • ora-16774 : error stopping Redo Apply
  • ora-30944 : Error during rollback for XML schema 'string' table string column 'string'
  • ora-32511 : cannot create watchpoint in memory needed by watchpointing code
  • ora-29384 : number of children for plan string exceeds string
  • ora-14461 : cannot REUSE STORAGE on a temporary table TRUNCATE
  • ora-12442 : policy column "string" already used by an existing policy
  • ora-12821 : invalid value for INSTANCES
  • ora-06922 : CMX: bad write length
  • ora-13644 : The user "string" is invalid.
  • ora-12316 : syntax error in database link's connect string
  • ora-24090 : at least one protocol must be enabled
  • ora-13212 : failed to compare tile with the window object
  • 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.