As the manager of the automated Web to Case user, I received an email this morning stating that an incoming case could not be created. This has happened in the past due to incorrect field values, but this was actually a legitimate, well-formed request. The stack trace the email contained was this:

Reason: common.ownership.share.OperationWithInactiveUserException: common.exception.SfdcSqlException: ORA-20096:
ORA-06512: at "BASHFUL.CSAVEUTILS", line 203
ORA-06512: at "BASHFUL.TCASE", line 1044
ORA-06512: at line 1


{call tCase.insert_cases(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}

{call tCase.insert_cases(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}


The exception noted seems inaccurate, as the automated user is definitely active and all case assignment is done to queues and not directly to users, so it doesn't seem relevant. There is a trigger on Cases, but given the nature of this error I'm not quite sure it even reaches the apex code when this hits. 
Has anyone seen anything like this before?

As the manager of the automated Web to Case user, I received an email this morning stating that an incoming case could not be created. This has happened in the past due to incorrect field values, but this was actually a legitimate, well-formed request. The stack trace the email contained was this:

Reason: common.ownership.share.OperationWithInactiveUserException: common.exception.SfdcSqlException: ORA-20096:
ORA-06512: at "BASHFUL.CSAVEUTILS", line 203
ORA-06512: at "BASHFUL.TCASE", line 1044
ORA-06512: at line 1


{call tCase.insert_cases(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}

{call tCase.insert_cases(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}


The exception noted seems inaccurate, as the automated user is definitely active and all case assignment is done to queues and not directly to users, so it doesn't seem relevant. There is a trigger on Cases, but given the nature of this error I'm not quite sure it even reaches the apex code when this hits. 
Has anyone seen anything like this before?