ACD Database

Hi,

the table egrp ist used to create groups of exption-days.
For every exection-group you can select a maximum of 14 exeptions-days (ID1, ID2...) which are referenced by their exept_ID from table exept_day.
The defined exeption-groups are used in the schedules to determine if the schedule should run as usual or not.

When a schedule runs which executes a procedure, start and finish of the procedure is logged in the activity-log of the active controller.
The schedule settings may be confusing if you don't play with them all day long...
BUT... we had a similar problem (v8.3) when a procedure did not run one day.

You can verify your settings just by issuing SQL-queries.
If it helps, I can post my scripts to show the schedules wich run DNIS-procedures. They produce a list of DNIS and all the procedure steps which activate the CCTs on them together with the settings of all the schedules referencing them.

In the System-Administrator is an option to activate and deactivate DB-Audit. I'm not shure if you need a technician account to use it.
But the usual DB-account has not the privileges to query the oracle-audit-tables, just the table "audit" in the DTA-schema where login/logout and loading/deleting of CCTs is logged. Can't imagine that all the selects/update of the DB are logged there when audit is on, but perhaps it's worth to talk with Aspect about that. I even wouldn't try to enable audit without having talked to their support people. We had conditions where entries to call_today where written with delay caused by our high load even without audit enabled...

Another hint is to get the release-notes of the service-packs and CMs which are not yet installed on your system from eService and look for any issues/fixes concerning procedures and schedules.

Hope I can celp,
Chris

Thanks for that Chris, much appreciated. Yeah, I seen that option on Sys Admin to have audit enabled. I cant find much on it tho? What is it, what does it do and where is the audit trail stored?

Thx

The online help for the audit setting in system manager is confusing mea little bit.
I think this setting enables logging of granting/revoking access-rights to/from DB-users ("Reporting Client Security"). I played around with that, but couldn't find apropriate entries in the audit table.

BUT there is a table named "DB_audit". It is listet in the catalog of tables which may be grantet access, but doing so produces errors, can't grant any user access to this table. There is no description of this table in the docs...

Whatever, I don't think this would help you to determine if a scheduled procedure was running or not.

to find out is a procedure was run or not the ACD activity log is the place to go. It will show the begin/end of procedure 5:

01012005 060000 SYSINFO Background procedure activity(Begin/Comp Action BEGIN ProcNum 5

01012005 060000 SYSINFO Background procedure activity(Begin/Comp Action FINISHED ProcNum 5

To access use System Manager / Tools / Activity Log and login as "customer"

A possible reason for procedure not to run are if you schedule procedures at exactly the same time. Ideal one procedure or group at a time.
An invalid step also cause a procedure to fail, for example if a DNIS was deleted, which is used in the procedure.

BTW, the ACD uses the windows scheduling service.