Start the database and start the oracle database

Start the database and start the oracle database

Database STARTUP (STARTUP)

Three steps are required to start a database:

1. Create an Oracle instance (not in the installation phase)

2. Database Installation By instance (installation phase)

3. Open the database (open stage)

In the Startup command, different options can be used to control different database Startup steps.

1. STARTUP NOMOUNT

The NOMOUNT option only creates an Oracle instance. Read the init. ora initialization parameter documentation, start the background process, and initialize the system global zone (SGA ). The Init. ora document defines instance configurations, including the size of the memory structure and the number and type of background processes. The instance name is configured according to Oracle_SID and does not have to be the same as the name of the opened database. When the instance is turned on, the system displays a list of SGA Memory Structures and sizes, as shown below:

SQL> startup nomount

The ORACLE routine has been started.

Total System Global Area 35431692 bytes

Fixed Size 70924 bytes

Variable Size 18505728 bytes

Database Buffers 16777216 bytes

Redo Buffers 77824 bytes

2. STARTUP MOUNT

This command creates an instance and installs the database, but does not open the database. This document does not open the data document and rebuild log document in the Oracle read control document. This method is often used in database maintenance operations, such as renaming data documents, changing duplicate logs, and opening and archiving methods. In this way, in addition to the SGA system list, the system will also prompt "database load is complete.

 

How to start a Database Server

Is it mssql or mysql or other? You can see the corresponding service (run-> services. msc) in the service management interface)

Does the oracle database enable the listener first or the master service first ??

It doesn't matter when it is started. If it is disabled
1. First, disable the listener (so that the remote client cannot be connected again );
2. Issue a system checkpoint to unify the system modification numbers of data files and control files; (alter system checkpoint ;)
3. shutdown immediate & shutdown transactional;

If the database is busy, there may be a lot of transactions being executed. if you issue a close command, rollback may occur, which may take a long time, generally, you can kill these sessions before step 2. You can kill sessions in the database or at the system level (for linux or unix systems). For example:
Ps-ef | grep LOCAL = NO | grep-v grep | awk '{print $2}' | xargs kill-9