Hi Don,

Thank you for your cooperation. Here I am trying to list the answer of your questions.

Code:

grep -e linkId=1ddoic abc-2012-10-01_000* | cut -f 2,5,14 | awk '{$1=$1;print}' OFS=, > /tmp.output.xls

Yes.
Yes. it matches more than one line.
Yes. of course. It will never be in same line.
Only comma. No space.
Yes. It matters. It has to be in sorted order of timestamp.
This is not the additional file. This is the output file that I use as input to generate the final output. After I create the output file after replacing the invalid 'none1111' field I read that file and on top of those values I do some database call and then creates a report.
Yes. It will appear. To resolve that problem we have to run the second grep like below.

Code:

grep id= 82c6a15ca06b2372c3b3ec2133fc8b14 abc-2012-10-01_000* | grep 'page|clk'

The purpose of running above grep is that. The id

Code:

82c6a15ca06b2372c3b3ec2133fc8b14

can appear in two different event, either 'page' or 'clk'. We can take any one 5th column from that log. And also this log will be found in the same file where 'none11111' was found.
Suppose for linkId=1ddoic we found one invalid 'none11111' value in 5th column of the log file abc-2012-10-01_00002 then in abc-2012-10-01_00002 file only the corresponding id should be found with proper 5th column.

Thank you a lot Don for looking into it.