S
steve pittman
Guest
We were able to check this out a little quicker than expected. The problem you are seeing is a known problem which will be fixed in the upcoming 11.7.1 service pack. There is no simple workaround. One possible workaround would be to give all your stored procs unique names and make changes to all the callers. If using this workaround, don't disconnect and re-connect to one of your aux databases. That hits the same problem exposure. Clearly this workaround is a lot of work and disruption, so it may not be so useful. 11.7.1 is your best alternative. hope this helps, ....steve pittman
Continue reading...
Continue reading...