Ora-00257 errors and oracle Character Set

Ora-00257 errors and oracle Character Set sqlplus/nologconn charge/charge cause ora-00257 errors are generally caused by an archiving log storage directory full and archive failure. // * Cause: The archiver process has ed an error while trying to archive // a redo log. if the problem is not resolved soon, the database // will stop executing transactions. the most likely cause of this // message is the destination device is out of space to store the // redo log file. // * Action: Check archiver trace file for a detailed description // of the problem. also verify that the // device spe Cified in the initialization parameter // ARCHIVE_LOG_DEST is set up properly for archiving and view my parameters in the archive storage directory: show parameter ARCHIVE_LOG_DEST: name type value certificate ----------- export audit_file_dest string/app/oracle/admin/oradb/export string/app/oracle/admin/oradb/bdumpcore_dump_dest string/app/oracle/admin/oradb/cdumpdb_re Ate_file_dest too many bytes before using stringdb_recovery_file_dest string/app/oracle/flash_recovery_are adb_recovery_file_dest_size big integer 1Glog_archive_dest too many bytes string SERVICE = Export arc h VALID_FOR = (ONLINE_LOGFILES, P RIMARY_ROLE) DB_UNIQUE_NAME = or adg. You can see that I have done DG. If the archive in this file is not configured with log_archive_dest, in addition, if I set 1 GB to view the Directory: du-sh/app/oracle/flash_recovery_area/archivelog used 928 M, delete the archive log immediately, note: To delete an archive, delete it in RMAN. The following are the deletion steps: rman target/---- connect to crosscheck archivelog all; ------- check useless archive logs delete archivelog until time 'sysdate-1 '; --------------- the archived SQ for the last day is retained. L> select * from v $ values; FILE_TYPE PERCENT_SPACE_USED limit NUMBER_OF_FILES ------------ ------------------ limit ----------------- CONTROLFILE 0 0 0 ONLINELOG 0 0 ARCHIVELOG 0 0 0 0 BACKUPPIECE 1.14. 57 2 IMAGECOPY 0 0 0 FLASHBACKLOG 7.42 5.94 5 check that the usage returns to normal The following describes the oracle character set: first, how to view the oracle Character Set 1. select * from props $ where name in ('nls _ Language', 'nls _ TERRITO RY ', 'nls _ CHARACTERSET', 'nls _ NCHAR_CHARACTERSET '); 2. select userenv ('language') "LANGUAGE" from dual; both methods can be used to view the database system Character Set NLS_LANG = language_territory.charset. It has three components (Language, region, and character set ), each component controls the NLS subset features. For example: AMERICAN _ AMERICA. description of ZHS16GBK character set encoding: <Language> <bit size> <encoding> that is, <Language> <bit number> <encoding> for example: ZHS · 16 · GBK and above are server-side character sets. below is the client-side character set. For linux, you can search for NLS_LANG in the Registry under echo $ NLS_LANGwindows. Here we will mainly introduce how to modify the dmp file Character Set: we believe that we often encounter Character Set troubles when using exp/imp. Here we can actually modify the header information of the dmp file, which is consistent with the modification to be imported, generally, this is also possible, but it actually bypasses the oracle check. The 2nd byte of the dmp file records the character set information. Theoretically, this field supports modification from the subset to the superset. Specifically, you can use the UE to open the DMP file, find 2 and 3 bytes of select nls_charset_name (to_number ('123', 'xxx') from dual; if dmp is large, you can use the linux Command cat and awk to view the select to_char (nls_charset_id ('utf8'), 'xxxx') from dual; 367 open the dmp file and modify the corresponding 2 and 3 bytes. The modification of the database character set is not detailed here, so pay attention to it when creating the database.