Hi
I am getting an error when trying to update a power Cube. Cognos support thinks something has been changed on the back end SQL database but nothing has.
Does anyone have any ideas on this issue.
{TR0153} transformer can't read the database.
RQP-DEF-0177 An error occurred while preforming operation 'sqlPreparewithOptions' status ='205'
UDA-SQL-0191. The column admit category was not found in the table or view.
Any ideas!!!!!!!!!!!!!
Did you check to see if the column is still in the view/table?
What's the datasource for the cube? If it's a cognos report, can you still run the report?
HI
the column is still in the model but when you test it produces an error such as follows
'This query contains an error that cannot be reached.RQP-DEF-0177 an error occurred whie preforming operation 'sqlprepareWithOptions' ststus ='205'
UDA-SQL-0191 the column was not found in table or view.
Looking at the source database SQL i see the fileds in question
bunker
can you do a select * on that column using the id that Transformer uses?
Is the database that Transformer using the same one as te one on you see that column on while querying?
Is your source(FM package or report or IQD) correctly pointing to the table in which the column resides?
hi,
I can do a select * in SQl on the table in question and get all the data. The transformer model is based on a frameowrk manager cube view. When i do a test on the on certain column in the query subject it gives me test results on some and then these errors messages on some others.
It sounds like this isn't a transformer problem but something is wrong with your model.
How does your query subject pick up the table? Are you doing a Select * or individually selecting the fields? If you run the EXACT SQL from your model for that dimension on your source database, does it run?
I'm guessing they changed the name of the field slightly...
hi,
I went into the current model and created an exact duplicate query subject and brought in the entire table and tested at that satge and it worked correctly.
are the tables in question present in another environment? Say, UAT/QA? If so, temporarily point the data source to the UAT server and database and test the FM query subject to see if you get the same situation where you get an error sometime and works correctly other times
The original query subject doesn't work but an exact replica works?
How did you make the exact replica? Are there other joins in the original? Does the database layer query subject run?
HI,
It seems it is releted to the model and package in framework manager. if i try and do a report now on the framework model and use certain elements from the specific query model i amd getting the "An error occurred while preforming operation 'sqlPrepareWithOptions' status ='205' error.
Any ideas
Go to framework manager and test the query subject. If you aren't doing a select * to create the query subject, check all the fields that are bringing in.
You might want to post this in the framework manager area.
hi
issue resolved. since issue was related to orginal model - i restored a backup of the orginal model when it was working correctly and things work fine. cube rebuilt on weekly basis automatical now.
thanks for help
I don't know if this is the same problem you were having, but I was also getting this error while converting cubes from Cognos v7 to v10:
RQP-DEF-0177 An error occurred while performing operation 'sqlPreparewithOptions' status ='-205'
UDA-SQL-0191. The column "Open Amount" was not found in the table or view "Capital_PO_Detail".
The problem originated when we were converting IQD queries to Query Subjects in Framework Manager. I was able to validate and run the Query Subjects in FM, and was also able to validate and run the query in a report in Report Studio, but when I tried to add the query/report into a Transformer model, I received the error.
The problem was that in FM, the field name had a space appended to the end of its name when converted so it was named "Open Amount " instead of "Open Amount". This was caused by the IQD file having a space at the end of the line for that field: "COLUMN, 18, Open Amount ". That was the only field with that space at the end of the line in the IQD file, and it had gotten copied over to the query subject during conversion. Anyway: problem solved! :)