Unable to open project XXXXX. The expected data type from the stream was different from what the stream contained on launching OWB
Steps to Reproduce:
- Open any plan from Clarity into Open Workbench (OWB)
Expected Results: Project Plan is opened in to OWB
Actual Results: The error "Unable to open project XXXXX. The expected data type from the stream was different from what the stream contained" is received and the plan is not launched to OWB
A custom attribute, of the Project Object, in Clarity Studio showed that the associated lookup was a number based lookup, but the actual lookup had CODE as its hidden key which is character based. The standard lookup SELECT query that is built to retrieve the lookup values links the select data value id to the lookups hidden key. This caused a database data type mismatch error (ORA-01722 Invalid Number) which halted any plan to be opened.
The custom attribute should be deleted and recreated, ensuring that the correct lookup data type is configured.
Keywords: CLARITYKB, owb different stream ORA-01722, invalid number data type.