Our team has run into an interesting situation. Upon checking out an object from a schema and it’s the very first checkout for that schema (this is important to note), the object is completely locked prohibiting any modifications or check ins even by the user who did the check out or by the TC Admin. As the TC Admin (with TC_ADMIN_ROLE), tried ‘Break Team Coding Lock’ but that didn’t do anything. The only workaround we could find was to update the “check out” record in the TCX_OBJECTS table, which released the lock on the object. Subsequent checkouts in the same schema on the same or different objects have no issues. Has anyone encountered this and if so, how did you resolve it?
Object: Stored Procedure
Toad Version: 184.108.40.206
Toad Message: "Info - Procedure WHS.F_DISTR_CCS_LOAD checked out from Team Coding." "Output: Procedure WHS.F_DISTR_CCS_LOAD is locked by . Team Coding prevented compilation." (see screenshot if possible - looks small here) Note the message doesn't state who has the object locked. It only says "locked by" with no name.
Thanks for the help!