No Audit data Extracted when the SAP Audit database is on a Sybase/SQL Anywhere server.
Environment
Product version(s): All current 360Suite versions
Third-party technology: SAP Audit database hosted on Sybase / SQL Anywhere
Database: Sybase / SQL Anywhere
Symptoms
A job run with Audit data extraction enabled, where the SAP Audit database is hosted on a Sybase/SQL Anywhere server, completes with no action: the SQL query executed by the job returns 0 rows.
Running the exact same SQL query manually from SQL Anywhere's SQL Central tool works as expected and returns data.
Steps to Reproduce
Configure a job with Audit data extraction enabled, targeting an SAP Audit database hosted on Sybase/SQL Anywhere.
Run the job.
Observe that the job completes with no action and the underlying SQL query returns 0 rows.
Cause
Context: This issue occurs when the JDBC driver used to connect to the Sybase/SQL Anywhere database is outdated or incorrect.
Technical explanation: The incorrect/outdated JDBC driver is located in the /libs folder of the 360Suite Tomcat.
Resolution
Follow the steps below to update the JDBC driver.
Option 1: Permanent Fix
Stop the 360Suite Tomcat.
Delete the existing jconn4.jar from the /libs folder.
Copy the approved jconn4.jar file into the /libs folder. The approved driver (jconn4_APPROVED.zip) is attached to this article.
Start the 360Suite Tomcat.
Rerun the job.
Additional Information
If the issue persists after updating the driver, contact support with your 360Suite logs, the JDBC URL used, and the steps you followed in this article.
Related Articles
SAP BusinessObjects Auditing vs. 360Suite – Understanding the Difference
Purpose This article clarifies a common misconception: SAP BusinessObjects Auditing (commonly referred to as "Auditor") is not a 360Suite module. It is a native SAP BusinessObjects feature. This distinction matters when checking whether Auditing is ...How to expand Dataprovider SQL Query column in 360Eyes database
Symptom When running 360Eyes Impact Analysis Reports (such as Report 52), users observe that the SQL query stored in the 360eyes_REPORTS.unx / Eye Document / Dataprovider / Dataprovider Sql Queryfield is incomplete, partial or truncated. This often ...SQL Anywhere: JZ0C0: Connection already closed
Symptoms When running Web Intelligence (WebI) jobs in SAP BusinessObjects connected to a SQL Anywhere (Sybase) audit database, the job may fail with the following error: JZ0C0: Connection already closed. This results in WebI job crashes and ...360Eyes Jobs Running Slowly During Snapshot Copy Due to Database Index Fragmentation
Summary This article explains why 360Eyes jobs may run slower than usual, particularly during the snapshot copy step, and how to resolve the most common cause of this issue. Symptoms You may notice one or more of the following: 360Eyes jobs are ...Audit Snapshot Fails in 360Eyes — Unsupported DB URL (jdbc:sqlanywhere)
Symptoms When running the 360Eyes – Audit job, the job fails during DO_SPECIFIC_JOB_ACTIONS and the log displays: Could not generate snapshot : Current DB URL (jdbc:sqlanywhere:DSN=BIA_Audit_PROD) is not supported. Cause The Audit data source is ...