Where is init.ora in oracle 11g

If no server parameter file is found, the instance searches for a text initialization parameter file. Instructions for starting an instance using a server parameter file are contained in "Starting Up a Database".

If you are currently using a text initialization parameter file, then use the following steps to migrate to a server parameter file. If the initialization parameter file is located on a client system, then transfer the file for example, FTP from the client system to the server system. See "Creating a Server Parameter File" for instructions.

This statement reads the text initialization parameter file to create a server parameter file. However, if the instance has been started using a server parameter file, an error is raised if you attempt to re-create the same server parameter file that is currently being used by the instance. In this example no SPFILE name is specified, so the file is created with the platform-specific default name and location shown in Table The next example illustrates creating a server parameter file in the default location from the current values of the initialization parameters in memory.

All other comments are ignored. Oracle recommends that you allow the database to give the SPFILE the default name and store it in the default location. This eases administration of your database. If it is a raw device, the default name could be a logical volume name or partition device name, and the default location could differ. In the same disk group as the data files Foot 2.

In the same disk group as the data files Footref 2. Footnote 1 OH represents the Oracle home directory. For more information, see "Starting Up a Database". If you are using a text initialization parameter file, the ALTER SYSTEM statement changes the value of a parameter only for the current instance, because there is no mechanism for automatically updating text initialization parameters on disk.

You must update them manually to be passed to a future instance. Using a server parameter file overcomes this limitation. Dynamic initialization parameters can be changed for the current Oracle Database instance. The changes take effect immediately. Static initialization parameters cannot be changed for the current instance.

You must change these parameters in the text initialization file or server parameter file and then restart the database before changes take effect. For both dynamic and static parameters, the change is effective at the next startup and is persistent.

For dynamic parameters, the effect is immediate, but it is not persistent because the server parameter file is not updated. When specified, the change is effective only for future sessions. The comment is written to the server parameter file. The following statement changes the maximum number of failed login attempts before the connection is dropped. It includes a comment, and explicitly states that the change is to be made only in the server parameter file.

The next example sets a complex initialization parameter that takes a list of attributes. This statement could change an existing setting for this parameter or create a new archive destination.

When a value consists of a list of parameters, you cannot edit individual attributes by the position or ordinal number. You must specify the complete list of values each time the parameter is updated, and the new list completely replaces the old list. Doing so might be necessary for several reasons:. For diagnostic purposes, listing all of the parameter values currently used by an instance.

The exported file is created on the database server system. It contains any comments associated with the parameter in the same line as the parameter setting.

Because no names were specified for the files, the database creates an initialization parameter file with a platform-specific name, and it is created from the platform-specific default server parameter file. The following example creates a text initialization parameter file from a server parameter file, but in this example the names of the files are specified:.

If your server parameter file SPFILE becomes lost or corrupted, the current instance may fail, or the next attempt at starting the database instance may fail. If the instance is running, issue the following command to re-create the SPFILE from the current values of initialization parameters in memory:. See "Creating a Server Parameter File" for examples. If none of the previous methods are possible in your situation, perform these steps:.

Create a text initialization parameter file PFILE from the parameter value listings in the alert log. When an instance starts up, the initialization parameters used for startup are written to the alert log. If an error occurs while reading or writing the server parameter file during a parameter update, the error is reported in the alert log and all subsequent parameter updates to the server parameter file are ignored.

At this point, you can take one of the following actions:. Shut down the instance, recover the server parameter file and described earlier in this section, and then restart the instance.

Continue to run the database if you do not care that subsequent parameter updates will not be persistent. You can view parameter settings in several ways, as shown in the following table. Database services services are logical abstractions for managing workloads in Oracle Database. Services divide workloads into mutually disjoint groupings. Each service represents a workload with common attributes, service-level thresholds, and priorities.

The grouping is based on attributes of work that might include the application function to be used, the priority of execution for the application function, the job class to be managed, or the data range used in the application function or job class.

For example, the Oracle E-Business suite defines a service for each responsibility, such as general ledger, accounts receivable, order entry, and so on. When you configure database services, you give each service a unique global name, associated performance goals, and associated importance. The services are tightly integrated with Oracle Database and are maintained in the data dictionary. Connection requests can include a database service name. If no service name is included and the Net Services file listener.

Services enable you to configure a workload, administer it, enable and disable it, and measure the workload as a single entity. Enterprise Manager supports viewing and operating services as a whole, with drill down to the instance-level when needed.

In an Oracle Real Application Clusters Oracle RAC environment, a service can span one or more instances and facilitate workload balancing based on transaction performance. This provides end-to-end unattended recovery, rolling changes by workload, and full location transparency. Services also offer an extra dimension in performance tuning. Tuning by "service and SQL" can replace tuning by "session and SQL" in the majority of systems where all sessions are anonymous and shared.

With services, workloads are visible and measurable. Resource consumption and waits are attributable by application. Additionally, resources assigned to services can be augmented when loads increase or decrease.

This dynamic resource allocation enables a cost-effective solution for meeting demands as they occur. For example, services are measured automatically and the performance is compared to service-level thresholds. Performance violations are reported to Enterprise Manager, enabling the execution of automatic or scheduled solutions. Several Oracle Database features support services.

AWR records service performance, including execution times, wait classes, and resources consumed by service. AWR alerts warn when service response time thresholds are exceeded. The dynamic views report current service performance metrics with one hour of history.

Each service has quality-of-service thresholds for response time and CPU consumption. In addition, the Database Resource Manager can map services to consumer groups. Therefore, you can automatically manage the priority of one service relative to others.

You can use consumer groups to define relative priority in terms of either ratios or resource consumption. You also can specify an edition attribute for a service. Editions make it possible to have two or more versions of the same objects in the database. When you specify an edition attribute for a service, all subsequent connections that specify the service use this edition as the initial session edition. Specifying an edition as a service attribute can make it easier to manage resource usage.

For example, services associated with an edition can be placed on a separate instance in an Oracle RAC environment, and the Database Resource Manager can manage resources used by different editions by associating resource plans with the corresponding services. Services describe applications, application functions, and data ranges as either functional services or data-dependent services. Functional services are the most common mapping of workloads.

Sessions using a particular function are grouped together. In contrast, data-dependent routing routes sessions to services based on data keys. The mapping of work requests to services occurs in the object relational mapping layer for application servers and TP monitors. For example, in Oracle RAC, these ranges can be completely dynamic and based on demand because the database is shared. You can also define preconnect application services in Oracle RAC databases. Preconnect services span instances to support a service in the event of a failure.

Using services requires no changes to your application code. Client-side work can connect to a named service. Server-side work, such as Oracle Scheduler, parallel execution, and Oracle Streams Advanced Queuing, set the service name as part of the workload definition. Work requests executing under a service inherit the performance thresholds for the service and are measured as part of the service. For Oracle Scheduler, you optionally assign a service when you create a job class.

During execution, jobs are assigned to job classes, and job classes can run within services. Using services with job classes ensures that the work executed by the job scheduler is identified for workload management and performance tuning. For parallel query and parallel DML, the query coordinator connects to a service just like any other client. The parallel query processes inherit the service for the duration of the execution. At the end of query execution, the parallel execution processes revert to the default service.

If your single-instance database is not being managed by Oracle Restart, do one of the following:. You may want to perform other actions, some of which are discussed in this section.

In this release of Oracle Database, several enhancements were made to ensure the security your database. You can find security guidelines for this release in Oracle Database Security Guide.

Oracle recommends that you read these guidelines and configure your database accordingly. After the database is created, you can configure it to take advantage of Oracle Identity Management. Additional administrative accounts are provided that should be used only by authorized users. To protect these accounts from being used by unauthorized users familiar with their Oracle-supplied passwords, these accounts are initially locked with their passwords expired.

As the database administrator, you are responsible for the unlocking and resetting of these accounts. Oracle Database Security Guide to learn how to add new users and change passwords. Transparent data encryption is a feature that enables encryption of individual database columns before storing them in the data file, or enables encryption of entire tablespaces.

If users attempt to circumvent the database access control mechanisms by looking inside data files directly with operating system tools, transparent data encryption prevents such users from viewing sensitive information. The data is encrypted in the data files and in the audit logs if audit is turned on. Database users with appropriate privileges can view the data in unencrypted format. For large-scale deployments where applications use password credentials to connect to databases, it is possible to store such credentials in a client-side Oracle wallet.

An Oracle wallet is a secure software container that is used to store authentication and signing credentials. Storing database password credentials in a client-side Oracle wallet eliminates the need to embed usernames and passwords in application code, batch jobs, or scripts.

This reduces the risk of exposing passwords in the clear in scripts and application code, and simplifies maintenance because you need not change your code each time usernames and passwords change. In addition, not having to change application code also makes it easier to enforce password management policies for these user accounts. When you configure a client to use the external password store, applications can use the following syntax to connect to databases that use password authentication:.

Instead your system looks for database login credentials in the client wallet. Oracle Database Security Guide. The Oracle Database distribution media includes various SQL files that let you experiment with the system, learn SQL, or create additional tables, views, or synonyms. Oracle Database includes sample schemas that help you to become familiar with Oracle Database functionality.

All Oracle Database documentation and training materials are being converted to the Sample Schemas environment as those materials are updated. The Sample Schemas can be installed automatically by the Database Configuration Assistant, or you can install them manually. The schemas and installation instructions are described in detail in Oracle Database Sample Schemas.

It is often necessary to clone a production database for testing purposes or other purposes. Common reasons to clone a production database include the following:. Before deploying a new application, performing an operating system upgrade, or using new storage, thorough testing is required to ensure that the database works properly under the new conditions. Cloning can be achieved by making copies of the production data files in one or more test environments, but these copies typically require large amounts of storage space to be allocated and managed.

With CloneDB, you can clone a database multiple times without copying the data files into several different locations. Instead, Oracle Database creates the files in the CloneDB database using copy-on-write technology, so that only the blocks that are modified in the CloneDB database require additional storage on disk. The CloneDB databases use the data files of a database backup.

The storage required for the database backup depends on the method used to perform the backup. A single full RMAN backup requires the most storage. Storage snapshots carried out using the features of a storage appliance adhere to the requirements of the storage appliance. A single backup can support multiple CloneDB databases. The amount of storage required for each CloneDB database depends on the write activity in that database. Every block that is modified requires an available block of storage.

Therefore, the total storage requirement depends on the number of blocks modified in the CloneDB database over time.

This section describes the steps required to create one CloneDB database and uses these sample databases and directories:. If you perform a full offline backup, then ensure that the backup files are accessible to the CloneDB database environment.

You can use RMAN to make image copies while the database is open. Ensure that the copied database files are accessible to the CloneDB database environment.

Ensure that this directory contains only the backup of the data files of the production database. Otherwise, do not set this environment variable. Set this environment variable only if cloning must be done using storage snapshots. For an Oracle Database 11 g Release 2 The default is crtdb.

The default is dbren. The clonedb. Check the two SQL scripts that were generated by the clonedb. See Oracle Database Reference for information about initialization parameters. For example, if the scripts use the default names, then run the following scripts at the SQL prompt:. Generate a backup control file script from your production database by completing the following steps:.

This statement generates a trace file that contains the SQL statements that create the control file. Check the database alert log for the name and location of this trace file. Change the name of the database to the name of the CloneDB database you are creating. Change the locations of the log files to a directory in the CloneDB database environment. Change the locations of the data files to the backup location. If you have a storage level snapshot taken on a data file, then you can replace the RMAN backup file names with the storage snapshot names.

Make a note of the name and location of the new SQL script. You will run the script in a subsequent step. This statement prompts for the archived redo log files for the period when the backup was performed. After a CloneDB database is created, you can use it in almost any way you use your production database. Initially, a CloneDB database uses a minimal amount of storage for each data file. Changes to rows in a CloneDB database cause storage space to be allocated on demand.

You can use the same backup files to create multiple CloneDB databases. This backup can be taken either by RMAN or by storage level snapshots. This information includes the data file name in the backup, the corresponding data file name in the CloneDB database, the number of blocks read from the backup file, and the number of requests issued against the backup file.

Because CloneDB databases use the backup files as their backend storage, the backup files must be available to each CloneDB database for it to run. If the backup files become unavailable, then the CloneDB databases return errors. You can delete all of the files in the CloneDB database environment without affecting the production database environment or the backup environment.

Dropping a database involves removing its data files, redo log files, control files, and initialization parameter files. It then shuts down the database instance. It is best to use RMAN to delete such files. If the database is on raw disks, the actual raw disk special files are not deleted.

If you used the Database Configuration Assistant to create your database, you can use that tool to delete drop your database and remove the files. In addition to the views listed previously in "Viewing Parameter Settings" , you can view information about your database content and structure using the following views:. About Creating an Oracle Database After you plan your database using some of the guidelines presented in this section, you can create the database with a graphical tool or a SQL command.

Reasons to create a database after installation are as follows: You used Oracle Universal Installer OUI to install software only, and did not create a database. You want to make a copy of clone a database. The following topics can help prepare you for database creation.

Table lists some recommended actions: Table Database Planning Tasks Action Additional Information Plan the database tables and indexes and estimate the amount of space they will require. See "Selecting a Character Set" for details.

Chapter 16, "Managing Undo" Develop a backup and recovery strategy to protect the database from failure. Chapter 3, "Starting Up and Shutting Down".

Please give your inputs. Problem on init 0, execution is the same with init 6. When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc Hi all, Am intermittently getting the following errors on one of my databases.

How to I change init levels after typing init 1. How do I change the init back to 3? Everytime when i issue command init 6 OR init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init I can only reboot the system using reboot RedHat Commands.

OpenSolaris Commands. Linux Commands. SunOS Commands. FreeBSD Commands. Full Man Repository. Advanced Search. Contact Us. Forum Rules. Mark Forums Read. Thread Tools. View Public Profile for matrixmadhan. Find all posts by matrixmadhan. Verify experience!

Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications. Oracle technology is changing and we strive to update our BC Oracle support information. If you find an error or have a suggestion for improving our content, we would appreciate your feedback.