ORACLE11G cloning An instance by DBCA:
1. Modeling
Dbca-silent (silent mode)-createclonetemplate (create clone template with existing database)-sourcedb (target data source)-templatename (template name)
Cases:
Dbca-silent-createclonetemplate-sourcedb satetest-templatename Satedev 2, copy template (both sides of the environment need to be consistent, installation path is not required) copy the template file to the target host's template directory
Path:
$ORACLE _home/assistants/dbca/templates/
File:
Templatename.ctl, Templatename.dbc, TEMPLATENAME.DFB 3, creating a new instance from a template
Dbca-silent-createdatabase (CREATE DATABASE)-templatename (template name)-gdbname (Global database name)-SID (database system identifier)-syspassword (SYS user password)- Systempassword (System user password)
-datafiledestination (destination directory for all database files)-characterset (the database's character set)-nationalcharacterset (the national character set of the database)
Cases:
dbca-silent-createdatabase-templatename/home/oracle/product/11.2.0/dbhome_1/assistants/dbca/templates/ Satedev.dbc-gdbname satedev-sid Satedev-syspassword 12345678-systempassword 12345678-datafiledestination $ORACLE _ Base/oradata-characterset zhs16gbk-nationalcharacterset al16utf16 4, user unlock reset Password
Alter user user_name identified by password account unlock; 5. Delete Database
Cases:
Dbca-silent-deletedatabase-sourcedb database Instance name Appendix I, Dbca-help
[Email protected] ~]$ Dbca-help
DBCA [-silent |-progressonly |-customcreate] {<command> <options>} | {[<command> [options]]-responsefile <response file >} [-continueonnonfatalerrors <true | False>]
Please refer to the manual for more information.
You can enter one of the following commands: Create a database by specifying the following parameters:
-createdatabase
-templatename < name of existing template >
[-clonetemplate]
-gdbname < global database name >
[-policymanaged |-adminmanaged < policy Management or administrator-managed database, default is administrator-managed database;]
[-createserverpool < Create a server pool that will be used by the database to be created;]
[-force < forces the creation of a server pool without enough idle servers. This may affect the database that is already running;]
-serverpoolname < If a server pool is created, it is a server pool name; If you use a server pool, a comma-delimited list of server pool names >
-[cardinality < Specify cardinality for the new server pool to be created, default is the number of qualified nodes;]
[-sid < database system identifier;]
[-syspassword <sys user password;]
[-systempassword <system user password;]
[-emconfiguration <central| local| all| nobackup| noemail| None>
-dbsnmppassword <DBSNMP User Password >
-sysmanpassword <sysman User Password >
[-hostusername <em the host user name of the backup job >
-hostuserpassword <em The host user password for the backup job >
-backupschedule < daily backup plan using hh:mm format;]
[-smtpserver < e-mail notifications for outgoing (SMTP) servers >
e-mail address of-emailaddress < e-mail notification;]
[-centralagent <enterprise Manager Central Agent main directory;]
[-disablesecurityconfiguration <all| Audit| password_profile| None>
[-datafiledestination < target directory for all database files > | -datafilenames < contains text files for SPFile, such as control files, tablespace, redo log File database objects, and raw device file name mappings that correspond to these objects by Name=value format. ;]
[-redologfilesize < size of each redo log file (MB);]
[-recoveryareadestination < target directory of all recovered files;]
[-datafilejarlocation < data file jar location, only for cloning database creation;]
[-storagetype < FS | ASM >
[-asmsnmppassword < asmsnmp password for ASM monitoring;]
-diskgroupname < database area Disk Group name >
-recoverygroupname < Recovery area Disk Group name >
[-characterset < database's character set;]
[-nationalcharacterset < database of the national character set;]
[-registerwithdirservice <true | false>
User name for-dirserviceusername < directory service >
-dirservicepassword < directory service password >
-walletpassword < database Wallet password;]
[-listeners < Listener list, which is used to configure a database with the following objects;]
[-variablesfile < file name for paired variables and values in the template;]]
[-variables < comma-delimited list of name=value;]
[-initparams < comma-delimited list of name=value;]
[-memorypercentage < percent of physical memory used for Oracle;]
[-automaticmemorymanagement]
[-totalmemory < Memory allocated for Oracle (MB);]
[-databasetype <multipurpose| Data_warehousing| Oltp>]]Configure the database by specifying the following parameters:
-configuredatabase
-sourcedb < source database sid>
[-sysdbausername < username (with SYSDBA permission) >
-sysdbapassword <sysdbausername user name password;]
[-registerwithdirservice|-unregisterwithdirservice|-regeneratedbpassword <true | false>
User name for-dirserviceusername < directory service >
-dirservicepassword < directory service password >
-walletpassword < database Wallet password;]
[-disablesecurityconfiguration <all| Audit| password_profile| None>
[-enablesecurityconfiguration <true|false>
[-emconfiguration <central| local| all| nobackup| noemail| None>
-dbsnmppassword <DBSNMP User Password >
-symanpassword <sysman User Password >
[-hostusername <em the host user name of the backup job >
-hostuserpassword <em The host user password for the backup job >
-backupschedule < daily backup plan using hh:mm format;]
[-smtpserver < e-mail notifications for outgoing (SMTP) servers >
e-mail address of-emailaddress < e-mail notification;]
[-centralagent <enterprise Manager Central Agent main directory;]
Create a template using an existing database by specifying the following parameters:
-createtemplatefromdb
-sourcedb < services using -templatename < new template name >
-sysdbausername < username (with SYSDBA permissions) >
-sysdbapassword password for <sysdbausername user name >
[-maintainfilelocations <true | False>]
Create a clone template using an existing database by specifying the following parameters:
-createclonetemplate
-sourcesid < source database sid>
-templatename < new template name >
[-sysdbausername < username (with SYSDBA permission) >
-sysdbapassword <sysdbausername user name password;]
[-maintainfilelocations <true | False>]
[-datafilejarlocation < store the compressed format data file directory;] Generate a script to create a database by specifying the following parameters:
-generatescripts
-templatename < name of existing template >
-gdbname < global database name >
[-scriptdest < target location of all script files;] Delete the database by specifying the following parameters:
-deletedatabase
-sourcedb < source database sid>
[-sysdbausername < username (with SYSDBA permission) >
-sysdbapassword <sysdbausername user name password;]
Query for help by specifying the following options:-H | -HELP Appendix II, viewing the Oracle character set
The database character set is specified when the database is created and cannot normally be changed after it is created. When you create a database, you can specify a character set (CHARACTER set) and a national character set (Nation CHARACTER set).
1. Character Set:
(1) used to store char, VARCHAR2, CLOB, long and other types of data
(2) to indicate such as table name, column name, and PL/SQL variable, etc.
(3) used to store SQL and PL + + program units, etc.
2. National Character Set:
(1) to store nchar, NVARCHAR2, NCLOB and other types of data
(2) The national character set is essentially the additional character set chosen for Oracle, primarily to enhance the character processing capabilities of Oracle, since the nchar data type provides support for the use of fixed-length multibyte encoding in Asia, and the database character set is not. The national character set is redefined in oracle9i and can only be selected in Af16utf16 and UTF8 in Unicode encoding, and the default value is Af16utf16
3. Query Character Set parameters:
You can query the following data dictionary or view to view the set of character sets
Nls_database_parameters, props$, v$nls_parameters
Nls_characterset represents the character set in the query results, Nls_nchar_characterset represents the national character set
4. Modify the database character set:
As stated above, the database character set cannot be changed in principle after it is created. If you need to modify the character set, you typically need to export the database data, rebuild the database, import the database data in a way to convert, or modify the character set through the ALTER DATABASE CHARACTER SET statement, but there is a limit to modifying the character set after the database is created. The database character set can be modified only if the new character set is a superset of the current character set, for example UTF8 is a superset of us7ascii, and modifying the database character set can use the Alter
Existing instances Oracle under new instance (2) clone instances by DBCA