Application Development Software

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Delivery Notification: Delivery has been delayed

807574Apr 25 2008 — edited Feb 11 2020

I'm not getting only "Delivery Notification: Delivery has failed" but no "Delivery Notification: Delivery has been delayed"
please help me on this.

Chinthake

# /opt/sun/comms/messaging64/sbin/imsimta qm
qm.maint> sum
Queued Queued
Channel Messages = Active + Delayed Size (Mb)

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
process 0 0 0 0.0
process_dsn 0 0 0 0.0
reprocess 0 0 0 0.0
tcp_intranet 0 0 0 0.0
tcp_local 60147 60147 0 322.8
tcp_notify 6267 6267 0 39.0
tcp_yahoo 790 790 0 10.5

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
Totals 67204 67204 0 372.3
qm.maint> top tcp_notify
Building a list of message files to scan from the queue directory tree...
The list will contain only messages from channels matching "tcp_notify"
Scanning 6268 message files...
Scanned 6268 message files in 12.9481 seconds (484.09 messages/second)
Top 20 Subject: header lines which occur 2 or more times

Count Subject
====== ======================================================================
6178 Delivery Notification: Delivery has failed
qm.maint>

# /opt/sun/comms/messaging64/sbin/imsimta version
Sun Java(tm) System Messaging Server 6.3-5.02 (built Oct 12 2007; 64bit)
libimta.so 6.3-5.02 (built 17:38:05, Oct 12 2007; 64bit)
SunOS whale1 5.10 Generic_118833-33 sun4u sparc SUNW,Sun-Fire-V240

18-Apr-2008 10:51:44.86 tcp_local tcp_local E 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk
18-Apr-2008 10:56:02.29 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 12:39:56.56 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 14:36:56.22 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 16:46:57.58 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
18-Apr-2008 21:18:53.01 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 01:22:37.67 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 05:26:21.68 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 13:45:08.09 tcp_local Q 1 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
19-Apr-2008 22:08:13.46 tcp_local Q 2 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
20-Apr-2008 06:11:57.68 tcp_local Q 2 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
20-Apr-2008 14:46:20.35 tcp_local Q 2 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
20-Apr-2008 23:29:46.72 tcp_local Q 2 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 07:37:34.24 tcp_local Q 2 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 11:39:57.29 tcp_local Q 2 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 13:26:22.90 tcp_local Q 3 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out
21-Apr-2008 21:44:28.30 tcp_local Q 3 chinthake@gmail.com rfc822;test@spamwalltest.slt.lk test@spamwalltest.slt.lk TCP active open: Failed connect() 203.115.0.139:25 Error: Connection timed out

# cat imta.cnf
!
! IMTA configuration file
!
! part I : rewrite rules
!
! Domain Rewrite Rules.
! Uncomment this line to use domain rewrite rules
! from the configuration file instead of the domain database.
! Please refer to the iMS documentation for details.
!<IMTA_TABLE:domains.rules
!
! Rules to select local users
$* $A$E$F$U%$H$V$H@whale1.slt.lk
whale1.slt.lk $U%$D@whale1.slt.lk
siore.com $U%$D@whale1.slt.lk
yahoo.com $U@yahoo.com
!
! ims-ms
.ims-ms-daemon $U%$H.ims-ms-daemon@ims-ms-daemon
!
! lmtp
!.lmtp $U%$H@lmtpcs-daemon
!
! lmtpn
!.lmtpn $U%$H@lmtpcn-daemon
!
! native
.native-daemon $U%$H.native-daemon@native-daemon
!
! pipe
.pipe-daemon $U%$H.pipe-daemon@pipe-daemon
!
<IMTA_TABLE:internet-dsn.rules
!
! tcp_local
! Rules for top level internet domains
<IMTA_TABLE:internet.rules
!
! tcp_intranet
! Do mapping lookup for internal IP addresses
[] $E$R${INTERNAL_IP,$L}$U%[$L]@tcp_intranet-daemon
.siore.com $U%$H.siore.com@tcp_intranet-daemon
* $U%$&0.siore.com
!
! reprocess
reprocess $U%reprocess.whale1.slt.lk@reprocess-daemon
reprocess.whale1.slt.lk $U%reprocess.whale1.slt.lk@reprocess-daemon
!
! process
process $U%process.whale1.slt.lk@process-daemon
process.whale1.slt.lk $U%process.whale1.slt.lk@process-daemon
!
! defragment
defragment $U%defragment.whale1.slt.lk@defragment-daemon
defragment.whale1.slt.lk $U%defragment.whale1.slt.lk@defragment-daemon
!
! conversion
conversion $U%conversion.whale1.slt.lk@conversion-daemon
conversion.whale1.slt.lk $U%conversion.whale1.slt.lk@conversion-daemon
!
! bitbucket
bitbucket $U%bitbucket.whale1.slt.lk@bitbucket-daemon
bitbucket.whale1.slt.lk $U%bitbucket.whale1.slt.lk@bitbucket-daemon
!
! deleted
deleted-daemon $U%$H@deleted-daemon
.deleted-daemon $U%$H@deleted-daemon
!
! inactive
inactive-daemon $U%$H@inactive-daemon
.inactive-daemon $U%$H@inactive-daemon
!
! hold
hold-daemon $U%$H@hold-daemon
.hold-daemon $U%$H@hold-daemon

!
! part II : channel blocks
!
!defaults notices 1 2 4 7 copywarnpost copysendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siore.com siore.com
!defaults notices 1 2 4 nowarnpost nosendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siore.com siore.com logging notificationchannel process_dsn dispositionchannel process_dsn
defaults notices 1 2 4 copywarnpost nosendpost postheadonly noswitchchannel immnonurgent maxjobs 7 defaulthost siore.com siore.com logging notificationchannel process_dsn dispositionchannel process_dsn

!
! delivery channel to local /var/mail store
l subdirs 20 viaaliasrequired maxjobs 7
whale1.slt.lk

!
! ims-ms
ims-ms defragment subdirs 20 notices 1 7 14 21 28 backoff "pt5m" "pt10m" "pt30m" "pt1h" "pt2h" "pt4h" maxjobs 2 pool IMS_POOL fileinto $U+$S@$D
ims-ms-daemon

!
! native
native defragment subdirs 20 maxjobs 1
native-daemon

!
! pipe
pipe single defragment subdirs 20
pipe-daemon

!
! tcp_local
!tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 loopcheck
tcp_local smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 7 pool SMTP_POOL maytlsserver maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 loopcheck disconnectbadcommandlimit 5 mailfromdnsverify
tcp-daemon

!
! tcp_intranet
tcp_intranet smtp mx single_sys subdirs 20 dequeue_removeroute maxjobs 7 pool SMTP_POOL maytlsserver allowswitchchannel saslswitchchannel tcp_auth missingrecipientpolicy 4
tcp_intranet-daemon

!
! tcp_submit
tcp_submit submit smtp mx single_sys mustsaslserver maytlsserver missingrecipientpolicy 4
tcp_submit-daemon

!
! tcp_auth
tcp_auth smtp mx single_sys mustsaslserver missingrecipientpolicy 4
tcp_auth-daemon

!
! tcp_tas
tcp_tas smtp mx single_sys allowswitchchannel mustsaslserver maytlsserver deliveryflags 2
tcp_tas-daemon

!
! tcp_lmtpss (LMTP server - store)
!tcp_lmtpss lmtp flagtransfer
!tcp_lmtpss-daemon

!
! tcp_lmtpcs (LMTP client - store)
!tcp_lmtpcs defragment lmtp port 225 nomx single_sys subdirs 20 maxjobs 7 pool SMTP_POOL dequeue_removeroute
!lmtpcs-daemon

!
! tcp_notify
!tcp_notify smtp mx single_sys remotehost inner subdirs 20 maxjobs 10 pool NOTIFY_POOL backoff "pt4h" "pt8h" notices 1 loopcheck
tcp_notify smtp mx single_sys remotehost inner subdirs 20 maxjobs 10 pool NOTIFY_POOL notices 1 backoff "pt4h" "pt8h" nosendpost loopcheck
tcp_notify-daemon

!
!tcp_yahoo
tcp_yahoo smtp mx single_sys remotehost inner switchchannel identnonenumeric subdirs 20 maxjobs 30 threaddepth 32 pool SMTP_POOL maysaslserver saslswitchchannel tcp_auth missingrecipientpolicy 0 recipientlimit 125
!tcp_yahoo-daemon
yahoo.com

!
! reprocess
reprocess
reprocess-daemon

!
! process
process
process-daemon

!
! defragment
defragment
defragment-daemon

!
! conversion
conversion
conversion-daemon

!
! bitbucket
bitbucket
bitbucket-daemon

!
! deleted
deleted
deleted-daemon

!
! inactive
inactive
inactive-daemon

!
! hold
hold
hold-daemon

!
!process_dsn
process_dsn
process_dsn-daemon

mseberg

I would review this :

What Is the Redo Log ( Its a little over a page )

http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/onlineredo001.htm

Best Regards

mseberg

Srini Chavali-Oracle

Check the Concepts Guide - http://download.oracle.com/docs/cd/E11882_01/server.112/e16508/process.htm#CNCPT1251

HTH
Srini

712622

Go through this link...

http://download.oracle.com/docs/cd/B28359_01/server.111/b28318/memory.htm

845641

My question is not WHAT IS REDO LOG or about how LGWR writes to redo log files? You have given me links which i already know? my question is simple which process transferrs data from buffer cache to log buffer and how ? which is not given in these concepts guide.. and also what is IMU buffers ? is it the one from which it transfers changed buffers to log buffer ? Because when waiting for event [ log file switch (private strand flush incomplete) ] oracle says LGWR waits for DBWR to complete flushing redo from IMU buffers into the redo log buffer; when DBWR is complete LGWR can then finish writing the current log, and then switch log files. THANKS

PavanG

It is the sever process that performs the copy from the buffer to the log buffer.

1 person found this helpful

AronTunzi

IMU means "In-memory undo"

From the link of Srini you can read that:

LGWR writes one contiguous portion of the buffer to the online redo log. By separating the tasks of modifying database buffers, performing scattered writes of dirty buffers to disk, and performing fast sequential writes of redo to disk, the database improves performance.

In the following circumstances, LGWR writes all redo entries that have been copied into the buffer since the last time it wrote:

A user commits a transaction (see "Committing Transactions").

An online redo log switch occurs.

Three seconds have passed since LGWR last wrote.

The redo log buffer is one-third full or contains 1 MB of buffered data.

DBWn must write modified buffers to disk.

Jonathan Lewis

Answer

842638 wrote:
Hi EXPERTS,

Im on 11G R2, RHEL 5 my question that when data is modified in database buffer cache how immediately it is copied to redo log buffer. I mean which process copies it. I read it in oracle documentation that when waiting for event [ log file switch (private strand flush incomplete) ] LGWR waits for DBWR to complete flushing redo from IMU buffers into the redo log buffer; when DBWR is complete LGWR can then finish writing the current log, and then switch log files.

In general each session writes its own redo into private buffers (a matched pair - one for the forward changes, one for the undo block changes - it's the latter that's named the IMU pool) and copies the private redo into the public log buffer on commit. There are various events that will cause the private redo to be flushed to the public thread before the commit. One of these is the special case that you've mentioned where DBWR instigates a flush.

If DBWR has to copy a datablock from the db cache to disc it has to copy the latest version of the block, but any redo that describes changes to that block has to be written first. So if DBWR finds that a block it wants to write is subject to private redo it flushes the redo to the log buffer and applies it to the data buffer before calling lgwr to write the log buffer to disc - once the log writer has written dbwr can write that data block to disc.

Private strand flush incomplete is the event you get from a foreground session when something else (such as DBWR) is doing the flush for it and it's waiting to generate more redo. It can't put it into the private buffer because that buffer is now locked against change because of the flush; it can't put it into the public buffer otherwise the redo might get there before the sessions earlier redo, so it has to wait temporarily for the private buffer to become unlocked because that's the only way it can tell that the flush is complete and it's now safe to carry on - and when it carries on it has to switch to the public buffer.

I've just finished rewriting half a dozen pages of my book explaining this, so a short answer that hits a few of the highlights is all you can expect in a forum note.

Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk

To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}

{noformat} (lowercase, curly brackets, no spaces) so that the text appears in

fixed format

.

There is a +"Preview"+ tab at the top of the text entry panel. Use this to check what your message will look like before you post the message. If it looks a complete mess you're unlikely to get a response. (Click on the +"Plain text"+ tab if you want to edit the text to tidy it up.)

Marked as Answer by 845641 · Sep 27 2020

845641

thanks jonathan for this deep reply.. you are just a genius always and pavanG also for answering me straight in few lines rather than giving me links of those complete huge manuals... thanks again

user12050217

If you think server process copies the buffer to the log buffer; then my questions are:
1.Which buffer i.e. redo log bufer, database buffer ?
2.Then who writes in Redologs i.e. server process or LGWR ?
3.If server process writes, then what does LGWR ?
4.If server process is writing in redologs, then why and when DBWR signal to LGWR ?

Thank you.

1 - 9

Locked Post

New comments cannot be posted to this locked post.

Locked on May 25 2008

Added on Apr 25 2008

#e-mail-calendar-collaboration, #webcenter

2 comments

386 views

Application Development Software

Delivery Notification: Delivery has been delayed

Comments

Post Details