7

creating oracle 10g database manually in linux

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:creating oracle 10g database manually in linux.pdf
Size: 4073 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 13 May 2019, 16:34 PM
Rating: 4.6/5 from 649 votes.

Status: AVAILABLE

Last checked: 1 Minutes ago!

In order to read or download creating oracle 10g database manually in linux ebook, you need to create a FREE account.

Download Now!

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

creating oracle 10g database manually in linuxIt 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.obuvmusilova.cz/UserFiles/eclipse-manual-transmission-problems.xml

Tags:
• creating oracle 10g database manually in linux, creating oracle 10g database manually in linux download, creating oracle 10g database manually in linux windows 10, creating oracle 10g database manually in linux version, creating oracle 10g database manually in linux pdf.

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://www.rabco.cl/userfiles/eclipse-manual-transmission-for-sale.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. 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. For example, on Windows, use the following command to configure the database service to start the instance upon computer restart: Legal Notices. You need only create a database once, regardless of how many datafiles it has or how many instances access it. Creating a database can also erase information in an existing database and create a new database with the same name and physical structure. The following are some recommended actions: For example, placing redo log files on separate disks or striping; placing datafiles to reduce contention; and controlling density of data (number of rows to a data block). This feature eases their administration. Become familiar with the concept and operation of a server parameter file. A server parameter file allows you to 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. Additionally, you can specify up to four non-standard 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 up 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.Additionally, the Oracle Universal Installer will guide you through your installation and provide help in setting up environment variables, directory structure, and authorizations. A few of these actions are creating users and temporary tablespaces, building views of the data dictionary tables, and installing Oracle built-in packages. This is why the database creation process involves executing prepared scripts. But, you do not necessarily have to prepare this script yourself. You can chose not to use DBCA, or you can launch it as a standalone tool at any time in the future to create a database.However, consider editing your existing script to take advantage of new Oracle features. Oracle provides a sample database creation script and a sample initialization parameter file with the database software files it distributes, both of which can be edited to suit your needs.You can upgrade your existing Oracle database and use it with the new release of the Oracle software. Database upgrades are not discussed in this book. The Oracle9i Database Migration manual contains information about upgrading an existing Oracle database. DBCA is launched automatically by the Oracle Universal Installer, but it can be invoked standalone from the Windows operating system start menu (under Configuration Assistants) or by entering the following on the UNIX command line: This mode presents a wizard like GUI interface and provides complete DBCA functionality. Online help is provided. For example, it is used by the Oracle Universal Installer, the Enterprise Manager Configuration Assistant, and the Oracle Internet Directory Configuration Assistant. In this mode, only a progress bar is displayed, and it is used when creating databases and templates. There is no other user interaction. Informational, error, and warning message are written to a log file. You specify the template of your choice, for customization or for the creation of a database. It contains the following topics: It allows you to provide varying levels of detail. You can provide a minimum of input and allow Oracle to make decisions for you, eliminating the need to spend time deciding how best to set parameters or structure the database. Optionally, it allows you to be very specific about parameter settings and file allocations. A template is a description of a database.If you or others have created templates, those will be displayed also. You select the appropriate template for the database that you want to create.This determines whether you use a seed template (includes datafiles), or a non-seed template (does not include datafiles), to create your database. Some of the listed options might already be included depending upon the database template that you selected. Those options that are already installed are noted as such (grayed out). These are features that Oracle recommends you always install, but you have the option of excluding them. These include: You specify mode (dedicated server of shared server), set initialization parameters, and specify datafile locations. Oracle can determine specific values for you based upon your description of the database you are trying to create. For example, Oracle can choose appropriate settings for SGA memory sizing parameters depending upon whether you select a typical or custom database. This provides you the opportunity to add options and features that you did not include when you created the database.When you do so, you delete the database instance and its control file(s), redo log files, and datafiles. Any server parameter file (SPFILE) or initialization parameter file used by the database is also deleted. Templates are used in DBCA to create new databases and make clones of existing databases. The information in templates includes database options, initialization parameters, and storage attributes (for datafiles, tablespaces, control files and redo logs). But they are more powerful than scripts, because you have the option of cloning a database. This saves time in database creation, because copying an already created seed database's files to the correct locations takes less time than creating them as new. You can quickly change database options from the template settings. They can be copied from one machine to another. When you select a seed template, database creation is faster because the physical files and schema of the database have already been created. Your database starts as a copy of the seed database, rather than having to be built. It contains the characteristics of the database to be created. Seed templates are more flexible than their seed counterparts because all datafiles and redo logs are created to your specification (not copied), and names, sizes, and other attributes can be changed as required. Response time, accuracy, and availability are key issues. Availability, speed, concurrence, and recoverability are key issues. It combines features of both the DSS and OLTP database templates. You can add or change any template settings such as initialization parameters, storage parameters, or use custom scripts. User defined schema and their data will not be part of the created template. The source database can be either local or remote. Databases created using such a template are identical to the source database. User defined schema and their data will be part of the created template. The source database must be local. OFA is recommended if the machine on which you plan to create the database using the template has a different directory structure. Non-OFA can be used if the target machine has a similar directory structure. It outputs all messages including information, errors, and warnings into a log file. These steps should be followed in the order presented. You will previously have created your environment for creating your Oracle database, including most operating system dependent environmental variables, as part of the Oracle software installation process. These steps contain many cross references to other parts of this book to allow you to learn about and understand these parameters and structures. 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: One way of getting started on your initialization parameter file is to edit a copy of the sample initialization parameter file that Oracle provides on the distribution media, or the sample presented in this book. That way, when you start your database, it is not necessary to specify the PFILE parameter because Oracle automatically looks in the default location for the initialization parameter file. Typically, you do this only during database creation or while performing maintenance on the database. Use the STARTUP command with the NOMOUNT option. In this example, because the initialization parameter file is stored in the default location, you are not required to specify the PFILE clause: Only the SGA is created and background processes are started in preparation for the creation of a new database. The following statement creates database mynewdb: These two clauses that specify the passwords for SYS and SYSTEM are not mandatory in this release of Oracle9 i. 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. Some of these limits are also subject to superseding limits of the operating system and can be affected by them. For example, if you set MAXDATAFILES, Oracle 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. If the file already exists, it is overwritten. This is customary during database creation and an ALTER DATABASE statement can be used later to switch to ARCHIVELOG mode.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 Oracle9i 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's data dictionary. The instance is shut down, then restarted using the server parameter file (in the default location). For information on backing up a database, see Oracle9i Backup and Recovery Concepts. The actual operations performed are in large part determined by the clauses that you specify in the CREATE DATABASE statement or initialization parameters that you have set. To protect your database, you should change these passwords using the ALTER USER statement after database creation. The default passwords are commonly known, and if you neglect to change them later, you leave yourself vulnerable to attack by malicious users. These options, and their associated CREATE DATABASE clauses, are discussed briefly in the following sections, and in more detail in later sections of this book: This requires the use of a different set of initialization parameters, and optionally, the inclusion of the UNDO TABLESPACE clause in your CREATE DATABASE statement. If you want to create and name a specific tablespace for the undo tablespace, you can include the UNDO TABLESPACE clause at database creation time.This tablespace is used as the default temporary tablespace for users who are not otherwise assigned a temporary tablespace. But, if no temporary tablespace is specified, they default to using the SYSTEM tablespace. It is not good practice to store temporary data in the SYSTEM tablespace. To avoid this problem, and to avoid the need to assign every user a default temporary tablespace at CREATE USER time, you can use the DEFAULT TEMPORARY TABLESPACE clause of CREATE DATABASE. You do this by creating a new temporary tablespace ( CREATE TEMPORARY TABLESPACE ), 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 temporary default tablespace. When using a locally managed SYSTEM tablespace, the new default temporary tablespace must also be locally managed. You are not allowed to change a default temporary tablespace to a permanent tablespace, nor can you take a default temporary tablespace offline. 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, the default is to create a dictionary-managed SYSTEM tablespace. A locally managed SYSTEM tablespace is created AUTOALLOCATE by default, meaning that it is system managed with extent sizes determined and controlled by Oracle. 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. Attempting to create a rollback segment in a dictionary-managed tablespace will fail if the SYSTEM tablespace is locally managed. You can include the UNDO TABLESPACE clause in the CREATE DATABASE statement to create a specific undo tablespace, or if you do not include the clause, Oracle creates a locally managed undo tablespace for you using the default name and in a default location. These restrictions are: They cannot be altered to READ WRITE. However, there is no procedure for backward migration. The database time zone can be changed for a session with an ALTER SESSION statement. The following information is included for each zone (note that abbreviations are only used in conjunction with the zone names): It contains the most commonly used time zones and is smaller, thus enabling better database performance. Also, all databases that share information must use the same time zone datafile. Specifying NOLOGGING can speed up operations that can be easily recovered outside of the database recovery mechanisms, but it causes problems for media recovery and for a standby database. Oracle never generates redo records for temporary tablespaces and temporary segments, so forced logging has no affect for these. If you do not specify this clause, the database is not placed into FORCE LOGGING mode. This statement can potentially wait 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 mode 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 state. However, if you re-create the control file, the database not restarted in the FORCE LOGGING mode unless you specify the FORCE LOGGING clause in the CREATE CONTROL FILE statement. If there is no standby database active, but the primary reason for specifying FORCE LOGGING is to ensure complete media recovery, then consider the following: This is because media recovery is not possible in this mode, thus there is performance degradation with little benefit. After correcting the error that caused the failure of the database creation, try running the script again. You may want to perform other actions, some of which are discussed in this section. Some of these users are: A CREATE DATABASE statement issued manually also lets you supply passwords for these two users. Some Oracle documents and books use these sample schemas for presenting examples. There is an ongoing effort for most Oracle books to convert to the use of Sample Schemas based examples. The Order Entry (OE) schema has links into HR schema The OE schema has links into the HR schema and PM schema. This schema also has synonyms defined on HR objects to make access transparent to users. It consists of one big range partitioned fact table sales and five dimension tables: times, promotions, channels, products and customers. The additional countries table linked to customers shows a simple snowflake. The schemas and installation instructions are described in detail in Oracle9i Sample Schemas. 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, Oracle 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 traditional text initialization parameter file, your changes are only for the current instance. To make them permanent, you must update them manually in the initialization parameter file, otherwise they will be lost over the next shutdown and startup of the database. 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, pay special attention to this initialization parameter before database creation. If you inadvertently specify a file that you did not intend and execute the CREATE DATABASE statement, the previous contents of that file will be overwritten. Oracle can support up to four additional non-standard block sizes. In many cases, this is the only block size that you need to specify. If not specified, the default data block size is operating system specific, and is generally adequate. If a database's block size is different from the operating system block size, make the database block size a multiple of the operating system's block size. Such cases include the following scenarios: 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. These non-standard block sizes can have any power-of-two value between 2K and 32K: specifically, 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 datawarehouse 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. Granule size is determined by total SGA size. Generally speaking, on most platforms, if the total SGA size is equal to or less than 128 MB, then granule size is 4 MB. Otherwise, granule size is 16 MB. For example, on 32-bit Windows NT, the granule size is 8 MB for SGAs larger than 128 MB. Consult your operating system specific documentation for more details. The same granule size is used for all dynamic components in the SGA. You use them to specify the sizes of caches for the various block sizes used by the database. These initialization parameters are all dynamic. Larger cache sizes generally reduce the number of disk reads and writes. However, a large cache may take up too much memory and induce memory paging or swapping. For example: The size of the cache of standard block size buffers will be 12M. Additionally, 2K and 8K caches will be configured with sizes of 8M and 4M respectively. The value of this parameter must be 6 or greater (5 for the background processes plus 1 for each user process). For example, if you plan to have 50 concurrent users, set this parameter to at least 55. Such information consists of records of the actions of transactions, primarily before they are committed. Oracle refers to these records collectively as undo. Oracle allows you to store undo in an undo tablespace or in rollback segments. For backward compatibility, the default is MANUAL. This is the undo tablespace that Oracle normally selects whenever you start up the database. This is not recommended in normal circumstances, and an alert message is written to the alert file to warn that the system is running without an undo tablespace. An undo tablespace is easier to administer and enables you to explicitly set an undo retention time. If no rollback segments are specified, the system rollback segment is used. You can set a limit on the number of users created in the database. Once this limit is reached, you cannot create more users. Therefore, so that named user licensing can help you ensure compliance with your Oracle license agreement, do not allow multiple users to log in using the same user name. Starting with Oracle9 i, you can choose to maintain initialization parameters in a binary server parameter file. The following topics are contained in this section. It is, by design, a server-side initialization parameter file. Initialization parameters stored in a server parameter file are persistent, in that any changes made to the parameters while an instance is running can persist across instance shutdown and startup. This eliminates the need to manually update initialization parameters to make changes effected by ALTER SYSTEM statements persistent.