Working with Oracle database supported application, which we want to internationalize, and then\u00a0 \u2018charset\u2019 is crucial factor to provide Unicode storage ability.<\/p>\n
If we are going to internationalize a new project then we can start by creating a Unicode supported database.<\/p>\n
For example, we can select AL32UTF8 charset while creating the database.<\/p>\n
If we are going to support internationalization on an existing database then, we need to change the charset of database.<\/p>\n
There are two ways of changing charset of a database.<\/p>\n
Either you can directly alter the charset of existing database or by performing full import export.<\/p>\n
First you need to know the current charset of database<\/p>\n
<pre><\/p>\n
SELECT value$ FROM sys.props$ WHERE name = \u2018NLS_CHARACTERSET\u2019 ;<\/p>\n
<\/pre><\/p>\n
This query will tell you current charset of your database.<\/p>\n
Other Oracle database NLS parameters can be known by following query<\/p>\n
<pre><\/p>\n
SELECT * FROM NLS_DATABASE_PARAMETERS;<\/p>\n
<\/pre><\/p>\n
To alter charset of database directly, the target charset should be a strict superset of current database charset.<\/p>\n
You can alter charset with following steps:<\/p>\n
1.\u00a0 Shut down the database, using either a SHUTDOWN IMMEDIATE or a SHUTDOWN NORMAL statement.<\/p>\n
2.\u00a0 Do a full backup of the database, because the CSALTER script cannot be rolled back.<\/p>\n
3.\u00a0 Start up the database.<\/p>\n
4.\u00a0 Run the Database Character Set Scanner utility.<\/p>\n
<pre><\/p>\n
CSSCAN \/AS SYSDBA FULL=Y…<\/p>\n
<\/pre><\/p>\n
5.\u00a0 Run the CSALTER script.<\/p>\n
<pre><\/p>\n
@@CSALTER.PLB<\/p>\n
SHUTDOWN IMMEDIATE; — or SHUTDOWN NORMAL;<\/p>\n
STARTUP;<\/p>\n
<\/pre><\/p>\n
The other way is quite safer and recommended.<\/p>\n
Following are the steps to export and import data in oracle 11g R2:<\/p>\n
To export database:<\/p>\n
1.\u00a0 Start SqlDeveloper.<\/p>\n
2.\u00a0 Create connections for source and destination. (Note: Use system user)<\/p>\n
3.\u00a0 From View menu select DBA. DBA pane will appear.<\/p>\n
4.\u00a0 Now in DBA pane, add connections.<\/p>\n
5.\u00a0 Click and expand the source connection, then right-click on ‘Data Pump’, and then click on ‘Data Pump Export Wizard.’ Export Wizard will start.<\/p>\n
6.\u00a0 In ‘Data Pump Export Wizard,’ select Schema option in Types to be Exported in ‘Data Pump’ and click on ‘Next.’<\/p>\n
7.\u00a0 Select(double click) a schema that you want to export and click ‘Next.’<\/p>\n
8.\u00a0 Skip the step Filter and click ‘Next.’<\/p>\n
9.\u00a0 Now, click on ‘More,’ now select Type as ‘ALL OBJECTS’ and click on ‘Lookup.’ All the objects are displayed.<\/p>\n
10. From the interface select and add objects to include for export and click ‘Next.’ To include all objects just click on down double-arrow button.<\/p>\n
11. Specify the name for log file or just leave the default and click ‘Next.’<\/p>\n
12. In ‘Choose Output Files’ section, specify the File Names (For example exportdata.dmp), choose an appropriate option if file already exists, and click ‘Next.’<\/p>\n
13. Now leave the default settings and click ‘Next.’<\/p>\n
14. In ‘Summary’ section, verify whether the desired schema is included, and finally click ‘Finish.’ You will see this job and its status in ‘Data Pump’ > ‘Export Jobs’ of DBA pane.<\/p>\n
15. Now, copy this file from the source machine to the destination machine.<\/p>\n
For importing database:<\/p>\n
1.\u00a0 Start SqlDeveloper and open ‘Data Pump Import Wizard.’<\/p>\n
2.\u00a0 In Wizard, select Connection where you want to import(destination system).<\/p>\n
3.\u00a0 Select Schema and specify file Name. In this case, file is exportdata.dmp and then click ‘Next.’<\/p>\n
4.\u00a0 Now, include the schema that you want to import from ‘Available Source Schemas’ to ‘Selected Source Schemas’ and click ‘Next.’<\/p>\n
5.\u00a0 Skip Remapping step by clicking ‘Next.’<\/p>\n
6.\u00a0 In Options step, select appropriate options for ‘Action On Table’ if Table Exists and click ‘Next.’<\/p>\n
7.\u00a0 Click ‘Next’ and finally Click ‘Finish.’<\/p>\n
Your database will be imported as per selected options and schemas.<\/p>\n","protected":false},"excerpt":{"rendered":"
Working with Oracle database supported application, which we want to internationalize, and then\u00a0 \u2018charset\u2019 is crucial factor to provide Unicode storage ability. If we are going to internationalize a new…<\/p>\n","protected":false},"author":9192191,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[3],"tags":[],"class_list":["post-1065","post","type-post","status-publish","format-standard","hentry","category-technology"],"_links":{"self":[{"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/posts\/1065","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/users\/9192191"}],"replies":[{"embeddable":true,"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/comments?post=1065"}],"version-history":[{"count":1,"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/posts\/1065\/revisions"}],"predecessor-version":[{"id":1066,"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/posts\/1065\/revisions\/1066"}],"wp:attachment":[{"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/media?parent=1065"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/categories?post=1065"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.allerin.com\/blog\/wp-json\/wp\/v2\/tags?post=1065"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}