create oracle 9i database manually

create oracle 9i database manually

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).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.This ensures that the system will not waste time using replacement characters to facilitate conversions. You can also specify an alternate character set. 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.http://bmdmi-media.org/editoruploads/canon-selphy-cp730-service-manual.xml

• create database in oracle 9i manually, create oracle 9i database manually, create oracle 9i database manually download, create oracle 9i database manually file, create oracle 9i database manually list, create oracle 9i database manually software.

You can chose not to use the Database Configuration Assistant, 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.Otherwise, you can migrate or upgrade your existing Oracle database managed by a previous version or release of Oracle and use it with the new version of the Oracle software. Database migration and upgrade are not discussed in this book. The Oracle9i Database Migration manual contains information about migrating an existing database. Online help is available to assist you in its use.You can configure database options so as to add options that have not been previously configured. Additionally, the Database Configuration Assistant enables you to create and manage database templates. You can create a template of a database definition and later modify that template, or you can modify templates supplied by Oracle. You can also create a template of an existing database and clone it.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. When you select a template, you can choose either to include datafiles or not. If you select a template with datafiles, you will be able to save the database creation information as a template or script. You can run the script later to create a new database. Rather, it is intended to provide an introduction to its use. Wizards will guide you in making choices for defining the database that you want to create.http://www.apnikheti.com/userfiles/canon-selphy-cp730-manual.xml

Response time, accuracy, and availability are key issues.Availability, speed, concurrence, and recoverability are key issues.The following types of databases are created accordingly:If you select a template without datafiles, database creation will take longer since all scripts must be run to create the schema. In effect, this template copies a prebuilt seed, or starter, database. In the seed database, Oracle automatically includes features that result in a highly effective and easier to manage database. Also, all log files and control files are automatically created for the database. You can change only the following:You can also use custom scripts for additional modification. You provide a global database name, specify database options to include, determine mode (dedicated server of shared server), and ultimately you can specify initialization parameter.You select one of the following options:You do not specify specific initialization parameter values; instead, you specify the maximum number of concurrent users, the percentage of physical memory reserved for Oracle, and a database type (OLTP, Multipurpose or Data Warehousing). Oracle uses this information to create an efficient and effective database for your environment. It can be used by very experienced database administrators who have specific tuning needs. Other areas that you will be allowed to customize include:For more information on the creation parameters, refer to the summary dialog that appears when you start the database creation process. This template will be automatically added to the list of available database creation templates. The scripts are generated from the database parameters you specified in the previous pages. You can use the scripts as a checklist, or to create the database later without using the Database Creation Assistant. Some of the listed options might already be installed depending upon how you defined the database.

Those options that are already installed are noted as such (grayed out).When you do so, you delete the database instance and its control file(s), redo log files, and data files. The initialization parameter file is not deleted. These saved definitions can then be used to create new databases in the future, without having to completely redefine them. Oracle saves templates in XML files.They can be copied from one machine to another. You can add or change any template settings such as initialization parameters, storage parameters, or use custom scripts.This includes tablespaces and storage. You can use an existing database that is either local or remote.You can only use an existing database that is local. 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.When you execute a CREATE DATABASE statement, Oracle performs (at least) the following operations. Other operations are performed depending upon the clauses that you specify in the CREATE DATABASE statement or initialization parameters that you have set.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. MAXLOGHISTORY, MAXLOGFILES, and MAXLOGMEMBERS define limits for the redo log.This is customary during database creation and an ALTER DATABASE statement can be used later to switch to ARCHIVELOG mode.If omitted (as it is in this case), the default database time zone is the operating system time zone. The database time zone can be changed for a session with an ALTER SESSION statement.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 the Oracle9i Backup and Recovery Concepts. There are clauses, some shown in the above CREATE DATABASE statement, which are discussed in this section. Additionally, you can choose to use the Oracle Managed Files feature, which automatically creates and manages the underlying operating system files of your database.This requires the use of a different set of initialization parameters and, if creating the database for the first time, the UNDO TABLESPACE clause of the CREATE DATABASE statement. You also must include the following initialization parameter:In this mode rollback information, referred to as undo, is stored in an undo tablespace rather than rollback segments and is managed by Oracle.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.You are not allowed to change a default temporary tablespace to a permanent tablespace, nor can you take a default temporary tablespace offline.Also, all databases that share information must use the same time zone data file. 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:In addition, a CREATE DATABASE SQL statement issued manually will require you to specify 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 for the current instance with the ALTER SYSTEM statement. Later, you can choose to permanently add or change parameter values by updating them manually in the traditional text initialization parameter file. Or, you can create a binary server parameter file that enables you to use the ALTER SYSTEM statement to make initialization parameter changes that 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, 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 4 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.It addresses the monitoring and tuning of the components of 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 will normally select 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. If your site is licensed by concurrent usage, you can track and limit the number of sessions concurrently connected to an instance. If your site is licensed by named users, you can limit the number of named users created in a database. To use this facility, you need to know which type of licensing agreement your site has and what the maximum number of sessions or named users is. Your site might use either type of licensing (session licensing or named user licensing), but not both.Once this limit is reached, additional users can continue to connect (up to the maximum limit), but Oracle sends a warning to each connecting user.However, the sum of the instances' limits must not exceed the site's session license.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. It also provides a basis for self tuning by the Oracle database server. It is a binary file that cannot be browsed or edited using a text editor. Oracle provides other interfaces for viewing and modifying parameter settings.Doing so will corrupt the file. You will not be able to start you instance, and if the instance is running, it could crash. The STARTUP command with no PFILE clause, reads the server parameter file from an operating system specific location. If you choose to use the traditional text initialization parameter file, you must specify the PFILE clause when issuing the STARTUP command. Explicit instructions for starting an instance using a server parameter file are contained in Starting Up a Database.Instructions for doing this, and other actions unique to using a server parameter file for Oracle Real Application Cluster instances, are discussed in: This statement reads the initialization parameter file to create a server parameter file. The database does not have to be started to issue a CREATE SPFILE statement. It must be created prior to its use in the STARTUP command. The CREATE SPFILE statement is used to create a server parameter file. You must have the SYSDBA or the SYSOPER system privilege to execute this statement. If a server parameter file of the same name already exists on the server, it is overwritten with the new information. This will ease administration of your database. For example, the STARTUP command assumes this default location to read the parameter file.All other comments are ignored.

However, if the instance has been started using a server parameter file, an error is raised if you attempt to recreate the same server parameter file that is currently being used by the instance.When the default server parameter file is used by the server (that is, you issue a STARTUP command and do not specify a PFILE ), the value of SPFILE is internally set by the server.You use the SPFILE parameter to specify a server parameter file located in a nondefault location. Do not use an IFILE initialization parameter within a traditional initialization parameter file to point to a server parameter file; instead, use the SPFILE parameter.When the ALTER SYSTEM statement is used to alter a parameter setting in a traditional initialization parameter file, the change affects only the current instance, since there is no mechanism for automatically updating initialization parameters on disk. They must be manually updated in order to be passed to a future instance. Using a server parameter file overcomes this limitation.Additionally, the SCOPE clause specifies the scope of a change as described in the following table:The effect is as follows:This is the only SCOPE specification allowed for static parameters.The effect is as follows:The effect is as follows:When specified, the change is effective only for future sessions.When you specify SCOPE as SPFILE or BOTH, the comment is written to the server parameter file.It also specifies a comment, and explicitly states that the change is to be made only in memory (that is, it is not persistent across instance shutdown and startup).The case could be that either the parameter is being changed to a new value or a new archive destination is being added. You must specify the complete list of values each time the parameter is updated and the new list completely replaces the old list.Reasons for doing this include:You must have the SYSDBA or the SYSOPER system privilege to execute this statement.

The exported file is created on the database server machine. It contains any comments associated with the parameter in the same line as the parameter setting.At this point, you have the following options:It is easier to distinguish list parameter values in this view because each list parameter value appears as a row. The view returns NULL values if a server parameter file is not being used by the instance. When a database is created, a name is associated with it and stored in its control files. If you provide the database keyword, either in the CREATE DATABASE statement or when prompted by Database Configuration Assistant, then that value becomes the name for that database. This restriction exists only for Oracle8 i and later versions. Any Oracle7 instances running simultaneously with an Oracle9 i instance are not subject to this restriction. If you specified non-OFA directories during installation, then your directory paths will differ. UNC is a PC format for specifying locations of resources on a local area network. UNC uses the following format: If you set it to a UNC specification, then Oracle9 i database does not start and you receive the following errors: Control files required the additional backslashes for Oracle8 release 8.0.4, but redo log files and datafiles did not. If this is not done, then the database on the member server will randomly get ACCESS DENIED errors when accessing Active Directory. If the database is running as a local user, then trying to register the database with Active Directory using Database Configuration Assistant fails, because this user cannot log on to Active Directory. If the database service is running as a LocalSystem, then manually add the computer name. If the database service is running as a domain user, then manually add the username. If this is not done, then you may not be able to use Active Directory to grant an enterprise role. It can also be used during installation to create a database.

If Database Configuration Assistant is run from a user account that is not part of the Administrator's group, then it displays a warning stating that you do not have administrative privileges to create the database. For more information, see Oracle9i Database Installation Guide for Windows. Custom lets you specify initialization parameter values and other options including: When you finish, click Next. For the OLTP sample schema, enter: For the OLTP sample schema, enter: As part of its database software files, Oracle provides a sample database creation script and a sample initialization parameter file, both of which can be edited to suit your needs. Alternatively, if you have an existing script you can use it as-is to create a database manually or edit it using the sample database creation script as a guide. Each step is explained in detail in the following subsections. In this example, the existing database is the starter database with a SID of orcl located in directory C:\oracle\oradata\orcl. You will copy orcl to a new database with a database name and SID of prod located in directory C:\oracle\oradata\prod. You will then delete starter database orcl. You will use Export utility for this task. Although you can start Export utility in either parameter mode or interactive mode, Oracle Corporation recommends parameter mode. Interactive mode provides less functionality than parameter mode and exists for backward compatibility only. For example: In the following example, you delete the database files of starter database orcl. However, you can use the sample initialization parameter file initsmpl.ora provided in You can use up to eight characters for a database name. The name is not required to match the SID of the database service. Ensure that you specify the complete path and filename, including drive letter. The value of 100 is used for this example. This service is the Oracle9 i database process, oracle.exe, installed in the form of a Windows NT service.

After it has been created, the service starts automatically.You can check if the service is started in the Services window of the Control Panel. A script containing this statement can be used anytime you create a database. Oracle Managed Files eliminates the requirement to directly manage operating system files comprising an Oracle database, because you specify operations in terms of database objects rather than filenames. For more information on using Oracle Managed Files see Oracle9i Database Administrator's Guide. In this example, the service name is OracleServicePROD, and its status column must display Started. If not, then select the service name and choose Start. If OracleServicePROD is missing from the list, then enter: Interactive mode exists solely for backward compatibility. For example: Datafiles are not required to be identical. Only tablespace names are important. Back up your database now to prevent loss of data. Wait until the Control Panel indicates service OracleServicePROD has stopped. If you do not do this, then the backup may be useless because it was taken while data was being written to datafiles. This can result in write errors and decreased performance. You are required to use ORADIM utility only if you are manually creating, deleting, or modifying databases. Database Configuration Assistant is an easier tool to use for this purpose. Note that each command is preceded by a dash ( - ). To get a list of ORADIM utility parameters, enter: You must check this file to verify success of an operation. Double-click Administrative Tools first, then double-click Services. This is a mandatory parameter. You must specify either this parameter or parameter -SRVC. You must specify either this parameter or parameter -SID. This is the password for the user logged in with SYSDBA privileges. Option -INTPWD is not required. If you do not specify it, then operating system authentication is used, and no password is required. The default is 5. Default is manual.

Ensure that you specify the complete path name of this file, including drive letter. This is a mandatory parameter. This is a mandatory parameter. One or both values can be specified. If it is not specified, then the registry is checked for the current setting. Ensure that you specify the complete path name of this file, including drive letter. This is a mandatory parameter. This is a mandatory parameter. One or both values can be specified. If it is not specified, then the registry is checked for the current setting. This is an optional parameter. If you do not specify how to stop an instance, then normal is the default mode. To use ORADIM utility to modify an instance, enter: This is a mandatory parameter. This is a mandatory parameter. This is an optional parameter. Default is manual. Ensure that you specify the complete path name of this file, including drive letter. This is an optional parameter. If you do not specify how to stop an instance, then normal is the default mode. One or both values can be specified. If it is not specified, then the registry is checked for the current setting. This is a mandatory parameter. You must specify either this parameter or parameter -SRVC. You must specify either this parameter or parameter -SID. 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.