Re: disable a sequences

there was a post on the oracle-l list last week about a sequence being exhausted. one poster thought that perhaps it was taking a vacation.

it could be a namespace issue (private or public synonym). it could be a security issue (a grant of select on the sequence to the app user role or user account)
it could be that the sequence was created with a maxvalue that had been reached, with a nocycle clause.
it could be (as others have posted) that the trigger became invalid due to a broken dependency.
all of these answers can be found in the data dictionary and also perhaps as error messages to the calling application.

-bdabfh Received on Fri Feb 25 2005 - 12:38:47 CST