Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

(8 Ratings)
facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

ERROR: "WRT_8165 TIMEOUT BASED COMMIT POINT" in session log in PowerCenter
Problem Description

A PowerCenter session with a poor performance runs for a long duration. In the session log file, the following message is displayed: 

2011-03-22 00:54:27 : INFO : (442698 | WRITER_1_*_1) : (IS | IS) : NE_Prod_Node : WRT_8165 : TIMEOUT BASED COMMIT POINT
2011-03-22 00:57:58 : INFO : (442698 | WRITER_1_*_1) : (IS | IS) : NE_Prod_Node : WRT_8165 : TIMEOUT BASED COMMIT POINT
2011-03-22 00:59:03 : INFO : (442698 | WRITER_1_*_1) : (IS | IS) : NE_Prod_Node : WRT_8165 : TIMEOUT BASED COMMIT POINT
2011-03-22 01:00:15 : INFO : (442698 | WRITER_1_*_1) : (IS | IS) : NE_Prod_Node : WRT_8165 : TIMEOUT BASED COMMIT POINT

Cause

After monitoring the disk activity, it is identified as a disk I/O issue.

Gathering a pmstack output file of the running process displays the following:  

 

The running threads are mentioned below. Thread 30 has reference about reading data from the disk:

Thread 2 :
iosl.select(??, ??, ??, ??, ??) at 0x9000000001209d8
iceos.ICEOS::select(ICESelectHandle*,int,const ICETimeValue*)(??, ??, ??) at 0x90000000345a9a0
connmodule.IAConnModule::run()(??) at 0x900000000afaf1c
connmodule.IAConnModule::startFunc(void*)(??) at 0x900000000af8d84
icethrmgr.mainThreadFcnWrapper(void*)(??) at 0x900000003452364
Thread_Adapter.ACE_Thread_Adapter::invoke_i()() at 0x900000004ba1188
Thread_Adapter.ACE_Thread_Adapter::invoke()() at 0x900000004ba01bc
Base_Thread_Adapter.ace_thread_adapter() at 0x900000004b9fc98

Thread 5 :
warning: Thread is in kernel mode, not all registers can be accessed.
.() at 0x90000004a0d7d3c
osutil.PmSleep(int,short)(??, ??) at 0x9000000020cfc9c
monrun.SMonitorRunnable::run()(??) at 0x10038e8ec
monrun.SMonitorRunnable::handleRequest(const SManagerRequest&)(??, ??) at 0x10038e798
worker.SWorker::run()(??) at 0x10039043c
runnable.SPETLRunnable::mainLoop()(??) at 0x10038a03c
dtmrun.SDTMRunnable::MainEntryPoint()(??) at 0x10038b8a4
thread.runit(void*)(??) at 0x900000014cbc0f8

Thread 30 :
read.read(??, ??, ??) at 0x90000000006dcf8
pmsysio.pmsys_read(int,void*,unsigned long)(??, ??, ??) at 0x9000000020da674
psdiskfile.PSDiskFile::read(long long,void*,int)(??, ??, ??, ??) at 0x100484b54
pmcachemgr.PmCacheMgr::pin(long long,PageAccess&,int,int)(??, ??, ??, ??, ??) at 0x10047f6a4
lkupcmgr.cacheAccess::UnlockCurAndReadLockBlock(PageAccess,long long,PageAccess&,char**)(0x11278b680, 0x0, 0x0, 0x0, 0x0, 0x0, 0x9001000a47103d8) at 0x100505544
lkupcmgr.cacheAccess::fetchDataRow(long long,char**,PageAccess&)(??, ??, ??, ??) at 0x1005056ac
wlkup.SLookupWidget::rowExec()(??) at 0x1002a6174
wlkup.SLookupWidget::execRows(SCmnExecInfo&,int,unsigned long)(??, ??, ??, ??) at 0x1002a8ff8
wlkup.SLookupWidget::blkExecute(unsigned long)(??, ??) at 0x1002a9304
widget.SWidget::blkPush(unsigned long,unsigned long,SRowBlockingInfo*)(??, ??, ??, ??) at 0x1002de27c
widget.SWidget::blkPushDown(unsigned long,SRowBlockingInfo*)(??, ??, ??) at 0x1002dd668
wlkup.SLookupWidget::blkExecute(unsigned long)(??, ??) at 0x1002a9438
widget.SWidget::blkPush(unsigned long,unsigned long,SRowBlockingInfo*)(??, ??, ??, ??) at 0x1002de27c
widget.SWidget::blkPushDown(unsigned long,SRowBlockingInfo*)(??, ??, ??) at 0x1002dd668
wexpr.SExprWidget::blkExecute(unsigned long)(??, ??) at 0x1006f7e00
widget.SWidget::blkPush(unsigned long,unsigned long,SRowBlockingInfo*)(??, ??, ??, ??) at 0x1002de27c
widget.SWidget::blkPushDown(unsigned long,SRowBlockingInfo*)(??, ??, ??) at 0x1002dd668
wlkup.SLookupWidget::blkExecute(unsigned long)(??, ??) at 0x1002a9438
widget.SWidget::blkPush(unsigned long,unsigned long,SRowBlockingInfo*)(??, ??, ??, ??) at 0x1002de27c
widget.SWidget::blkPushDown(unsigned long,SRowBlockingInfo*)(??, ??, ??) at 0x1002dd668
wexpr.SExprWidget::blkExecute(unsigned long)(??, ??) at 0x1006f7e00
widget.SWidget::blkPush(unsigned long,unsigned long,SRowBlockingInfo*)(??, ??, ??, ??) at 0x1002de27c
wnormal.SNormalWidget::blkNormalPush(int)(??, ??) at 0x1006a4500
wnormal.SNormalWidget::flushOneRowMaxOutBlks()(??) at 0x1006a48a0
wnormal.SNormalWidget::blkExecute(unsigned long)(??, ??) at 0x1006ab18c
widget.SWidget::blkPush(unsigned long,unsigned long,SRowBlockingInfo*)(??, ??, ??, ??) at 0x1002de27c
widget.SWidget::blkPushDown(unsigned long,SRowBlockingInfo*)(??, ??, ??) at 0x1002dd668
widget.SWidget::blkFormSegmentAndPushDown(unsigned long,SRowBlockingInfo*)(??, ??, ??) at 0x1002dd26c
exchange.TLeafExchangeWidget::PushSegment(TLeafExchangeWidget**,unsigned int,unsigned int,unsigned long&)(??, ??, ??, ??, ??) at 0x1001e8640
tranrun.STransformationRunnable::processOneBlk()(??) at 0x10043f044
tranrun.STransformationRunnable::run()(??) at 0x10043e170
tranrun.STransformationRunnable::handleRequest(const SManagerRequest&)(??, ??) at 0x10043dcd0
worker.SWorker::run()(??) at 0x10039043c
runnable.SPETLRunnable::mainLoop()(??) at 0x10038a03c
dtmrun.SDTMRunnable::MainEntryPoint()(??) at 0x10038b8a4
thread.runit(void*)(??) at 0x900000014cbc0f8
Solution

To resolve this issue, change vmo parameters for tuning disk I/O. 

More Information

This unexpected behavior occurs due to disk I/O issue. In this case, the issue occurred on an AIX machine. However, it might occur on other platforms too.

Applies To
Product: PowerCenter
Problem Type:
User Type:
Project Phase:
Product Version: PowerCenter
Database:
Operating System:
Other Software:

Reference

For more information on IBM vmo parameters, refer to List of vmo parameters and tuning recommendations

Attachments
Last Modified Date:4/9/2014 2:02 AMID:138428
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)