Error 8203

1

Adaptive Server expected a descriptor it was trying to get to be in state “active,” but it was not.

2

When Adaptive Server prepared to clean up a descriptor, it expected the descriptor to be in state “destroy,” but it was not.

3

When Adaptive Server prepared to return a descriptor from the resource free list, it expected the descriptor to be in state “free,” but it was not.

4

Adaptive Server prepared to move a descriptor from state “drop” to state “destroy,” but the descriptor was not in state “drop.”

5

Adaptive Server expected a descriptor it was creating for use to be in state “create,” but it was not.

6

Adaptive Server expected a descriptor it was creating for use to be in state “create.” However, Adaptive Server received an invalid status and could not determine what state the descriptor was in. Therefore, even though it expected the descriptor to be in state “create,” the message shows it expected the state to be “Invalid Stat Return.”

7

When Adaptive Server prepared to move a descriptor to state “free,” it expected the descriptor to be in state “clean,” but it was not.

8

When Adaptive Server needed to mark a descriptor as “active” and it had previously marked it for “drop,” it expected the descriptor to be in state “drop” and it was not.

9

When Adaptive Server prepared to move a descriptor from “active” to “drop”, it checked to make sure the descriptor was in state “active,” but it was not.

10

When Adaptive Server prepared to store information about a new descriptor, it expected the descriptor to be in state “create,” but it was not.

11

When Adaptive Server tried to initialize the lock promotion information in the descriptor, it expected the descriptor to be in state “create,” but it was not. This state is only raised by diagserver.