Visit the Below Website to access unlimited exam questions for all IT vendors and Get Oracle Certifications for FREE
http://www.free-online-exams.com
http://www.free-online-exams.com
Problem Description: Audit trail tables does not show historical changes
running AuditTrail Update Tables concurrent request finsihed with error
TOLERANCE_ID
Fatal error in fdasql, quitting...
Fatal error in fdacv, quitting...
Explanation:
he FNDATUPD concurrent request fails to complete successfully when auditing is enabled on "AP_SYSTEM_PARAMETERS_ALL" because this table has too many columns and by default auditing is enabled on every single column of this table. When the concurrent request runs, it tries to create a view for this table and hits a database limit on the number of columns of a table that can be audited (128 columns).
Therefore, if you really want to audit the "AP_SYSTEM_PARAMETERS_ALL" table then you will need to select fewer columns of this table to be able to successfully run the concurrent request.
If you do not want to audit this table, then do the following to remove auditing on this table and resolve the error:
1. Navigate to the audit group tables, and query the "AP_SYSTEM_PARAMETERS_ALL" table.
2. Set the Group state to "Disable - Purge Table" for this table.
Note: This option drops the auditing triggers and views and deletes all data from the shadow table.
3. Run the "AuditTrail Update Tables" concurrent program again.It should now run successfully.
Solution:
As per Note id 60828.1 point II,d) Set the profile option "AuditTrail:Activate" to yes to begin auditing data.
Now _AC tables is showing historical data per invoice id
AP_SYSTEM_PARAMETERS_ALL table is still in the audit, please review Note.274755.1 for the steps to take to clean up the audit trail.
Follow the steps in the referenced note to clean up the audit trail, recreate audit trail groups and respecify audit trail information via audit trail forms in apps and then run the FNDATUPD progr
As you would have seen when you ran the FNDATUPD program there are a number of views created, there are 2 types _AC and _AV each giving a different view of the data. To build up a change history of the data you need to join the data from a number of views and not just query the one single view.
Each view allows slightly different access to data, one allows you to reconstruct the value for a row at a given time (_AC), while the other provides simple access to when the value was changed (_AV). You will need to join views to get a change history of the data, this is explained in the documentation.
running AuditTrail Update Tables concurrent request finsihed with error
TOLERANCE_ID
Fatal error in fdasql, quitting...
Fatal error in fdacv, quitting...
Explanation:
he FNDATUPD concurrent request fails to complete successfully when auditing is enabled on "AP_SYSTEM_PARAMETERS_ALL" because this table has too many columns and by default auditing is enabled on every single column of this table. When the concurrent request runs, it tries to create a view for this table and hits a database limit on the number of columns of a table that can be audited (128 columns).
Therefore, if you really want to audit the "AP_SYSTEM_PARAMETERS_ALL" table then you will need to select fewer columns of this table to be able to successfully run the concurrent request.
If you do not want to audit this table, then do the following to remove auditing on this table and resolve the error:
1. Navigate to the audit group tables, and query the "AP_SYSTEM_PARAMETERS_ALL" table.
2. Set the Group state to "Disable - Purge Table" for this table.
Note: This option drops the auditing triggers and views and deletes all data from the shadow table.
3. Run the "AuditTrail Update Tables" concurrent program again.It should now run successfully.
Solution:
As per Note id 60828.1 point II,d) Set the profile option "AuditTrail:Activate" to yes to begin auditing data.
Now _AC tables is showing historical data per invoice id
AP_SYSTEM_PARAMETERS_ALL table is still in the audit, please review Note.274755.1 for the steps to take to clean up the audit trail.
Follow the steps in the referenced note to clean up the audit trail, recreate audit trail groups and respecify audit trail information via audit trail forms in apps and then run the FNDATUPD progr
As you would have seen when you ran the FNDATUPD program there are a number of views created, there are 2 types _AC and _AV each giving a different view of the data. To build up a change history of the data you need to join the data from a number of views and not just query the one single view.
Each view allows slightly different access to data, one allows you to reconstruct the value for a row at a given time (_AC), while the other provides simple access to when the value was changed (_AV). You will need to join views to get a change history of the data, this is explained in the documentation.
No comments:
Post a Comment