monitoring alert log [message #242117] |
Thu, 31 May 2007 13:02 |
jagmohan81@gmail.com
Messages: 6 Registered: May 2007 Location: new jersey
|
Junior Member |
|
|
HI Oracle Guru's
My dev database is not running in archivelog mode .
when i check my alert log
i see a constant message which is being generated after every minute.
Thu May 31 13:35:07 2007
ARC1: Archiving disabled
Thu May 31 13:36:08 2007
ARC1: Archiving disabled
Thu May 31 13:37:09 2007
ARC1: Archiving disabled
Thu May 31 13:38:11 2007
ARC1: Archiving disabled
Thu May 31 13:39:12 2007
ARC1: Archiving disabled
Thu May 31 13:40:14 2007
ARC1: Archiving disabled
Thu May 31 13:41:15 2007
ARC1: Archiving disabled
Thu May 31 13:42:17 2007
ARC1: Archiving disabled
Thu May 31 13:43:18 2007
ARC1: Archiving disabled
Thu May 31 13:44:20 2007
ARC1: Archiving disabled
Thu May 31 13:45:21 2007
ARC1: Archiving disabled
Thu May 31 13:46:22 2007
ARC1: Archiving disabled
Thu May 31 13:47:24 2007
ARC1: Archiving disabled
Thu May 31 13:48:25 2007
ARC1: Archiving disabled
Thu May 31 13:49:27 2007
ARC1: Archiving disabled
Thu May 31 13:50:28 2007
ARC1: Archiving disabled
Thu May 31 13:51:30 2007
ARC1: Archiving disabled
Thu May 31 13:52:31 2007
ARC1: Archiving disabled
Thu May 31 13:53:32 2007
ARC1: Archiving disabled
Thu May 31 13:54:34 2007
ARC1: Archiving disabled
what can be reason for this message .
How can i disable this message.
Thanks in advance.
Jagmohan
|
|
|
|
Re: monitoring alert log [message #242163 is a reply to message #242117] |
Thu, 31 May 2007 16:37 |
jagmohan81@gmail.com
Messages: 6 Registered: May 2007 Location: new jersey
|
Junior Member |
|
|
I am extremely sorry that i have written that my database is in archivelog mode , my mistake in typing .
SQL> select log_mode from v$database;
LOG_MODE
------------
NOARCHIVELOG
SQL> select * from v$version;
BANNER
----------------------------------------------------------------
Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Prod
PL/SQL Release 10.1.0.3.0 - Production
CORE 10.1.0.3.0 Production
TNS for Linux: Version 10.1.0.3.0 - Production
NLSRTL Version 10.1.0.3.0 - Production
SQL> show parameter log_archive_start
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
log_archive_start boolean FALSE
SQL>
But the problem is the same, as i have discussed earlier
[Updated on: Thu, 31 May 2007 16:39] Report message to a moderator
|
|
|
|
Re: monitoring alert log [message #242310 is a reply to message #242117] |
Fri, 01 June 2007 09:56 |
jsingh
Messages: 36 Registered: June 2007 Location: ny
|
Member |
|
|
SQL> archive log list
Database log mode No Archive Mode
Automatic archival Disabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 13336
Current log sequence 13338
Thanks Michel for your patience and replies.
Regards
Jagmohan
|
|
|
|
Re: monitoring alert log [message #242406 is a reply to message #242117] |
Fri, 01 June 2007 16:43 |
jagmohan81@gmail.com
Messages: 6 Registered: May 2007 Location: new jersey
|
Junior Member |
|
|
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE MOUNT
Fri May 18 20:20:48 2007
Starting Data Guard Broker (DMON)
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=14762
ARC0: Archival started
Fri May 18 20:20:48 2007
ARCH: STARTING ARCH PROCESSES COMPLETE
Fri May 18 20:20:48 2007
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC1 started with pid=15, OS id=14764
ARC1: Archival started
ARC1: Becoming the heartbeat ARCH
Fri May 18 20:20:55 2007
alter database noarchivelog
Fri May 18 20:20:55 2007
Completed: alter database noarchivelog
Fri May 18 20:21:06 2007
alter database open
Fri May 18 20:21:06 2007
Maximum redo generation record size = 120832 bytes
Maximum redo generation change vector size = 116476 bytes
Private_strands 4 at log switch
Thread 1 opened at log sequence 13007
Current log# 1 seq# 13007 mem# 0: /usr/local/oracle/product/10.1.0/Db_1/oradat
a/MODVMXLA/redo01.log
Successful open of redo thread 1
Fri May 18 20:21:06 2007
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri May 18 20:21:06 2007
SMON: enabling cache recovery
Fri May 18 20:21:06 2007
Successfully onlined Undo Tablespace 1.
Fri May 18 20:21:06 2007
SMON: enabling tx recovery
Fri May 18 20:21:06 2007
Database Characterset is WE8ISO8859P1
Fri May 18 20:21:06 2007
Starting background process QMNC
QMNC started with pid=16, OS id=14819
Fri May 18 20:21:06 2007
replication_dependency_tracking turned off (no async multimaster replication fou
nd)
Fri May 18 20:21:07 2007
Starting background process MMON
Starting background process MMNL
MMON started with pid=17, OS id=14821
MMNL started with pid=18, OS id=14823
Fri May 18 20:21:07 2007
Completed: alter database open
Fri May 18 20:21:10 2007
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Fri May 18 20:21:49 2007
ARC1: Archiving disabled
Fri May 18 20:22:50 2007
ARC1: Archiving disabled
Fri May 18 20:23:52 2007
IS IT HAS SOMETHING TO DO WITH DATA BROKER.( COZ MAY BE SOMEBODY BEFORE ME TRIED DATAGUARD CONFIGURATION ON IT)
RIGHT NOW I HAVE NO DATAGUARD INSTALLED ON THE DATABASE.
NOW WHEN I DO
SQL> show parameter dg_broker_start;
NAME TYPE VALUE
------------------------------------ ----------- ------------------------------
dg_broker_start boolean TRUE
SQL>
MY DATABASE IS RUNNING WITH SPFILE .
I CANNOT DISABLE THIS ALTER SYSTEM SET DG_BROKER_START='FALSE';
ALSO NOT EVEN BY
DGMGRL
CONNECT /
DISABLE CONFIGURATION.
DGMGRL> DISABLE configuration
Error: ORA-16596: object not part of the Data Guard broker configuration
unable to describe configuration
IDONT KNOW WHAT IS IT.......
??????
|
|
|
|
Re: monitoring alert log [message #242460 is a reply to message #242117] |
Sat, 02 June 2007 06:13 |
jagmohan81@gmail.com
Messages: 6 Registered: May 2007 Location: new jersey
|
Junior Member |
|
|
Thanks michel
Its weekend now , you better enjoy ur weekend.
Thanks for ur time to time help.
I believe the suggestion you gave me should work.
I will check out again when i get back on monday.
Thanks
&
Regards
Jagmohan
|
|
|