Page 1 of 1

ds_ipcgetnext() - timeout waiting for mutex

Posted: Thu Feb 14, 2013 9:05 am
by igorlp
HI,

I have job:
SHARED_CLONE_STG_FAC_TABLES
(Can't put a picture)

Code: Select all

Table of Contents

Job Properties
Source Stages
T1
Processing Stages
T2
CLONE_STG_FAC_TABLES
Target Stages
CLONE_STATUS


Job Properties

Category:	SHARED\CLONE_STG_FAC_TABLES
Job version number:	50.0.0
Runtime column propagation:	Enabled
Allow multiple invocations:	Yes
NLS Locale:	Time=(Project default) Numeric=(Project default) Currency=(Project default) CType=(Project default) Collate=(Project default)
Parameters

Parameter Name	Default Value
$STG_CPM_USER	$PROJDEF
$STG_CPM_PSWD	********
$DB_CPM_NAME	$PROJDEF
$QRY_CPM_PSWD	********
$PROJECT	$PROJDEF
$QRY_CPM_USER	$PROJDEF
SRC_TABLE	
TRG_TABLE	
Source Stages

Transformer : T1
Stage variable: PROD


Derivation: 1
Output: LinkToCLONE_STG_FAC_TABLES

Outputs to Stored Procedure stage CLONE_STG_FAC_TABLES
Constraint:	@OUTROWNUM=1
Derived Columns

SRC_TABLE	SRC_TABLE
TRG_TABLE	TRG_TABLE
Pass-through Columns

Processing Stages

Transformer : T2
Input: LinkFromCLONE_STG_FAC_TABLES

Input from Stored Procedure stage CLONE_STG_FAC_TABLES
Output: LinkToCLONE_STATUS

Outputs to Sequential File stage CLONE_STATUS
Constraint:	
Derived Columns

Pass-through Columns

ProcCode	 from link LinkFromCLONE_STG_FAC_TABLES
ProcMess	 from link LinkFromCLONE_STG_FAC_TABLES
STATUS	 from link LinkFromCLONE_STG_FAC_TABLES
Stored Procedure : CLONE_STG_FAC_TABLES
Database Vendor:	Oracle
Data Source Name:	#$DB_CPM_NAME#
User Name:	#$QRY_CPM_USER#
Password:	********
Database name:	#$DB_CPM_NAME#
Stored Procedure Name:	CLONE_STG_FAC_TABLES_OLD
Generate Procedure Call:	Yes
Procedure Type:	Transform
Stored Procedure Statement:	BEGIN CLONE_STG_FAC_TABLES_OLD(:1); END;
Stored Procedure Parameters:	SRC_TABLE-+-SRC_TABLE-+-?-+-I+-+TARGET_TABLE-+-TRG_TABLE-+-?-+-I+-+STATUS-+-STATUS-+-?-+-O
Transaction isolation level:	None
Input: LinkToCLONE_STG_FAC_TABLES

Input from Transformer stage T1
Forward Row Data:	No
Rows per transaction:	0
Execute Procedure For Each Row:	Yes
Output: LinkFromCLONE_STG_FAC_TABLES

Outputs to Transformer stage T2
Procedure Return Code:	Yes
Return Multiple Rows:	No
Output Columns

ProcCode	Integer(10)
ProcMess	VarChar(128)
STATUS	VarChar(30)
Target Stages

Sequential File : CLONE_STATUS
Line termination:	DOS
Stage uses named pipes:	File
First character is Byte Order Mark:	Yes
Use UNICODE map:	Yes
Allow per-column mapping:	No
Stage uses filter commands:	No
Input: LinkToCLONE_STATUS

Input from Transformer stage T2
File name:	F:\ETL\#$PROJECT#\TEMP\#TRG_TABLE#_CLONE_STATUS.TXT
Delimiter:	,
Quote character:	"
First line is column names:	Yes
Omit last new-line:	No
Append to existing file:	No
Backup existing file:	No
Fixed-width columns:	No
Spaces between columns:	0
Missing columns action:	0
Write timeout:	0
Wait for reader timeout:	0
Default padding:	#
Some times i get a fatal:
"LinkFromCLONE_STG_FAC_TABLES: ds_ipcgetnext() - timeout waiting for mutex"

Log from previos run:

Code: Select all

From previous run
DataStage Job 6125 Phantom 7176
Program "DSD.ParseTextProp": Line 92, Exception raised in GCI subroutine:
Access violation.

From previous run
DataStage Job 6125 Phantom 9256
Program "DSD.ParseTextProp": Line 92, Exception raised in GCI subroutine:
Access violation.

From previous run
DataStage Job 6125 Phantom 7176
Program "DSD.ParseTextProp": Line 92, Exception raised in GCI subroutine:
Access violation.

From previous run
DataStage Job 6125 Phantom 6600
Program "DSD.LinkReport": Line 68, Exception raised in GCI subroutine:
Access violation.
Please help :roll:

Posted: Thu Feb 14, 2013 3:45 pm
by ray.wurlod
Please Search

You'll get lots of hits. Ignore the "waiting for mutex" part - that's just indicating the semaphore mechanism.

In short, your job has waitied too long for something to occur which hasn't occurred in the allotted time.

At a guess it's an inter-process communication, which may mean that an upstream stage has failed and the downstream stage has given up waiitng.

Posted: Fri Feb 15, 2013 12:05 am
by igorlp
ray.wurlod wrote:Please Search

You'll get lots of hits. Ignore the "waiting for mutex" part - that's just indicating the semaphore mechanism.

In short, your job ha ...
ray. thnks for your answer...
but i can't see premium content((( :oops: