oracle| Data | database
1. Various procedures for application-level shutdown.
2. Stop Oralce Listening process:
$lsnrctl stop
3. Under the exclusive system user, back up the control file:
Sql>alter database backup controlfile to trace;
4. Under exclusive system users, manually switch redo log files to ensure that the currently modified data is stored in the file:
Sql>alter system switch logfile;
5. Under the exclusive system user, run the following SQL statement to generate the Kill_all_session.sql file that kills the database user connection:
Set head off;
Set feedback off;
Set NewPage none;
Spool/oracle_backup/bin/kill_all_session.sql
Select ' Alter system kill session ' ' | | sid| | ', ' | | serial#| | '; ' from v$session where username was not null;
Spool off;
6. Under the exclusive system user, executes the Kill_all_session.sql file that kills the database user connection
Sql>@/oracle_backup/bin/kill_all_session.sql
7. Close the database in immediate mode under exclusive system users:
Sql>shutdown immediate;
Or
Svrmgrl>shutdown immediate;
8. Start the ORALCE monitoring process
$lsnrctl start
9. Enter the exclusive system user, start the Oralce database
$sqlplus/nolog
Sql>connect/as SYSDBA
sql>startup;
Or
$svrmgrl
Svrmgrl>connect internal;
svrmgrl>startup;
10. Start the application layer of the various procedures.