Discussion:
[cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Brian Meade
2016-09-12 19:24:40 UTC
Permalink
This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or
anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file
will be on cisco.com soon as well if you don't mind waiting.

More discussion-
https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
Brian Meade
2016-09-12 19:26:40 UTC
Permalink
Looks like the COP file is now posted on the supportforums post.
Post by Brian Meade
This issue seems to be affecting everyone.
Bug ID is CSCvb27878 but not publicly visible yet.
There is a COP file fix available from TAC that doesn't require a reboot
or anything.
I'm sure there's a field notice coming soon. I'm guessing the COP file
will be on cisco.com soon as well if you don't mind waiting.
More discussion- https://supportforums.cisco.com/
discussion/13118806/cuic-uccx-dataset-status-failed-database-error
Jose Colon II
2016-09-12 19:29:31 UTC
Permalink
I hit this issue on Friday and TAC got back to me today with that COP file
as a fix with no reboot required. I will however wait until after hours of
course.

Certain reports were not able to be run with the "TODAY" parameter selected
as the time frame. It would give the error.
Post by Brian Meade
Looks like the COP file is now posted on the supportforums post.
Post by Brian Meade
This issue seems to be affecting everyone.
Bug ID is CSCvb27878 but not publicly visible yet.
There is a COP file fix available from TAC that doesn't require a reboot
or anything.
I'm sure there's a field notice coming soon. I'm guessing the COP file
will be on cisco.com soon as well if you don't mind waiting.
More discussion- https://supportforums.cisco.com/discussion/
13118806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
Stephen Welsh
2016-09-12 19:35:56 UTC
Permalink
Brian,

Thank you for this, we had an customer install our WallboardFX product and co-incdently hit this issue and thought our product may have been to blame (not technically possibly anyway), however not only could we clarify that it was a co-incidence this helps the customer to get to the bottom of the issue a lot quicker.

Your Cisco TAC Bug search skills are truly legendary, if we get the chance to cross paths at Cisco Live you get our best swag ;)

Kind Regards

Stephen Welsh
CTO
UnifiedFX

On 12 Sep 2016, at 20:24, Brian Meade <***@vt.edu<mailto:***@vt.edu>> wrote:

This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file will be on cisco.com<http://cisco.com/> soon as well if you don't mind waiting.

More discussion- https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
Damisch, Kevin
2016-09-12 19:42:14 UTC
Permalink
I applied the cop file to 3 customers over the weekend and can confirm that it is a quick fix. There are no service restarts, reboots, or anything, so there is absolutely no reason to wait until afterhours. If you are a partner or work with multiple customers, you better grab the cop file and keep it handy for a while as you'll likely need it as customers are going to call you when they try to run the CUIC reports that contains dates beyond 9/9 and run into that error. It affects all releases of UCCX 8/9/10/11.

Thanks,
Kevin

From: cisco-voip [mailto:cisco-voip-***@puck.nether.net] On Behalf Of Stephen Welsh
Sent: Monday, September 12, 2016 2:36 PM
To: Brian Meade <***@vt.edu>
Cc: cisco-***@puck.nether.net
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date

Brian,

Thank you for this, we had an customer install our WallboardFX product and co-incdently hit this issue and thought our product may have been to blame (not technically possibly anyway), however not only could we clarify that it was a co-incidence this helps the customer to get to the bottom of the issue a lot quicker.

Your Cisco TAC Bug search skills are truly legendary, if we get the chance to cross paths at Cisco Live you get our best swag ;)

Kind Regards

Stephen Welsh
CTO
UnifiedFX

On 12 Sep 2016, at 20:24, Brian Meade <***@vt.edu<mailto:***@vt.edu>> wrote:

This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file will be on cisco.com<http://cisco.com/> soon as well if you don't mind waiting.

More discussion- https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
Lelio Fulgenzi
2016-09-12 20:44:10 UTC
Permalink
Yup. Affecting our installation of historical reporting. Not just cuic.

Sent from my iPhone

On Sep 12, 2016, at 3:25 PM, Brian Meade <***@vt.edu<mailto:***@vt.edu>> wrote:

This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file will be on cisco.com<http://cisco.com> soon as well if you don't mind waiting.

More discussion- https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
Erick Bergquist
2016-09-12 21:30:11 UTC
Permalink
Ran into this Friday. One client reported it then a few others and knew
something weird was going on. Called it the 9/9 bug and worked with TAC and
they had workaround ready to apply.
Post by Lelio Fulgenzi
Yup. Affecting our installation of historical reporting. Not just cuic.
Sent from my iPhone
This issue seems to be affecting everyone.
Bug ID is CSCvb27878 but not publicly visible yet.
There is a COP file fix available from TAC that doesn't require a reboot or anything.
I'm sure there's a field notice coming soon. I'm guessing the COP file
will be on cisco.com soon as well if you don't mind waiting.
More discussion- https://supportforums.cisco.com/
discussion/13118806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
Abhiram Kramadhati (akramadh)
2016-09-13 00:57:45 UTC
Permalink
Hi all,

There is a cop already available which has been provided to TAC. Only the CAD email reports are yet to be fixed, so we have a fix already there but just formalising it as a cop. We will have one cop released externally which will fix all the reports - the cop currently available fixes everything apart from CAD email reports. For that, please ask TAC for a manual workaround (there will be one cop very soon with all the fixes).

A bit of context:
There is a datediff function which calculates the time difference between today's date and reference date. The reference date hardcoded is 1985-01-01 00:00:00 and starting from 8th September 2016, this difference is coming out to be a length that cannot be handled by the variable supposed to be storing it.

This will be fixed and cop will be available. This cop should be installed on both the nodes via CLI and requires no restarts.

Apologies, I am on travel - was meaning to send a heads-up when this got highlighted. Please feel free to reach out in case you are having challenges. Thank you.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065

From: cisco-voip <cisco-voip-***@puck.nether.net<mailto:cisco-voip-***@puck.nether.net>> on behalf of Erick Bergquist <***@gmail.com<mailto:***@gmail.com>>
Date: Tuesday, 13 September 2016 at 7:30 AM
To: Lelio Fulgenzi <***@uoguelph.ca<mailto:***@uoguelph.ca>>
Cc: "cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>" <cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>>
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date

Ran into this Friday. One client reported it then a few others and knew something weird was going on. Called it the 9/9 bug and worked with TAC and they had workaround ready to apply.


On Monday, September 12, 2016, Lelio Fulgenzi <***@uoguelph.ca<mailto:***@uoguelph.ca>> wrote:
Yup. Affecting our installation of historical reporting. Not just cuic.

Sent from my iPhone

On Sep 12, 2016, at 3:25 PM, Brian Meade <***@vt.edu<javascript:_e(%7B%7D,'cvml','***@vt.edu');>> wrote:

This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file will be on cisco.com<http://cisco.com> soon as well if you don't mind waiting.

More discussion- https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
Brian Meade
2016-09-13 01:50:46 UTC
Permalink
Agent Not Ready State report was the big one that hit our clients. It's
any report/stored procedure that utilizes the datediff function.

Anything including a date after September 8th seemed to be an issue.

On Mon, Sep 12, 2016 at 9:44 PM, Anthony Holloway <
So, should this be impacting every CUIC install in the world? Does this
impact all reports or just some? For the reports which are impacted, is
only when certain date filters are applied, or any filters? Are there any
instances where a system wouldn't be impacted by reportgate? I just ran
one random report on a 10.6(1)SU1 system, and I don't see a problem.
On Mon, Sep 12, 2016 at 7:57 PM, Abhiram Kramadhati (akramadh) <
Post by Abhiram Kramadhati (akramadh)
Hi all,
There is a cop already available which has been provided to TAC. Only the
CAD email reports are yet to be fixed, so we have a fix already there but
just formalising it as a cop. We will have one cop released externally
which will fix all the reports – the cop currently available fixes
everything apart from CAD email reports. For that, please ask TAC for a
manual workaround (there will be one cop very soon with all the fixes).
There is a *datediff *function which calculates the time difference
between today’s date and reference date. The reference date hardcoded
is 1985-01-01 00:00:00 and starting from 8th September 2016, this
difference is coming out to be a length that cannot be handled by the
variable supposed to be storing it.
This will be fixed and cop will be available. This cop should be
installed on both the nodes via CLI and requires no restarts.
Apologies, I am on travel – was meaning to send a heads-up when this got
highlighted. Please feel free to reach out in case you are having
challenges. Thank you.
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065
Date: Tuesday, 13 September 2016 at 7:30 AM
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Ran into this Friday. One client reported it then a few others and knew
something weird was going on. Called it the 9/9 bug and worked with TAC and
they had workaround ready to apply.
Post by Lelio Fulgenzi
Yup. Affecting our installation of historical reporting. Not just cuic.
Sent from my iPhone
This issue seems to be affecting everyone.
Bug ID is CSCvb27878 but not publicly visible yet.
There is a COP file fix available from TAC that doesn't require a reboot or anything.
I'm sure there's a field notice coming soon. I'm guessing the COP file
will be on cisco.com soon as well if you don't mind waiting.
More discussion- https://supportforums.cisco.com/discussion/13118
806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
Abhiram Kramadhati (akramadh)
2016-09-13 02:07:32 UTC
Permalink
This impacts agent based reports and not just CUIC (can attempt 8.x as well). Reports we know:
Agent Sumary
Agent Not Ready State
CAD email reports

Best way to confirm if the report error is due to this issue is by running the corresponding SQL query on the UCCX CLI and verifying the error:
admin:run uccx sql db_cra {call sp_agent_summary('2016-09-10 07:00:00','2016-09-11 06:59:59','0',null,'John Doe,Dan Marino','Support',null,null,null,null,null,null,null,null,null,null,null)}

Internal CLI Error: java.sql.SQLException: Overflow occurred on a datetime or interval operation.

The issue is triggered when the date is 8th September and later.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065

From: <***@gmail.com<mailto:***@gmail.com>> on behalf of Brian Meade <***@vt.edu<mailto:***@vt.edu>>
Date: Tuesday, 13 September 2016 at 11:50 AM
To: Anthony Holloway <avholloway+cisco-***@gmail.com<mailto:avholloway+cisco-***@gmail.com>>
Cc: akramadh <***@cisco.com<mailto:***@cisco.com>>, "cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>" <cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>>
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date

Agent Not Ready State report was the big one that hit our clients. It's any report/stored procedure that utilizes the datediff function.

Anything including a date after September 8th seemed to be an issue.

On Mon, Sep 12, 2016 at 9:44 PM, Anthony Holloway <avholloway+cisco-***@gmail.com<mailto:avholloway+cisco-***@gmail.com>> wrote:
So, should this be impacting every CUIC install in the world? Does this impact all reports or just some? For the reports which are impacted, is only when certain date filters are applied, or any filters? Are there any instances where a system wouldn't be impacted by reportgate? I just ran one random report on a 10.6(1)SU1 system, and I don't see a problem.

On Mon, Sep 12, 2016 at 7:57 PM, Abhiram Kramadhati (akramadh) <***@cisco.com<mailto:***@cisco.com>> wrote:
Hi all,

There is a cop already available which has been provided to TAC. Only the CAD email reports are yet to be fixed, so we have a fix already there but just formalising it as a cop. We will have one cop released externally which will fix all the reports – the cop currently available fixes everything apart from CAD email reports. For that, please ask TAC for a manual workaround (there will be one cop very soon with all the fixes).

A bit of context:
There is a datediff function which calculates the time difference between today’s date and reference date. The reference date hardcoded is 1985-01-01 00:00:00 and starting from 8th September 2016, this difference is coming out to be a length that cannot be handled by the variable supposed to be storing it.

This will be fixed and cop will be available. This cop should be installed on both the nodes via CLI and requires no restarts.

Apologies, I am on travel – was meaning to send a heads-up when this got highlighted. Please feel free to reach out in case you are having challenges. Thank you.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065

From: cisco-voip <cisco-voip-***@puck.nether.net<mailto:cisco-voip-***@puck.nether.net>> on behalf of Erick Bergquist <***@gmail.com<mailto:***@gmail.com>>
Date: Tuesday, 13 September 2016 at 7:30 AM
To: Lelio Fulgenzi <***@uoguelph.ca<mailto:***@uoguelph.ca>>
Cc: "cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>" <cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>>
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date

Ran into this Friday. One client reported it then a few others and knew something weird was going on. Called it the 9/9 bug and worked with TAC and they had workaround ready to apply.


On Monday, September 12, 2016, Lelio Fulgenzi <***@uoguelph.ca<mailto:***@uoguelph.ca>> wrote:
Yup. Affecting our installation of historical reporting. Not just cuic.

Sent from my iPhone

On Sep 12, 2016, at 3:25 PM, Brian Meade <***@vt.edu> wrote:

This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file will be on cisco.com<http://cisco.com> soon as well if you don't mind waiting.

More discussion- https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Erick Bergquist
2016-09-13 02:26:03 UTC
Permalink
Also, if you have any scheduled reports those may be stuck or failed (red
x). If you rerun the scheduled reports after the fix that are stuck it
fixes them.

Wallboard servers or dashboards using the report functions effected will
also be impacted.


On Monday, September 12, 2016, Abhiram Kramadhati (akramadh) <
Post by Abhiram Kramadhati (akramadh)
This impacts agent based reports and not just CUIC (can attempt 8.x as
Agent Sumary
Agent Not Ready State
CAD email reports
Best way to confirm if the report error is due to this issue is by running
*admin:run uccx sql db_cra {call sp_agent_summary('2016-09-10
07:00:00','2016-09-11 06:59:59','0',null,'John Doe,Dan
Marino','Support',null,null,null,null,null,null,null,null,null,null,null)}*
*Internal CLI Error: java.sql.SQLException: Overflow occurred on a
datetime or interval operation.*
The issue is triggered when the date is 8th September and later.
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065
Date: Tuesday, 13 September 2016 at 11:50 AM
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Agent Not Ready State report was the big one that hit our clients. It's
any report/stored procedure that utilizes the datediff function.
Anything including a date after September 8th seemed to be an issue.
On Mon, Sep 12, 2016 at 9:44 PM, Anthony Holloway <
So, should this be impacting every CUIC install in the world? Does this
impact all reports or just some? For the reports which are impacted, is
only when certain date filters are applied, or any filters? Are there any
instances where a system wouldn't be impacted by reportgate? I just ran
one random report on a 10.6(1)SU1 system, and I don't see a problem.
On Mon, Sep 12, 2016 at 7:57 PM, Abhiram Kramadhati (akramadh) <
Post by Abhiram Kramadhati (akramadh)
Hi all,
There is a cop already available which has been provided to TAC. Only
the CAD email reports are yet to be fixed, so we have a fix already there
but just formalising it as a cop. We will have one cop released externally
which will fix all the reports – the cop currently available fixes
everything apart from CAD email reports. For that, please ask TAC for a
manual workaround (there will be one cop very soon with all the fixes).
There is a *datediff *function which calculates the time difference
between today’s date and reference date. The reference date hardcoded
is 1985-01-01 00:00:00 and starting from 8th September 2016, this
difference is coming out to be a length that cannot be handled by the
variable supposed to be storing it.
This will be fixed and cop will be available. This cop should be
installed on both the nodes via CLI and requires no restarts.
Apologies, I am on travel – was meaning to send a heads-up when this got
highlighted. Please feel free to reach out in case you are having
challenges. Thank you.
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065
Date: Tuesday, 13 September 2016 at 7:30 AM
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Ran into this Friday. One client reported it then a few others and knew
something weird was going on. Called it the 9/9 bug and worked with TAC and
they had workaround ready to apply.
Post by Lelio Fulgenzi
Yup. Affecting our installation of historical reporting. Not just cuic.
Sent from my iPhone
This issue seems to be affecting everyone.
Bug ID is CSCvb27878 but not publicly visible yet.
There is a COP file fix available from TAC that doesn't require a reboot or anything.
I'm sure there's a field notice coming soon. I'm guessing the COP file
will be on cisco.com soon as well if you don't mind waiting.
More discussion- https://supportforums.cisco.com/discussion/13118
806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
Abhiram Kramadhati (akramadh)
2016-09-15 00:47:42 UTC
Permalink
Team,

The final cop has been posted and is available with TAC, will be on CCO as well. The primary issue is on the UCCX DB and therefore, has the potential to impact reporting clients (not just CUIC). If you have any questions or challenges, let me know.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065

From: Erick Bergquist <***@gmail.com<mailto:***@gmail.com>>
Date: Tuesday, 13 September 2016 at 12:26 PM
To: akramadh <***@cisco.com<mailto:***@cisco.com>>
Cc: Brian Meade <***@vt.edu<mailto:***@vt.edu>>, Anthony Holloway <avholloway+cisco-***@gmail.com<mailto:avholloway+cisco-***@gmail.com>>, "cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>" <cisco-***@puck.nether.net<mailto:cisco-***@puck.nether.net>>
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date


Also, if you have any scheduled reports those may be stuck or failed (red x). If you rerun the scheduled reports after the fix that are stuck it fixes them.

Wallboard servers or dashboards using the report functions effected will also be impacted.


On Monday, September 12, 2016, Abhiram Kramadhati (akramadh) <***@cisco.com<mailto:***@cisco.com>> wrote:
This impacts agent based reports and not just CUIC (can attempt 8.x as well). Reports we know:
Agent Sumary
Agent Not Ready State
CAD email reports

Best way to confirm if the report error is due to this issue is by running the corresponding SQL query on the UCCX CLI and verifying the error:
admin:run uccx sql db_cra {call sp_agent_summary('2016-09-10 07:00:00','2016-09-11 06:59:59','0',null,'John Doe,Dan Marino','Support',null,null,null,null,null,null,null,null,null,null,null)}

Internal CLI Error: java.sql.SQLException: Overflow occurred on a datetime or interval operation.

The issue is triggered when the date is 8th September and later.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065

From: <***@gmail.com<javascript:_e(%7B%7D,'cvml','***@gmail.com');>> on behalf of Brian Meade <***@vt.edu<javascript:_e(%7B%7D,'cvml','***@vt.edu');>>
Date: Tuesday, 13 September 2016 at 11:50 AM
To: Anthony Holloway <avholloway+cisco-***@gmail.com<javascript:_e(%7B%7D,'cvml','avholloway%2Bcisco-***@gmail.com');>>
Cc: akramadh <***@cisco.com<javascript:_e(%7B%7D,'cvml','***@cisco.com');>>, "cisco-***@puck.nether.net<javascript:_e(%7B%7D,'cvml','cisco-***@puck.nether.net');>" <cisco-***@puck.nether.net<javascript:_e(%7B%7D,'cvml','cisco-***@puck.nether.net');>>
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date

Agent Not Ready State report was the big one that hit our clients. It's any report/stored procedure that utilizes the datediff function.

Anything including a date after September 8th seemed to be an issue.

On Mon, Sep 12, 2016 at 9:44 PM, Anthony Holloway <avholloway+cisco-***@gmail.com<javascript:_e(%7B%7D,'cvml','avholloway%2Bcisco-***@gmail.com');>> wrote:
So, should this be impacting every CUIC install in the world? Does this impact all reports or just some? For the reports which are impacted, is only when certain date filters are applied, or any filters? Are there any instances where a system wouldn't be impacted by reportgate? I just ran one random report on a 10.6(1)SU1 system, and I don't see a problem.

On Mon, Sep 12, 2016 at 7:57 PM, Abhiram Kramadhati (akramadh) <***@cisco.com<javascript:_e(%7B%7D,'cvml','***@cisco.com');>> wrote:
Hi all,

There is a cop already available which has been provided to TAC. Only the CAD email reports are yet to be fixed, so we have a fix already there but just formalising it as a cop. We will have one cop released externally which will fix all the reports – the cop currently available fixes everything apart from CAD email reports. For that, please ask TAC for a manual workaround (there will be one cop very soon with all the fixes).

A bit of context:
There is a datediff function which calculates the time difference between today’s date and reference date. The reference date hardcoded is 1985-01-01 00:00:00 and starting from 8th September 2016, this difference is coming out to be a length that cannot be handled by the variable supposed to be storing it.

This will be fixed and cop will be available. This cop should be installed on both the nodes via CLI and requires no restarts.

Apologies, I am on travel – was meaning to send a heads-up when this got highlighted. Please feel free to reach out in case you are having challenges. Thank you.

Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065

From: cisco-voip <cisco-voip-***@puck.nether.net<javascript:_e(%7B%7D,'cvml','cisco-voip-***@puck.nether.net');>> on behalf of Erick Bergquist <***@gmail.com<javascript:_e(%7B%7D,'cvml','***@gmail.com');>>
Date: Tuesday, 13 September 2016 at 7:30 AM
To: Lelio Fulgenzi <***@uoguelph.ca<javascript:_e(%7B%7D,'cvml','***@uoguelph.ca');>>
Cc: "cisco-***@puck.nether.net<javascript:_e(%7B%7D,'cvml','cisco-***@puck.nether.net');>" <cisco-***@puck.nether.net<javascript:_e(%7B%7D,'cvml','cisco-***@puck.nether.net');>>
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date

Ran into this Friday. One client reported it then a few others and knew something weird was going on. Called it the 9/9 bug and worked with TAC and they had workaround ready to apply.


On Monday, September 12, 2016, Lelio Fulgenzi <***@uoguelph.ca<javascript:_e(%7B%7D,'cvml','***@uoguelph.ca');>> wrote:
Yup. Affecting our installation of historical reporting. Not just cuic.

Sent from my iPhone

On Sep 12, 2016, at 3:25 PM, Brian Meade <***@vt.edu> wrote:

This issue seems to be affecting everyone.

Bug ID is CSCvb27878 but not publicly visible yet.

There is a COP file fix available from TAC that doesn't require a reboot or anything.

I'm sure there's a field notice coming soon. I'm guessing the COP file will be on cisco.com<http://cisco.com> soon as well if you don't mind waiting.

More discussion- https://supportforums.cisco.com/discussion/13118806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
cisco-***@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
Brian Meade
2016-09-26 14:53:10 UTC
Permalink
Just to follow up on this, Cisco released a field notice on this with a
link to the updated COP file-
http://www.cisco.com/c/en/us/support/docs/field-notices/642/fn64203.html


On Wed, Sep 14, 2016 at 8:47 PM, Abhiram Kramadhati (akramadh) <
Post by Abhiram Kramadhati (akramadh)
Team,
The final cop has been posted and is available with TAC, will be on CCO as
well. The primary issue is on the UCCX DB and therefore, has the potential
to impact reporting clients (not just CUIC). If you have any questions or
challenges, let me know.
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065
Date: Tuesday, 13 September 2016 at 12:26 PM
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Also, if you have any scheduled reports those may be stuck or failed (red
x). If you rerun the scheduled reports after the fix that are stuck it
fixes them.
Wallboard servers or dashboards using the report functions effected will also be impacted.
On Monday, September 12, 2016, Abhiram Kramadhati (akramadh) <
Post by Abhiram Kramadhati (akramadh)
This impacts agent based reports and not just CUIC (can attempt 8.x as
Agent Sumary
Agent Not Ready State
CAD email reports
Best way to confirm if the report error is due to this issue is by
*admin:run uccx sql db_cra {call sp_agent_summary('2016-09-10
07:00:00','2016-09-11 06:59:59','0',null,'John Doe,Dan
Marino','Support',null,null,null,null,null,null,null,null,null,null,null)}*
*Internal CLI Error: java.sql.SQLException: Overflow occurred on a
datetime or interval operation.*
The issue is triggered when the date is 8th September and later.
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065
Date: Tuesday, 13 September 2016 at 11:50 AM
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Agent Not Ready State report was the big one that hit our clients. It's
any report/stored procedure that utilizes the datediff function.
Anything including a date after September 8th seemed to be an issue.
On Mon, Sep 12, 2016 at 9:44 PM, Anthony Holloway <
So, should this be impacting every CUIC install in the world? Does this
impact all reports or just some? For the reports which are impacted, is
only when certain date filters are applied, or any filters? Are there any
instances where a system wouldn't be impacted by reportgate? I just ran
one random report on a 10.6(1)SU1 system, and I don't see a problem.
On Mon, Sep 12, 2016 at 7:57 PM, Abhiram Kramadhati (akramadh) <
Post by Abhiram Kramadhati (akramadh)
Hi all,
There is a cop already available which has been provided to TAC. Only
the CAD email reports are yet to be fixed, so we have a fix already there
but just formalising it as a cop. We will have one cop released externally
which will fix all the reports – the cop currently available fixes
everything apart from CAD email reports. For that, please ask TAC for a
manual workaround (there will be one cop very soon with all the fixes).
There is a *datediff *function which calculates the time difference
between today’s date and reference date. The reference date hardcoded
is 1985-01-01 00:00:00 and starting from 8th September 2016, this
difference is coming out to be a length that cannot be handled by the
variable supposed to be storing it.
This will be fixed and cop will be available. This cop should be
installed on both the nodes via CLI and requires no restarts.
Apologies, I am on travel – was meaning to send a heads-up when this
got highlighted. Please feel free to reach out in case you are having
challenges. Thank you.
Regards,
Abhiram Kramadhati
Technical Solutions Manager, CCBU
CCIE Collaboration # 40065
Date: Tuesday, 13 September 2016 at 7:30 AM
Subject: Re: [cisco-voip] UCCX CUIC Reports Stopped Working After Certain Date
Ran into this Friday. One client reported it then a few others and knew
something weird was going on. Called it the 9/9 bug and worked with TAC and
they had workaround ready to apply.
Post by Lelio Fulgenzi
Yup. Affecting our installation of historical reporting. Not just cuic.
Sent from my iPhone
This issue seems to be affecting everyone.
Bug ID is CSCvb27878 but not publicly visible yet.
There is a COP file fix available from TAC that doesn't require a
reboot or anything.
I'm sure there's a field notice coming soon. I'm guessing the COP
file will be on cisco.com soon as well if you don't mind waiting.
More discussion- https://supportforums.cisco.com/discussion/13118
806/cuic-uccx-dataset-status-failed-database-error
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
https://puck.nether.net/mailman/listinfo/cisco-voip
Loading...