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 : 17-08-2017

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

  • ora-27461 : The value for attribute string is too large.
  • ora-07426 : spstp: cannot obtain the location of dbs directory.
  • ora-24508 : Buffer is not aligned correctly.
  • ora-14270 : table is not partitioned by Range or Hash or List method
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-26745 : cursors (string) are not sufficient
  • ora-26024 : SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
  • ora-01194 : file string needs more recovery to be consistent
  • ora-39959 : invalid warning number (string)
  • ora-16700 : the standby database has diverged from the primary database
  • ora-04076 : invalid NEW or OLD specification
  • ora-23375 : feature is incompatible with database version at string
  • ora-22282 : non-contiguous append to a buffering enabled LOB not allowed
  • ora-00310 : archived log contains sequence string; sequence string required
  • ora-23474 : definition of "string"."string" has changed since generation of replication support
  • ora-30387 : invalid rewrite mode for REWRITE_EQUIVALENCE API
  • ora-31054 : The string operator cannot have an ancillary operator
  • ora-25207 : enqueue failed, queue string.string is disabled from enqueueing
  • ora-12817 : parallel query option must be enabled
  • ora-00299 : must use file-level media recovery on data file string
  • ora-06301 : IPA: Cannot allocate driver context
  • ora-12809 : cannot set string_INSTANCES when mounted in exclusive mode
  • ora-00051 : timeout occurred while waiting for a resource
  • ora-12071 : definition query of "string"."string" is invalid for offline instantiation
  • ora-29319 : datafile string is not correct
  • ora-36849 : (XSLMGEN19) AW owner does not match View token owner
  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-19016 : attributes cannot occur after element specifications
  • ora-01784 : RECOVERABLE cannot be specified with database media recovery disabled
  • ora-16643 : unable to determine location of broker configuration 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.