Avoid putting database in quiesce mode

Hello all,
had a question with regards to dropping EM repositry.
When i run below on 11.2.0.2 i get a warning saying DB will be put in quiesce mode
emca -deconfig dbcontrol db -repos drop
WARNING : While repository is dropped the database will be put in quiesce mode.
but when i do the same for 11.2.0.1 it do not get any warning or anything...
is this something new for 11.2.0.2 ?? How can i avoid this??
As its hard for us to get some downtime for this system(which is 11.2.0.2)...
is there any other way to drop the repositry with putting DB in quiesce mode..
reson for this is, we are going to install OEM Agent on this, so need to drop the repositry of exsitnig DB
here is the exacty error...
$ emca -deconfig dbcontrol db -repos drop
STARTED EMCA at Nov 15, 2011 4:04:15 PM
EM Configuration Assistant, Version 11.2.0.0.2 Production
Copyright (c) 2003, 2005, Oracle. All rights reserved.
Enter the following information:
Database SID: ORCL
Listener port number: 1521
Password for SYS user:
Nov 15, 2011 4:04:25 PM oracle.sysman.emcp.DatabaseChecks checkRestrictedMode
WARNING: ORA-01034: ORACLE not available
Nov 15, 2011 4:04:25 PM oracle.sysman.emcp.DatabaseChecks checkDataGuardEnabled
WARNING: ORA-01034: ORACLE not available
Password for SYSMAN user:
WARNING : While repository is dropped the database will be put in quiesce mode.
Do you wish to continue? [yes(Y)/no(N)]: N
$
Edited by: user8363520 on Nov 15, 2011 8:05 AM

It's an harmless message.
This topic is explained at MOS:
Bug 12861049 Trying to drop or recreate the database control in 11.2.0.2 using emca shows following Warning : While repository is dropped the database will be put in quiesce mode.

Similar Messages

Can I rebuild dbconsole without putting database in quiesce mode?

I have a database (10Gr2) that the dbconsole just won't start up, while it say's its starting up, and during that time I can actually log into the console and look at things, navigate around etc., but then I get a message saying that it could not be started, and I lose the console connection.
I know the fast way is to just do the dbconsole recreate, but this puts the database in quiesce mode, which amounts to an outage, which I would sooner avoid.
Is there a way to drop and recreate without affecting users?
thanks

what you can do here launch dbca and create another instance dbconsole

How to put database in RESTRICTED mode ?

Hi,
in 9.2.0.6 on Windows 2003 server how to put database in RESTRICTED mode ?
Many thanks before.

ERROR at line 1:
ORA-12719: operation requires database is in RESTRICTED mode
That's because 'ALTER SYSTEM QUIESCE RESTRICTED' doesn't actually put the database into restricted mode:
SQL> select logins, active_state from v$instance;
LOGINS       ACTIVE_ST
ALLOWED       NORMAL
SQL> alter system quiesce restricted;
System altered.
SQL> select logins, active_state from v$instance;
LOGINS       ACTIVE_ST
ALLOWED       QUIESCEDTry staring the database in restricted mode and then quiescing it:
SQL>
SQL> shutdown immediate;
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup restrict;
ORACLE instance started.
Total System Global Area 167772160 bytes
Fixed Size                  1289508 bytes
Variable Size             117441244 bytes
Database Buffers           46137344 bytes
Redo Buffers                2904064 bytes
Database mounted.
Database opened.
SQL> alter system quiesce restricted;
System altered.
SQL> select logins, active_state from v$instance;
LOGINS           ACTIVE_ST
RESTRICTED       QUIESCED
SQL>As you can see from V$INSTANCE, when you are running in restricted mode LOGINS will have a value of 'RESTRICTED'
However - I still think that if you are dealing with users logging in to your (RESTRICTED) database via the listener then the easiest option is to stop the listener whilst the database is down and restart it once your alter database command has completed.
PS : No any other user is connected.No, they wouldn't be this time because you had quiesced the database... but you still need to get the database into restricted mode for this alter database command.

Database in quiesce mode

How should I come out of this?
Suddenly I am seeing this message in the alert log after everyone complained that they couldn't do anything with the database?
I tried this
SQL> ALTER SYSTEM UNQUIESCE
2 ;
ALTER SYSTEM UNQUIESCE
ERROR at line 1:
ORA-25502: concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
SQL> v$blocking_quiesce
SP2-0734: unknown command beginning "v$blocking..." - rest of line ignored.
SQL> select * from v$blocking_quiesce
2 ;
no rows selected
SQL> select active_state from V$INSTANCE
2 ;
ACTIVE_ST
QUIESCINGThanks
Nith
Edited by: user645399 on Oct 15, 2010 10:50 AM
Edited by: user645399 on Oct 15, 2010 10:56 AM

This forum is dedicated to issues related to database upgrades. Your question is better suited to the General Forum (General Database Discussions
You are correct in that creating an OEM repository will cause the database to enter quiesce mode, depending on your OEM/database version. This is documented in MOS Doc 375946.1 (Running EMCA Results in Database quiesce And No New Connections or Operations Can Be Performed During the DB Control Repository Creation).
HTH
Srini

Why we need oracle database reboot to put database in archivelog mode?

I know how to enable archivelog mode, but what is the reason that to enable archive log we need database restart. which process forces to do that.

SantoshGanjure wrote:
Thanks a lot EdStevens for ur prompt response...I need something that satisfies my managers query.
If the question has originated with the PHB, then my flippant answer is even more relevant ...
PHB's are incapable of understanding the technical details, so I prefer to give them the 'executive summary':
"Because that's the way Oracle is written. We can argue over the technical merits of such a requirement 'till the cows come home. But at the end of the day, we have to shut down the database because the 'alter database archivelog' command will only succeed when the database is in mount (not open) mode. Now, let's work out how we can achieve our objective of putting the database in archivelog mode with minimal and appropriately scheduled down time."
As for the actual down time, it's about as minimal as you can get. How long does it take your database to complete a shutdown once the command is given? How long does it take you to type "startup mount"? How long does it take you to type "alter database archivelog"? to type "alter database open;"? For the database to complete the 'open' process? You could even script it so as to eliminate the keyboard typing time.

Put database in archivelog mode

I know how to do it.
using oracle 9.2.0.8 on AIX 5.3
My question is that can I mention a different location
my database installed in /opt/oracle/product/9.2
datafiles/control files and redolof files
in /var/data/oracle/product/9.2/orcl
I want archive to be in
/var/data/oracle/product/9.2
How can I do this
please suggest

Is this standard or enterprise edition?
On the enterprise edition you can use the log_archive_dest_N (n=1..10) instance parameter file to configure up to ten different locations. As an example, you would configure: log_archive_dest_1="location=/var/data/oracle/product/9.2 mandatory" You have to configure log_archive_format as well (unless you want the default format mask); log_archive_format=arch%S.arc and the log_archive_start parameter to true.
Shutdown normal or immediate your database. Once it is shutdown start it up to the mount state:
startup mount
and issue the alter command:
ALTER DATABASE ARCHIVELOG
open your database and you will be working on archivelog mode.
If you are on a standard edition, just proceed as previously indicated, the difference is that log_archive_dest_N parameter is not available, and you can define up to two different file locations, parameters are:
LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST
and to indicate mandatory or optional, you'll have to use the LOG_ARCHIVE_MIN_SUCCEED_DEST instance parameter.
~ Madrid

How to put database in single user mode?

hi
how to put database in single user mode?and what could be the impact of this to EBS R12 RUP 6.DB 10.2.0.0
rgrds

hsawwan wrote:
Hi,
Are you referring to restricted mode? If yes, please see these links/docs.
Restricting Access to an Open Database
http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/start002.htm#ADMIN11155
Note: 1059291.6 - How to Put a Database into Restricted Mode and Verify Restricted Mode
The impact is none of the users will be able to connect to the database/application (except for the sys user which can connect to the database). Usually, you would need to put the database in restricted mode when doing upgrade/migrate (i.e. you do not want to have active user sessions in the database during that time).
Thanks,
HusseinHi
i want to mean:
ALTER SYSTEM QUIESCE RESTRICTEDThe ALTER SYSTEM QUIESCE RESTRICTED statement may wait a long time for active sessions to become inactive. You can determine the sessions that are blocking the quiesce operation by querying the V$BLOCKING_QUIESCE view. This view returns only a single column: SID (Session ID). You can join it with V$SESSION to get more information about the session, as shown in the following example:
select bl.sid, user, osuser, type, program
from v$blocking_quiesce bl, v$session se
where bl.sid = se.sid;I suspect all apps user can.t login to db?
Edited by: new2appsdba on Aug 19, 2010 1:54 AM

Can we put RAC database in Archivelog mode without shutting down

All,
Can we put RAC database in Archivelog mode without shutting down.
Currently our new production database (2 node RAC) is in no archive log mode, Need to enable archive log in the database...
I believe we need to set the cluster_database=false and then put the DB in archive log mode then we need to bounce the database to take effect...
Just curious to know in 11gR2 ...Can we put the RAC database in archive log mode without any downtime ...?

Even RAC or non-RAC, database should bounced and enable/disable archive log mode from mount status.

How to put RAC database in restricted mode?is it with srvctl?

I know for standalone database its
SQL> startup restrict --if its down
SQL> alter system enable restricted session; --if its up
Any idea for RAC ? any option with srvctl ? what are the steps .....
Thanks in advance for help
Gagan

Hi
There is no option like that. It's as same as keeping normal database in restricted mode.
alter database enable restricted session;
and end with
alter database disable restricted session.
Regards,
Phani Kumar P
+919948677317

Database in suspect mode

i was going through this article about recovering a database in suspect mode :
http://www.mytechmantra.com/LearnSQLServer/Repair_Suspect_Database_P2.html
in the article the error seems to indicate corruption in the log :
Error: 9003, Severity: 20, State: 9. The log scan number (189624:16:2) passed to log scan in database
'BPO' is not valid. This error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf
if the corruption is in the log, then is not the logical solution to bypass the recovery process and then truncate the log with no_log option and then bring the database online?
and dbcc checkdb (<db>,repair_allow_data_loss) repairs the data pages or the log pages?
and any other options/ways/articles about bringing a suspect database online?
appreciate the insights.

datafile corruption : put db in emergency mode / put db in single user mode / dbcc checkdb with REPAIR_ALLOW_DATA_LOSS/ dbcc checkdb on database
again/put db back in multi user mode.
There is no need to do this. This is totally not required.
You can
Switching the database to the Simple recovery model
Performing a checkpoint (which should clear the active log as long as nothing else requires the log to be kept active)
Switching back to the Full recovery model
Reestablishing the log backup chain by performing a full or differential backup
Or you can rebuild log as already pointed in my reply.
Or you can restore from known valid backup.
There is no need to move data as well because actually its not related to data.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Running a physical standby database in noarchivelog mode

Primary Database: 2 node rac cluster, 11.2.0.2 GI and RDBMS
Standby Database: single instance 11.2.0.2
OS: AIX 7.1
Hello,
I'm in the process of implementing a data guard standby system. To make this system simpler to admin, I want to run the standby database in NOARCHIVELOG mode. This standby is used only as a mirror of production (to be copied to a 3rd site for separate user activity) and will never be switched to active mode. Maintaining another set of archive logs seems to be redundant to me and another point of failure, so I want to disable archiving. I wanted to ask if any of the DG experts on the forums have ever had experience with this? Does anyone know if this is recommended? I've searched the Oracle Data guard documentation online... it says that the primary obviously needs to be in archive mode, but I'm not seeing anything specific about the standby. Please let me know if anyone has experience with this.
Thanks

Hello again;
If this is the case, then I have nothing to worry about here. Does that sound right to you?Yes.
For this :
b) monthly, shutdown this system and copy it to a 3rd site to host a separate set of business activityI would consider RMAN Duplicate in which case you may avoid the shutdown.
And for this :
resync the "mirror" with productionAll you have to do if DEFER the primary to the standby, then ENABLE and Data Guard will catch up.
--- Will post a detailed example here in a moment.
Right at the first of the year they wanted to work on our Primary server room ( Power ). What I did was switchover to the Standby but I kept log_archive_dest_state_2 on the new primary set to DEFER. Then I shutdown
all the databases at the Primary site. At the end of work two days later I started the databases at the Primary site in standby mode. Switched log_archive_dest_state_2 to ENABLE. When the databases were back in SYNC
I did another switchover and it was done. I used TAF and none of the users even noticed.
Best Regards
mseberg

Changing database to noarchivelog mode during impdp

Hi Guys,
I am using Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production on RHEL5.
I am in the middle on the impdp and I want my database to run on noarchivelog as it creates a lot of archivelogs.
Will it be proper if I stop the import:
e.g Import> STOP_JOB=IMMEDIATE
and shutdown the database put the database on noarchivelog mode.
then opne database and
impdp hr/hr@mydb ATTACH=myfulljob Will these work fine?
Or should I execute:
alter system archive log stop;
Please Help !!!!!!!!!!!

Vinod Dhandapani wrote:
Running the database in Noarchivelog mode means you should be ready to lose data incase there is any crash. I would recommend you to change the size of the redologs so that it will not create frequent archivelogs. Which does nothing about the space required for the archivelogs. If you are generating redo at the rate of 1gb/hour, you will consume archivelog dest space at the rate of 1gb/hour. Doesn't matter if those files are 10mb each or 100mb each.
If space is the problem then use a shell script to move the archivelog to another location (Tape)....And hopefully that shell script is invoking rman to do the work, so that in the event of recovery, rman will know that backups were taken and where they are located.
>
Incase you want to convert the database from archivelog to noarchivelog, follow the steps provided in the following link.
http://racadmin.blogspot.com/2011/06/convert-archivelog-mode-to-noarchivelog.html
Thanks

Database in Archivelog mode

Hi
All,
I have oracle 9.2.0.6 at my workplace.right now my database running in ARCHIVELOG MODE. I want to set it to NOARCHIVELOG MODE.
can I do on the fly? in other way, Do I need to shutdown and restart database?
Any help will be appreciated.
Thanks,
Vishal

Hi,
Issue the following commands to put a database into NOARCHVELOG mode:
1) Take Back up of Present SPfile by creating pfile
create pfile from present spfile.
2) Shutdown the database by SUTDOWN IMMEDIATE.
3) Take Cold backup of the database.
4) Change the parameter in the pfile.
log_archive_start = FALSE
#log_archive_dest_1 = 'LOCATION='Your location'
log_archive_dest_state_1 = DISABLE
#log_archive_format = %d_%t_%s.arc
5) And make a spfile from the modified pfile in default location .
6) Start the database with spfile.
SQL> CONNECT sys AS SYSDBA
SQL> STARTUP MOUNT ;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ARCHIVE LOG START;
SQL> ALTER DATABASE OPEN;
NOTE 1: Remember to take a baseline database backup right after disabling archivelog mode. Without it one would not be able to recover.
Regards
Jafar

Oracle Database in fibre mode

Hi everybody,
Recently i was going through one document where the Cons and prons of Running Oracle Database Server(10g) in Microsoft Windows Operating Systems was being Discussed.
There i came across of Running the oracle Database in Fibre Mode which as it states: Employs Oracle Scheduled Fibres instead of O/S Scheduled threads...
Can anybody share some more light on running the DB in Fibre Mode...
What is this Fibre Mode actually....
Any help Appreciated...
Thanks & Regards,
Prosenjit Mukherjee

The pros and cons can be found at a far more easily visible level than getting into fibres versus threads.
1. Put antivirus software on the Windows server and performance will become glacial
2. In testing in my lab, without antivirus software, Oracle Enterprise Linux gives superior performance too all versions of Windows except 2008 Server.

Database in backup mode

Hi Guys,
If I put my database in backup mode and perform the backup (hotbackup/online) of the database.
When I need to do restoration, do I need any archive logs at all? (not necessary to recover up to point in time) Can i just restore the datafiles and do a alter database open resetlogs?
Will the database be inconsistent and can't startup without applying any archive logs at all? as the datatabase is not shutdown when doing the backup.
thanks

dbaing wrote:
Hi Guys,
If I put my database in backup mode and perform the backup (hotbackup/online) of the database.
When I need to do restoration, do I need any archive logs at all? (not necessary to recover up to point in time) Can i just restore the datafiles and do a alter database open resetlogs?Yes, even if you won't be required to do an point in time recovery, you need the archive logs to make the database consistent which it won't be in a hot backup mode.
Will the database be inconsistent and can't startup without applying any archive logs at all? as the datatabase is not shutdown when doing the backup.Yep.
That said, use RMAN to do the same thing. It would be much better to use it than using the backup mode .
HTH
Aman....

Avoid putting database in quiesce mode

Similar Messages

Maybe you are looking for