BI Publisher Audit Entries Are Not Captured In Database Schema DEV_IAU_VIEWER.BIPUBLISHER_V and Generated Unable to get a Unique Sequence Number using query:SELECT ID_SEQ.NEXTVAL FROM DUAL Error
(Doc ID 2742095.1)
Last updated on DECEMBER 14, 2021
Applies to:
BI Publisher (formerly XML Publisher) - Version 12c to 12c [Release 12.0]Information in this document applies to any platform.
Symptoms
On : 12.2 version, Enterprise: User Interface test
Recently moved BI publisher Repository from 12c database server to other 19c database server.
Audit entries are not captured in database schema dev_iau_viewer.BIPublisher_v.
The following error occurs:
ERROR
-----------------------
2020-09-21T23:16:26.906-04:00] [bi_server1] [ERROR] [] [oracle.security.audit.logger] [tid: [ACTIVE].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: ] [ecid: c1029f4e-a46a-4f4d-b4af-9f7c2052d10b-00000096,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] IAU:Unable to get a Unique Sequence Number using query:SELECT ID_SEQ.NEXTVAL FROM DUAL
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Migrate database from 12c to 19c.
2. Check BI Publisher audit entries.
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot see BI Publisher auditing updates.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |