Messages QBC30 through QBC50

Messages on this page are sorted by SQLSTATE. Locate the appropriate code in the table below, and click the link for a full description of the message.

SQL State Msg Type Number SQL Code Message Possible Cause
QBC30 Error 20468 -1006230L "lock request was interrupted" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC31 Error 20469 -1006231L "ACCESS exception: OS error %2: %3 %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC32 Error 20470 -1006232L "Unknown ParamSet error %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC33 Error 20471 -1006233L "CONSTRAINT exception: OS error %2: pathname len is %3, your buffer size is %4. Pathname is %5 %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC34 Error 20472 -1006234L "The IQ SET command has no option named '%2' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC35 Error 20473 -1006235L "The IQ SET SERVERDEFAULT command requires the SA_ROLE %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC37 Error 20475 -1006237L "The IQ SET option, '%2', can not be set server-wide %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC38 Error 20476 -1006238L "The IQ SET option, '%2', can only be set server-wide and not for a session %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC39 Error 20477 -1006239L "The IQ SET option, '%2', can only be changed by users with SA_ROLE or DBO_ROLE %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC40 Error 20478 -1006240L "The value, %2, is not valid for the SQL Anywhere option, '%3' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC41 Error 20479 -1006241L "The value, %2, is not valid for the integer option, '%3' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC42 Error 20480 -1006242L "The value, %2, is not valid for the unsigned integer option, '%3' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC43 Error 20481 -1006243L "The value, %2, is not valid for the boolean option, '%3' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC44 Error 20482 -1006244L "The value, %2, is not valid for the unsigned 64bit integer option, '%3' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC45 Error 20483 -1006245L "The value, %2, is not valid for the string option, '%3' %1" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC46 Error 20484 -1006246L No message No additional information available.

Click here for a list of possible parameters and odbc states.

QBC47 Error 20485 -1006247L "shared segment: os error" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC48 Error 20486 -1006248L "shared segment: virtual addr does not match" No additional information available.

Click here for a list of possible parameters and odbc states.

QBC49 Error 20487 -1006249L "Shared segment attach failed because the shared memory segment was created by a process running a different version of sybase_iq." No additional information available.

Click here for a list of possible parameters and odbc states.

QBC50 Error 20488 -1006250L "Requested shared memory size, SHMEMMB & TEMPSHMEMMB, too big for available shared memory segments, SYSTEMSHMMAX & SYSTEMSHMSEG" No additional information available.

Click here for a list of possible parameters and odbc states.


Created April 27, 2010. Send feedback on this help topic to Sybase Technical Publications: pubs@sybase.com