One procedure in a custom package appears correctly in the New Database Task Schedule's method LOV, but a second procedure in the same package doesn't, despite identical-looking setup, granted permissions, and confirmed working execution when run directly in PL/SQL Developer.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check whether a Database Task was actually created for that second procedure first — creating the Database Task record itself is a separate step that has to happen before it becomes available to select in New Database Task Schedule, and skipping straight to scheduling without first creating the task for that specific procedure is an easy step to miss when a package already has one working procedure making it look like the setup should be identical.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions