You can certainly try :)
From memory (the last time i attempted which was prob about 2 years ago) I had all sorts of probs with oracle (using 8 client) as Cognos (FM and reporting studios) were generating case statements which wouldnt run on the database.
There are a few options for you
*...
I saw this once when reporting from a JDE database.
From memory, it was something to do with the number of joins your base query is using (ie. joining more than 31 tables).
J
Im guessing your query already includes the following columns:
* "Qty" (The measure - ie. 900, 100)
* "Product" (The rows - ie. Product A, Product B)
Create a new query item called "Percent of Qty", and define it as
percentage([Qty] within set [Product])
J
The settings you need to change are in "Text Flow and Justification"
You'll need to alter the "writing mode" settings. This will solve the 90 degrees issue, but i dont know how to get 270 degrees....
J
Hi - this probably isnt the answer you are looking for, but I can guarantee it will work!
Build your cubes to a temp area, such as as "cube builds" directory. Then at some time when no one is using cognos, and when all your cube builds are finished, (like 3am in the morning) kick off a bat...
You can definitely hide the packages in the public folders via a change to one of the system.xml files (try searching through this forum, or looking in www.cognoise.com as this question has been answered many times).
However, this hides the packages but the users are still able to access them...
I wouldnt consider this a 'ridiculous flaw' as much as a 'design feature'.
The relationships between the dimensional query subjects should be handled by the underlying query subjects in the layer that precedes the dimensional layer (as these have determinants etc). The dimensional query...
The quote character is used as part of the syntax in the expression editor, so you'll need to use an escape sequence to let datastage know that you are searching for the quote character rather than trying to end your expressions.
I can't remember what the escape secuences in datastage are, but...
The error message that you are getting is an Oracle error rather than a ReportNet error. The oracle database is complaining that your SQL query's IN(...) clause has more than 1000 items. I dont know if this is something you can change in oracle.
Are you selecting distinct material values in...
Check that there isnt something conflicting with IIS.
I had the exact same problem when I installed Cognos8, and this was because I had also the 'OracleOraHome92HTTPServer' running on my computer.
To see if there is anything else running, instead of trying to go to http://computername/cognos8...
I'm not 100% sure that I understand your problem, I dont know what the "Solve Order" property is...
You should be able to get it to aggregate properly...Look at the following example (copy the code below, and in report studio use Tools --> Open report from clipboard)
This example is...
Firstly, you can change the type of prompt that reportnet generates by default by changing one of the properties for the data item in framework manager.
You could try to edit the query that populates the prompt control by auto grouping and summarizing (so that the sql generates a 'select...
Assuming you are talking about selecting values from a multi select prompt.....
1. Add the parameter item to the query, and name it (lets call it ParmItem)
2. Add the 'ParmItem' data item to the report
3. Group the list by the 'ParmItem'
4. Go into the pagination settings, and break the...
Assuming you are using a selection prompt (as opposed to a type in prompt), i'd look at revising the query that is building the prompt control - the poor performance sounds like reportnet is trawling through a large table trying to retrieve the unique values to build the prompt control.
You...
in the transformer output column derivation, convert the integer to a string, and concatenate substrings from the string and the '/' characters to put it all together.
Assuming your input column with the integer is called inputdateval
Try the following...
You could always include the whole table and use the rank() function in Report Studio reports, and add a filter in the report that is rank(...) <= 50 to return the top 50.
OR
You could get the whole lot done in the database (in a view?)
OR
You could have a database table/view created which ranks...
Also check the sqlnet.ora file that is in the same directory as the tnsnames.ora file.
I've had a few problems with this file in the past causing datasources to not connect correctly through Cognos, even though you can connect through the oracle tools.
Try commenting out (by adding a # at...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.