While running batch optimizer, when the job encountered a sql statement with bind variables, it stops and waits for values.
Is there a way to tell the sql optimizer to use a script for these variables or ignore them somehow without the need to enter the values for every sql statement?
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center