Scheduled Batch Validation Stops After User Password Is Changed
(Doc ID 1354785.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Clinical - Version 4.6.0 and later
Information in this document applies to any platform.
User noticed that their scheduled Batch Validation jobs no longer ran even though the job was still scheduled after changing their database password (ie records for batch validation runs which get kicked off by the scheduled job no longer appear in the Batch Jobs screen after password is changed) .
symptoms that can be observed:
- the users database account gets locked (if the Profiles => 'FAILED_LOGIN_ATTEMPTS' database feature is being used and the number of failed logins exceed the configured value)
- the 'REP-501: Unable to connect to the specified database' error is seen in the Reports Queue Manager for the Batch Validation jobs which get kicked off by the scheduled job but fail to run
Why is that? Is there an alternative to stop this from happening?
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|