An object's team coding status is not correct when checking it out.
Steps that cause the error:
1) Open an instance of Toad, load an object (procedure/package/etc.) and check-out.
2) Open another instance of Toad as another user and connect to the same instance.
3) Load the Schema Browser and look at the object checked out in the first session, its status is locked.
4) Switch back to the first session and either check-in or undo the check-out.
5) Switch back to the second session - In the Schema Browser, the object's Team Coding status is still locked.
Refreshing the screen or closing the Schema Browser window will not change the status, the only way to do so is to disconnect and re-connect. The same behavior is also present if the object is opened in the Editor window instead.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center