Re: about archivelog and database status

From: Dino Hsu <dino1_at_ms1.hinet.net>
Date: Thu, 23 Aug 2001 23:16:40 +0800
Message-ID: <ti6aotcpv22php4el9pvknm6iqnip1lv7c@4ax.com>

On Wed, 22 Aug 2001 13:21:28 +0100, "Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote:

>"Dino Hsu" <dino1_at_ms1.hinet.net> wrote in message
>news:2i05otomqhaooh8a2oh0gmrm63a23lsjvn_at_4ax.com...
>> Dear all,
>>
>> Quoting a book: (Jason Couchman, p.667)
>> "The following code block shows how to put the database into
>> archivelog mode:
>> SQL> alter database dismount;
>> Database altered.
>> SQL> alter database archivelog;
>> Database altered.
>> SQL> alter database open;
>> Database altered."
>
>The first line should read alter database mount;

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This is not exactly correct.
When the current status is 'open', the only way is to: 'shutdown immediate' and then 'startup mount'. Everyone can easily test it.

><snip>
>
>> I found the following points:
>> 1.'alter database close' is used to go from 'open' to 'mount' status,
>> but there are some unknown sessions existing that prevents us from
>> doing this. We cannot go from 'open' to 'nomount', either. Therefore,
>> we can only 'shutdown immediate' and then 'startup mount'.
>
>IIRC Alter database close; is the equivalent of shutdown normal; In other

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

>words No new sessions can connect but the database waits for existing
>sessions to terminate before closing.
>

This is not exactly correct, either.
My problem is I cannot 'alter database close' successfuly because some sessions are there, knowing this, I can still connect with 'scott' because the status is still 'open'. I guess if I can do 'alter database close', the status becomes 'mount', when scott tries to log on: ORA-01033: ORACLE initialization or shutdown in progress. Only those with sysdba or sysop privilleges can log on.

Dino Received on Thu Aug 23 2001 - 10:16:40 CDT