UCCX Reporting from Informix

Below is an email exchange between myself and Cisco TAC. Though there was some interesting information in it so though i would share.


P.s Best to read from the bottom up 🙂

Hi Alex,
1. This is correct. We will ensure that you can successfully connect to the UCCX database using the System DSN.
2. No, you will not be breaching the support contract. You will just need to understand that this is an unsupported configuration. If any issues arise where this implementation may be of conflict, TAC will likely ask you to disable the feature for troubleshooting purposes since it is an unsupported configuration. If disabling the implementation fixes the issue, TAC will likely not continue troubleshooting since the issue arises in an unsupported configuration. In simple, just be aware that the configuration is not supported by Cisco TAC.
3. Uccxhruser only has permission to perform SELECT statements on the database. This is read-only access to the database, therefore you will not be able to alter the database in any way.
4. Aside from doing select statements, you could stand up a SQL server and configure a connection to UCCX using the ODBC to replicate the database. However, keep in mind, this is not supported as well and TAC cannot assist with implementation or troubleshooting. A few important things to note:
a. Select statements can lock the database tables. Consider using select statements that will not lock the database (example: Informix dirty reads).
b. Excessive and repeated querying of the historical tables can put a load on the server processing. You will want to schedule the export of data during off-times of the Contact Center.
c. It will probably be best to perform a one-time export of the historical tables at first. Then, you can schedule nightly queries to export any changed data (possibly using SQL delta changes) from the database.
d. You will not want to run the select statements during call center hours or frequently, especially in a standalone environment. The historical tables grow very large and can take a considerable time to query. A nightly execution, only querying for updates to the database, will be best.

Please let me know if you have any questions.

Thank you!


From: Alex
Sent: Monday, May 20, 2013 12:43 PM

OK that’s create so just to be clear:
You will support if we have any issue connecting to UCCX using the System DSN for ODBC connection. Correct?
By using the ODBC connection and running SQL statement on the database we are not breaching or making the support contract with Cisco void. Correct?
Can I ask what happen if one of the SQL statements we use corrupts the database? Do we still get support to restore UCCX from backups?
Is there a way to export table’s from the database instead of doing “Select * ” SQL statements on the tables? with making the support contract void?

On 20 May 2013 17:15, Ashton Webb (ashwebb) wrote:
Hi Alexis,

My name is ******* with Cisco TAC and I have accepted ownership of SR ******. I see that you have some questions about the process of exporting data from the UCCX database.

The user “uccxhruser” has permissions to read and execute stored procedures on the historical database tables. You can set up an ODBC connection to the database using the uccxhruser to connect and collect data. The process for setting up the ODBC connections beings on page 174 of the Historical Reporting Admin and Developer guide:


TAC only supports the connection to the database using the System DSN for ODBC connection. We will assist with any problems configuring the DSN and ensure that you have connectivity to the database. However, if you choose to implement the ODBC connection in a workflow as mentioned on the support site, we cannot assist with the custom implementation of the workflow. You would just need to determine how often you would like to query the database and collect the information for export.

Please let me know if you have any questions.

Thank you!

Tags: ,

About Alexis Katsavras

Working as Freelance Cisco Unified Communications Consultant in the UK. www.NetPacket.co.uk