The following errors are observed when attempting to set a Shareplex parameter to a value other than default:
sp_ctrl (name:2205)> set param sp_opo_debug_flag 0xx0f0021ff
Parameter type checking failed - look in param-defaults file
The value specified for parameter does not conform to the format, range, etc.
When a value for a parameter is changed, Shareplex will check if the value conforms to the range of values allowed for that parameter or if the format for the value is correctly specified. If one of these conditions is not met, then the error "Parameter type checking failed - look in param-defaults file" is returned. Re-issue the command by correcting the value. In our above example, the correct way to set it is:
sp_ctrl (name:2205)> set param sp_opo_debug_flag 0x0f0021ff
In some of the following examples, the set param failed due to reasons mentioned against each failure:
sp_ctrl (name:2111)> set param SP_OCT_GEN_DEBUG_OBJID "OWNER"."TABLENAME"
Parameter type checking failed - look in param-defaults file
Reason: Incorrect format of value
sp_ctrl (name:2100)> set param SP_OPO_DISABLE_OBJECT_NUM default
Parameter type checking failed - look in param-defaults file
Reason: Incorrect format of value
sp_ctrl (name:2201)> set param SP_OSY_LOCK_TIMEOUT 300
Parameter type checking failed - look in param-defaults file
Reason: Incorrect value (out of range)
sp_ctrl (name:2100)> set param SP_OPO_SQL_TRACE_ON =1
Parameter type checking failed - look in param-defaults file
Reason: Incorrect format of value (the "=" sign specified when none expected)
sp_ctrl (name:2100)> set param SP_OPO_READRELEASE_INTERVAL 10000;
Parameter type checking failed - look in param-defaults file
Reason: Incorrect format of value (the ";" sign specified when none expected)
