ORA-12710: CREATE CONTROLFILE character set is not known

Cause : The chraacter est specfiied whne creatnig the ocntrol ifle is nuknown.

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

none

update : 19-08-2017
ORA-12710

ORA-12710 - CREATE CONTROLFILE character set is not known
ORA-12710 - CREATE CONTROLFILE character set is not known

  • ora-36178 : (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-07427 : spstp: cannot change directory to dbs.
  • ora-26753 : Mismatched columns found in 'string.string'
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-14110 : partitioning column may not be of type ROWID
  • ora-03216 : Tablespace/Segment Verification cannot proceed
  • ora-13768 : Snapshot ID must be between string and string.
  • ora-00333 : redo log read error block string count string
  • ora-29917 : cannot lock a table which gets its rows from a collection operand
  • ora-19916 : %s
  • ora-10259 : get error message text from remote using explicit call
  • ora-23300 : %s
  • ora-09851 : soacon: Archmon unable to lock named pipe.
  • ora-38708 : not enough space for first flashback database log file
  • ora-07287 : sksagdi: unsupported device for log archiving.
  • ora-13126 : unable to determine class for spatial table string
  • ora-00397 : instance recovery process terminated with error
  • ora-29293 : A stream error occurred during compression or uncompression.
  • ora-12829 : Deadlock - itls occupied by siblings at block string of file string
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-19271 : XP0051 - invalid atomic type definition
  • ora-26093 : input data column size (number) exceeds the maximum input size (number)
  • ora-01371 : Complete LogMiner dictionary not found
  • ora-14458 : attempt was made to create a temporary table with INDEX organization
  • ora-10700 : Alter access violation exception handler
  • ora-39070 : Unable to open the log file.
  • ora-32618 : incorrect use of MODEL PREVIOUS function
  • ora-12554 : TNS:current operation is still in progress
  • ora-12448 : policy string not applied to schema 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.