how to create manual database in oracle 10g step by step
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:how to create manual database in oracle 10g step by step.pdf
Size: 1414 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 26 May 2019, 16:10 PM
Rating: 4.6/5 from 817 votes.
Status: AVAILABLE
Last checked: 10 Minutes ago!
In order to read or download how to create manual database in oracle 10g step by step ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
how to create manual database in oracle 10g step by stepIt is something that will take thought and planning and something that you should understand early, both in your career and in your exam preparations. This chapter shows you how to create a database manually and use the GUI interface. The database may be one created automatically as a part of the initial Oracle 9i Server installation, or it can be created later, either using the Database Configuration Assistant or manually with database creation scripts. If you are migrating a database from an earlier version (8i, for example), you can accomplish this either through the use of the database migration assistant or the use of migration scripts. It is a task needed only once for a database, regardless of how many data files that database ultimately has. Because of the importance of this task, careful decisions must be made on many of the database settings. Included in yourAlthough a data warehouse may not need to have archive logs for normalAll rights reserved. If you use the CREATE DATABASE statement, you must complete additional actions before you have an operational database. You perform these actions by running prepared scripts. Refer to the Oracle Real Application Clusters (Oracle RAC) installation guide for your platform for instructions for creating an Oracle RAC database. In fact, multiple Oracle instances (and their associated databases) can run on a single host computer. A single-instance database is a database that is accessed by only one Oracle instance, as opposed to an Oracle RAC database, which is accessed concurrently by multiple Oracle instances on multiple nodes. See Oracle Real Application Clusters Administration and Deployment Guide for more information on Oracle RAC. The examples create a database named mynewdb. If you are using Oracle Automatic Storage Management (ASM) to manage your disk storage, you must start the ASM instance and configure your disk groups before performing these steps.http://www.mc-opony.pl/files/how-much-does-it-cost-to-repair-manual-transmission.xml
- Tags:
- how to create manual database in oracle 10g step by step, how to create manual database in oracle 10g step by step steps, how to create manual database in oracle 10g step by step pdf, how to create manual database in oracle 10g step by step equations, how to create manual database in oracle 10g step by step authentication.
For information about Automatic Storage Management, see Oracle Database Storage Administrator's Guide. Use this command windows for the subsequent steps. On some platforms, the SID is case-sensitive. It is common practice to set the SID to be equal to the database name. The maximum number of characters for the database name is eight.On the UNIX and Linux platforms, you must set these environment variables manually.You can authenticate as an administrator with the required privileges in the following ways: If you decide to authenticate with operating system authentication, ensure that you log in to the host computer with a user account that is a member of the appropriate operating system user group. On the UNIX and Linux platforms, for example, this is typically the dba user group. On the Windows platform, the user installing the Oracle software is automatically placed in the required user group. This file can be a text file, which can be created and modified with a text editor, or a binary file, which is created and dynamically modified by the database. The binary file, which is preferred, is called a server parameter file. In this step, you create a text initialization parameter file. In a later step, you create a server parameter file from the text file. Then when you start your database, it will not be necessary to specify the PFILE clause of the STARTUP command, because Oracle Database automatically looks in the default location for the initialization parameter file. The ORADIM command creates an Oracle instance by creating a new Windows service. This command creates the instance but does not start it. Do not set the -STARTMODE argument to AUTO at this point, because this causes the new instance to start and attempt to mount the database, which does not exist yet. You can change this parameter to AUTO, if desired, in Step 14. Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production.http://quiltandsewingplace.com/I09GGiVsZciNEgX1.xml With the Partitioning, OLAP and Data Mining optionsYou may have connected to the wrong instance.You create the server parameter file from your edited text initialization file. The database must be restarted before the server parameter file takes effect. Although creating a server parameter file is optional at this point, it is recommended. If you do not create a server parameter file, the instance continues to read the text initialization parameter file whenever it starts.Typically, you do this only during database creation or while performing maintenance on the database. Use the STARTUP command with the NOMOUNT clause. In this example, because the initialization parameter file or server parameter file is stored in the default location, you are not required to specify the PFILE clause: The database itself does not yet exist. This example assumes the following: Its global database name is mynewdb.us.oracle.com, where the domain portion ( us.oracle.com ) is taken from the initialization file.Beginning with Release 11 g, the passwords are case-sensitive. The two clauses that specify the passwords for SYS and SYSTEM are not mandatory in this release of Oracle Database. However, if you specify either clause, you must specify both clauses.MAXLOGFILES, MAXLOGMEMBERS, and MAXLOGHISTORY define limits for the redo log.This number affects the initial sizing of the control file. You can set several limits during database creation. Some of these limits are limited by and affected by operating system limits. For example, if you set MAXDATAFILES, Oracle Database allocates enough space in the control file to store MAXDATAFILES filenames, even if the database has only one datafile initially. However, because the maximum control file size is limited and operating system dependent, you might not be able to set all CREATE DATABASE parameters at their theoretical maximums.This is customary during database creation.http://www.drupalitalia.org/node/78358 You can later use an ALTER DATABASE statement to switch to ARCHIVELOG mode.The CREATE DATABASE statement does not create directories. If you receive an error message that contains a process number, examine the trace file for that process. Look for the trace file that contains the process number in the trace file name.This parameter defines the base directory for the various database files that the database creates and automatically names. The following statement is an example of setting this parameter in the initialization parameter file: Note that these properties and the other default database properties set by this method may not be suitable for your production environment, so it is recommended that you examine the resulting configuration and modify it if necessary. UNDO TABLESPACE undotbs1. DEFAULT TABLESPACE users;If your CREATE DATABASE statement fails, and if you did not complete Step 7, ensure that there is not a pre-existing server parameter file (SPFILE) for this instance that is setting initialization parameters in an unexpected way. For example, an SPFILE contains a setting for the complete path to all control files, and the CREATE DATABASE statement fails if those control files do not exist. Ensure that you shut down and restart the instance (with STARTUP NOMOUNT ) after removing an unwanted SPFILE.The following sample script creates some additional tablespaces: Grants PUBLIC access to the synonyms. The scripts that you run are determined by the features and options you choose to use or install. Many of the scripts available to you are described in the Oracle Database Reference. Some products require you to create additional data dictionary tables. Usually, command files are provided to create and load these tables into the database data dictionary. For information on backing up a database, see Oracle Database Backup and Recovery User's Guide. See your operating system documentation for instructions.https://danceofcyprus.com/images/boyce-solutions-manual-pdf.pdf For example, on Windows, use the following command to configure the database service to start the instance upon computer restart: Legal Notices. You can also launch DBCA as a standalone tool at any time after Oracle Database installation to create or make a copy (clone) of a database. Refer to Oracle Database 2 Day DBA for detailed information on creating a database using DBCA. If you do so, you must complete additional actions before you have an operational database. These actions include creating users and temporary tablespaces, building views of the data dictionary tables, and installing Oracle built-in packages. These actions can be performed by executing prepared scripts, many of which are supplied for you. Oracle provides a sample database creation script and a sample initialization parameter file with the Oracle Database software files. Both the script and the file can be edited to suit your needs.You can upgrade your existing Oracle Database and use it with the new release of the database software. The Oracle Database Upgrade Guide manual contains information about upgrading an existing Oracle Database. You need only create a database once, regardless of how many datafiles it has or how many instances access it. You can create a database to erase information in an existing database and create a new database with the same name and physical structure. Table 2-1 lists some recommended actions: For example, you can place redo log files on separate disks or use striping. You can situate datafiles to reduce contention. And you can control data density (number of rows to a data block). Become familiar with the concept and operation of a server parameter file. A server parameter file lets you store and manage your initialization parameters persistently in a server-side disk file. You must specify the database character set when you create the database. Otherwise, character conversions may be necessary at the cost of increased overhead and potential data loss.https://www.bountyvacation.com/wp-content/plugins/formcraft/file-upload/server/content/files/1627efa0468375---brother-sewing-machine-manual-ls-2125.pdf It is equivalent to the IANA registered standard UTF-8 encoding, which supports all valid XML characters. Database character set UTF8 has been superseded by AL32UTF8. Do not use UTF8 for XML data. UTF8 supports only Unicode version 3.1 and earlier; it does not support all valid XML characters. AL32UTF8 has no such limitation. This will terminate parsing and raise an exception. The default time zone file is timezonelrg.dat. It contains more time zones than the other time zone file, timezone.dat. Additionally, you can specify up to four nonstandard block sizes when creating tablespaces. It is important to protect the control file by multiplexing, to choose the appropriate backup mode, and to manage the online and archived redo logs. This includes setting various environment variables unique to your operating system and establishing the directory structure for software and database files. You must be specially authenticated by your operating system or through a password file, allowing you to start up and shut down an instance before the database is created or opened.If you use the Oracle Universal Installer, it will guide you through your installation and provide help in setting environment variables and establishing directory structure and authorizations. These steps should be followed in the order presented. The prerequisites described in the preceding section must already have been completed. That is, you have established the environment for creating your Oracle Database, including most operating system dependent environmental variables, as part of the Oracle software installation process. These cross-references take you to material that will help you to learn about and understand the initialization parameters and database structures with which you are not yet familiar. This identifier is used to distinguish this instance from other Oracle Database instances that you may create later and run concurrently on your system.airbornelabs.com/images/editor/files/camera-eyewear-v13-user-manual.pdf You can use the password file or operating system authentication method. Database administrator authentication and authorization is discussed in the following sections of this book: The binary file, which is preferred, is called a server parameter file. In this step, you create a text initialization parameter file. In a later step, you can optionally create a server parameter file from the text file. On Unix operating systems, the Oracle Universal Installer installs a sample text initialization parameter file in the following location:Then when you start your database, it will not be necessary to specify the PFILE clause of the STARTUP command, because Oracle Database automatically looks in the default location for the initialization parameter file. The server parameter file enables you to change initialization parameters with database commands and persist the changes across a shutdown and startup. You create the server parameter file from your edited text initialization file.The script can be executed before or after instance startup, but after you connect as SYSDBA. The database must be restarted before the server parameter file takes effect. Typically, you do this only during database creation or while performing maintenance on the database. Use the STARTUP command with the NOMOUNT clause. In this example, because the server parameter file is stored in the default location, you are not required to specify the PFILE clause: The database itself does not yet exist. The following statement creates database mynewdb: The two clauses that specify the passwords for SYS and SYSTEM are not mandatory in this release of Oracle Database. However, if you specify either clause, you must specify both clauses.MAXLOGFILES, MAXLOGMEMBERS, and MAXLOGHISTORY define limits for the redo log.This number affects the initial sizing of the control file. You can set several limits during database creation. Some of these limits are limited by and affected by operating system limits.https://laneopx.com/wp-content/plugins/formcraft/file-upload/server/content/files/1627efa176be4c---brother-serger-instruction-manual.pdf For example, if you set MAXDATAFILES, Oracle Database allocates enough space in the control file to store MAXDATAFILES filenames, even if the database has only one datafile initially. However, because the maximum control file size is limited and operating system dependent, you might not be able to set all CREATE DATABASE parameters at their theoretical maximums.This is customary during database creation. You can later use an ALTER DATABASE statement to switch to ARCHIVELOG mode.The following sample script creates some additional tablespaces: CREATE TABLESPACE users LOGGING CREATE TABLESPACE indx LOGGING Grants PUBLIC access to the synonyms. The scripts that you run are determined by the features and options you choose to use or install. Many of the scripts available to you are described in the Oracle Database Reference. Some products require you to create additional data dictionary tables. Usually, command files are provided to create and load these tables into the database data dictionary. For information on backing up a database, see Oracle Database Backup and Recovery Basics. The actual operations performed depend on the clauses that you specify in the CREATE DATABASE statement and the initialization parameters that you have set. Oracle Database performs at least these operations: Many of the CREATE DATABASES clauses discussed here can be used to simplify the creation and management of your database. To protect your database, you should change these passwords using the ALTER USER statement immediately after database creation. The default passwords are commonly known, and if you neglect to change them later, you leave database vulnerable to attack by malicious users. The COMPATIBLE initialization parameter must be set to 9.2 or higher for this statement to be successful. If you do not specify the EXTENT MANAGEMENT LOCAL clause, by default the database creates a dictionary-managed SYSTEM tablespace. Dictionary-managed tablespaces are deprecated.http://julieesteban.com/wp-content/plugins/formcraft/file-upload/server/content/files/1627efa282d912---brother-sewing-machines-manual-ls-2125.pdf You may notice an increase in the initial size of objects created in a locally managed SYSTEM tablespace because of the autoallocate policy. It is not possible to create a locally managed SYSTEM tablespace and specify UNIFORM extent size. If you omit that clause, Oracle Database creates a locally managed undo tablespace for you using the default name and in a default location. The SYSAUX tablespace serves as an auxiliary tablespace to the SYSTEM tablespace. Because it is the default tablespace for many Oracle Database features and products that previously required their own tablespaces, it reduces the number of tablespaces required by the database and that you must maintain. Other functionality or features that previously used the SYSTEM tablespace can now use the SYSAUX tablespace, thus reducing the load on the SYSTEM tablespace. Mandatory attributes of the SYSAUX tablespace are set by Oracle Database and include: You cannot drop or rename the SYSAUX tablespace. See Table 2-2 for a list of all SYSAUX occupants. Based on the initial sizes of these components, the SYSAUX tablespace needs to be at least 240 MB at the time of database creation. The space requirements of the SYSAUX tablespace will increase after the database is fully deployed, depending on the nature of its use and workload.This book discusses the creation of the SYSAUX database at database creation. When upgrading from a release of Oracle Database that did not require the SYSAUX tablespace, you must create the SYSAUX tablespace as part of the upgrade process. This is discussed in Oracle Database Upgrade Guide. In this mode, undo data is stored in an undo tablespace and is managed by Oracle Database. If you want to define and name the undo tablespace yourself, you must also include the UNDO TABLESPACE clause in the CREATE DATABASE statement at database creation time.Oracle Database assigns to this tablespace any non- SYSTEM users for whom you do not explicitly specify a different permanent tablespace.aidsaccess.com/ckupload/files/camera-eyewear-v12-manual.pdf If you do not specify this clause, then the SYSTEM tablespace is the default permanent tablespace for non- SYSTEM users. Oracle strongly recommends that you create a default permanent tablespace. Oracle Database assigns this tablespace as the temporary tablespace for users who are not explicitly assigned a temporary tablespace. However, if you do not do so, and if no default temporary tablespace has been specified for the database, then by default these users are assigned the SYSTEM tablespace as their temporary tablespace. It is not good practice to store temporary data in the SYSTEM tablespace, and it is cumbersome to assign every user a temporary tablespace individually. Therefore, Oracle recommends that you use the DEFAULT TEMPORARY TABLESPACE clause of CREATE DATABASE. When you specify a locally managed SYSTEM tablespace, the SYSTEM tablespace cannot be used as a temporary tablespace. In this case the database creates a default temporary tablespace.You do this by creating a new temporary tablespace or tablespace group with a CREATE TEMPORARY TABLESPACE statement, and then assign it as the temporary tablespace using the ALTER DATABASE DEFAULT TEMPORARY TABLESPACE statement. Users will automatically be switched (or assigned) to the new default temporary tablespace. When using a locally managed SYSTEM tablespace, the new default temporary tablespace must also be locally managed. You cannot change a default temporary tablespace to a permanent tablespace. You do this either by specifying a directory in which your files are created and managed by Oracle Database, or by using Automatic Storage Management. When you use Automatic Storage Management, you specify a disk group in which the database creates and manages your files, including file redundancy and striping. Oracle Database will automatically create and manage the operating system files for the following database structures, depending on which initialization parameters you specify and how you specify clauses in your CREATE DATABASE statement: Bigfile tablespaces can contain only one file, but that file can have up to 4G blocks. The maximum number of datafiles in an Oracle Database is limited (usually to 64K files). Therefore, bigfile tablespaces can significantly enhance the storage capacity of an Oracle Database. Specify either SET DEFAULT BIGFILE TABLESPACE or SET DEFAULT SMALLFILE TABLESPACE. If you omit this clause, the default is a smallfile tablespace, which is the traditional type of Oracle Database tablespace. A smallfile tablespace can contain up to 1022 files with up to 4M blocks each. SQL syntax for the ALTER TABLESPACE statement has been extended to allow you to perform operations on tablespaces, rather than the underlying datafiles. However, you can explicitly override the default tablespace type for the UNDO and DEFAULT TEMPORARY tablespace during the CREATE DATABASE operation. If you do not set the database time zone, then it defaults to the time zone of the server's operating system. The following information is also included for each time zone: The NOLOGGING setting can speed up operations that can be easily recovered outside of the database recovery mechanisms, but it can negatively affect media recovery and standby databases. The database never generates redo records for temporary tablespaces and temporary segments, so forced logging has no affect for objects. If you do not specify this clause, the database is not placed into FORCE LOGGING mode. This statement can take a considerable time for completion, because it waits for all unlogged direct writes to complete. However, if FORCE LOGGING mode is in effect for the database, it takes precedence over the tablespace setting. If it is not in effect for the database, then the individual tablespace settings are enforced. Oracle recommends that either the entire database is placed into FORCE LOGGING mode, or individual tablespaces be placed into FORCE LOGGING mode, but not both. That is, if the database is shut down and restarted, it remains in the same logging mode. However, if you re-create the control file, the database is not restarted in the FORCE LOGGING mode unless you specify the FORCE LOGGING clause in the CREATE CONTROL FILE statement. If the primary reason for specifying FORCE LOGGING is to ensure complete media recovery, and there is no standby database active, then consider the following: Media recovery is not possible in NOARCHIVELOG mode, so if you combine it with FORCE LOGGING, the result may be performance degradation with little benefit. The binary file is called a server parameter file, and it always resides on the server. A server parameter file enables you to change initialization parameters with ALTER SYSTEM commands and to persist the changes across a shutdown and startup. It also provides a basis for self-tuning by the Oracle Database server. For these reasons, it is recommended that you use a server parameter file. You can create one from your edited text initialization file or by using the Database Configuration Assistant. Upon startup, the Oracle instance first searches for a server parameter file in a default location, and if it does not find one, searches for a text initialization parameter file. You can also override an existing server parameter file by naming a text initialization parameter file as an argument of the STARTUP command. You can edit these Oracle-supplied initialization parameters and add others, depending upon your configuration and options and how you plan to tune the database. For any relevant initialization parameters not specifically included in the initialization parameter file, the database supplies defaults. As you become more familiar with your database and environment, you can dynamically tune many initialization parameters using the ALTER SYSTEM statement. If you are using a text initialization parameter file, your changes are effective only for the current instance. To make them permanent, you must update them manually in the initialization parameter file, or they will be lost over the next shutdown and startup of the database. If you are using a server parameter file, initialization parameter file changes made by the ALTER SYSTEM statement can persist across shutdown and startup.The combination of the settings for these two parameters must form a database name that is unique within a network. If the database you are about to create will ever be part of a distributed database system, give special attention to this initialization parameter before database creation. It is distinct from the database area, which is a location for the Oracle-managed current database files (datafiles, control files, and online redo logs). It cannot be a raw file system. You must disable those parameters before setting up the flash recovery area.If you inadvertently specify a file that already exists and execute the CREATE DATABASE statement, the previous contents of that file will be overwritten. This block size is used for the SYSTEM tablespace and by default in other tablespaces. Oracle Database can support up to four additional nonstandard block sizes. In many cases, this is the only block size that you need to specify. If you do not set a value for this parameter, the default data block size is operating system specific, which is generally adequate. If the database block size is different from the operating system block size, ensure that the database block size is a multiple of the operating system block size.For example, databases controlled by mainframe computers with vast hardware resources typically use a data block size of 4K or greater. For best performance in this case, a database block should consist of multiple operating system blocks. Your operating system specific Oracle documentation for details about the default block size. These nonstandard block sizes can have any of the following power-of-two values: 2K, 4K, 8K, 16K or 32K. Platform-specific restrictions regarding the maximum block size apply, so some of these sizes may not be allowed on some platforms. You can, for example, transport a tablespace that uses a 4K block size from an OLTP environment to a data warehouse environment that uses a standard block size of 8K. The size of the SGA is dynamic, and can grow or shrink by dynamically altering these parameters. All SGA components allocate and deallocate space in units of granules. Oracle Database tracks SGA memory use in internal numbers of granules for each SGA component. Granule size is determined by total SGA size. Generally speaking, on most platforms, if the total SGA size is equal to or less than 1 GB, then granule size is 4 MB. For SGAs larger than 1 GB, granule size is 16 MB. Some platform dependencies may arise. For example, on 32-bit Windows NT, the granule size is 8 MB for SGAs larger than 1 GB. Consult your operating system specific documentation for more details. The same granule size is used for all dynamic components in the SGA. This parameter in effect replaces the parameters that control the memory allocated for a specific set of individual components, which are now automatically and dynamically resized (tuned) as needed. This is discussed in detail later in this section. An easier way to enable automatic shared memory management is to use Oracle Enterprise Manager (EM).Do this by editing the text initialization parameter file, or by issuing ALTER SYSTEM statements similar to the one in step 2. Do this by editing the text initialization parameter file, or by issuing ALTER SYSTEM statements similar to the one in step 2. Doing so can be useful if you know that an application cannot function properly without a minimum amount of memory in specific components. You specify the minimum amount of SGA space for a component by setting a value for its corresponding initialization parameter. Here is an example configuration: The remaining 124M (256 minus 132) is available for use by all the manually and automatically sized components. You can also see the current actual values of the SGA components in the Oracle Enterprise Manager memory configuration page. This reduction in turn limits the ability of the system to adapt to workload changes. Therefore, this practice is not recommended except in exceptional cases. The default automatic management behavior maximizes both system performance and the use of available resources. It usually converges on this value by increasing in small increments over time. Therefore, the tuning algorithm only tries to increase the shared pool in conservative increments, starting from a conservative size and stabilizing the shared pool at a size that produces the optimal performance benefit. Consider the following combination of parameters: Therefore the rules governing resize for all component parameters are the same as in earlier releases. However, when automatic shared memory management is enabled, the manually specified sizes of automatically sized components serve as a lower bound for the size of the components. You can modify this limit dynamically by changing the values of the corresponding parameters. The new setting only limits the automatic tuning algorithm to that reduced minimum size in the future. For example, consider the following configuration: However, rather than setting a minimum size, the value of the parameter specifies the precise size of the corresponding component. When you increase the size of a manually sized component, extra memory is taken away from one or more automatically sized components.