It's unbelievable the quantity of patches GIS has already received in order to increase its functionality and to fix the bugs previous patches have introduced!
I've lost two mornings working with the functional team in the account module just to find out that we were on a witch chase.
The problem was on GIS and we have just been informed that the new patch fixes the errors we were getting. The problem is that these errors only appeared after a previous software installation the week before.
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Tuesday, January 11, 2011
Thursday, December 23, 2010
Day 632 - Christmas Break
This is the last work day before a short Christmas break.
It seems the "I'll tell you how to do your job" symptom is getting worst.
Now management, instead of managing, is, literally, querying the target database with SQL in AS/400 and is creating a fuss by asking and making assumptions about things that he finds awkward.
The problem is that he doesn't know the target system that well and is just getting on everyone's nerves because people has to stop working the data migration and waste time to get data right to answer him and showing how he was wrong.
I hope this short Christmas break helps everyone to calm down.
It seems the "I'll tell you how to do your job" symptom is getting worst.
Now management, instead of managing, is, literally, querying the target database with SQL in AS/400 and is creating a fuss by asking and making assumptions about things that he finds awkward.
The problem is that he doesn't know the target system that well and is just getting on everyone's nerves because people has to stop working the data migration and waste time to get data right to answer him and showing how he was wrong.
I hope this short Christmas break helps everyone to calm down.
Day 630 - Qualification Preliminary Report
The preliminary report indicates a very good success rate.
It has been presented to management, and administration, during the weekly meeting.
But even with good results, management is really panicking and it's showing it semi-publicly.
Now management is trying to tell everybody how to do their work, me included.
Management really told me how to do my work, technically, with database details and everything. When we started discussing the problem I realised pretty quickly that actually, he didn't knew what he was talking about. So, I've just agreed with him and let it go. The other way was to "beat him up" in front of his entire team showing that he didn't not even had a clue about how the process was set up, and he knew even less about our requirements and the technical solutions we had to set up to met them.
This kind of action is one more panic symptom, and it's not helping the team.
It has been presented to management, and administration, during the weekly meeting.
But even with good results, management is really panicking and it's showing it semi-publicly.
Now management is trying to tell everybody how to do their work, me included.
Management really told me how to do my work, technically, with database details and everything. When we started discussing the problem I realised pretty quickly that actually, he didn't knew what he was talking about. So, I've just agreed with him and let it go. The other way was to "beat him up" in front of his entire team showing that he didn't not even had a clue about how the process was set up, and he knew even less about our requirements and the technical solutions we had to set up to met them.
This kind of action is one more panic symptom, and it's not helping the team.
Day 629 - Last Qualification Day
As I predicted, account took ages and it's loading has been aborted at 21:50.
This means that not only account was only partially loaded but also that some other residual, but important, data didn't had the chance to be loaded.
Management seems to be unhappy, but my initial report data indicate a very good success rate, except for three insurance claims areas.
This means that not only account was only partially loaded but also that some other residual, but important, data didn't had the chance to be loaded.
Management seems to be unhappy, but my initial report data indicate a very good success rate, except for three insurance claims areas.
Day 628 - Second Qualification Weekend Day
Some insurance claims have been loaded but only one area had no errors, all the other areas had insignificant success rates.
The data migration is running late because the car insurance data loading had to be repeated yesterday and account will take ages to load. This means that the data migration will not be completed during the weekend.
The data migration is running late because the car insurance data loading had to be repeated yesterday and account will take ages to load. This means that the data migration will not be completed during the weekend.
Day 627 - First Qualification Weekend Day
The first weekend day will be mainly for insurance data loading.
All insurances have problems, including the car insurance data.
It seems to be am insignificant amount of errors, but I was not expecting any errors from data insurance.
All insurances have problems, including the car insurance data.
It seems to be am insignificant amount of errors, but I was not expecting any errors from data insurance.
Wednesday, January 6, 2010
Day 279 - Happy New Year and Happy News
Clients are now being loaded with a marginal number of rejections.
The GIS configuration issues still have an impact but that problem is being solved quickly.
I'm still around the report load query problem, but it is not easy to test the performance on a slow system, since it takes too much time to process a query and return its result.
The GIS configuration issues still have an impact but that problem is being solved quickly.
I'm still around the report load query problem, but it is not easy to test the performance on a slow system, since it takes too much time to process a query and return its result.
Day 273 - Configuration Issues
The GIS configuration is changing and that has a direct impact in the mapping rules.
We are now facing an increase number of data being rejected by GIS because its configuration has been changed but the mapping hasn't.
We are now facing an increase number of data being rejected by GIS because its configuration has been changed but the mapping hasn't.
Day 266 - Christmas Break
The project will be stopped for a short Christmas break.
The overall number of data being rejected by the GIS loader is decreasing every day.
But we are now facing a performance problem again. It takes too much time to query GIS in order to know how many errors and what time of errors occurred in the loading procedure. I'll have to take a look at these query performance so that the loading report does not take half-day for a simple auto claim data load.
The overall number of data being rejected by the GIS loader is decreasing every day.
But we are now facing a performance problem again. It takes too much time to query GIS in order to know how many errors and what time of errors occurred in the loading procedure. I'll have to take a look at these query performance so that the loading report does not take half-day for a simple auto claim data load.
Day 264 - Error Free Loading
Finally we are start to get error free data loading.
Some types of clients are already loading into GIS and this is reducing the number of claims rejected by the GIS loader.
I'm expecting to stop worrying with client problems soon.
Some types of clients are already loading into GIS and this is reducing the number of claims rejected by the GIS loader.
I'm expecting to stop worrying with client problems soon.
Subscribe to:
Posts (Atom)
Posts
