Check to see if there are multiple Shareplex users and their login entries in the connections.yaml file and if so, comment out the ones that do not belong to the Shareplex instance in question. Then re-run the script create_ignore.sql as the correct Shareplex user. This will create the SHAREPLEX_IGNORE_TRANS procedure in the Shareplex schema.
Another common reason for the failure of the procedure SHAREPLEX_IGNORE_TRANS is that the script create_ignore.sql is run as the incorrect Shareplex user. If so, re-run the script as the correct Shareplex user to create the procedure in Shareplex schema.
After doing one of the above, test out the procedure to see if it is ignoring the transactions as desired before deploying it in production environment.
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center