Follow the below steps: -
1. Go to configuration Manager --> Open current configuration
2. Expand Cognos Planning --> Cognos planning - Analyst Excel Addin --> General
3. Set Enable Terminal Services Support to YES.
4. Apply the settings.
When a client connects to cognos contributor website, there are 2 components that are downloaded on the client PCs: -
1. Cognos Planning - Cognos Component Grid Client.
2. Cognos Planning - Cognos Component Web Client.
IPC (InterProcess Communications) is a protocol that can be used with an Oracle Database, the default protocol is TCP/IP. It can only be used by a calling software, like PowerPlay Transformer, that is running on the same machine as the database. This protocol can be configured to allow a greater throughput of data, when doing large queries.
IPC is configured by the DBA in the tnsnames.ora. The calling software must use that name to call the Database. When that name is used to call the Database it will not go out to the network to find the Database, all of the calls will stay on the machine. The DBA can then tweak the settings of the IPC protocol. (example: TCP/IP Name for Oracle client is mollie.oracle.creatcomp.com this is what impromptu client would use. The tnsnames.ora Database name on the machince that Oracle resides on would be identical the under lying settings would be IPC.)
Main reason to use IPC is because it can increase performance on queries by about 25% maybe more. It will also remove networking from the puzzle of why a large query may not perform.
Example: At CDPHP we had 2 queries one that returned 26 million rows by about 400 bytes wide, in just over 4 hours through TCP/IP. We changed it to IPC and it took just over 3 hours for the same query. Query 2 returned about 11 million rows by about 60 bytes in 45 minutes with TCP/IP. With IPC setup it took 23 minutes.
Analyst uses the workspace setting to reserve part of your computer’s memory. The
setting should not normally exceed 50% of your system memory (e.g. 64,000 on a
128MgB PC).
Unless a D-Cube or Macro is struggling to open or run, respectively, there should be no
need to amend the default setting. However, you can gauge what the optimum
workspace setting should ideally be, based on the largest D-Cube.
Calculating the Optimum Workspace Setting
1. Multiply number of cells in largest D-Cube by 8 (1 cell = 8 bytes)
2. Divide the number of bytes by 1024 to get KB total
3. Double the result and enter this number in the Workspace field
4. Example: 1,500,000 * 8 / 1024 * 2 = 23,438
Following Error is received when opening or saving a node on the Contributor website: -
"Contributor Web CLient Event Handler"(errorAppServerErrorUnknown) Error information was returned from the server"Further Information:"Component error:(0x80004005)Component DescriptionInvalid Internal conditionSCript Catching error:GenericRequestServerImpl.cpp:perform:134--------------------------------------------All other errors/error stack:(errorCatch) planning21.htm::onMessageRequest"
In planningerrorlog.csv:
Unable to load url http://servername/cognos/contributor/planning33.asp?appid=xxxxxx into document.
The Root cause of this problem is that ASP Settings is too low in metabase.xml file. This is can be improved by addings/ changes settings in ASP.
Follow the below steps for the same: -
1. Close the web browser.
2. Stop the IIS and WWW services in Control Panel >Administrative Tools >Services
3. Open the following file using Notepad C:\Windows\System32\Inetsrv\metabase.xml
4. Find AspBufferingLimit and increase the value to 8388608.
5. Find aspmaxrequestentityallowed and increase the value to 8388608.
6. Save and close the file.
7. Restart the IIS and WWW services.
8. Open new web browser and try the node again.
You can estimate the approximate size of a data warehouse made up of only fact and dimension tables by estimating the approximate size of the fact tables and ignoring the sizes of the dimension tables.
To estimate the size of the fact table in bytes, multiply the size of a row by the number of rows in the fact table. A more exact estimate would include the data types, indexes, page sizes, etc. An estimate of the number of rows in the fact table is obtained by multiplying the number of transactions per hour by the number of hours in a typical work day and then multiplying the result by the number of days in a year and finally multiply this result by the number of years of transactions involved. Divide this result by 1024 to convert to kilobytes and by 1024 again to convert to megabytes.
E.g.
A data warehouse will store facts about the help provided by a company’s product support representatives. The fact table is made of up of a composite key of 7 indexes (int data type) including the primary key. The fact table also contains 1 measure of time (datetime data type) and another measure of duration (int data type). 2000 product incidents are recorded each hour in a relational database. A typical work day is 8 hours and support is provided for every day in the year. What will be approximate size of this data warehouse in 5 years?
First calculate the approximate size of a row in bytes (int data type = 4 bytes, datetime data type = 8 bytes):
size of a row = size of all composite indexes (add the size of all indexes) + size of all measures (add the size of all measures).
Size of a row (bytes) = (4 * 7) + (8 + 4).
Size of a row (bytes) = 40 bytes.
Number of rows in fact table = (number of transactions per hour) * (8 hours) * (365 days in a year).
Number of rows in fact table = (2000 product incidents per hour) * (8 Hours ) * (365 days in a year).
Number of rows in fact table = 2000 * 8 * 365
Number of rows in fact table = 5840000
Size of fact table (1 year) = (Number of rows in fact table) * (Size of a row)
Size of fact table (bytes per year) = 5840000 * 40
Size of fact table (bytes per year) = 233600000.
Size of fact table (megabytes per year) = 233600000 / (1024*1024)
Size of fact table (in megabytes for 5 years) = (23360000 * 5) / (1024 *1024)
Size of fact table (megabytes) = 1113.89 MB
Size of fact table (gigabytes) = 1113.89 / 1024
Size of fact table (gigabytes) = 1.089 GB
