OBIEE11g: Error: 'IAU:IAU-5046: Stopping AuditLoader, caught exception: ' BI Publisher Auditing has Stopped Writing to Database (Doc ID 1509625.1)

Symptoms

Following the removal of BISystemUser from an extenally defined LDAP (OID), the auditing component for BI Publisher has stopped writing to the database.
You do see however that audit logs are still being written to the respective managed server directories under ( eg. ../bifoundation_domain/servers/bi_server1/logs/auditlogs).

When starting the managed servers you see the following in the diagnostic log (bi_server1-diagnostic.log):

[2012-10-25T09:41:18.053+01:00] [bi_server1] [ERROR] [] [oracle.security.audit.ajl.loader.AuditLoaderManager] [tid: AuditLoaderRunner] [userId: ] [ecid: <ECID>] IAU:IAU-5046: Stopping AuditLoader, caught exception: java.lang.NumberFormatException: For input string: "11.1.1.6.0"[[
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Long.parseLong(Long.java:419)
at java.lang.Long.parseLong(Long.java:468)
at oracle.security.audit.config.Attribute$DataType.parseXMLValue(Attribute.java:112)
at oracle.security.audit.ajl.reader.FileSetLogReader.setAttribute(FileSetLogReader.java:981)
at oracle.security.audit.ajl.reader.BusStopTxtLogReader.parseRecord(BusStopTxtLogReader.java:367)
at oracle.security.audit.ajl.reader.FileSetLogReader.read(FileSetLogReader.java:956)
at oracle.security.audit.ajl.loader.AuditLoader$SingleLookaheadBusStopLogReader.gotoNextRecord(AuditLoader.java:355)
at oracle.security.audit.ajl.loader.AuditLoader.readMessages(AuditLoader.java:456)
at oracle.security.audit.service.AuditLoaderManager.readMessages(AuditLoaderManager.java:209)
at oracle.security.audit.service.AuditLoaderManager$Runner.run(AuditLoaderManager.java:284)
 

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.