Change capture-Segment violation error

logic · Post by **logic** » Fri Dec 02, 2005 12:49 pm

Hi ,
I am getting the sigsev error while trying to use the change capture stage. There is no string larger than permitted size.Config file is ok.
We are getting the following warnings before hitting the fatal error.

Code: Select all

Before,0: signalHandler__Fi() at 0x204ffb28
Before,0: moveeq.memmove() at 0x3079a6dc
Before,0: SwapEndian(0x2, 0x2) at 0x307a4af8
Before,0: des_def(0x306ea3e8, 0x306ad0c8) at 0x3078cc5c
Before,0: DRSOpen(0x306ad0c8) at 0x30795988
Before,0: Open(0x306ad0c8) at 0x30783950
Before,0: Call__9DSCStageCFR10DSContextCPFP7DSLinkC_vP7DSLinkC(0x306acea8, 0x2ff1f098, 0x3065d508, 0x30785640, 0x306ad0c8) at 0xd2da0348
Before,0: Open__16DSPassiveCStageCFR10DSContextCP7DSLinkC(0x306ace28, 0x2ff1f154, 0x3065d508, 0x306ad0c8) at 0xd2da3708
Before,0: ORPHCallPassivePluginOpen(0x306ad0c8) at 0xd2ee2a94
Before,0: openPassiveOutputLinks()(0x300e3f78), line 958 in "dscapiop.C"

I understand that it would be a memory problem...trying to access non existing memory....These jobs were running fine. We are using the change capture stage to compare to tables. Oracle Tables are accessed by DRS stage.
What could be the problem and possible fix to it.
Thanks.

kumar_s · Post by **kumar_s** » Sat Dec 03, 2005 4:14 am

Hi,
How about the resource consumption.
Please check the swap space consumption before and at the moment of the abort.

Code: Select all

lsps -s

would help you to find the results.
If that strikes the extreme limit of your box, talk to unix admin to increase the swap space.

-kumar