Hi All,

I need to implement the data profiling FOCUS code to in fex. please educate me here.

Thanks In Advance.

-Neelima

This message has been edited. Last edited by: FP Mod Chuck,

I had never seen that before, good to know!

Thank you Frans!!

When I am applying this code on cluster.its taking lots of time.
Can we improve this performance by selected columns. if yes , please help me with the code.

Thank you so much!!!

-Neelima

You can profile an individual column, for example:

PROFDATA CAR.COUNTRY.ORIGIN 

However if you want multiple columns that would require multiple calls.

If your signature is correct and you are still using 7.7.03 you would see improved performance by upgrading to the current Release 7.7.09. Also in that release the full syntax of the command is:

PROFDATA synonym[.segment[.field]] [,,,BRIEF]  

Where the new option, BRIEF, suppresses generation of the statistics Patterns Count, Mode and Median resulting in faster processing.

I had not used PROFDATA so played with it. It could be very useful for profiling data.

Turning SQL traces on, however, you can see it runs into optimization issues when profiling SQL tables.

 SET TRACEOFF = ALL
 SET TRACEON = STMTRACE//CLIENT
 SET TRACEON = SQLAGGR//CLIENT
 SET XRETRIEVAL = ON
 SET TRACEUSER = ON 

The PROFDATA command wants to do multiple LST prefix operations which the SQL adapter doesn't like. The SQL engine doesn't summarize the answer set, but instead returns all records to let WebFOCUS do the aggregation and prefix operators. Here is the message:

 (FOC2590) AGGREGATION NOT DONE FOR THE FOLLOWING REASON:
 (FOC2617) MULTIPLE LST. IN REQUEST: 

Even when profiling a single column, PROFDATA still has a SQL optimization issue:

 (FOC2590) AGGREGATION NOT DONE FOR THE FOLLOWING REASON:
 (FOC2595) ONLY ADD, SUM, CNT, AVE, MIN, AND MAX PREFIXES CAN BE AGGREGATED 

Using WF8.2.04, the BRIEF option didn't seem to help with this issue.

So perhaps somebody can tweak the PROFDATA command for SQL optimization.

This message has been edited. Last edited by: Doug at Kencura,

DataMigrator 7.7.09 corresponds to WebFOCUS 8.2.05.

Hi Clif, I am using 8204.

Doug,

Is there any way to get the location of PROFDATA batch file. So that we can drive the method from there.

Thanks.

If PROFDATA is a FOCEXEC, it is hidden well. I suspected a LET command might be changing what PROFDATA actually meant but don't see that either.

It could very well be that PROFDATA is an internal function that only IB can change. Opening a case about PROFDATA and SQL optimization might be a good idea.

This message has been edited. Last edited by: Doug at Kencura,

Hi Doug,

OK. I opened the case for same and lets wait for their some good response.

Thanks
Neelima

We've opened a case once for the performance thing, the problem is that patern, median, mode etc. cannot be converted to SQL in most cases.

if you use the BRIEF option it will only use optimized statements, be be aware to use the right syntax with 3 comma's:

PROFDATA CAR,,,BRIEF
HOLD AS TST

TABLE FILE TST PRINT *
END