Release 2 (9.2) Part Number A96521-01 Home Book List Contents Index Master Index Feedback
4 Starting Up and Shutting Down This chapter describes the procedures for starting up and shutting down an Orace database! and contains the foowing topics" Starting #p a $atabase %tering $atabase %&aiabiit' Shutting $own a $atabase (uiescing a $atabase Suspending and )esuming a $atabase See Also: For additiona information specific to an Orace )ea %ppication Custers en&ironment" Oracle9i Real Application Clusters Administration Oracle9i Real Application Clusters Setup and Configuration Starting Up a Database *hen 'ou start up a database! 'ou create an instance of that database! and 'ou choose the state in which the database starts+ ,orma'! 'ou woud start up an instance b' mounting and opening the database! thus making it a&aiabe for an' &aid user to connect to and perform t'pica data access operations+ Howe&er! there are other options and these are aso discussed in this section+ This section contains the foowing topics reating to starting up an instance of a database" Options for Starting #p a $atabase -reparing to Start an Instance #sing S(L.-us to Start #p a $atabase Starting an Instance" Scenarios Options for Starting Up a Database There are options as to the method 'ou use for starting up /and administering0 an instance of 'our database+ Using SQL*Plus To start up a database use S(L.-us to connect to Orace with administrator pri&ieges and then issue the STARTUP command+ *hie three methods are presented! using S(L.-us is the on' method that is within the scope of this book+ Using Recoer! "anager 1ou can aso use )eco&er' Manager /)M%,0 to execute STARTUP /and SHUTDOWN0 commands+ 1ou ma' prefer to do this if 'our are within the )M%, en&ironment and do not want to in&oke S(L.-us+ See Also: Oracle9i Recovery Manager User's Guide Using Oracle #nterprise "anager 1ou can choose to use the Orace 2nterprise Manager for administering 'our database! incuding starting it up and shutting it down+ The Orace 2nterprise Manager is a separate Orace product! that combines a graphica consoe! agents! common ser&ices! and toos to pro&ide an integrated and comprehensi&e s'stems management patform for managing Orace products+ It enabes 'ou to perform the functions discussed in this book using a 3#I interface! rather than command ines+ See Also: Oracle Enterprise Manager Concepts Guide Oracle Enterprise Manager Administrator's Guide Preparing to Start an $nstance 1ou must perform some preiminar' steps before attempting to start an instance of 'our database using S(L.-us+ 4+ Start S(L.-us without connecting to the database" 2. SQLPLUS /NOLOG 3. 2. Connect to Orace as SYSDBA" 3. CONNECT username/password AS SYSDBA 4. ,ow 'ou are connected to Orace and read' to start up an instance of 'our database+ See Also: SQ!"lus User's Guide and Reference for descriptions and s'ntax for the CONNECT! STARTUP! and SHUTDOWN commands+ These commands are S(L.-us commands+ Using SQL*Plus to Start Up a Database 1ou use the STARTUP command to start up a database instance+ To start an instance! Orace must read instance configuration parameters /the initiai5ation parameters0 from either a ser&er parameter fie or a traditiona text initiai5ation parameter fie+ *hen 'ou issue the STARTUP command with no PFILE cause! Orace reads the initiai5ation parameters from a ser&er parameter fie /SPFILE0 in a patform6specific defaut ocation+ %ote: For #,I7! the patform6specific defaut ocation /director'0 for the ser&er parameter fie /or text initiai5ation parameter fie0 is" $ORACLE_HOME/d! For *indows ,T and *indows 8999 the ocation is" $ORACLE_HOME"d#$##!% In the patform6specific defaut ocation! Orace ocates 'our initiai5ation parameter fie b' examining fienames in the foowing order" &. !'()*%$ORACLE_SID.+,# 2. !'()*%.+,# 3. )-)$$ORACLE_SID.+,# %ote: The !'()*%.+,# fie is incuded in this search path because in a )ea %ppication Custers en&ironment one ser&er parameter fie is used to store the initiai5ation parameter settings for a instances+ There is no instance specific ocation for storing a ser&er parameter fie+ For more information about the ser&er parameter fie for a )ea %ppication Custers en&ironment! see Oracle9i Real Application Clusters Administration+ 1ou can direct Orace to read initiai5ation parameters from a traditiona text initiai5ation parameter fie! b' using the PFILE cause of the STARTUP command+ For exampe" STARTUP PFILE . //0&/+,#1*%/d!/)-)$.+,# Further! 'ou can use this PFILE cause to start an instance with a nondefaut ser&er parameter fie as foows" 1. Create a one ine text initiai5ation parameter fie that contains on' the SPFILE parameter+ The &aue of the parameter is the nondefaut ser&er parameter fie ocation+ For exampe! create a text initiai5ation parameter fie //0&/+,#1*%/d!/!'(_)-)$.+,# that contains on' the foowing parameter" SPFILE . //0&/+,#1*%/d!/$%!$_!'()*%.+,# %ote: 1ou cannot use the IFILE initiai5ation parameter within a text initiai5ation parameter fie to point to a ser&er parameter fie+ In this context! 'ou must use the SPFILEinitiai5ation parameter+ 8+ Start up the instance pointing to this initiai5ation parameter fie+ 3. STARTUP PFILE . //0&/+,#1*%/d!/!'(_)-)$.+,# 4. Since the ser&er parameter fie must reside on the machine running the database ser&er! the abo&e method aso pro&ides a means for a cient machine to start a database that uses a ser&er parameter fie+ It aso eiminates the need for a cient machine to maintain a cient6side initiai5ation parameter fie+ *hen the cient machine reads the initiai5ation parameter fie containing the SPFILE parameter! it passes the &aue to the ser&er where the specified ser&er parameter fie is read+ 1ou can start an instance in &arious modes" Start the instance without mounting a database+ This does not aow access to the database and usua' woud be done on' for database creation or the re6 creation of contro fies+ Start the instance and mount the database! but ea&e it cosed+ This state aows for certain $B% acti&ities! but does not aow genera access to the database+ Start the instance! and mount and open the database+ This can be done in unrestricted mode! aowing access to a users! or in restricted mode! aowing access for database administrators on'+ %ote: 1ou cannot start a database instance if 'ou are connected to the database through a shared ser&er process+ In addition! 'ou can force the instance to start! or start the instance and ha&e compete media reco&er' begin immediate'+ The STARTUP command options that 'ou specif' to achie&e these states are iustrated in the foowing section+ See Also: Chapter 8! :Creating an Orace $atabase: for more information about initiai5ation parameters! initiai5ation parameter fies! and ser&er parameter fies Starting an $nstance: Scenarios The foowing scenarios describe and iustrate the &arious states in which 'ou can start up an instance+ Some restrictions app' when combining options of the STARTUP command+ %ote: It is possibe to encounter probems starting up an instance if contro fies! database fies! or redo og fies are not a&aiabe+ If one or more of the fies specified b' theCONTROL_FILES initiai5ation parameter does not exist or cannot be opened when 'ou attempt to mount a database! Orace returns a warning message and does not mount the database+ If one or more of the datafies or redo og fies is not a&aiabe or cannot be opened when attempting to open a database! Orace returns a warning message and does not open the database+ See Also: SQ!"lus User's Guide and Reference for information about the restrictions that app' when combining options of the STARTUP command Starting an $nstance& and "ounting and Opening a Database ,orma database operation means that an instance is started and the database is mounted and open+ This mode aows an' &aid user to connect to the database and perform t'pica data access operations+ Start an instance! read the initiai5ation parameters from the defaut ser&er parameter fie ocation! and then mount and open the database b' using the STARTUP command b' itsef /'ou can! of course! optiona' specif' aPFILE or SPFILE cause0" STARTUP Starting an $nstance 'ithout "ounting a Database 1ou can start an instance without mounting a database+ T'pica'! 'ou do so on' during database creation+ #se the STARTUP command with the NOMOUNT option" STARTUP NOMOUNT Starting an $nstance and "ounting a Database 1ou can start an instance and mount a database without opening it! aowing 'ou to perform specific maintenance operations+ For exampe! the database must be mounted but not open during the foowing tasks" (as) *or +ore infor+ation,,, )enaming datafies Chapter 48! :Managing $atafies: %dding! dropping! or renaming redo og fies Chapter ;! :Managing the Onine )edo Log: 2nabing and disabing redo og archi&ing options Chapter <! :Managing %rchi&ed )edo Logs: -erforming fu database reco&er' Oracle9i User#Managed $ac%up and Recovery Guide (as) *or +ore infor+ation,,, Oracle9i Recovery Manager User's Guide Start an instance and mount the database! but ea&e it cosed b' using the STARTUP command with the MOUNT option" STARTUP MOUNT Restricting Access to a Database at Startup 1ou can start an instance and mount and open a database in restricted mode so that the database is a&aiabe on' to administrati&e personne /not genera database users0+ #se this mode of database startup when 'ou need to accompish one of the foowing tasks" -erform an export or import of database data -erform a data oad /with S(L.Loader0 Temporari' pre&ent t'pica users from using data $uring certain migration and upgrade operations T'pica'! a users with the CREATE SESSION s'stem pri&iege can connect to an open database+ Opening a database in restricted mode aows database access on' to users with both the CREATE SESSION andRESTRICTED SESSION s'stem pri&iege+ On' database administrators shoud ha&e the RESTRICTED SESSION s'stem pri&iege+ Start an instance /and! optiona'! mount and open the database0 in restricted mode b' using the STARTUP command with the RESTRICT option" STARTUP RESTRICT Later! use the ALTER SYSTEM statement to disabe the RESTRICTED SESSION feature" ALTER SYSTEM DISABLE RESTRICTED SESSION2 If 'ou open the database in nonrestricted mode and ater find 'ou need to restrict access! 'ou can use the ALTER SYSTEM statement to do so! as described in :)estricting %ccess to an Open $atabase:+ See Also: Oracle9i SQ Reference for more information on the ALTER SYSTEM statement *orcing an $nstance to Start In unusua circumstances! 'ou might experience probems when attempting to start a database instance+ 1ou shoud not force a database to start uness 'ou are faced with the foowing" 1ou cannot shut down the current instance with the SHUTDOWN NORMAL! SHUTDOWN IMMEDIATE! or SHUTDOWN TRANSACTIONAL commands+ 1ou experience probems when starting an instance+ If one of these situations arises! 'ou can usua' so&e the probem b' starting a new instance /and optiona' mounting and opening the database0 using the STARTUP command with the FORCE option" STARTUP FORCE If an instance is running! STARTUP FORCE shuts it down with mode ABORT before restarting it+ See Also: :Shutting $own with the %BO)T Option: to understand the side effects of aborting the current instance Starting an $nstance& "ounting a Database& and Starting -o+plete "edia Recoer! If 'ou know that media reco&er' is re=uired! 'ou can start an instance! mount a database to the instance! and ha&e the reco&er' process automatica' start b' using the STARTUP command with the RECO3ER option" STARTUP OPEN RECO3ER If 'ou attempt to perform reco&er' when no reco&er' is re=uired! Orace issues an error message+ Auto+atic Database Startup at Operating S!ste+ Start Man' sites use procedures to enabe automatic startup of one or more Orace instances and databases immediate' foowing a s'stem start+ The procedures for performing this task are specific to each operating s'stem+ For information about automatic startup! see 'our operating s'stem specific Orace documentation+ Starting Re+ote $nstances If 'our oca Orace ser&er is part of a distributed database! 'ou might want to start a remote instance and database+ -rocedures for starting and stopping remote instances &ar' wide' depending on communication protoco and operating s'stem+ Altering Database Aailabilit! 1ou can ater the a&aiabiit' of a database+ 1ou ma' want to do this in order to restrict access for maintenance reasons or to make the database read on'+ The foowing sections expain how to ater a database>s a&aiabiit'" Mounting a $atabase to an Instance Opening a Cosed $atabase Opening a $atabase in )ead6On' Mode )estricting %ccess to an Open $atabase "ounting a Database to an $nstance *hen 'ou need to perform specific administrati&e operations! the database must be started and mounted to an instance! but cosed+ 1ou can achie&e this scenario b' starting the instance and mounting the database+ To mount a database to a pre&ious' started! but not opened instance! use the S(L statement ALTER DATABASE with the MOUNT option as foows" ALTER DATABASE MOUNT See Also: :Starting an Instance and Mounting a $atabase: for a ist of operations that re=uire the database to be mounted and cosed /and procedures to start an instance and mount a database in one step0 Opening a -losed Database 1ou can make a mounted but cosed database a&aiabe for genera use b' opening the database+ To open a mounted database! use the ALTER DATABASE statement with the OPEN option" ALTER DATABASE OPEN %fter executing this statement! an' &aid Orace user with the CREATE SESSION s'stem pri&iege can connect to the database+ Opening a Database in Read.Onl! "ode Opening a database in read6on' mode enabes 'ou to =uer' an open database whie eiminating an' potentia for onine data content changes+ *hie opening a database in read6on' mode guarantees that datafie and redo og fies are not written to! it does not restrict database reco&er' or operations that change the state of the database without generating redo+ For exampe! 'ou can take datafies offine or bring them onine since these operations do not effect data content+ If a =uer' against a database in read6on' mode uses temporar' tabespace! for exampe to do disk sorts! then the issuer of the =uer' must ha&e a oca' managed tabespace assigned as the defaut temporar' tabespace+ Otherwise! the =uer' wi fai+ This is expained in :Creating a Loca' Managed Temporar' Tabespace:+ Idea'! 'ou open a database in read6on' mode when 'ou aternate a standb' database between read6on' and reco&er' mode+ Be aware that these are mutua' excusi&e modes+ The foowing statement opens a database in read6on' mode" ALTER DATABASE OPEN READ ONLY2 1ou can aso open a database in read6write mode as foows" ALTER DATABASE OPEN READ WRITE2 Howe&er! read6write is the defaut mode+ %ote: 1ou cannot use the RESETLOGS cause with a READ ONLY cause+ See Also: Oracle9i SQ Reference for more information about the ALTER DATABASE statement Restricting Access to an Open Database To pace an instance in restricted mode! use the S(L statement ALTER SYSTEM with the ENABLE RESTRICTED SESSION cause+ %fter pacing an instance in restricted mode! 'ou shoud consider kiing a current user sessions before performing an' administrati&e tasks+ To ift an instance from restricted mode! use ALTER SYSTEM with the DISABLE RESTRICTED SESSION option+ See Also: :)estricting %ccess to a $atabase at Startup: to earn some reasons for pacing an instance in restricted mode Shutting Down a Database To initiate database shutdown! use the S(L.-us SHUTDOWN command+ Contro is not returned to the session that initiates a database shutdown unti shutdown is compete+ #sers who attempt connections whie a shutdown is in progress recei&e a message ike the foowing" ORA40&0506 !7/$d+8- )- ',+9,%!! 4 1+--%1$)+- )! -+$ '%,:)$$%d %ote: 1ou cannot shut down a database if 'ou are connected to the database through a shared ser&er process+ To shut down a database and instance! 'ou must first connect as SYSOPER or SYSDBA+ There are se&era modes for shutting down a database+ These are discussed in the foowing sections" Shutting $own with the ,O)M%L Option Shutting $own with the IMM2$I%T2 Option Shutting $own with the T)%,S%CTIO,%L Option Shutting $own with the %BO)T Option Shutting Down with the %OR"AL Option To shut down a database in norma situations! use the SHUTDOWN command with the NORMAL option" SHUTDOWN NORMAL ,orma database shutdown proceeds with the foowing conditions" ,o new connections are aowed after the statement is issued+ Before the database is shut down! Orace waits for a current' connected users to disconnect from the database+ The next startup of the database wi not re=uire an' instance reco&er' procedures+ Shutting Down with the $""#D$A(# Option #se immediate database shutdown on' in the foowing situations" To initiate an automated and unattended backup *hen a power shutdown is going to occur soon *hen the database or one of its appications is functioning irreguar' and 'ou cannot contact users to ask them to og off or the' are unabe to og off To shut down a database immediate'! use the SHUTDOWN command with the IMMEDIATE option" SHUTDOWN IMMEDIATE Immediate database shutdown proceeds with the foowing conditions" ,o new connections are aowed! nor are new transactions aowed to be started! after the statement is issued+ %n' uncommitted transactions are roed back+ /If ong uncommitted transactions exist! this method of shutdown might not compete =uick'! despite its name+0 Orace does not wait for users current' connected to the database to disconnect+ Orace impicit' ros back acti&e transactions and disconnects a connected users+ The next startup of the database wi not re=uire an' instance reco&er' procedures+ Shutting Down with the (RA%SA-($O%AL Option *hen 'ou want to perform a panned shutdown of an instance whie aowing acti&e transactions to compete first! use the SHUTDOWN command with the TRANSACTIONAL option" SHUTDOWN TRANSACTIONAL Transactiona database shutdown proceeds with the foowing conditions" ,o new connections are aowed! nor are new transactions aowed to be started! after the statement is issued+ %fter a transactions ha&e competed! an' cient sti connected to the instance is disconnected+ %t this point! the instance shuts down ?ust as it woud when a SHUTDOWN IMMEDIATE statement is submitted+ The next startup of the database wi not re=uire an' instance reco&er' procedures+ % transactiona shutdown pre&ents cients from osing work! and at the same time! does not re=uire a users to og off+ Shutting Down with the A/OR( Option 1ou can shut down a database instantaneous' b' aborting the database>s instance+ If possibe! perform this t'pe of shutdown only in the foowing situations" The database or one of its appications is functioning irreguar' and none of the other t'pes of shutdown works+ 1ou need to shut down the database instantaneous' /for exampe! if 'ou know a power shutdown is going to occur in one minute0+ 1ou experience probems when starting a database instance+ *hen 'ou must do a database shutdown b' aborting transactions and user connections! issue the SHUTDOWN command with the ABORT option" SHUTDOWN ABORT %n aborted database shutdown proceeds with the foowing conditions" ,o new connections are aowed! nor are new transactions aowed to be started! after the statement is issued+ Current cient S(L statements being processed b' Orace are immediate' terminated+ #ncommitted transactions are not roed back+ Orace does not wait for users current' connected to the database to disconnect+ Orace impicit' disconnects a connected users+ The next startup of the database &ill re=uire instance reco&er' procedures+ Quiescing a Database There are times when there is a need to put a database into a state where on' $B% transactions! =ueries! fetches! or -L@S(L statements are aowed+ This is caed a =uiesced state! in the sense that there are no ongoing non6$B% transactions! =ueries! fetches! or -L@S(L statements in the s'stem+ This =uiesced state aows 'ou or other administrators to perform actions that cannot safe' be done otherwise+ These actions are categori5ed as foows" %ctions that can fai if concurrent user transactions access the same ob?ect+ For exampe! changing the schema of a database tabe or adding a coumn to an existing tabe where a no6wait ock is re=uired+ %ctions whose undesirabe intermediate effect can be seen b' concurrent user transactions+ For exampe! a mutistep procedure for reorgani5ing a tabe where the tabe is first exported! then dropped! and fina' imported+ % concurrent user who attempted to access the tabe after it was dropped! but before import! woud see disturbing resuts+ *ithout the abiit' to =uiesce the database! 'ou woud be re=uired to shut down the database and reopen it in restricted mode+ This is a serious restriction! especia' for s'stems re=uiring 8A x ; a&aiabiit'+ (uiescing a database is much ess of a restriction because it eiminates the disruption to users and downtime associated with shutting down and restarting the database+ %ote: For this reease of OraceBi! in the =uiesce database context a $B% is defined as user SYS or SYSTEM+ Other users! incuding those with the DBA roe are not aowed to issue theALTER SYSTEM QUIESCE DATABASE statement or proceed after the database is =uiesced+ Placing a Database into a Quiesced State To pace a database into a =uiesced state! issue the foowing statement" ALTER SYSTEM QUIESCE RESTRICTED2 %n' non6$B% acti&e sessions wi proceed unti the' become inacti&e+ %n acti&e session is defined as a session that is current' inside of a transaction! a =uer'! a fetch! or a -L@S(L statementC or a session that is current' hoding an' shared resources /for exampe! en=ueues0+ ,o inacti&e sessions are aowed to become acti&e+ If a user! for exampe! issues a S(L =uer' in an attempt to force an inacti&e session to become acti&e! the =uer' wi appear to be hung+ *hen the database is ater un=uiesced! the session is resumed! and the bocked action /for exampe! the pre&ious' mentioned S(L =uer'0 wi be processed+ Once a non6$B% sessions become inacti&e! the ALTER SYSTEM QUIESCE RESTRICTED statement finishes! and the database is considered as in a =uiesced state+ In an Orace )ea %ppication Custers en&ironment! this statement affects a instances! not ?ust the one that issues the statement+ %ote: 1ou must ha&e the $atabase )esource Manager feature acti&ated! and it must ha&e been acti&ated since instance startup /a instances in an Orace )ea %ppication Custers en&ironment0 to successfu' issue the ALTER SYSTEM QUIESCE RESTRICTED statement+ It is through the faciities of the $atabase )esource Manager that non6$B% sessions are pre&ented from becoming acti&e+ %so! whie this statement is in effect! an' attempt to change the current resource pan wi be =ueued unti after the s'stem is un=uiesced+ For information about the $atabase )esource Manager! see Chapter 8;! :#sing the $atabase )esource Manager:+ The ALTER SYSTEM QUIESCE RESTRICTED statement ma' wait a ong time for acti&e sessions to become inacti&e+ If 'ou interrupt the re=uest! or if 'our session abnorma' terminates for some reason before a acti&e sessions are =uiesced! Orace wi automatica' undo an' partia effects of the statement+ If a =uer' is carried out b' successi&e mutipe Orace Ca Interface /OCI0 fetches! the ALTER SYSTEM QUIESCE RESTRICTED statement does not wait for a fetches to finishC it on' waits for the current fetch to finish+ For both dedicated and shared ser&er connections! a non6$B% ogins after this statement is issued are =ueued b' the $atabase )esource Manager! and are not aowed to proceed+ To the user! it appears as if the ogin is hung+ The ogin wi resume when the database is un=uiesced+ The database remains in the =uiesced state e&en if the session that issued the statement exits+ % $B% must og in to the database to issue the statement that specifica' un=uiesces the database+ *hie in the =uiesced state! 'ou cannot use fie s'stem cop' to backup the database>s datafies as cod backups! e&en if 'ou do a checkpoint on e&er' instance+ The reason for this is that in the =uiesced state the fie headers of onine datafies continue to ook ike the' are being accessed+ The' do not ook the same as if a cean shutdown were done+ Simiar'! to perform a hot backup of the datafies of an' onine tabespace whie the database is in a =uiesced state! 'ou are sti re=uired to first pace the tabespace into backup mode using the ALTER TABLESPACE... BEGIN BAC;UP statement+ Restoring the S!ste+ to %or+al Operation The foowing statement restores the database to norma operation" ALTER SYSTEM UNQUIESCE2 % non6$B% acti&it' is aowed to proceed+ In an Orace )ea %ppication Custers en&ironment! this statement is not re=uired to be issued from the same session! or e&en the same instance! as that which imposed the =uiesce state+ If the session issuing the ALTER SYSTEM UNQUIESCE statement shoud terminate abnorma'! the Orace database ser&er ensures that the un=uiesce operation finishes+ 0iewing the Quiesce State of an $nstance The 3$INSTANCE &iew can be =ueried to see the current state of an instance+ It contains a coumn named ACTI3E_STATE! whose &aues are shown in the foowing tabe" ACTIVE_STATE Description NORMAL ,orma un=uiesced state QUIESCING Being =uiesced! but there are sti acti&e non6$B% sessions running QUIESCED (uiesced! no acti&e non6$B% sessions are acti&e or aowed Suspending and Resu+ing a Database The ALTER SYSTEM SUSPEND statement suspends a database b' hating a input and output /I@O0 to datafies /fie header and fie data0 and contro fies! thus aowing a database to be backed up without I@O interference+ *hen the database is suspended a preexisting I@O operations are aowed to compete and an' new database accesses are paced in a =ueued state+ The suspend command suspends the database! and is not specific to an instance+ Therefore! in an Orace )ea %ppication Custers en&ironment! if the suspend command is entered on one s'stem! then interna ocking mechanisms wi propagate the hat re=uest across instances! thereb' =uiescing a acti&e instances in a gi&en custer+ Howe&er! do not start a new instance whie 'ou suspend another instance! since the new instance wi not be suspended+ #se the ALTER SYSTEM RESUME statement to resume norma database operations+ 1ou can specif' the SUSPEND and RESUME from different instances+ For exampe! if instances 4! 8! and D are running! and 'ou issue anALTER SYSTEM SUSPEND statement from instance 4! then 'ou can issue a RESUME from instance 4! 8! or D with the same effect+ The suspend@resume feature is usefu in s'stems that aow 'ou to mirror a disk or fie and then spit the mirror! pro&iding an aternati&e backup and restore soution+ If 'ou use a s'stem that is unabe to spit a mirrored disk from an existing database whie writes are occurring! then 'ou can use the suspend@resume feature to faciitate the spit+ The suspend@resume feature is not a suitabe substitute for norma shutdown operations! howe&er! since copies of a suspended database can contain uncommitted updates+ -aution: $o not use the ALTER SYSTEM SUSPEND statement as a substitute for pacing a tabespace in hot backup mode+ -recede an' database suspend operation b' an ALTER TABLESPACE BEGIN BAC;UP statement+ The foowing statements iustrate ALTER SYSTEM SUSPEND/RESUME usage+ The 3$INSTANCE &iew is =ueried to confirm database status+ SQL< ALTER SYSTEM SUSPEND2 S=!$%: #*$%,%d SQL< SELECT DATABASE_STATUS FROM 3$INSTANCE2 DATABASE_STATUS 444444444 SUSPENDED SQL< ALTER SYSTEM RESUME2 S=!$%: #*$%,%d SQL< SELECT DATABASE_STATUS FROM 3$INSTANCE2 DATABASE_STATUS 444444444 ACTI3E See Also: Oracle9i User#Managed $ac%up and Recovery Guide for detais about backing up a database using the database suspend@resume feature Cop'right E 8994! 8998 Orace Corporation+ % )ights )eser&ed+ Home Book List Contents Index Master Index Feedback
Icertify Training - The Ultimate AWS® Certified Cloud Practitioner Training Manual - The Complete Guide To Get You AWS Cloud Practitioner Certified On Your First Attempt (2021)