Printable View
8.1.7 - advance server linux
Database running in archive log mode.
To stop the archiving without shutting down the DB i executed this command at the system schema user
ALTER SYSTEM ARCHIVE LOG STOP;
system altered.
after this i wanted to check at the SQL prompt connecting as system
to issues this command
select * from v$database;
when i enter username/password it is not getting me sql prompt. i waited for 2 5 minutes but still not getting the sql prompt
what could be the reason.?
Have a look in the alrt.log
(I'd guess it's hung trying to switch log files when the next one hasn't been archived yet.)
Thu Jan 27 02:24:23 2005
Thread 1 advanced to log sequence 2700152
Current log# 2 seq# 2700152 mem# 0: /buildback/ora/app/oracle/oradata/HNS/redo02.log
Thu Jan 27 02:25:00 2005
Thread 1 advanced to log sequence 2700153
Current log# 3 seq# 2700153 mem# 0: /buildback/ora/app/oracle/oradata/HNS/redo01.log
Thu Jan 27 02:25:09 2005
ORACLE Instance HNS - Can not allocate log, archival required
ARCH: Connecting to console port...
Thread 1 cannot allocate new log, sequence 2700154
All online logs needed archiving
Current log# 3 seq# 2700153 mem# 0: /buildback/ora/app/oracle/oradata/HNS/redo01.log
Thu Jan 27 02:43:53 2005
Restarting dead background process EMN0
EMN0 started with pid=299
Thu Jan 27 02:43:56 2005
As your database is in Archivelog mode and you have disabled the automatic archiving, do a manual archiving , its just waiting for the redo logs to be archived.
VoilĂ*!Quote:
Originally posted by gajananpkini
ORACLE Instance HNS - Can not allocate log, archival required
ARCH: Connecting to console port...
Thread 1 cannot allocate new log, sequence 2700154
All online logs needed archiving
Logon " / as sysdba" and restart the archiving e.g. ALTER SYSTEM ARCHIVE LOG START;
manual says that we can stop archiving any time,
no need to restart the db
but what caused the issue here
I suppose you could have issued log switches to ensure there wasn't anything left in your online redo logs that needed archiving before you switched it off.
As long as it's in ARCHIVELOG MODE the logs will need to be archived - so it should be very exceptional to stop the archiving process (which normally should be done automatically: ALTER SYSTEM ARCHIVE LOG START; ) Yes, you can stop the process, but WHY?Quote:
Originally posted by gajananpkini
manual says that we can stop archiving any time,
no need to restart the db
but what caused the issue here
OK: What are you really trying to do? What is your objective?