cancel
Showing results for 
Search instead for 
Did you mean: 

BI 4.0: Auditing inconsistency

rafiq_islam
Explorer
0 Kudos

Hi Folks,

I am currently working with a client who has BI 4.0 SP4 and Patch 1 on Linux.

They have auditing enabled and we are experiencing some intermittent issues with audit logs.

We have created a report (on Webi) to audit modification to existing universes. Most of the occasions the audit report is capturing the correct audit details. But sometimes they seem to be skipping some events. For instance, one universe has been modified last week, but it never appeared in the auditor/audit report.

Please let me know if anyone of you have come across this inconsistent auditing issue. Could this be a patch related issue?

Your input will be much appreciated,

Rafiq Islam,

BI Consultant

Accepted Solutions (0)

Answers (4)

Answers (4)

rafiq_islam
Explorer
0 Kudos

Thanks for your kind responses.

Sohel and Asma,

If I reconfigure the audit database again won't I risk losing previous audited data?

What causes this non zero byte files to stay? Is there any way to prevent this auditing inconsistency to happen moving forward?

Will appreciate your comments.

Rafiq

former_member190781
Active Contributor
0 Kudos

Hi Rafiq,

Reconfiguring audit database to the same schema wont cause any issues.

The switches which I have suggested will help CMS to identify the corrupted events and mark them as .bad files but unfortunately there is no way to prevent the corruption.

Regards,

Sohel

rafiq_islam
Explorer
0 Kudos

So when they are marked as bad files, CMS will clear them automatically from audit folders? I So if a file gets corrupted then the logs are not written to audit database and thus this inconsistency occurs, right?

I assume this audit inconsistency is common in BI 4.0 then, is that correct?

former_member190781
Active Contributor
0 Kudos

Hi Rafiq,

The reason for corruption is unknown, you may find some information in CMS logs. There may be network communication failures, DB connectivity issues, local disk corruption etc.

with the help of -saveCorruptedFiles will still save the corrupted temp files in the audit folder with .bad extension but there is no way to inject these .bad files in Audit DB.

This is not a common behavior but yes observed on many environments.

Please enable trace on CMS and review the logs to check if you can find out the root cause.

Regards,

Sohel

rafiq_islam
Explorer
0 Kudos

Thanks Sohel

former_member190781
Active Contributor
0 Kudos

Hi Rafiq,

As Asma suggested clear auditing folder. Follow the procedure given below.

> Stop SIA.

> Clear/Move audit temp files.

> Run cmsdbsetup.sh and reconfigure audit database.

> Start SIA.

> Logon to CMC and add following commands to the command line of all the servers on which audit events are enabled.

-saveCorruptedFiles -checkForCorruptEvents

Hope this helps.

Regards,

Sohel

0 Kudos

Hi Rafiq,

- If you check the Auditing folder (Under ..\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\Auditing), are there non-zero byte files that are old?

- If there is one file that was not properly deleted from the folder, so try to clear your Auditing folder :

1. Take a backup of the files in the Auditing folder.

2. Delete all the files from the Auditing folder

3. Restart the Server Intelligence Agent (SIA)

I hope that can help you.

Thanks,

Asma

former_member182521
Active Contributor
0 Kudos

Hi Rafiq,

Have you enabled logging for your client applications? I would suggest you to have a look at

SAP Note : 1586166 - How to enable tracing for BI4.0 client applications

Regards,

Mani