Parameter LOG_BUFFER

Hello guys,
a litte question about parameter LOG_BUFFER.
I thought all the time, that the modified data are immediately written to the redo log files by the LGWR, if a value is changed. But in the documentation for parameter LOG_BUFFER stands:
LOG_BUFFER specifies the amount of memory (in bytes) that Oracle uses when buffering redo entries to a redo log file. Redo log entries contain a record of the changes that have been made to the database block buffers. The LGWR process writes redo log entries from the log buffer to a redo log file.
In general, larger values for LOG_BUFFER reduce redo log file I/O, particularly if transactions are long or numerous. In a busy system, a value 65536 or higher is reasonable.
http://saturn.uab.es/server.920/a96536/ch1100.htm
So i think, if the instance and db crashed and the redo log entries are cashed in the sga (and not written immediately to redo files), they are lost and no recovery can be done.
Or do i missunderstood the documentation about that parameter? But then how can be I/O reduced, if the data is written immediately to redolog files....
Thanks
Regards
Stefan

Ahh ok ...
But a last information about the log_buffer:
Here is a statement from an articel:
LGWR will clean up buffers if log_buffer 1/3 full, 1mb log_buffer full or commit occurs. If we change log_buffer to 10mb will it helpful to improve performance.
Ok now ... the log_buffer is in the sga.. and i activated Automatic Memory Management (sga_target is set)
Now i saw this strange thing...
Oracle AMM only sizes the follwing parameters SID.* (example values from my database) ... the sga_target and log_buffer i was setting by hand:
SID.__db_cache_size=2785017856
SID.__java_pool_size=16777216
SID.__large_pool_size=16777216
SID.__shared_pool_size=838860800
SID.__streams_pool_size=0
*.sga_target=3670016000
*.log_buffer=1048576
I set log_buffer to 1048576 in my spfile... but if i make "show parameter" ... i get the following:
SQL> show parameter log_buffer
NAME TYPE VALUE
log_buffer integer 14254080
So Oracle sizes the log_buffer with AMM ... but didn't write it down to the spfile like the other caches (db_cache_size, java_pool_size, and so on...)
Kind of strange...
Regards
Stefan

Similar Messages

  • BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, val

    Dear SAP Gurus,
    We are getting the following error in Check Database in DB13
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14254080 (>< 4096,512 KB)
    The current Parameter : 14254080
    We have change the parameter as per SAP Note#830576, still the same error is comming.
    Kinldy Help.
    Thanks in advance.

    Hi Vijay,
    Are you trying to change log_buffer to a smaller size and you can't? If you on Oracle 10g, you won't be able to reduce log_buffer as according to Oracle Metalink 351857.1, "The Log_buffer Default Size Cannot Be Reduced In 10g R2".
    If you are concern about the warning in DB13, go to txn DB17 to change the condition will help to get rid of the warning.
    Regards,
    Annie

  • Can we change log_buffer parameter online e.g. when all users are working..

    Hi,
    Can we change log_buffer parameter online e.g. when all users are working.. ???
    What is relation between redo buffer in sga and log_buffer parameter ?
    SQL> show sga
    Total System Global Area 3758096384 bytes
    Fixed Size 1983152 bytes
    Variable Size 553655632 bytes
    Database Buffers 3187671040 bytes
    Redo Buffers 14786560 bytes
    SQL>
    SQL> show parameter log_buffer
    NAME TYPE VALUE
    log_buffer integer 14338048
    SQL>
    SQL>
    If the log_buffer parameter is 14 MB then why redo buffer is no as same size e.g.
    14 MB
    SSM

    I am hoping your Oracle Consultant know what he's talking about.
    According to Oracle Performance Guide,
    http://download-west.oracle.com/docs/cd/B19306_01/server.102/b14211/memory.htm#sthref654
    "On most systems, sizing the log buffer larger than 1M does not provide any performance benefit. Increasing the log buffer size does not have any negative implications on performance or recoverability. It merely uses extra memory.
    The best method to determine if bigger redo buffer is needed is
    SELECT NAME, VALUE
    FROM V$SYSSTAT
    WHERE NAME = 'redo buffer allocation retries';
    The value of redo buffer allocation retries should be near zero over an interval. If this value increments consistently, then processes have had to wait for space in the redo log buffer. The wait can be caused by the log buffer being too small or by checkpointing. Increase the size of the redo log buffer, if necessary, by changing the value of the initialization parameter LOG_BUFFER. The value of this parameter is expressed in bytes. Alternatively, improve the checkpointing or archiving process.
    Other than that, hight log file sync event indicate you need faster disk for your redo logfiles. However, please also post your commits per second and redo per second from your AWR report.
    100M redo logs might be small for your environment.

  • Error occured processing parameter

    Hi,
    I need to set new value for log_buffer. so what I did was i issued the following command at sql command prompt
    alter system set log_buffer=50M scope=spfile;
    it throws
    ORA-012095: specified initialization paramer cannot be modified
    so i brought the DB down and I made an entry(log_buffer=50m) in the initfile
    and saved. Then, when I try to create spfile from pfile;
    it throws error
    ORA-91978:failure in processing system parameters
    ORA-32003:error occured processing parameter 'log_buffer'
    Due to this I couldn't resize the log buffer.
    can anyone help me in how to set log_buffer
    Please help in this..... I will e grateful to you
    OS:AIX
    oracle:10.2.0.2.0
    Thanks in advance
    With Regards
    Boo

    What are you trying to resolve or trying to accomplish?
    Setting log_buffer to 50M doesn't make any sense at all,
    as the log_buffer will be written when 1M is dirty or when it's one third full, whichever occurs first.
    You are likely wasting some 45M of memory.
    Sybrand Bakker
    Senior Oracle DBA

  • Resizing of log_buffer in oracle, how to increase it?

    Please can one tell me how to increase log_buffer in oracle please. I am doing import and found it is running long.. looks like it is related to log_buffer issue.. i want to increase.. please tell me how to increase log_buffer.
    Oracle 10g and OS is SunOS

    Hi,
    To check if you are using spfile run:
    SQL> SHOW PARAMETER spfileif return null you are using pfile if return a filename you are using spfile.
    If using spfile use the alter system command in the previous posts.
    If using pfile, change the parameter log_buffer direct in the ini.ora .
    In both cases you need to bounce the instance to take effect.
    I recommend you to take a look in this link also:
    - resizing the redo_buffer
    Cheers,
    Francisco Munoz Alvarez
    http://www.oraclenz.com

  • SGA_TARGET and LOG_BUFFER

    Hello guys,
    i am a little bit confused about setting sga_target and sizing log_buffer manually.
    At first the documentation:
    http://download-uk.oracle.com/docs/cd/B19306_01/server.102/b14237/initparams192.htm#sthref792
    The following pools are manually sized components and are not affected by Automatic Shared Memory Management:
    * Log buffer
    * Other buffer caches, such as KEEP, RECYCLE, and other block sizes
    * Fixed SGA and other internal allocations
    Ok.. now my Oracle 10gR2 database:
    - spfile:
    *.log_buffer=1048576
    *.sga_target=3154116608
    Ok now in my opinion, the log_buffer should not be changed by oracle AMM.
    So lets have a look:
    SQL> show parameter log_buffer
    NAME TYPE VALUE
    log_buffer integer 14254080
    SQL> show sga
    Total System Global Area 3154116608 bytes
    Fixed Size 2074600 bytes
    Variable Size 603981848 bytes
    Database Buffers 2533359616 bytes
    Redo Buffers 14700544 bytes
    Oh ok.... why does oracle change my manually sized value log_buffer from 1MB up to 14MB!!! (have a look at the output of show sga!)
    Hmm and now?
    What is right and what is wrong?
    Maybe someone can clear the confusion...
    Thanks and Regards
    Stefan

    Hi Satheesh,
    this forum is amazing :-)
    But... i try to calculate like your information:
    So have a look at my test database:
    SQL> show sga
    Total System Global Area 2097152000 bytes
    Fixed Size 2072576 bytes
    Variable Size 520093696 bytes
    Database Buffers 1560281088 bytes
    Redo Buffers 14704640 bytes
    SQL> show parameter log_buffer
    NAME TYPE VALUE
    log_buffer integer 14258176
    The lgwr.trc shows:
    Maximum redo generation record size = 132096 bytes
    Maximum redo generation change vector size = 124412 bytes
    And the table entry:
    SQL> select name, count(*) from v$latch_children where name='redo allocation' group by name;
    NAME COUNT(*)
    redo allocation 2
    Ok and now 132096 bytes * 2 = 264192 bytes... and not 14704640 bytes like in show sga or parameter log_buffer.
    Regards
    Stefan

  • Warning while doing a DB Check on my PRD server

    Dear Experts,
    I have been going through a series of warnings on my DB13 since a week now whenever i perform a Check DB activity.
    I have been scheduling my tasks as follows
    Start Time -
    Period -
    Action
    01:00:00               1                 Check and update optimizer statistics
    02:00:00               1                  Check database
    03:00:00               0                 Whole database online + redo log backup
    ==============================================
         But for the Check database the job log is as follows
    =============================================
    BR0972I Checking database operations...
    BR0973W Database operation alert - level: WARNING, operation: adybgofl.cds, time: 2008-06-03 00.23.09, condition: Last archive l
    BR0280I BRCONNECT time stamp: 2008-06-03 02.00.56
    BR0974I Checking database messages in /oracle/RT2/saptrace/background/alert_RT2.log ...
    BR0976W Database message alert - level: WARNING, line: 213333, time: 2008-05-31 10.48.51, message:
    Checkpoint not complete
    BR0976W Database message alert - level: WARNING, line: 213345, time: 2008-05-31 10.51.15, message:
    Checkpoint not complete
    BR0976W Database message alert - level: WARNING, line: 213392, time: 2008-05-31 11.02.39, message:
    Checkpoint not complete
    BR0976W Database message alert - level: WARNING, line: 213411, time: 2008-05-31 11.05.05, message:
    Checkpoint not complete
    BR0976W Database message alert - level: WARNING, line: 213430, time: 2008-05-31 11.07.42, message:
    Checkpoint not complete
    BR0976W Database message alert - level: WARNING, line: 213449, time: 2008-05-31 11.09.46, message:
    Checkpoint not complete
    BR0976W Database message alert - level: WARNING, line: 213468, time: 2008-05-31 11.13.16, message:
    Checkpoint not complete
    BR0280I BRCONNECT time stamp: 2008-06-03 02.00.57
    BR0977I Checking database profile...
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14254080 (>< 4096,512 KB)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
    BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value:2152 (>< 16384,4096)
    BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
    BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
    BR0280I BRCONNECT time stamp: 2008-06-03 02.00.57
    BR0980I Number of changed database profile parameters: 0
    BR0280I BRCONNECT time stamp: 2008-06-03 02.00.57
    BR0955I Number of signaled error/warning/exception alerts for database administration: 0/0/0
    BR0956I Number of signaled error/warning/exception alerts for database operations: 0/1/0
    BR0957I Number of signaled error/warning/exception alerts for database messages: 0/7/0
    BR0958I Number of signaled error/warning/exception alerts for database profile: 2/5/0
    BR0806I End of BRCONNECT processing: cdybgwvi.chk2008-06-03 02.00.58
    BR0280I BRCONNECT time stamp: 2008-06-03 02.00.58
    BR0803I BRCONNECT completed successfully with warnings
    External program terminated with exit code 1
    BRCONNECT returned error status E
    Job finished
    Check and update optimizer statistics
    Check database
    +Whole database online + redo log backup+
    I request you to kindly help on this as i am unsure WHY this is happening.
    The back up and the optimizer stats end without any errors or warnings...
    Kindly suggest as this is very urgent and happening daily
    Regards
    Hunter

    Hi Harry,
    You need to apply SAP recommendations on your database profile. Please check "Note 830576 - Parameter recommendations for Oracle 10g (<= 10.2.0.2)" on sap.service.com. This is because, "Check DB" checks whether db parameters are correctly setup.
    Best regards,
    Orkun Gedik

  • DB13 bakcground job - error

    Hi,
    I have scheduled for the update optimizer statistics immediately in DB 13 it failed with the error as
    "Job started                                                                 
    Step 001 started (program RSDBAJOB, variant &0000000000012, user name SBUDDAR
    Execute logical command SAPDBA On host sap2dqsrv
    Parameters: -u / -analyze DBSTATCO
    Can't exec external program (No such file or directory)
    WaitForSingleObject failedwith %d (No such deviceor address)
    Job finished"
    similarly for  " Check optimizer stattistics"                                         
    "Job started                                                                             
    Step 001 started (program RSDBAJOB, variant &0000000000013, user name SBUDDARA)         
    Execute logical command SAPDBA On host sap2dqsrv                                        
    Parameters: -u / -checkopt DBSTATC_TAB                                                  
    Can't exec external program (No such file or directory)                                 
    WaitForSingleObject failedwith %d (No such deviceor address)                            
    Job finished"
    similarly for "Adapt next extents"
    "Job started                                                                          
    Step 001 started (program RSDBAJOB, variant &0000000000015, user name SBUDDARA)      
    Execute logical command SAPDBA On host sap2dqsrv                                     
    Parameters: -u / -next PSAPBTABD                                                     
    Can't exec external program (No such file or directory)                              
    WaitForSingleObject failedwith %d (No such deviceor address)                         
    Job finished"
    Our environment is windows 2003 server, SAP 4.6C.
    Please help us how resolve above issue.
    Thanks and Regards
    Satya

    Hi Eric,
    Thank you for the information that is really helpful. After following that note, I can successfully ran it.
    When I ran database check in db13 calendar in production, I got the following issue.
    BR0978W Database profile alert - level: ERROR, parameter: COMPATIBLE, value: 10.2.0.2.0 (<> 10.2.0)               
    BR0978W Database profile alert - level: WARNING, parameter: DB_FILE_MULTIBLOCK_READ_COUNT, value: 8(not default)  
    BR0978W Database profile alert - level: ERROR, parameter: FILESYSTEMIO_OPTIONS, value:   (<> SETALL)              
    BR0978W Database profile alert - level: WARNING, parameter: LOG_CHECKPOINTS_TO_ALERT, value: FALSE (<> TRUE)      
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_INDEX_CACHING, value: 0 (>< 100,20)         
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_INDEX_COST_ADJ, value: 100 (>< 50,10)       
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_MODE, value: CHOOSE (not default)           
    BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)           
    BR0978W Database profile alert - level: ERROR, parameter: RECYCLEBIN, value: ON (<> OFF)                          
    BR0978W Database profile alert - level: ERROR, parameter: REMOTE_OS_AUTHENT, value: FALSE (<> TRUE)               
    BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE) 
    BR0978W Database profile alert - level: WARNING, parameter: TIMED_STATISTICS, value: TRUE (not default)           
    Similarly for my quality..
    BR0970W Database administration alert - level: ERROR, type: ARCHIVE_STUCK, object: E:\oracle\QA1\saparch\QA1arch, value: 93.62%  
    BR0970W Database administration alert - level: WARNING, type: MANY_EXTENTS, object: (index) SAPR3.D010TAB~0, value: 80.67% (> 80 
    BR0970W Database administration alert - level: ERROR, type: TABLES_NOT_IN_TABLE_TABLESPACE, object:(index) SAPR3.MLICHECK~0, va  
    BR0280I BRCONNECT time stamp: 2009-04-27 04.01.26                                                                               
    BR0972I Checking database operations...                                                                               
    BR0973W Database operation alert - level: ERROR, operation: 0811132000.opt, time: 2008-11-13 20.00.05, condition: Last successfu 
    BR0280I BRCONNECT time stamp: 2009-04-27 04.01.26                                                                               
    BR0974I Checking database messages in E:\ORACLE\QA1\SAPTRACE\BACKGROUND\alert_qa1.log ...                                        
    BR0976W Database message alert - level: ERROR, line: 5846, time: 2009-01-01 07.29.39, message:                                   
    Checkpoint not complete                                                                               
    BR0976W Database message alert - level: ERROR, line: 5864, time: 2009-01-01 07.29.52, message:                                   
    Checkpoint not complete                                                                               
    BR0976W Database message alert - level: ERROR, line: 5882, time: 2009-01-01 07.30.10, message:                                   
    Checkpoint not complete                                                                               
    BR0976W Database message alert - level: ERROR, line: 5900, time: 2009-01-01 07.30.29, message:                                   
    Checkpoint not complete                                                                               
    BR0976W Database message alert - level: ERROR, line: 38376, time: 2009-04-24 22.07.48, message:                  
    Checkpoint not complete                                                                               
    BR0976W Database message alert - level: ERROR, line: 38411, time: 2009-04-24 22.16.10, message:                  
    Checkpoint not complete                                                                               
    BR0280I BRCONNECT time stamp: 2009-04-27 04.01.26                                                                
    BR0977I Checking database profile...                                                                             
    BR0978W Database profile alert - level: WARNING, parameter: DB_BLOCK_BUFFERS, value: 0 (< 8960)                  
    BR0978W Database profile alert - level: WARNING, parameter: DB_FILE_MULTIBLOCK_READ_COUNT, value: 128 (> 8)      
    BR0978W Database profile alert - level: ERROR, parameter: LOG_ARCHIVE_START, value: FALSE (<> TRUE)              
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 54942720 (>< 1100,300 KB)         
    BR0978W Database profile alert - level: WARNING, parameter: LOG_CHECKPOINT_INTERVAL, value: 0 (< 3000000000)     
    BR0978W Database profile alert - level: WARNING, parameter: LOG_CHECKPOINT_TIMEOUT, value: 1800 (> 0)            
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (<> 8.0.4)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_INDEX_COST_ADJ, value: 100 (<> 10)         
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_MODE, value: ALL_ROWS (<> CHOOSE)          
    Can you please help me how to correct this error?
    Thanks and Regards
    Satya
    Edited by: Satyanarayana Buddarapu on Apr 28, 2009 12:47 AM

  • Problems with spfile. How to change database parameters

    Hello
    My Oracle database is 10.2.0 and SAP version is NW2004s. I am having errors in alert.log file
    Thread 1 cannot allocate new log, sequence 3959     
    Checkpoint not complete                             
    Sun Aug 27 01:38:12 2006                            
    I have changed the parameter log_buffer from 14274560 to 1048576 following the SAP Note 830576. I changed the pfile and created a spfile from this pfile. Now the pfile and spfile reflect the parameter log_buffer as 1048576.
    But surprisingly, when I say
    SQL> show parameter log_buffer
    NAME                               TYPE                VALUE
    log_buffer                         integer         14274560
    Even after pfile and spfile reflecting 1048576 value for log_buffer, the database is showing this old value. Kindly let me know how to change the log_buffer parameter.

    hi,
    check which file it is reading
    sql>sho parameter spfile
    If it is reading spfile
    issue alter system set log_buffer=<value> scope=spfile;
    down and bring up database
    If it is not reading spfile means reading pfile change parameter in INIT<SID>.ORA file
    move all files which starts with spfile in dir $ORACLE_HOME/dbs to backup location
    connect to database
    create spfile from pfile
    check $ORACLE_HOME/dbs only one spfile<sid>.ora exists
    bring up database
    and look for log_buffer
    I guess ur changing in some other file which oracle is not reading.
    or u can issue startp pfile='path';
    then u can create spfile and issue startup force.
    regards
    Vinod

  • Error in the database check.

    hi all,
    I am getting following error while doing Database check in my system:
    BR0976W Database message alert - level: ERROR, line: 7649, time: 2010-08-26 22.56.27, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7650, time: 2010-08-26 22.56.27, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7654, time: 2010-08-26 22.56.27, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7657, time: 2010-08-26 22.56.27, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7658, time: 2010-08-26 22.56.27, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7662, time: 2010-08-26 22.56.27, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7669, time: 2010-08-26 22.56.27, message:
    ORA-16038: log 1 sequence# 28567 cannot be archived
    BR0976W Database message alert - level: ERROR, line: 7670, time: 2010-08-26 22.56.27, message:
    ORA-19502: write error on file "", blockno  (blocksize=)
    BR0976W Database message alert - level: ERROR, line: 7675, time: 2010-08-26 22.56.27, message:
    ORA-16038: log 1 sequence# 28567 cannot be archived
    BR0976W Database message alert - level: ERROR, line: 7676, time: 2010-08-26 22.56.27, message:
    ORA-19502: write error on file "", blockno  (blocksize=)
    BR0976W Database message alert - level: ERROR, line: 7686, time: 2010-08-26 22.57.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7687, time: 2010-08-26 22.57.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7691, time: 2010-08-26 22.57.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7694, time: 2010-08-26 22.57.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7695, time: 2010-08-26 22.57.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7699, time: 2010-08-26 22.57.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7709, time: 2010-08-26 22.58.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7710, time: 2010-08-26 22.58.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7714, time: 2010-08-26 22.58.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7717, time: 2010-08-26 22.58.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7718, time: 2010-08-26 22.58.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7722, time: 2010-08-26 22.58.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7734, time: 2010-08-26 22.59.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7735, time: 2010-08-26 22.59.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7739, time: 2010-08-26 22.59.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7742, time: 2010-08-26 22.59.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7743, time: 2010-08-26 22.59.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7747, time: 2010-08-26 22.59.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 69633 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7757, time: 2010-08-26 22.59.04, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7758, time: 2010-08-26 22.59.04, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7762, time: 2010-08-26 22.59.04, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7765, time: 2010-08-26 22.59.04, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7766, time: 2010-08-26 22.59.04, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7770, time: 2010-08-26 22.59.04, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7780, time: 2010-08-26 23.00.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7781, time: 2010-08-26 23.00.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7785, time: 2010-08-26 23.00.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7798, time: 2010-08-26 23.00.10, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7799, time: 2010-08-26 23.00.10, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7803, time: 2010-08-26 23.00.10, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7811, time: 2010-08-26 23.01.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7812, time: 2010-08-26 23.01.02, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7816, time: 2010-08-26 23.01.02, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7826, time: 2010-08-26 23.02.03, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7827, time: 2010-08-26 23.02.03, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7831, time: 2010-08-26 23.02.03, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 63489 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7839, time: 2010-08-26 23.03.03, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7840, time: 2010-08-26 23.03.03, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7844, time: 2010-08-26 23.03.03, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 77825 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7857, time: 2010-08-26 23.03.42, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7858, time: 2010-08-26 23.03.42, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7862, time: 2010-08-26 23.03.42, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7870, time: 2010-08-26 23.04.03, message:
    ORA-19502: write error on file "/oracle/IRQ/oraarch/IRQarch1_28567_661029934.dbf", blockno 65537 (blocksize=512)
    BR0976W Database message alert - level: ERROR, line: 7871, time: 2010-08-26 23.04.03, message:
    ORA-27063: number of bytes read/written is incorrect
    BR0976W Database message alert - level: ERROR, line: 7875, time: 2010-08-26 23.04.03, message:
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
    BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096)
    BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
    BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
    What are these and how to rectify these?
    Regards,
    Priya

    Hi Priya,
    When you perform database check either using brtools or in tx code db13, SAP will check the health of database system by reading the content of alert_<SID>.log file located in /oracle/<SID>/saptrace/background. Also it checks the contents of database parameters as per the threshold configuration in tx code db17.
    The content of oracle alert log file showed that it cannot write archive log file.. Please see the content of alert_<SID>.log file  and correct the  archive log error creation. The error indicates that either disk block is corrupted or damaged.
    As seen in the error message the error message was created in the month of Aug 2010 and appended in the alert_IRQ.log file located in /oracle/IRQ/saptrace/background.If the error is not present now and if you want to perform database check, then delete old contents from the first line to  till last month in alert_IRQ.log file using operating system. Then save the file and Then perform database check again.
    Please make sure you must monitor database check daily and ensure that if the error occurs for writing archive log file, it is dangerous as archive will stuck and the whole operation hangs.
    The message below is for warning and this can be ignored and this is becasue of threshold configuration. You may change the threshold configuration in tx code db17.
    However warning " WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB) BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file) BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096) BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE) BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE ( FALSE) BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE ( TRUE) BR0978W Database profile alert - level: WARNING, parameter"  - is for warning only it could be bug problems. SO there is no need to correct the problem.
    Hope this helps you.
    Thanks and Regards
    apr

  • Check DB finished with warning

    Dear all,
    Check DB finished with warning from DB13,
    kindly check the detail log .
    BR0969I Checking database administration...
    BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342337) 34959360 KB (> 28188060 KB)
    BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342338) 32747520 KB (> 26471824 KB)
    BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342339) 33157120 KB (> 17786284 KB)
    BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3, value: (max_extn of 5 files on disk 3342340) 34304000 KB (> 24094204 KB)
    BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3700, value: (max_extn of 4 files on disk 3342339) 24125440 KB (> 17786284 KB)
    BR0970W Database administration alert - level: WARNING, type: CRITICAL_TABLESPACE, object: PSAPSR3700, value: (max_extn of 5 files on disk 3342340) 29286400 KB (> 24094204 KB)
    BR0970W Database administration alert - level: ERROR, type: MISSING_INDEX, object: (table) SAPSR3.ZBIMIS
    BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCLOG
    BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCLOG1
    BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPSR3.ZHDFCMAP
    BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCLOG~0
    BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCLOG1~0
    BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (index) SAPSR3.ZHDFCMAP~0
    BR0280I BRCONNECT time stamp: 2010-03-12 01.04.29
    BR0972I Checking database operations...
    BR0280I BRCONNECT time stamp: 2010-03-12 01.04.29
    BR0974I Checking database messages in /oracle/IRP/saptrace/background/alert_IRP.log ...
    BR0280I BRCONNECT time stamp: 2010-03-12 01.04.31
    BR0977I Checking database profile...
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14251008 (>< 4096,512 KB)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
    BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096)
    BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
    BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
    BR0280I BRCONNECT time stamp: 2010-03-12 01.04.31
    BR0980I Number of changed database profile parameters: 0
    BR0280I BRCONNECT time stamp: 2010-03-12 01.04.32
    Kindly suggest
    Regards

    HI
    Go to DB20 , Enter the table name ( which are coming in warning) , Press "Refresh" button . You will see
    "Old number" and "New Number" are different for those table. Simply click on "Create Statistics" button.
    Once you create stats for all the tables  shown in warning, run your DB Check job once again.
    You have lots of other warning...do some google...you will get most of the information for those warning. Some good links are below
    http://download.oracle.com/docs/cd/B12037_01/server.101/b10755/initparams143.htm
    http://skywheel.sarang.net/docs/Oracle/10g/server.101/b10755/initparams168.htm
    http://youngcow.net/doc/oracle10g/server.102/b14237/initparams209.htm
    Regards
    Anindya
    Edited by: Anindya Bose on Mar 12, 2010 12:35 PM

  • Warning In Check DB

    Hello Guru's
    Vital Information About Server
    Database - ORACLE - 10.2.0.2.0
    O/s - Windows NT - 5.2
    SAP - Netweaver 04 - XI Server
    kernel Information - Patch Level - 129
    I am facing problem in my production server.
    In DB13 - Check DB job we are facing problem since very long time
    BR0978W Database profile alert - level: WARNING, parameter: DB_FILE_MULTIBLOCK_READ_COUNT, value: 128 (> 32)
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 2854912 (>< 2048,512 KB)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.2 (<> 9.2.0)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_INDEX_COST_ADJ, value: 20 (<> 10)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_MODE, value: ALL_ROWS (<> CHOOSE)
    Please suggest me so that I can rectify this problem.
    Thanks & Regards
    Shishir

    check note
    900522 - Incorrect alerts/warnings in database check for Oracle 10g
    Markus

  • Check DB Errors

    Dears,
    We are facing below errors in CheckDB in DB13:
    BR0978W Database profile alert - level: ERROR, parameter: FILESYSTEMIO_OPTIONS, value: ASYNCH (<> SETALL)
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 14230528 (>< 4096,512 KB)
    BR0978W Database profile alert - level: WARNING, parameter: MAX_DUMP_FILE_SIZE, value: UNLIMITED (>< 100000,10000)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_FEATURES_ENABLE, value: 10.2.0.1 (set in parameter file)
    BR0978W Database profile alert - level: WARNING, parameter: PARALLEL_EXECUTION_MESSAGE_SIZE, value: 2152 (>< 16384,4096)
    BR0978W Database profile alert - level: ERROR, parameter: QUERY_REWRITE_ENABLED, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: ERROR, parameter: REPLICATION_DEPENDENCY_TRACKING, value: TRUE (<> FALSE)
    BR0978W Database profile alert - level: WARNING, parameter: STAR_TRANSFORMATION_ENABLED, value: FALSE (<> TRUE)
    BR0978W Database profile alert - level: WARNING, parameter: STATISTICS_LEVEL, value: TYPICAL (set in parameter file)
    Please suggest reason and solutions of the issue.
    Shivam

    Hi,
    Please refer SAP Note 900522 - Incorrect alerts/warnings in database check for Oracle 10g along with other relative SAP Notes to get more  relevant information.
    You can customize such condition entries using DB17. Go there and identify the condition entries.
    Also use latest version of BR*tools corresponding the SAP Kernel release.
    Regards,
    Bhavik G. Shroff

  • Update Statistics of CRM Production system is terminated with errors

    Dear All,
    Update Statistics of CRM Production System is failing ie terminated with errors.
    Kindly help.
    Following  are the logs:
    BR0973W Database operation alert - level: WARNING, operation: cegnnbuz.chk, time: 2011-08-12 09.32.37, condition: Last successful 'chk' op
    BR0252E Function fopen() failed for '/oracle/KPC/saptrace/diag/rdbms/kpc/KPC/trace/alert_KPC.log' at location ora_alert_check-1
    BR0253E errno 13: Permission denied
    BR0280I BRCONNECT time stamp: 2011-12-22 04.07.36
    BR0977I Checking database profile...
    BR0978W Database profile alert - level: ERROR, parameter: COMPATIBLE, value: 11.2.0 (<> 10.2.0)
    BR0978W Database profile alert - level: WARNING, parameter: LOG_BUFFER, value: 11198464 (>< 4096,512 KB)
    BR0978W Database profile alert - level: WARNING, parameter: OPTIMIZER_INDEX_COST_ADJ, value: 20 (set in parameter file)
    BR0280I BRCONNECT time stamp: 2011-12-22 04.07.36
    BR0980I Number of changed database profile parameters: 0
    BR0280I BRCONNECT time stamp: 2011-12-22 04.07.37
    BR0955I Number of signaled error/warning/exception alerts for database administration: 0/0/0
    BR0956I Number of signaled error/warning/exception alerts for database operations: 0/1/0
    BR0957I Number of signaled error/warning/exception alerts for database messages: 0/0/0
    BR0958I Number of signaled error/warning/exception alerts for database profile: 1/2/0
    BR0806I End of BRCONNECT processing: cehmkvis.chk 2011-12-22 04.07.37
    BR0280I BRCONNECT time stamp: 2011-12-22 04.07.37
    BR0804I BRCONNECT terminated with errors
    Thanks
    -Madhura

    Hii
    I ve checked all conditions as:
    1.      -rwxrwxr-x   1 orakpc   dba      3406704 Aug 12 16:54 brtools
    2.
    SQL> show parameter compatible;
    NAME                                 TYPE        VALUE
    compatible                           string      11.2.0
    3.  Brtools version is 7.00 and oracle is 11G
    4.  drwxrwxrwx   6 orakpc   dba            6 Aug  7 14:19 saptrace
    Still we are facing this issue.
    pls help.
    -Madhura

  • Buffer Size error on Oracle 10.2.0 Database

    Hi Experts,
    I am getting th following error when my VB application executes on Oracle 10.2.0.
    ORA-01044: Size 5000000 of buffer bound to variable exceeds maximum SYSMAN.EMD_NOTIFICATION
    The Oracle documentation suggests to reduce the Buffer Size.
    As per my knowledge Oracle 10g has only one such parameter Log_Buffer.
    Which parameter is required to be changed in init.ora ?
    Any additional recommendation, which could arrest this error?
    Thanks and Regards

    Hi,
    The same Application works with the same schema and same Database Objects with Oracle 9i, which is pretty surprising. I took a backup of the schema objects from Oracle 10g, and uploaded it on Oracle 9i. The application works fine without a single modification.
    Next, I sat with my developer and checked the parameters, as suggested. Where the Procedure was being called, I found that it is thru command line (not with record set), and the parameter was set to 10000, which was modified it to 5000. This Procedure calling object is used globally across the application. The application started running fine on Oracle 10g, where it was earlier giving errors.
    Now the point is that should we go for the change of the parameter from 10000 to 5000 ?
    This value is very sensitive, and if the number or rows returned is more than 5000 (even 5001), the application shall give an error, and it is obvious that the number of rows in the table for most of the queries shall definitely exceed 5000.
    I feel this is a temporary solution, but can we go for some permanent solution? Definitely, in this fourm I am sure, we have plenty of brains who can trouble shoot this issue.
    Waiting for realtime solution.
    Edited by: user3299261 on Aug 31, 2009 2:14 PM

Maybe you are looking for