Skip to main content
CollegeSource Production

Pending Audits via job_queuq_list and job_queue_destination

This page provides troubleshooting information to resolve pending audits that were created by Transferology

 

Check the ceg4.log

Please check the ceg4.log for any obvious errors. If the ceg4.log is not available or the log does not contain obvious errors, then proceed with these instructions.

 

The JOB_QUEUE_LIST and JOB_QUEUE_DESTINATION tables provide information to assist troubleshooting pending Transferology audits. When the Connector accepts an audit request, a row is inserted into the JOB_QUEUE_LIST and JOB_QUEUE_DESTINATION tables.

Oracle Queries

-- QUERY_1 : Provides overview status of audit requests during the last 24 hours
select l.jobid, l.userid, l.status, l.servername, d.status, d.userid, d.destination_url, d.send_error_count
, d.send_date, d.send_error_message
from job_queue_list l
left outer join job_queue_destination d on d.jobid = l.jobid
where l.jobid >= to_char(sysdate-1,'yyyymmdd') and r.jobid < to_char(sysdate+1,'yyyymmdd')
and l.userid like '%@TRAN%'
order by 1;

-- QUERY_2 : Identifies output for an audit
select r.jobid, r.INT_SEQ_NO, count(o.jobq_seq_no) from job_queue_run r
left outer join job_queue_out o on o.jobq_seq_no = r.INT_SEQ_NO
where r.jobid >= to_char(sysdate-1,'yyyymmdd') and r.jobid < to_char(sysdate+1,'yyyymmdd')
and r.userid like '%@TRAN%'
group by r.jobid, r.INT_SEQ_NO order by 1;

SQL Server Queries

-- QUERY_1 : Provides overview status of audit requests during the last 24 hours
select l.jobid, l.userid, l.status, l.servername, d.status, d.userid, d.destination_url, d.send_error_count
, d.send_date, d.send_error_message 
from job_queue_list l
left outer join job_queue_destination d on d.jobid = l.jobid
where l.jobid >= convert(varchar(8), getdate()-1, 112) and r.jobid < convert(varchar(8), getdate()+1, 112)
and l.userid like '%@TRAN%'
order by 1;

-- QUERY_2 : Identifies output for an audit
select r.jobid, r.INT_SEQ_NO, count(o.jobq_seq_no) from job_queue_run r
left outer join job_queue_out o on o.jobq_seq_no = r.INT_SEQ_NO
where r.jobid >= convert(varchar(8), getdate()-1, 112) and r.jobid < convert(varchar(8), getdate()+1, 112)
and r.userid like '%@TRAN%'
group by r.jobid, r.INT_SEQ_NO order by 1;

JOB_QUEUE_LIST Status Values and Meanings

Status

Description

N Initial status, indicates the audit request is available for processing by DARwin or uAchieve
E DARwin or uAchieve encountered an error during audit processing
X DARwin got stuck processing the audit
D The audit was processed

 

JOB_QUEUE_DESTINATION Status Values and Meanings

Status

Description

A Audit request was accepted by the Connector
Q Audit is queued to send output to Transferology
R Audit is waiting to retry a send of output to Transferology. Check the send_error_message from the first query.
S Audit output was successfully sent to Transferology

 

Interpreting JOB_QUEUE_LIST and JOB_QUEUE_DESTINATION Results

JOB_QUEUE_LIST

status

JOB_QUEUE_DESTINATION

status

Meaning

no row no row

The Connector has not received the audit request from Transferology; review the following:

  • Your school's External Audit URL is correct
  • Your Connector can be reached by an external server through your firewall
N A

The Connector has received the audit request but DARwin or uAchieve has not processed the request; review the following:

  • The xservice.darwinDaemonServerName property defined in the cas4.properties correctly matches your DARwin or uAchieve daemon
  • The DARwin or uAchieve daemon is connecting as the same database user into the same database
E A

DARwin or uAchieve encountered an error while processing the audit request:

  • Review the DARwin/uAchieve logs and dump
X A

DARwin stopped processing the audit request:

  • Review the DARwin logs and dump
D A

DARwin or uAchieve processed the audit request, but possibly did not produce audit output:

  • Run QUERY_2 to determine whether audit output exists
D R

DARwin or uAchieve processed the audit request, but the output has not been sent to Transferology; review the following:

  • Run QUERY_2 to determine whether audit output exists
  • Run QUERY_1 to identify the error that is preventing the Connector from sending the audit output to Transferology
D Q See above for status D / R
D S

The Connector has successfully returned the audit output to Transferology. If the completed audit in Transferology is not visible:

  • Review if your Connector is using the older xservice.destinationUrl property and it is pointing to a different Transferology server

 

  • Was this article helpful?