Fast load Vs Mload when AMP is down

Tools & Utilities
Enthusiast

Fast load Vs Mload when AMP is down

Hello Experts,

No AMPs may go down (i.e., go offline) while fastload is processing,  where as Multiload can work based on the value set through the parameter AMPCHECK.  How is this achieved.  What kind of processing is done by the load utilities in this case.

Assuming the both fallback and non-fallback tables in this scenario, can you please explain this them relative to fast load and Mload.  Thank you for your time on this.

4 REPLIES
Junior Contributor

Re: Fast load Vs Mload when AMP is down

Hi Cheeli,

FastLoad directly loads into the target table and is simply not implemented to handle down AMPs.

MLoad uses worktables which are always Fallback protected, when an AMP is offline there's still the Fallback copy of the row to work with. And if the target table is also Fallback there's TD's "Down AMP Recovery Journal" to deal with it.

But when an AMP is down (data loss in a RAID?) you usually have more urgent things to do than running a load job :-)

Dieter

Enthusiast

Re: Fast load Vs Mload when AMP is down

Thank you Dieter for your time on this.
Enthusiast

Re: Fast load Vs Mload when AMP is down

what if the target table is created with no fallback option ?

Junior Contributor

Re: Fast load Vs Mload when AMP is down

A table without Fallback is destroyed when an AMP looses data.