Genesys CTI User Forum

Genesys CTI User Forum => Genesys CTI Technical Discussion => Topic started by: cherylw on May 29, 2013, 09:03:51 AM

Title: UCS archive via USM failing
Post by: cherylw on May 29, 2013, 09:03:51 AM
Anyone else had issues with records not archiving? I'm getting the below error in logs. Records meet the desired archive/prune criteria, however will not archive, scans them a leaves them in current schema.

UCS is v8.1.200.03 DB is Oracle 11G

09:46:30.172 Std 20145 [uningTask-9] <xxxxxxxxxxxxxxxx> Recover insertion of 'PhoneCall' with Id (xxxxxxxxxxxxxxx) failed with error Invalid IxnMedia 'Voice' for PhoneCall object, cannot recover
com.genesyslab.icc.api.contactserver.PersistentException: Invalid IxnMedia 'Voice' for PhoneCall object
at com.genesyslab.icc.contactserver.persistent.PhoneCallManager.insert(PhoneCallManager.java:212)


Also, USM randomly crashes with below error;

16:58:10.128 Dbg 29999 [7.82:207797] task-38 2 MANUAL 1369747178812 ERROR 27637/111486 1-1 error:-1-Exception counting thread id to process : com.genesyslab.icc.api.contactserver.PersistentException: Recoverable error 'com.genesyslab.sql.exception.RecoverableException: IO Error: Connection reset' occured in database server transaction - Vendor Code=17002, SQLSate=08006
Title: Re: UCS archive via USM failing
Post by: cavagnaro on May 29, 2013, 02:50:53 PM
The error is clear, your DB Server (not genesys) is closing the connection. Maybe can't handle all that info and has a timeout?
Check with your DBA to analyze the DB Server behavior in that moment
Title: Re: UCS archive via USM failing
Post by: cherylw on May 29, 2013, 03:35:30 PM
Thanks, so that would explain why the task is failing on the large number of records to archive. However, the process is still ignoring records that meet the 3 archive criteria specified by Genesys support documentation. Which means that the number of records to scan is not reducing and the db is closing the connection.

Any ideas?
Title: Re: UCS archive via USM failing
Post by: cavagnaro on May 29, 2013, 03:45:00 PM
Again...check with your DBA...he must analyze the server behavior and configuration. Probably also do some indexation and fine tuning.