create oracle database using asm manually via scripts
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:create oracle database using asm manually via scripts.pdf
Size: 1869 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 30 May 2019, 19:27 PM
Rating: 4.6/5 from 719 votes.
Status: AVAILABLE
Last checked: 3 Minutes ago!
In order to read or download create oracle database using asm manually via scripts 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
create oracle database using asm manually via scriptsYou can go through all parameters in Oracle Docs to better customize your Database. Though we haven’t created database yet, here we’re checking if database starts up on created pfile. Copyright (c) 1982, 2016, Oracle. All rights reserved. Connected to an idle instance. ORACLE instance started. Total System Global Area 268435456 bytes. Fixed Size 8619496 bytes. Variable Size 201329176 bytes. Database Buffers 50331648 bytes. Redo Buffers 8155136 bytes Database created. And grants public access to those synonym. This script will take a bit long to run. Connected. Do not forget to switch back to SYS user. Connected. File created.Tablespace created. Which gets created while running root.sh at the installation time of RDBMS Software. However, if you create your database manually using the CREATE DATABASE statement, then Oracle ASM enables you to create a database and all of its underlying files with a minimum of input. This example creates a database with the following Oracle ASM files: The tablespace is locally managed with automatic segment-space management. Legal Notices. 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.http://en.meress.sk/userfiles/ecler-nuo-5-manual-pdf.xml
- Tags:
- create oracle database using asm manually via scripts, create oracle database using asm manually via scripts, create oracle database using asm manually via scripts free, create oracle database using asm manually via scripts online, create oracle database using asm manually via scripts download, create oracle database using asm manually via scripts list.
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. 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.http://www.launchtwo.com.au/userfiles/ecler-pam-1000-service-manual.xml You can change this parameter to AUTO, if desired, in Step 14. Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production. 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. This feature is available from 11.2.0.3 ASMCA. You can find lot of articles helping you to do this. In a production environment this would be provided by storage admin. For this test setup I am utilizing VMware ability to add disks. I am adding three disks of size 4GB each. The below steps should be repeated for all the three disks. We also need oinstall and dba group to be created and assigned to oracle user. Login as root and perform following. Please note that from Linux 6 onwards raw devices are not supported and you should use ASMLib for configuring ASM instance.Later validate the same. Lets first install the GI binaries.The next step is to create ASM instance and then the database instance. Before starting the creation of ASM instance we need to ensure that CSSD service is up and running.Name Type Target State HostIf you are using NFS or NAS then you should specify your disks in this parameter. Multiple disk strings can be specified by comma separated values. ASM is not running. ASM is running on localhost. ASM listener was not found. PRCA-1032: ASM listener LISTENER does not exist. Name Type Target State HostAll rights reserved. Connected to. Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - Production. With the Automatic Storage Management optionIts time to create the disk groups. Diskgroup created.For ORA11G database instance I have created initORA11G.ora file under dbs directory of Oracle Database Home. You can further create spfile, enable archive logging or add a listener service as required. Thanks for sharing this Notify me of new posts via email. To find out more, including how to control cookies, see here. These steps should be followed in the order presented. Out of which 4 are system defined tablespace and 5th one, ie USERS tablespace is user defined. For this exercise, we will have one datafile per tablespace. You may have to create more redo logs depending on the database activity Later we will see how to create a spfile from pfile. Please make sure to execute them in the order given The name of the parameter file should be initmydb.ora Now create additional tablespaces Join more than 5000 subscribers who stays ahead on technology. Area of Interests: Database High Availability, Security, Goldengate. Loves to travel, Reading We will try our best for you:-) Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo. Showing recent items. But for some reason, if you want to create manually, then follow below steps: In this article, we will create a database in a 2 node rac.Learn how your comment data is processed. And, with Oracle 11g it only takes a few minutes to do:) Instance created.Copyright (c) 1982, 2007, Oracle. All rights reserved. Connected to an idle instance.File created.ORACLE instance started. Total System Global Area 150667264 bytes. Fixed Size 1331740 bytes. Variable Size 92278244 bytes. Database Buffers 50331648 bytes. Redo Buffers 6725632 bytesDatabase created.Tablespace created. Tablespace created. Database altered. Database altered.Database closed. Database dismounted. ORACLE instance shut down. ORACLE instance started. Total System Global Area 150667264 bytes. Fixed Size 1331740 bytes. Variable Size 92278244 bytes. Database Buffers 50331648 bytes. Redo Buffers 6725632 bytes. Database mounted. Database altered. Database altered.I'm new to DBA, I've one question, in 11i, is the extent management locally managed or dictionary managed by default. It's better, if we mention the locally managed for the non-system tablespaces, it will reduce the contention in the system tablespaces. When you do not I am not a DBA or OCP, but working as an Oracle developer. Database creation was a big issue for me, but now it will not be an issue any longer. The ASM functionality is an extention of the Oracle Managed Files (OMF) functionality that also includes striping and mirroring to provide balanced and secure storage. The new ASM functionality can be used in combination with existing raw and cooked file systems, along with OMF and manually managed files. This is not a full database instance, just the memory structures and as such is very small and lightweight. The physical disks are known as ASM disks, while the files that reside on the disks are know as ASM files. The locations and names for the files are controlled by ASM, but user-friendly aliases and directory structures can be defined for ease of reference. Default templates are provided for each file type stored by ASM, but additional templates can be defined as needed. For two-way mirroring you would expect a disk group to contain two failure groups so individual files are written to two locations. The valid values range from 1 to 11, with 1 being the default.This value is also used as the default when the POWER Altering the default value may improve the speedChanging the parameter to a value which prevents the discovery of already mounted disksThe default value is NULL allowing all suitable disks to be considered. Total System Global Area 125829120 bytes. Fixed Size 1301456 bytes. Variable Size 124527664 bytes. Database Buffers 0 bytes. Redo Buffers 0 bytesTo shutdown the ASM instance issue the following command. The options for the STARTUP command are: It doesn't wait for sessions to exit. There are a few basic points to consider when planning to use ASM:Typically, the FRA disk group will be twice the size of the DATA disk group, since it must hold all backups. This statement allows you to specify the level of redundancy: If you have hardware RAID it should be used in preference to ASM redundancy, so this will be the standard option for most installations. The FORCE option can be used to move a disk from another disk group into this one. The statement can be used to resize individual disks, all disks in a failure group or all disks in the disk group. If the SIZE clause is omitted the disks are resized to the size of the disk returned by the OS. It will not revert drops that have completed, or disk drops associated with the dropping of a disk group. Rebalancing is only needed when the speed of the automatic rebalancing is not appropriate. Manual mounting and dismounting can be accomplished using the ALTER DISKGROUP statement as seen below. The following example show how templates can be created, altered and dropped. This attribute cannot be set for external redundancy. This attribute cannot be set for external redundancy. This attribute cannot be set for external redundancy. The following examples show how ASM directories can be created, modified and deleted. For these circumstances it is necessary to manually delete the files, as shown below. Some forms are used during creation and some for referencing ASM files. The forms for file creation are incomplete, relying on ASM to create the fully qualified name, which can be retrieved from the supporting views. The forms of the ASM filenames are summarised below. ASM eliminates the Using ASM, the The SQL statements used for creating database structures, such as ASM was designed to preserve all existing database functionality. However, even in existing databases, This means that databases can have a To turn on ASM you must create a separate ASM instance before you An ASM instance does not require that ASM eliminates the need for the DBA to ASM does this by enabling ASM Using ASM, the management of thousands of Oracle However, even in existing Oracle 10g This means that databases can have a Oracle can handle cache much more Oracle has a This means that a Because redo writes address an arbitrary The use of ASM eliminates need for direct DBCA eases the configuring and creation of your database, while EM Oracle's Enterprise Manager (EM) product or the Database In order to use the ASM in a shared Each ASM instance has either an SPFILE or To use ASM in the RAC Thus there is no separate Oracle Home You can configure the Automated Storage Management (ASM) in the ASM is great for Oracle because it eliminates the management Using ASM, the DBA Unneeded data files are automatically deleted with ASM, rather ASM operates on disk groups which is a ASM rebalances the spread of We mentioned that any single ASM file is self-contained in a However, an ASM disk group can contain You can specify a ASM divides the datafiles into 1 MB extents and spreads the For files, such as log files, that require low latency, ASM Most installations will probably have tw o or more disk groups. Note: In any installation, non-ASM managed operating system Configuration of ASM high redundancy provides a greater degree In external redundancy, the underlying disks in the disk group All legitimate Oracle experts If you find an error. In this blog, we review the Oracle Database 12 c Release 2 (12.2.0.1) RAC installation process. Installing the Oracle RAC database software is the next logical step after installing Oracle Grid Infrastructure, and creating an Oracle 12.2 release database is your last step in the process. Installing the Oracle RAC software is quite similar to performing a single-instance Oracle Database software installation. Internally, the Oracle Universal Installer (OUI) installs the binaries on a single node, and it uses the underlying file-transfer mechanisms to propagate the files to other nodes, relinking them with the respective operating system binaries. If you’ve previously worked with Oracle 11 g Release 2, you might have noticed that Oracle has started delivering patch sets in the form of full-blown software instead of mere updates. In other words, they’re full releases. This facilitates out-of-place database upgrades and also avoids you having to install Oracle base release binaries and then upgrade to the latest patch set. If you’re planning to upgrade your databases that are running on previous releases, you’d be installing Oracle 12 c RAC binaries into a different Oracle home. Installing Oracle 12 c RAC binaries into pre-existing Oracle homes is not recommended, although it’s possible to do so. Before you perform the Oracle 12 c Release 1 RAC installation, make sure you have an operational Oracle Grid Infrastructure stack with the same or higher version. With RAC One Node, a single-instance RAC database runs on a single node in a cluster at any point in time. Oracle RAC One Node Oracle RAC One Node is a single-instance Oracle RAC database running on a single node preconfigured with Oracle Grid Infrastructure. By utilizing the clustering technology, the Oracle RAC One Node database allows on-demand migration of database instances to other servers, conversion to Oracle RAC without any downtime, and rolling patches for single-instance databases. Oracle RAC One Node also provides high availability for single-instance databases. Oracle provides the OMOTION utility to migrate Oracle RAC One Node database instances to other servers in the cluster online without any downtime. Oracle internally uses transaction shutdown to migrate single instances online without impacting the current transactions, but Oracle ensures that two servers do not provide the same services at the same time. This is really a great feature because it allows large organizations to consolidate smaller single-instance databases in one place and at the same time allows them to standardize the deployment of Oracle databases within the organization with the option to increase the scalability of single-instance databases by upgrading them to Oracle RAC databases without any downtime. You can run the Cluster Verification Utility in preinstallation mode to verify the basic node reachability and integrity of Oracle Clusterware. This also checks the basic kernel parameters and required operating system libraries. At the end, the utility checks the status of the Oracle Clusterware daemons and the network infrastructure issues.Verifying Physical Memory.PASSED. Verifying Group Membership: oinstall(Primary).PASSED. CVU operation performed. Verifying Group Membership: dba.PASSED. Verifying Run Level.PASSED. Date. CVU home. User:If you are currently using raw or block devices as your storage, you should plan on migrating to one of the supported shared storage options, such as ASM, CFS, or NFS, since Oracle 12 c no longer supports raw devices, even during upgrades. There’s no need to install and configure the ASM using Oracle database binaries before the database install because ASM is installed and configured with Oracle Grid Infrastructure. Because we’ll be using Oracle ASM to build this Oracle RAC database, you’ll need to create Oracle ASM disk groups to store the Oracle data and backups. This can be accomplished using the ASMCA utility running out of the Grid Infrastructure home. Before the installation, you can adjust the environment settings for your favorite shell and start the Installer with the tracing option turned on (as discussed in detail in the previous article ). In the following sections, we first describe the installation of the Oracle RAC software. Following this, we show how to use the Oracle Database Configuration Assistant (DBCA) to create an Oracle RAC database. Installing Oracle Real Application Clusters As with the Oracle Grid Infrastructure installation, you use the Oracle Universal Installer (OUI) to install the Oracle RAC binaries. OUI will install the Oracle RAC binaries on the first node and then copy them onto the other servers in the cluster. Verifying User Existence: oracle.PASSED. Verifying Group Existence: dba.PASSED. Verifying CRS Integrity.PASSED. Verifying ASM Integrity. Verifying Node Connectivity.PASSED. CVU operation performed: Date: stage -pre dbcfg. CVU home: Apr 25, 2017 6:08:53 PM. You can install the binaries from the installation media (CD-ROM or DVD) or from the staging area if you’ve extracted the software to disk. Uncheck the box labeled “I wish to receive security updates via My Oracle Support” on this screen. Click Next. The OUI will present the Select Installation Option screen, shown in Figure 2, where you specify the required installation and configuration option for the current install. This screen provides the following three installation options: FIGURE 2. The Select Installation Option screen Create and configure a database This option is the default installation option, which installs Oracle RAC binaries and creates a database based on a preconfigured template. This option is useful especially for beginners because Oracle provides separate templates for different types of workloads, such as for OLTP and decision support systems. Install database software only This option installs only the Oracle RAC software on all the servers in the cluster. Database administrators mostly use this option, which allows them more flexibility while creating the database using the Database Configuration Assistant once Oracle RAC binaries are installed. Upgrade an existing database This option upgrades the existing Oracle RAC database in the cluster. Because we’re going to create a database later with the Oracle Database Configuration Assistant (DBCA), select the second option (Install database software only) and click Next. In the Select Database Installation Option screen, shown in Figure 3, you can choose from among the following three options: FIGURE 3. The Select Database Installation Option screen Single instance database installation This option allows you to install single-instance database software on the local node only. Oracle Real Application Clusters database installation This option allows you to select and install Oracle Real Application Clusters binaries on the selected nodes in the cluster. Oracle RAC One Node database installation This option installs Oracle RAC One Node database binaries on the selected node. On this screen, select the option “Oracle Real Application Clusters database installation” and then click Next. After selecting the grid installation option, you will be taken to the Select List of Nodes screen, shown in Figure 4, where you select the list of nodes on which you want to install the RAC binaries. The local node is preselected for you. In our case, the local node is rac1. We’ll select the additional node named rac2. Click Next. FIGURE 4. The Select List of Nodes screen OUI will now show you the Select Database Edition screen, shown in Figure 5, where you can choose between the Enterprise and Standard Edition of the Oracle RAC database. Select the option on this screen carefully based on the purchased licenses. You should ensure that you are selecting the correct operating system group on this screen because a wrong selection may interfere with operation of the Oracle RAC database software. For simplicity, we’ll choose to specify the same group name (dba) as the value for all the groups. FIGURE 7. The Privileged Operating System Groups screen In the Perform Prerequisite Checks screen, shown in Figure 8, the Oracle Universal Installer verifies the minimum requirements for installing the Oracle RAC database software. Oracle Universal Installer internally executes the Cluster Verification Utility to verify the operating system and hardware prerequisites. Based on the results of the verification tests performed by the utility, Oracle displays the failed prerequisites on this screen. Because we’ve run the Cluster Verification Utility before starting the Installer, we don’t expect any surprises at this stage. FIGURE 8. The Perform Prerequisite Checks screen OUI provides what are called “fix-up” scripts to repair the failed but fixable prerequisite requirements. Oracle marks each failed prerequisite with a Fixable status of Yes if it can be repaired by a fix-up script, which is also displayed on the screen. Once the Installer verifies the required prerequisites successfully, click Next to continue. In the Summary screen, shown in Figure 9, Oracle displays the installation information. You should verify this information. You can also save this as a response file to use it for mass deployment with the silent install method. Refer to the Oracle Universal Installer Guide for running Oracle Universal Installer with a response file for automated deployment. Our step-by-step install process is known as an interactive installation process. FIGURE 9. The Summary screen Oracle Silent Installation The silent installation method is used for mass deployment of Oracle products because using the interactive method to install Oracle software multiple times on multiple machines is time consuming and error prone. Also, silent install provides an option to have a uniform deployment pattern across the organization. This ensures multiple users in the organization use a standard installation option to install their Oracle products. This greatly helps the internal Oracle support teams because they already know what components and options are installed on each server and their environment settings, including locations of various trace files. Once you verify that the information displayed in the Summary screen is correct, click Install to start the software installation. Installation of Oracle RAC software may take up to 30 minutes, depending on the hardware configuration. The Installer will copy all the required files to the Oracle database home directory and link the files with the operating system libraries. Once the installation and linking is done at the local node, the Installer will copy the files to the remote node. During the entire process, you can see the status in the progress bar of the Install Product screen (see Figure 10). This progress bar shows the completion percentage. FIGURE 5-10. The Install Product screen The OUI will next ask you to run the installation script as the superuser root. You need to open a new terminal window and run the root.sh script as the superuser on all nodes in the cluster (see Figure 11). Now that you’ve successfully installed the Oracle Database 12 c software, you can create an Oracle RAC database, as we explain in the following section. Creating the Oracle RAC Database Creating the RAC database in an Oracle RAC environment is as simple as creating the database in a single-instance environment. The only change in the creation process using DBCA is to select the nodes in the Database Identification screen. Optionally, you can generate the scripts using DBCA and run them later. To create a database using ASM-based storage for datafiles, walk through the following steps. (The number of steps may vary a bit based on the storage options you choose. However, the database-creation process is the same as creating the database in the ASM environment.) Create the ASM disk groups that will be used to store the datafiles.