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

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

  • ora-25298 : Only immediage visibility mode supported for buffered message enqueue or dequeue
  • ora-24300 : bad value for mode
  • ora-01517 : log member: 'string'
  • ora-00446 : background process started when not expected
  • ora-31154 : invalid XML document
  • ora-21500 : internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-31415 : change set string does not exist
  • ora-23364 : Feature not enabled: Advanced replication
  • ora-02772 : Invalid maximum server idle time
  • ora-13431 : GeoRaster metadata rasterType error
  • ora-09986 : wrong number of bytes read from SGA definition file
  • ora-39079 : unable to enqueue message string
  • ora-15028 : ASM file 'string' not dropped; currently being accessed
  • ora-31045 : Cannot store more than string extras outside the root XML node
  • ora-09202 : sfifi: error identifying file
  • ora-07425 : sdpri: error string in translating dump file location.
  • ora-29318 : datafile string is online
  • ora-23606 : invalid object string
  • ora-24144 : rules engine internal error, arguments: [string], [string]
  • ora-24341 : bad mode specified
  • ora-09360 : Windows 3.1 Two-Task driver unable to allocate context area
  • ora-38764 : flashback not started; datafile string enabled threads are different
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-12806 : could not get background process to hold enqueue
  • ora-24372 : invalid object for describe
  • ora-16020 : less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
  • ora-01978 : Missing sequence number
  • ora-30378 : MV_CAPABILITIES_TABLE is not compatible with Oracle version
  • ora-12545 : Connect failed because target host or object does not exist
  • 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.