Db_writer_processes alert log message

Oracle 11.2.0.3 running on HP-UX Itanium RX8640 with 16 CPUs and OS B.11.31
Upgraded to 11.2.0.3 last night and now I am receiving the following message in alert.log when starting database:
"NOTE: db_writer_processes has been changed from 4 to 1 due to NUMA requirements"
Any thoughts on what this means?

Is your system NUMA-enabled?
In a NUMA-enabled box, the minimum number of DBWR process is the number of processor groups, oracle MUST start this minimum of DBWR no matter the parameter you set.
You seem to have the opposite case, as in oracle is forcing it to 1. In this case, I'm led to believe that maybe oracle is mistakenly identifiying your system as NUMA perphaps.
Upload the results for this:
select a.ksppinm "Parameter",
b.ksppstvl "Session Value",
c.ksppstvl "Instance Value"
from x$ksppi a, x$ksppcv b, x$ksppsv c
where a.indx = b.indx and a.indx = c.indx
and a.ksppinm = '_db_block_numa';You may try to do this:
- Set the following OS variable in your database OS owner user profile: DISABLE_NUMA = true
- Set the DBWR to 4 in the SPFILE and bounce the database.
- Verify if the issue continues. In the OS: ps -ef | grep dbwr to see how many dbwr the instance spawned.

Similar Messages

10.2.0.4 Streams Alert log message

Good afternoon everyone,
Wanted to get some input on a message that ocasionally is logged to alert log of the owning QT instance in our RAC environment. In summary we have two RAC environments and perform bi-directional replication between the two environments. The message in question is usually logged in the busier environment.
krvxenq: Failed to acquire logminer dictionary lock
During that time it it seems that the Logminer process in not mining for changes, which could lead to latency between the two environments.
I have looked at AWR reports for times during the occurence of these errors and its common to see the following procedure running.
BEGIN dbms_capture_adm_internal.enforce_checkpoint_retention(:1, :2, :3); END;
This procedure, which I assume purges Capture chekcpoints that exceed the retention duration, takes between 10-20 minutes to run. The table which stores the checkpoints is logmnr_restart_ckpt$. I suspect that the issue could be caused by the size of the logmnr_restart_ckpt$ whcih is 12GB in our environemnt. A purge job needs to be scheduled to shrink the table.
If anyone has seen anything similar in her or his environment please offer any additional knowledge you may have about the topic.
Thank you,

There are 2 possibilities : either you have too much load on the table LOMNR_RESTART_CKPT$
due to the heavy system load or there is a bad streams query.
At this stage I would not like to admit the 'we-can't-cope-the-load' without having investigated more common issues.
Let's assume optimistically that one or many streams internal SQL do not run as intended. This is our best bet.
The table LOMNR_RESTART_CKPT$ is big is a perfect suspect.
If there is a problem with one of the queries involving this table, we find it using sys.col_usage$,
identify which columns are used and from there jump to SQL_ID checking plans:
set linesize 132 head on pagesize 33
col obj format a35 head "Table name"
col col1 format a26 head "Column"
col equijoin_preds format 9999999 head "equijoin|Preds" justify c
col nonequijoin_preds format 9999999 head "non|equijoin|Preds" justify c
col range_preds format 999999 head "Range|Pred" justify c
col equality_preds format 9999999 head "Equality|Preds" justify c
col like_preds format 999999 head "Like|Preds" justify c
col null_preds format 999999 head "Null|Preds" justify c
select r.name ||'.'|| o.name "obj" , c.name "col1",
      equality_preds, equijoin_preds, nonequijoin_preds, range_preds,
      like_preds, null_preds, to_char(timestamp,'DD-MM-YY HH24:MI:SS') "Date"
from sys.col_usage$ u, sys.obj$ o, sys.col$ c, sys.user$ r
where o.obj# = u.obj#    and o.name = 'LOMNR_RESTART_CKPT$'    -- and $AND_OWNER
        c.obj# = u.obj#    and
        c.col# = u.intcol# and
        o.owner# = r.user# and
       (u.equijoin_preds > 0 or u.nonequijoin_preds > 0)
   order by 4 desc
For each column predicate checks for full table scan :
define COL_NAME='col to check'
col PLAN_HASH_VALUE for 999999999999 head 'Plan hash |value' justify c
     col id for 999 head 'Id'
     col child for 99 head 'Ch|ld'
     col cost for 999999 head 'Oper|Cost'
     col tot_cost for 999999 head 'Plan|cost' justify c
     col est_car for 999999999 head 'Estimed| card' justify c
     col cur_car for 999999999 head 'Avg seen| card' justify c
     col ACC for A3 head 'Acc|ess'
     col FIL for A3 head 'Fil|ter'
     col OTHER for A3 head 'Oth|er'
     col ope for a30 head 'Operation'
     col exec for 999999 head 'Execution'
     break on PLAN_HASH_VALUE on sql_id on child
     select distinct
       a.PLAN_HASH_VALUE, a.id , a.sql_id, a.CHILD_NUMBER child , a.cost, c.cost tot_cost,
       a.cardinality est_car, b.output_rows/decode(b.EXECUTIONS,0,1,b.EXECUTIONS) cur_car,
       b.EXECUTIONS exec,
       case when length(a.ACCESS_PREDICATES) > 0 then ' Y' else ' N' end ACC,
       case when length(a.FILTER_PREDICATES) > 0 then ' Y' else ' N' end FIL,
       case when length(a.projection) > 0 then ' Y' else ' N' end OTHER,
        a.operation||' '|| a.options ope
from
    v$sql_plan a,
    v$sql_plan_statistics_all b ,
    v$sql_plan_statistics_all c
where
        a.PLAN_HASH_VALUE = b.PLAN_HASH_VALUE
    and a.sql_id = b.sql_id
    and a.child_number = b.child_number
    and a.id = b.id
    and a.PLAN_HASH_VALUE= c.PLAN_HASH_VALUE (+)
     and a.sql_id = c.sql_id
     and a.child_number = c.child_number and c.id=0
    and a.OBJECT_NAME = 'LOMNR_RESTART_CKPT$'       -- $AND_A_OWNER
    and   (instr(a.FILTER_PREDICATES,'&&COL_NAME') > 0
        or instr(a.ACCESS_PREDICATES,'&&COL_NAME') > 0
        or instr(a.PROJECTION, '$COL_NAME') > 0
order by sql_id, PLAN_HASH_VALUE, id
now for each query with a FULL table scan check the predicate and
see if adding and index will not improveAnother possibility :
One of the structure associated to streams, that you don't necessary see, may have remained too big.
Many of these structures are only accessed by streams maintenance using Full table scan.
They are supposed to remain small tables. But after a big streams crash, they inflate and whenever
the problem is solved, These supposed-to-be-small remain as the crash made them : too big.
In consequence, the FTS intended to run on small tables suddenly loop over stretches of empty blocks.
This is very frequent on big streams environment. You find these structures, if any exists using this query
Note that a long running of this query, imply big structures. You will have to assess if the number of rows is realistic with the number of blocks.
break on parent_table
col type format a30
col owner format a16
col index_name head 'Related object'
col parent_table format a30
prompt
prompt To shrink a lob associated to a queue type : alter table AQ$_<queue_table>_P modify lob(USER_DATA) ( shrink space ) cascade ;
prompt
select a.owner,a.table_name parent_table,index_name ,
       decode(index_type,'LOB','LOB INDEX',index_type) type,
      (select blocks from dba_segments where segment_name=index_name and owner=b.owner) blocks
   from
      dba_indexes a,
      ( select owner, queue_table table_name from dba_queue_tables
           where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
         union
         select owner, queue_table table_name from dba_queue_tables
                where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%')
     ) b
   where   a.owner=b.owner
       and a.table_name = b.table_name
       and a.owner not like 'SYS%' and a.owner not like 'WMSYS%'
union
-- LOB Segment for QT
select a.owner,a.segment_name parent_table,l.segment_name index_name, 'LOB SEG('||l.column_name||')' type,
                  (select sum(blocks) from dba_segments where segment_name = l.segment_name ) blob_blocks
             from dba_segments a,
                  dba_lobs l,
                  ( select owner, queue_table table_name from dba_queue_tables
                           where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
                    union
                    select owner, queue_table table_name from dba_queue_tables
                            where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%')
                  ) b
             where a.owner=b.owner and
                   a.SEGMENT_name = b.table_name and
                   l.table_name = a.segment_name and
                   a.owner not like 'SYS%' and a.owner not like 'WMSYS%'
union
-- LOB Segment of QT.._P
select a.owner,a.segment_name parent_table,l.segment_name index_name, 'LOB SEG('||l.column_name||')',
       (select sum(blocks) from dba_segments where segment_name = l.segment_name ) blob_blocks
   from dba_segments a,
          dba_lobs l,
          ( select owner, queue_table table_name from dba_queue_tables
                   where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
            union
            select owner, queue_table table_name from dba_queue_tables
                    where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%')
          ) b
   where a.owner=b.owner and
           a.SEGMENT_name = 'AQ$_'||b.table_name||'_P' and
           l.table_name = a.segment_name and
           a.owner not like 'SYS%' and a.owner not like 'WMSYS%'
union
-- Related QT
select a2.owner, a2.table_name parent_table, '-' index_name , decode(nvl(a2.initial_extent,-1), -1, 'IOT TABLE','NORMAL') type,
          case
               when decode(nvl(a2.initial_extent,-1), -1, 'IOT TABLE','NORMAL') = 'IOT TABLE'
                    then ( select sum(leaf_blocks) from dba_indexes where table_name=a2.table_name and owner=a2.owner)
               when decode(nvl(a2.initial_extent,-1), -1, 'IOT TABLE','NORMAL') = 'NORMAL'
                    then (select blocks from dba_segments where segment_name=a2.table_name and owner=a2.owner)
           end blocks
   from dba_tables a2,
       ( select owner, queue_table table_name from dba_queue_tables
                 where recipients='SINGLE' and owner NOT IN ('SYSTEM') and (compatible LIKE '8.%' or compatible LIKE '10.%')
          union all
          select owner, queue_table table_name from dba_queue_tables
                 where recipients='MULTIPLE' and (compatible LIKE '8.1%' or compatible LIKE '10.%' )
       ) b2
   where
         a2.table_name in ( 'AQ$_'||b2.table_name ||'_T' , 'AQ$_'||b2.table_name ||'_S', 'AQ$_'||b2.table_name ||'_H' , 'AQ$_'||b2.table_name ||'_G' ,
                            'AQ$_'|| b2.table_name ||'_I' , 'AQ$_'||b2.table_name ||'_C', 'AQ$_'||b2.table_name ||'_D', 'AQ$_'||b2.table_name ||'_P')
         and a2.owner not like 'SYS%' and a2.owner not like 'WMSYS%'
union
-- IOT Table normal
select
         u.name owner , o.name parent_table, c.table_name index_name, 'RELATED IOT' type,
         (select blocks from dba_segments where segment_name=c.table_name and owner=c.owner) blocks
   from sys.obj$ o,
        user$ u,
        (select table_name, to_number(substr(table_name,14)) as object_id , owner
                from dba_tables where table_name like 'SYS_IOT_OVER_%' and owner not like '%SYS') c
where
          o.obj#=c.object_id
      and o.owner#=u.user#
      and obj# in (
           select to_number(substr(table_name,14)) as object_id from dba_tables where table_name like 'SYS_IOT_OVER_%' and owner not like '%SYS')
order by parent_table , index_name desc;
"I hope it is one of the above case, otherwise thing may become more complicates.

RMAN ALert Log Message: ALTER SYSTEM ARCHIVE LOG

Created a new Database on Oracle 10.2.0.4 and now seeing "ALTER SYSTEM ARCHIVE LOG" in the Alert Log only when the online RMAN backup runs:
Wed Aug 26 21:52:03 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:52:03 2009
Thread 1 advanced to log sequence 35 (LGWR switch)
Current log# 2 seq# 35 mem# 0: /u01/app/oracle/oradata/aatest/redo02.log
Current log# 2 seq# 35 mem# 1: /u03/oradata/aatest/redo02a.log
Wed Aug 26 21:53:37 2009
ALTER SYSTEM ARCHIVE LOG
Wed Aug 26 21:53:37 2009
Thread 1 advanced to log sequence 36 (LGWR switch)
Current log# 3 seq# 36 mem# 0: /u01/app/oracle/oradata/aatest/redo03.log
Current log# 3 seq# 36 mem# 1: /u03/oradata/aatest/redo03a.log
Wed Aug 26 21:53:40 2009
Starting control autobackup
Control autobackup written to DISK device
handle '/u03/exports/backups/aatest/c-2538018370-20090826-00'
I am not issuing a log swiitch command. The RMAN commands I am running are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 2;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/exports/backups/aatest/%F';
CONFIGURE DEVICE TYPE DISK BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/u03/exports/backups/aatest/%d_%U';
BACKUP DATABASE PLUS ARCHIVELOG;
DELETE NOPROMPT OBSOLETE;
DELETE NOPROMPT ARCHIVELOG UNTIL TIME 'SYSDATE-2';
I do not see this message on any other 10.2.0.4 instances. Has anyone seen this and if so why is this showing in the log?
Thank you,
Curt Swartzlander

There's no problem with log switch. Please refer to documentation for more information on syntax "PLUS ARCHIVELOG"
http://download.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup003.htm#sthref377
Adding BACKUP ... PLUS ARCHIVELOG causes RMAN to do the following:
*1. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*2. Runs BACKUP ARCHIVELOG ALL. Note that if backup optimization is enabled, then RMAN skips logs that it has already backed up to the specified device.*
*3. Backs up the rest of the files specified in BACKUP command.*
*4. Runs the ALTER SYSTEM ARCHIVE LOG CURRENT command.*
*5. Backs up any remaining archived logs generated during the backup.*
This guarantees that datafile backups taken during the command are recoverable to a consistent state.

Alert log message and RMAN

Hi ,
following is the message from Alert log file and trace files.
This error encountered during RMAN backup but the backup was fine.
Didn't get any errors in RMAN log file.
Can anybody tell me what's the problem and solution?
----------- alert log file --------------------
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
Thu Mar 9 02:14:13 2006
Errors in file /app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc:
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
----------- trace files -------------------
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_950328.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 24
Unix process pid: 950328, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.053
*** SESSION ID:(77.60408) 2006-03-09 02:14:13.040
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
~
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1769540.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 25
Unix process pid: 1769540, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.311
*** SESSION ID:(53.5721) 2006-03-09 02:14:13.310
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4
/app/oracle/admin/SOFPDWB4/udump/sofpdwb4_ora_1392642.trc
Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
With the Partitioning and Oracle Data Mining options
JServer Release 9.2.0.5.0 - Production
ORACLE_HOME = /app/oracle/product/9.2.0
System name: AIX
Node name: sof016
Release: 1
Version: 5
Machine: 000CEF9C4C00
Instance name: SOFPDWB4
Redo thread mounted by this instance: 1
Oracle process number: 27
Unix process pid: 1392642, image: oracle@sof016 (TNS V1-V3)
*** 2006-03-09 02:14:13.549
*** SESSION ID:(59.52476) 2006-03-09 02:14:13.548
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: No such file or directory
Additional information: 4

Hello looks like when backing up database using RMAN it did not find the archivelogs hence you got the errors. Try doing "Crosscheck archivelog all" and see.
-Sri
<< Symptoms >>
Archivelog backup using RMAN failed with error :
RMAN-03002: failure of backup command at 08/18/2005 14:51:16
RMAN-06059: expected archived log not found, lost of archived log compromises recoverability
ORA-19625: error identifying file /arch/arch2/1_266_563489673.dbf
ORA-27037: unable to obtain file status
IBM AIX RISC System/6000 Error: 2: A file or directory in the path name does not exist.
Additional information: 3
<<Cause>>
RMAN get the information about what archivelog files are required to back up from the v$archived_log view.
RMAN cannot find the file archivelog in the archivelog destination. So itscannot continue taking the backup because this file does not exist.
<<Solution>>
Check if the archivelog exist in the log archive destination. If the is moved to some other location then restore the file back to its original location and then do RMAN back.
else
RMAN> crosscheck archivelog all;
After the crosscheck all take the rman backup.

Production database Alert log Message

Hi,
I am using oracle 10gR1 on windows.Recently i have created a physical standby database (sid=smtm) and production database (sid=mtm).My production alter log file dispaly some thing like please suggest my what it shows.
Mon Mar 02 00:18:31 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35722
Current log# 4 seq# 35722 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04.LOG
Current log# 4 seq# 35722 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO04_A.LOG
Mon Mar 02 00:18:31 2009
ARC1: Evaluating archive   log 2 thread 1 sequence 35721
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35721_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35721 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35721 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35721 destination SMTM)*Mon Mar 02 00:29:42 2009
Private_strands 7 at log switch
Thread 1 advanced to log sequence 35723
Current log# 3 seq# 35723 mem# 0: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03.LOG
Current log# 3 seq# 35723 mem# 1: D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\REDO03_A.LOG
Mon Mar 02 00:29:42 2009
ARC1: Evaluating archive   log 4 thread 1 sequence 35722
ARC1: Destination LOG_ARCHIVE_DEST_2 archival not expedited
Committing creation of archivelog 'E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_35722_500044525.ARC'
Invoking non-expedited destination LOG_ARCHIVE_DEST_2 thread 1 sequence 35722 host SMTM
*FAL[server, ARC1]: Begin FAL noexpedite archive (branch 500044525 thread 1 sequence 35722 dest SMTM)*
*FAL[server, ARC1]: Complete FAL noexpedite archive (thread 1 sequence 35722 destination SMTM)*
Thanks

Sorry i have no metalink account.
On production database there is no any ORA error and on standby database Alert log shows.
Mon Mar 02 03:40:38 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35728_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35729_500044525.ARC'
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35730_500044525.ARC'Mon Mar 02 04:29:14 2009
RFS[1]: No standby redo logfiles created
RFS[1]: Archived Log: 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Committing creation of archivelog 'E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35731_500044525.ARC'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...Mon Mar 02 11:01:57 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Mon Mar 02 11:01:57 2009
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35553_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER    CONTINUE DEFAULT ...Mon Mar 02 11:02:05 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35554_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Mon Mar 02 11:02:14 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\PRODUCT\10.1.0\ARCHIVES\MTM_945F37AC_1_35555_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Regards
Thanks for reply.

Rac Alert log message '

Dear All
My database is running on RAC configuration and the version is 10.1.0.5
Everyday i come across this error in the alert log of both the instances,
Unable to restore resource manager plan to '':
ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00439: feature not enabled: Database resource manager
pls help me if u have come across this error

Check metalink note 735798.1
HTH...

Alert log message : Load Indicator not supported by OS

I am running Oracle 8.1.5 on Red Hat Linux 6.1 , I am getting an alert message
"Load Indicator not supported by OS"
Kindly help me urgently on the below email address
[email protected]
Thanks

Try turning of the Multi-threaded server option (i.e. comment out "mts" references in the init[SID].ora file). This appears to be an MTS-related bug.
HTH
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by (Viral Shah):
I am running Oracle 8.1.5 on Red Hat Linux 6.1 , I am getting an alert message
"Load Indicator not supported by OS"
Kindly help me urgently on the below email address
[email protected]
Thanks<HR></BLOCKQUOTE>
null

DG Observer triggering SIGSEGV Address not mapped to object errors in alert log

Hi,
I've got a Data Guard configuration using two 11.2.0.3 single instance databases. The configuration has been configured for automatic failover and I have an observer running on a separate box.
This fast-start failover configuration has been in place for about a month and in the last week, numerous SEGSEGV (address not mapped to object) errors are reported in the alert log. This is happening quite frequently (every 4/5 minutes or so).
The corresponding trace files show the process triggering the error coming from the observer.
Has anyone experienced this problem? I'm at my wits end trying to figure out how to fix the configuration to eliminate this error.
I must also note that even though this error is occurring a lot, it doesn't seem to be affecting any of the database functionality.
Help?
Thanks in advance.
Beth

Hi..   The following is the alert log message, the traced file generated, and the current values of the data guard configuration. In addition, as part of my research, I attempted to apply patch 12615660 which did not take care of the issue. I also set the inbound_connection_timeout parameter to 0 and that didn't help either. I'm still researching but any pointer in the right direction is very much appreciated.
Error in Alert Log
Thu Apr 09 10:28:59 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
Errors in file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc (incident=69298):
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.
Thu Apr 09 10:29:02 2015
Sweep [inc][69298]: completed
Trace file:
Trace file /u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/trace/<SID>_ora_29902.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
With the Partitioning and Oracle Label Security options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.3/dbhome_1
System name:    Linux
Node name:      <host name>
Release:        2.6.32-431.17.1.el6.x86_64
Version:        #1 SMP Wed May 7 14:14:17 CDT 2014
Machine:        x86_64
Instance name: <SID>
Redo thread mounted by this instance: 1
Oracle process number: 19
Unix process pid: 29902, image: oracle@<host name>
*** 2015-04-09 10:28:59.966
*** SESSION ID:(416.127) 2015-04-09 10:28:59.966
*** CLIENT ID:() 2015-04-09 10:28:59.966
*** SERVICE NAME:(<db_unq_name>) 2015-04-09 10:28:59.966
*** MODULE NAME:(dgmgrl@<observer host> (TNS V1-V3)) 2015-04-09 10:28:59.966
*** ACTION NAME:() 2015-04-09 10:28:59.966
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x9] [PC:0x85CE503, nstimexp()+71] [flags: 0x0, count: 1]
DDE: Problem Key 'ORA 7445 [nstimexp()+71]' was flood controlled (0x6) (incident: 69298)
ORA-07445: exception encountered: core dump [nstimexp()+71] [SIGSEGV] [ADDR:0x9] [PC:0x85CE503] [Address not mapped to object] []
ssexhd: crashing the process...
Shadow_Core_Dump = PARTIAL
ksdbgcra: writing core file to directory '/u01/app/oracle/diag/rdbms/<db_unq_name>/<SID>/cdump'
Data Guard Configuration
DGMGRL> show configuration verbose;
Configuration - dg_config
Protection Mode: MaxPerformance
Databases:
    dbprim - Primary database
    dbstby - (*) Physical standby database
(*) Fast-Start Failover target
Properties:
    FastStartFailoverThreshold      = '30'
    OperationTimeout                = '30'
    FastStartFailoverLagLimit       = '180'
    CommunicationTimeout            = '180'
    FastStartFailoverAutoReinstate = 'TRUE'
    FastStartFailoverPmyShutdown    = 'TRUE'
    BystandersFollowRoleChange      = 'ALL'
Fast-Start Failover: ENABLED
Threshold:        30 seconds
Target:           dbstby
Observer:         observer_host
Lag Limit:        180 seconds
Shutdown Primary: TRUE
Auto-reinstate:   TRUE
Configuration Status:
SUCCESS
DGMGRL> show database verbose dbprim
Database - dbprim
Role:            PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
    DG_CONFIG
Properties:
    DGConnectIdentifier             = 'dbprim'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'MANUAL'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = 'dbstby'
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = ‘<sid>’
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose dbstby
Database - dbstby
Role:            PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag:   0 seconds
Apply Lag:       0 seconds
Real Time Query: ON
Instance(s):
    DG_CONFIG
Properties:
    DGConnectIdentifier             = 'dbstby'
    ObserverConnectIdentifier       = ''
    LogXptMode                      = 'ASYNC'
    DelayMins                       = '0'
    Binding                         = 'optional'
    MaxFailure                      = '0'
    MaxConnections                  = '1'
    ReopenSecs                      = '300'
    NetTimeout                      = '30'
    RedoCompression                 = 'DISABLE'
    LogShipping                     = 'ON'
    PreferredApplyInstance          = ''
    ApplyInstanceTimeout            = '0'
    ApplyParallel                   = 'AUTO'
    StandbyFileManagement           = 'AUTO'
    ArchiveLagTarget                = '0'
    LogArchiveMaxProcesses          = '4'
    LogArchiveMinSucceedDest        = '1'
    DbFileNameConvert               = ''
    LogFileNameConvert              = ''
    FastStartFailoverTarget         = 'dbprim'
    InconsistentProperties          = '(monitor)'
    InconsistentLogXptProps         = '(monitor)'
    SendQEntries                    = '(monitor)'
    LogXptStatus                    = '(monitor)'
    RecvQEntries                    = '(monitor)'
    SidName                         = ‘<sid>’
    StaticConnectIdentifier         = '(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=<db host name>)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=<service_name>)(INSTANCE_NAME=<sid>)(SERVER=DEDICATED)))'
    StandbyArchiveLocation          = 'USE_DB_RECOVERY_FILE_DEST'
    AlternateLocation               = ''
    LogArchiveTrace                 = '0'
    LogArchiveFormat                = '%t_%s_%r.dbf'
    TopWaitEvents                   = '(monitor)'
Database Status:
SUCCESS

Alert log: Private strand flush not complete

We are runnig Oracle 10.2
I noticed we are getting "Private strand flush not complete" line in alert log file.
Here is the snippet from the actual alert log file.
Thu Aug 31 06:27:23 2006
Thread 1 advanced to log sequence 17998
Current log# 3 seq# 17998 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 17998 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 06:31:12 2006
Thread 1 advanced to log sequence 17999
Current log# 4 seq# 17999 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 17999 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 06:35:49 2006
Thread 1 advanced to log sequence 18000
Current log# 5 seq# 18000 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18000 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 06:40:59 2006
Thread 1 advanced to log sequence 18001
Current log# 6 seq# 18001 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18001 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 06:45:03 2006
Thread 1 advanced to log sequence 18002
Current log# 1 seq# 18002 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18002 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 06:49:21 2006
Thread 1 advanced to log sequence 18003
Current log# 2 seq# 18003 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18003 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 06:52:04 2006
Thread 1 cannot allocate new log, sequence 18004
Private strand flush not complete
Current log# 2 seq# 18003 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18003 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thread 1 advanced to log sequence 18004
Current log# 3 seq# 18004 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18004 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.logThu Aug 31 06:55:40 2006
Thread 1 advanced to log sequence 18005
Current log# 4 seq# 18005 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18005 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 06:59:21 2006
Thread 1 advanced to log sequence 18006
Current log# 5 seq# 18006 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18006 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 07:03:35 2006
Thread 1 advanced to log sequence 18007
Current log# 6 seq# 18007 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18007 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 07:08:28 2006
Thread 1 advanced to log sequence 18008
Current log# 1 seq# 18008 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18008 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 07:11:31 2006
Thread 1 advanced to log sequence 18009
Current log# 2 seq# 18009 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18009 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 07:15:32 2006
Thread 1 advanced to log sequence 18010
Current log# 3 seq# 18010 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18010 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 07:23:10 2006
Thread 1 advanced to log sequence 18011
Current log# 4 seq# 18011 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18011 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 07:28:41 2006
Thread 1 advanced to log sequence 18012
Current log# 5 seq# 18012 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18012 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 07:32:35 2006
Thread 1 advanced to log sequence 18013
Current log# 6 seq# 18013 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18013 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 07:36:00 2006
Thread 1 advanced to log sequence 18014
Current log# 1 seq# 18014 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18014 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 07:39:42 2006
Thread 1 advanced to log sequence 18015
Current log# 2 seq# 18015 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18015 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 07:44:36 2006
Thread 1 advanced to log sequence 18016
Current log# 3 seq# 18016 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18016 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 07:49:13 2006
Thread 1 advanced to log sequence 18017
Current log# 4 seq# 18017 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18017 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 07:57:52 2006
Thread 1 advanced to log sequence 18018
Current log# 5 seq# 18018 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18018 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 08:02:52 2006
Thread 1 advanced to log sequence 18019
Current log# 6 seq# 18019 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18019 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 08:05:50 2006
Thread 1 advanced to log sequence 18020
Current log# 1 seq# 18020 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18020 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 08:08:24 2006
Thread 1 cannot allocate new log, sequence 18021
Private strand flush not complete
Current log# 1 seq# 18020 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18020 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thread 1 advanced to log sequence 18021
Current log# 2 seq# 18021 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18021 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 08:09:53 2006
Thread 1 advanced to log sequence 18022
Current log# 3 seq# 18022 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18022 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 08:12:02 2006
Thread 1 advanced to log sequence 18023
Current log# 4 seq# 18023 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18023 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 08:14:09 2006
Thread 1 advanced to log sequence 18024
Current log# 5 seq# 18024 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18024 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 08:14:22 2006
Thread 1 advanced to log sequence 18025
Current log# 6 seq# 18025 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18025 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 08:21:13 2006
Thread 1 advanced to log sequence 18026
Current log# 1 seq# 18026 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18026 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 08:23:42 2006
Thread 1 advanced to log sequence 18027
Current log# 2 seq# 18027 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18027 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 08:25:12 2006
Thread 1 advanced to log sequence 18028
Current log# 3 seq# 18028 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18028 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 08:32:06 2006
Thread 1 advanced to log sequence 18029
Current log# 4 seq# 18029 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18029 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 08:40:34 2006
Thread 1 advanced to log sequence 18030
Current log# 5 seq# 18030 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18030 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 08:41:25 2006
Thread 1 advanced to log sequence 18031
Current log# 6 seq# 18031 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18031 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 08:43:10 2006
Thread 1 advanced to log sequence 18032
Current log# 1 seq# 18032 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18032 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 08:44:22 2006
Thread 1 advanced to log sequence 18033
Current log# 2 seq# 18033 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18033 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 08:45:40 2006
Thread 1 advanced to log sequence 18034
Current log# 3 seq# 18034 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18034 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 08:46:20 2006
Thread 1 advanced to log sequence 18035
Current log# 4 seq# 18035 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18035 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 08:49:32 2006
Thread 1 advanced to log sequence 18036
Current log# 5 seq# 18036 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18036 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 08:50:51 2006
Thread 1 advanced to log sequence 18037
Current log# 6 seq# 18037 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18037 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 08:52:24 2006
Thread 1 advanced to log sequence 18038
Current log# 1 seq# 18038 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18038 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Thu Aug 31 08:53:47 2006
Thread 1 advanced to log sequence 18039
Current log# 2 seq# 18039 mem# 0: /Mvol01/oradata/amgoasp0/redo02a.log
Current log# 2 seq# 18039 mem# 1: /Mvol02/oradata/amgoasp0/redo02b.log
Thu Aug 31 08:54:55 2006
Thread 1 advanced to log sequence 18040
Current log# 3 seq# 18040 mem# 0: /Mvol01/oradata/amgoasp0/redo03a.log
Current log# 3 seq# 18040 mem# 1: /Mvol02/oradata/amgoasp0/redo03b.log
Thu Aug 31 08:56:51 2006
Thread 1 advanced to log sequence 18041
Current log# 4 seq# 18041 mem# 0: /Mvol01/oradata/amgoasp0/redo04a.log
Current log# 4 seq# 18041 mem# 1: /Mvol02/oradata/amgoasp0/redo04b.log
Thu Aug 31 08:58:12 2006
Thread 1 advanced to log sequence 18042
Current log# 5 seq# 18042 mem# 0: /Mvol01/oradata/amgoasp0/redo05a.log
Current log# 5 seq# 18042 mem# 1: /Mvol02/oradata/amgoasp0/redo05b.log
Thu Aug 31 08:59:14 2006
Thread 1 advanced to log sequence 18043
Current log# 6 seq# 18043 mem# 0: /Mvol01/oradata/amgoasp0/redo06a.log
Current log# 6 seq# 18043 mem# 1: /Mvol02/oradata/amgoasp0/redo06b.log
Thu Aug 31 09:00:17 2006
Thread 1 advanced to log sequence 18044
Current log# 1 seq# 18044 mem# 0: /Mvol01/oradata/amgoasp0/redo01a.log
Current log# 1 seq# 18044 mem# 1: /Mvol02/oradata/amgoasp0/redo01b.log
Can some one help me to understand what does it mean? Do we need to take any action?
TIA.
Regards,
Dharmesh Patel

There's a metalink note about this
(Alert Log Messages: Private Strand Flush Not Complete
Note:372557.1), but the most importannt message is :
These messages are not a cause for concern unless there is a significant gap between the "cannot allocate new log" message and the "advanced to log sequence" message.
This issue is infact not a bug and is expected behaviour.
Werner

Unix command needed to search alert log

Hi. Im trying to search the alert log file to see if there is any thing related to the checkpointing process.
Specifically Im looking for anything that includes "Checkpoint not complete".
If anyone knows the command for searching the file in UNIX for this then please post here!
Many thanks
DA

Hi Dan,
"Checkpoint not complete".In UNIX try: http://www.dba-oracle.com/op_unix_16_cat_grep_commands.htm
grep "checkpoint not complete" /u01/app/..../alertSID.log
In Windows:
http://www.dba-oracle.com/t_windows_alert_log_script.htm
I e-mail myself important alert log messages, using this technique:
http://www.remote-dba.cc/oracle_tips_table_alerts.htm
Also, you can read the alert log from SQL, if you want:
http://www.dba-oracle.com/t_oracle_alert_log_sql_external_tables.htm
Hope this helps. . .
Donald K. Burleson
Oracle Press author
Author of "Oracle Tuning: The Definitive Reference":
http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

Customize alerts on ALERT.log file? And another question

We just setup and have started to use Grid Control. So far, I have been very pleased with what I have seen.
Just some questions though.
Is there a way to customize the "Generic Alert Log Error Status"?
Can we have exclusions for that alert? We get are getting messages on alerts for a bug that exists in one of our DB's. If we can some how exclude this particular error, that would be great. That possible?
Secondly, can you schedule checks on a database to check the state of the database? This is something I would like to do if possible.
THanks.

Go to targets - databases - <database>
On this page on the left side, you'll see a heading "Diagnostic Summary"
The you'll see something like:Alert Log <date>
Click on the date, go to the bottom of the page and click on "Generic Alert Log Error Monitoring Configuration"
Here you can configure exactly what alert log messages you want.
Yes, depending on what it is you want to do. Look at User Defined Metrics, Reports and possibly Jobs to see what fits best with want you want to do.

Need to find the way to get the actual error message in the alert log.

Hi,
I have configured OEM 11G and monitoring target versions are from 9i to 11g. Now my problem is i have defined the metrics for monitoring the alert log contents and OEM is sending alert if there is any error in the alert log but it is not showing the actual error message just it is showing as below.
============================
Target Name=IDMPRD
Target type=Database Instance
Host=oidmprd01.ho.abc.com
Occurred At=Dec 21, 2011 12:05:21 AM GMT+03:00
Message=1 distinct types of ORA- errors have been found in the alert log.
Metric=Generic Alert Log Error Status
Metric value=1
Severity=Warning
Acknowledged=No
Notification Rule Name=RULE_4_PROD_DATABASES
Notification Rule Owner=SYSMAN
============================
Is there any way to get the complete error details in the OEM alert itself.
Regards
DBA.

You need to look at the Alert Log error messages, not the "status" messages. See doc http://docs.oracle.com/cd/E11857_01/em.111/e16285/oracle_database.htm#autoId2

Can I reduce the message in the alert log ?

Hi All,
I receive lot of message in my alert log. Can I reduce the message in the alert log ? please help me
Tue Sep 12 13:53:45 2006
ARC0: received prod
Tue Sep 12 13:56:13 2006
LGWR: prodding the archiver
Thread 1 advanced to log sequence 2105494
Tue Sep 12 13:56:13 2006
Current log# 4 seq# 2105494 mem# 0: E:\ORACLE\MMP\LOG\REDO04.LOG
Current log# 4 seq# 2105494 mem# 1: C:\ORACLE\MMP\LOG\REDO04.LOG
Tue Sep 12 13:56:14 2006
ARC1: received prod
Tue Sep 12 13:56:14 2006
ARC1: Beginning to archive log# 3 seq# 2105493
ARC1: Completed archiving log# 3 seq# 2105493
ARC1: re-scanning for new log files
ARC1: prodding the archiver
Tue Sep 12 13:56:18 2006
ARC0: received prod
Tue Sep 12 13:58:26 2006
LGWR: prodding the archiver
Thread 1 advanced to log sequence 2105495
Tue Sep 12 13:58:26 2006
Current log# 1 seq# 2105495 mem# 0: C:\ORACLE\MMP\LOG\REDO01.LOG
Current log# 1 seq# 2105495 mem# 1: E:\ORACLE\MMP\LOG\REDO01.LOG
Tue Sep 12 13:58:27 2006
ARC1: received prod
Tue Sep 12 13:58:27 2006
ARC1: Beginning to archive log# 4 seq# 2105494
ARC1: Completed archiving log# 4 seq# 2105494
ARC1: re-scanning for new log files
ARC1: prodding the archiver
Tue Sep 12 13:58:31 2006
ARC0: received prod

Hi,
The Oracle database writes an audit trail of the archived redo log files received from the primary database into a trace file. This parameter specifies the level of trace that should be generated when redo logs are archived. The value of the parameter indicates the level of trace to be generated.
Level      Description
0      Disabled (default)
1      Track archival of redo log file
2      Track status of each archivelog destination
4      Track archival operational phase
8      Track archivelog destination activity
16      Track detailed archivelog destination activity
32      Track archivelog destination parameter changes
64      Track ARCn process state activity
128      Track FAL server related activities
It can be used in a Primary Database or Standby Database
for more details see:
http://docs.nojabrsk.ru/sol10/B12037_01/server.101/b10823/trace.htm
Cheers

After effects alert last log message

What to do when I get this message when opening after effects cs6?
cs6 after effects Alert last log message was: <140735200987488> >GPUManager> <2>Sniffer Result Code: 3. Generating crash log, which may take a few minutes.
I just cannot open after effects anymore.

Hi,
Now I here again, my Mac os X version is 10.7.5
Prosessor is 2.66ghz intel core 2 duo
memory 4gt 1067 mhz DDR3
Graphic card: NVIDIA GeForce 9400 256 MB
After effects version is 11.0 if I am checking it right
I have used after effects about three mounths and suddenly it just quiet working. That´s not good for my work. Luckily I got almost everything in premiere pro. Because I can´t even use files from AE in Premiere pro.
I have rebooted machine.
I haven´t reinstall AE yet. I will.
How do I trash preferences and from where? I cannot open AE at all.

SMON ABOUT TO RECOVER UNDO SEGMENT s messages in alert log

Problem
======
There are lots of messages appearing in alert log of the following form:
SMON: about to recover undo segment %s
SMON: mark undo segment %s as available
Reason
======
When the recovery is going on after a abnormal shutdown. Cause These errors do not indicate rollback segment corruption. In oracle8i, this may becoz of problem with the "rollback_segments" parameter in the init.ora. where as in oracle9i, When the instance is shutdown, during the next startup instance recovery needs to take place.
In AUM we do not have any control over which undo segments will brought online after the instance startup.When SMON finds such offline undo segments with transactions needing recovery ,then it does what is intended to do recovery.
Solution
======
with oracle8i, we need to cross check rollback_segments" parameter in the init.ora
with oracle9i,
first note down segment from SMON: mark undo segment %s as available
sqlplus "/ as sysdba"
alter session set "_smu_debug_mode"=4;
alter rollback segment <offline segment name> online;
e.g. alter rollback segment "_SYSSMU11$" online;
Where 11 is the number that is appearing in the messages in the alert log.

What's the point duplicate metalink doc here,
SMON: ABOUT TO RECOVER UNDO SEGMENT %s messages in alert log
Doc ID: Note:266159.1
besides it's violation of Oracle support service contract.

Db_writer_processes alert log message

Similar Messages

Maybe you are looking for