The character set name is not recognized problem after RMAN migration solves a test machine. Due to unknown system problems, the operating system needs to be re-installed, and a database is running on the machine, you need to create a database and migrate it to a new machine. After the migration is complete, check the logs to find problems. Environment: www.2cto.com source redhat 5.1 oracle 10.2.0.1target centos 5.7 oracle 10.2.0.5 check the alarm log and the following information is recorded every 5 minutes: fri Dec 14 00:03:35 CST 2012 Errors in file/u01/oracle/10g/admin/DBSID/bdump/dbsid_mmon_00007.trc: fri Dec 14 00:03:35 CST 2012 Errors in file/u01/oracle/10g/admin/DBSID/bdump/dbsid_mmon_00007.trc: ORA-06550: line 1, column 7: PLS-00553: character set name is not recognizedORA-06550: line 0, column 0: PL/SQL: Compilation unit analysis terminatedFri Dec 14 00:03:35 CST 2012 Errors in file/u01/oracle/10g/admin/DBSID/bdump/dbsid_mmon_rj7.trc: fri Dec 14 00:03:35 CST 2012 Errors in file/u01/oracle/10g/admin/DBSID/bdump/dbsid_mmon_00007.trc: ORA-06550: line 1, column 7: PLS-00553: character set name is not recognizedORA-06550: line 0, column 0: PL/SQL: Compilation unit analysis terminated first checks the character set of the following database: Select parameter, value from nls_database_parameters; the query results on both sides are consistent. Check the/u01/oracle/10g/admin/DBSID/bdump/dbsid_mmon_00007.trc file and find that the file has recorded a large amount of information, and the file size has reached 291 Mb. Trc information: *** service name :( SYS $ BACKGROUND) 00:03:35. 510 *** session id: (1647.1) 00:03:35. 510 psdgbt: bind csid (852) does not match session csid (1) psdgbt: session charset is US7ASCII *** 00:03:35. 510 ksedmp: internal or fatal errorCurrent SQL statement for this session: BEGIN: success: = dbms_ha_alerts_prvt.post_instance_up; END ;........ * ** 09:53:10. 083 ksedmp: internal or fatal errorORA-06550: line 1, column 7: PLS-00553: character set name is not recognizedORA-06550: line 0, column 0: PL/SQL: compilation unit analysis terminated solves the modification problem by recreating related objects. Take a look at Note: 430146.1 from Metalink "How to recreate the SYS. ALERT_QUE [ID 430146.1] "connect/as sysdbaalter system enable restricted session; @ $ ORACLE_HOME/rdbms/admin/catnoalr. SQL @ $ ORACLE_HOME/rdbms/admin/dbmsslrt. SQL @ $ ORACLE_HOME/rdbms/admin/catalrt. SQL @ $ ORACLE_HOME/rdbms/admin/utlrp. sqlalter system disable restricted session; the problem is solved. -The End-