ORA-12734: Instant Client Light: unsupported client national character set string

Cause : Only UTF8 and AL16UTF16 are allowed to be used as the national character set. Instant Client Light has only minimal character sets.

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

Do not use Instant Client Light for this character set

update : 29-06-2017
ORA-12734

ORA-12734 - Instant Client Light: unsupported client national character set string
ORA-12734 - Instant Client Light: unsupported client national character set string

  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-25425 : connection lost during rollback
  • ora-01248 : file string was created in the future of incomplete recovery
  • ora-24302 : host connection in use by another thread
  • ora-01586 : database must be mounted EXCLUSIVE and not open for this operation
  • ora-26727 : Cannot alter queue_to_queue property of existing propagation.
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-36271 : (XSCGMDLAGG11) workspace object is not in the dimension list of valueset workspace object.
  • ora-08315 : sllfrb: Error reading file
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-09930 : LUB of two labels is invalid
  • ora-38748 : cannot flashback data file string - file is in use or recovery
  • ora-14021 : MAXVALUE must be specified for all columns
  • ora-06778 : TLI Driver: error sending ccode
  • ora-32302 : object materialized views must be object ID based
  • ora-16060 : Log file is current
  • ora-19276 : XP0005 - XPath step specifies an invalid element/attribute name: (string)
  • ora-29347 : Tablespace name validation failed - failed to match tablespace 'string'
  • ora-07642 : smprtset: $CMKRNL failure
  • ora-22064 : invalid NLS parameter string [string]
  • ora-23417 : unknown materialized view type: string
  • ora-30033 : Undo tablespace cannot be specified as default user tablespace
  • ora-14457 : disallowed Nested Table column in a Temporary table
  • ora-24071 : cannot perform operation string, queue table string is being migrated
  • ora-12411 : invalid label value
  • ora-29282 : invalid file ID
  • ora-30725 : JDWP-based debugging is not yet available
  • ora-03274 : both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified
  • ora-07474 : snclrd: close error, unable to close sgadef.dbf file.
  • ora-31689 : illegal value for base worker 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.