The particular character set is selected based on the current language locale of the operating system session that started OUI or DBCA. A Microsoft Windows character set is the default even for databases created on UNIX and Linux platforms because Microsoft Windows is the prevalent platform for client workstations. Oracle Client libraries automatically perform the necessary character set conversion between the database character set and the character sets used by non-Windows client applications.
You may also choose to use any other character set from the presented list of character sets. You can use this option to select a particular character set required by an application vendor, or choose a particular character set that is the common character set used by all clients connecting to this database.
Storage space requirements for text in most languages that use characters outside of the ASCII repertoire are higher in AL32UTF8 compared to legacy character sets supporting the language. Note that the increase in storage space concerns only character data and only data that is not in English. The universality and flexibility of Unicode usually outweighs these additional costs. Database Character Set— In this section, select one of the following options:.
Use the Default— Select this option to select only the language currently used by the operating system for all your database users and database applications. Choose from the list of character sets— Select this option if you want Oracle Database to use a character set other than the default character set used by the operating system. National Character Set— In this list, select a character set or accept the default. These data types allow storing of Unicode characters in a database that does not have a Unicode database character set.
Unless installation requirements of any of your applications specify otherwise, accept the default value of AL16UTF16 as the national character set. Default Language —In this list, select a default database language or accept the default.
The default language determines how the database supports locale-sensitive information such as day and month abbreviations, default sorting sequence for character data, and reading direction left to right or right to left. Default Territory— In this list, select the name of the territory whose conventions are to be followed for day and week numbering or accept the default. The default territory also establishes the default date format, the default decimal character and group separator, and the default International Standardization Organization ISO and local currency symbols.
Us e this window to select the database mode. You can run the database in either of the following modes:. Dedicated Server Mode —This mode allows a dedicated server process for each user process. Select this option when the number of total clients is expected to be small, for example, 50 or fewer.
You might also choose this option when database clients typically make persistent, long-running requests to the database. By default, the database is configured for dedicated server processes. Shared Server Mode— This mode allows several client connections to share a database-allocated pool of resources.
Use this mode in configurations in which client load is expected to cause a strain on memory and other system resources. If you choose shared server mode, then you must indicate the number of server processes you want to create when a database instance is started. For more information about setting this parameter, click Help.
In this window, a navigation tree displays the storage structure of your database control files, data files, online redo log groups, and so forth. If you are not satisfied with the storage structure or parameters, then you can make changes. Note that if you selected a preconfigured template for a database, then you cannot add or remove control files, data files, or undo segments. Save as a Database Template —Select this option to save the database definition as a template to use at a later time.
After you make your choice, click Finish. A confirmation window appears after a short period. You can also use DBCA to delete a database. When DBCA deletes a database, it shuts down the database instance and then deletes all database files. On the Windows platform, it also deletes associated Windows services. In the Operations window, select Delete a Database and click Next. Templates are used in DBCA to create new databases and duplicate existing databases.
The information in templates includes database options, initialization parameters, and storage attributes for data files, tablespaces, control files, and online redo log files.
Templates can be used just like scripts, but they are more powerful than scripts because you have the option of duplicating a database. Duplication saves time because you copy the files of an existing database, referred to as a seed database , to the correct locations. Easy duplication. By creating a template containing your database settings, you can easily create a duplicate database without specifying parameters twice. This type of template contains both the structure and the physical data files of an existing database, referred to as the seed database.
Your new database starts as a copy of the seed database, and requires only the following changes:. The data files for the seed database are stored in compressed RMAN backup format in a file with a. The seed database control file is stored in a file with.
This type of template is used to create a new database. It contains the characteristics of the database to be created. Nonseed templates are more flexible than their seed counterparts because all data files and online redo log files are created to your specification, and names, sizes, and other attributes can be changed as required. Users perform numerous, complex queries that process large volumes of data.
Response time, accuracy, and availability are key issues. These queries SELECT statements range from a fetch of a few records to queries that sort thousands of records from many different tables. Many concurrent users perform numerous transactions that require rapid access to data. Availability, speed, concurrency, and recoverability are key issues. This template allows you maximum flexibility in defining a database because you can change any of the settings for the database being created.
In the Operations window, select Manage Templates and click Next. In the Template Management window, select Create a database template and one of the following options, and click Next. Using an existing template, you can create a new template based on the predefined template settings. You can add or change any template settings such as initialization parameters, storage parameters, or whether to use custom scripts.
You can create a new template that contains structural information from an existing database, including database options, tablespaces, data files, and initialization parameters.
User-defined schemas and their data will not be part of the created template. The source database can be either local or remote. Select this option when you want the new database to be structurally similar to the source database, but not contain the same data. You can create a new template that has both the structural information and physical data files of an existing database. Databases created using such a template are identical to the source database.
User-defined schemas and their data will be part of the created template. The source database must be local. Select this option when you want a template from which you can create an exact replica of the source database.
When creating templates from existing databases, you can translate file paths into Optimal Flexible Architecture OFA or maintain existing file paths. OFA is a set of file naming and placement guidelines for Oracle software and databases. Using OFA is recommended if the target computer on which you plan to create a database using the template has a different directory structure than computer on which the template was defined.
Standard file paths can be used if the target computer has a directory structure that is similar to the directory structure on the source computer. When you delete a template, it is no longer available to create a new database or a new template.
In the Template Management window, select Delete a database template and click Next. This OBE steps you through the tasks in this chapter and includes annotated screenshots. Before you start the installation process, see the following sections for information about prerequisites and installation choices: Checking Prerequisites Deciding on Installation Choices If you do not create a database during installation, then you must run DBCA at some point after installation to create a database.
Note: After you create a database, either during installation or as a standalone operation, you do not have to create another. Each Oracle instance works with a single database only. Rather than requiring that you create multiple databases to accommodate different applications, Oracle Database uses a single database, and accommodates multiple applications by enabling you to separate data into different schemas within the single database.
See "About User Accounts" for more information about schemas. Checking Prerequisites Before installing the software, OUI performs several automated checks to ensure that your computer fulfills the basic hardware and software requirements for an Oracle Database installation. The requirements may vary depending upon the type of computer and operating system you are using, but some prerequisites include: There is a minimum of 1 GB of physical memory. Sufficient paging space is available.
The appropriate service packs or patches for your operating system are installed. An appropriate file system format is being used. See Also: Oracle Database Installation Guide for your platform for more information about exact requirements. Deciding on Installation Choices Oracle Universal Installer guides you through an interview phase where you specify your choices for installation and database creation.
Note: If you must create a new database, then Oracle recommends that you install a preconfigured database, which is faster and easier. You can customize the database after it has been created. Installation Method The installation methods are divided into Desktop Class and Server Class: Desktop Class —This installation class is most appropriate for laptop or desktop computers.
Installation Type When you install Oracle Database during basic and advanced installations, you need answers for the questions listed in this section. Your choices are: Enterprise Edition —This installation type is the full-featured Oracle Database product that provides data management for enterprise-level applications. What are your database configuration options?
Software Installation Directories You must specify the directory in which the Oracle Database software is installed, or the location where the product binary files are copied from the installation media. Database File Location A database includes several files that store the user data, database metadata, and information required to recover from failures.
You can select from the following options: File System —This default option creates database files that are managed by the file system of your operating system. If you are not certain about which option to use, then select File System the default. With Oracle Database 11 g release 2 About Advanced Installation During advanced installations using the Server Class method you are prompted to make the additional choices listed in this section, and the choices for a typical installation.
Product Languages You choose which language the software should use after it is installed. Use the oracle operating system user. The examples are included in the Oracle Shell for Hadoop Loaders installation on your cluster. Unzip the file examples. Run the following command to configure the environment on your cluster node. Note that the user name must be all uppercase. Before running the examples, verify the above directories exist at the operating system level.
Both directories must be owned by the oracle operating system user, with read and write permissions. If these directories don't exist, you can create them using the following commands:.
You must configure the co-managed Database service node in order to run the examples, as shown below. For example,. Check that the following variables are configured correctly. If it's not already configured, use Apache Ambari to download the Hadoop Client configuration archive file, as follows:.
Migrates one XMLType table from the 9. An exclusive lock is taken on the table before it is operated on. An exclusive lock is taken each table before it is operated on. Simply updating the configuration file, causes a new version of the file to be generated. At the start of each session, the current version of the configuration is bound to that session. The session will use this configuration for its life, unless you invoke an explicit call to refresh to the latest configuration.
It includes Web application specific parameters, for example, icon name, display name for the application, list of servlets in Oracle XML DB, and so on. It exposes the following functions:. If you have a few parameters to update in the configuration file, you can use the following:.
If you have many parameters to update, the preceding example may prove too cumbersome. Note: If the Listener is running on a non-standard port for example, not then in order for the protocols to register with the correct listener the init. Note: Make sure that the database is started with Oracle9 i Release 2 9. See Also SQL access through resource and path views. See Repository Access Using Protocols. Query-based access. This can be most suited to data oriented applications.
Java access through JDBC. What levels of security you need. See Repository Access Control. Whether you need to version the data. See Resource Versions.
0コメント