Yes I think you're doing something wrong.  You don't mention a bridge table for your N:N relationship, which you probably would want to have for any legitimate bridge table scenario but I really don't think this is one of them. 

Quotecovering the time between START_DATE and END_DATE.

Can you clarify what you mean by this.  Is this a duration?  What are you trying to do here?

Also is the N:N in the time dimension or the relationship between it and the fact table?  You are unclear.


I can not comment about possible other modelling problems because I have not seen your model and all the information I have is what you have chosen to reveal.



One very big problem with data sets is that you can't define data security on them, unlike tables in a loaded schema.

I use Active Directory on prem, even though we have Azure Active Directory.

I'm sorry, but I'm not up on my acronyms.  What specifically is "ADS"?  Unfortunately, when I search the web for ADS is get ads (advertisements).  Not something I typically need to search for deliberately.  I get plenty already.

That is expected.  The dashboard that gets data from the database must perform these tasks for every visualization every time the user touches something.
write SQL
connect to the database server
run a query that involves joins between multiple tables
get a response back
update the viz

Put another way, when you are connecting to the database:
Cognos must write a more complex query.
Cognos spends time communicating with the db server.
the database server must perform lookups and filters across joins.
Cognos spends more time communicating with the db server.
Cognos waits for the data to be downloaded across the network.

In contrast, using a Cognos dataset means
write SQL
get data from a single table
update the viz

Choosing to use a Cognos dataset involves considering the tradeoffs between size and speed.  For most cases, a dataset will perform much faster than a direct database connection.


This is the same as using Power BI and comparing Import vs. Direct Query.

Hello,

We normally use Azure SSO for user login in Cognos.
To free up some licenses, we wanted users to be able to log in using ADS authentication instead.

I set "Selectable for authentication" = True for the ADS namespace and tried logging in with ADS, but the login keeps failing.

During testing, I noticed something odd:

When Cognos prompts for the user ID and uses the saved password, the login fails.

If I enter the same user ID but retype the password (not using the saved one), the test works.

So it looks like the stored/saved password for ADS is invalid, even though the password itself is correct.

This behavior is consistent every time I test.

Has anyone else seen this when switching from SSO to ADS, or know why Cognos rejects the saved credentials but accepts the manually entered ones?

Thanks!

Good morning!

As the title says: I have made a number of datasets in Cognos, and connected them logically in a data module. On this module I built a dashboard that performs perfectly.

To save the local cognos server, I asked our local ETL specialist to recreated the datasets with ETL, and to write them off in an Oracle database. These tables I have then connected again in a data module, in the exact same way as I did with the datasets. On this module I built an identical dashboard as well. The performance of this dashboard is absolutely horrable, and most visualisations time-out on loading.

The fact table in question is a table with about 130.000 records, using several foreign keys for which dimensions were built. Most of these dimensions are 1:N to the fact table, but I also built a date dimension that is N:N, covering the time between START_DATE and END_DATE. When using this dimension, the number of records increases to 170 million.

Am I doing something wrong, or is the discrepancy in performance between the Oracle-database and the Datasets to be expected?

Thanks for your insights!

Hard to judge what is actually happening without looking at logs.  But there are a few things it could be.  Here are some things to check:
1. Start Cognos on cognosprod01 first and wait until it is fully up.
Then start Cognos on cognosprod02.
On prod02, check cognosserver.log for messages like "unable to register with Content Manager". If you still see that, it almost always points back to keys or URIs not matching.

2. Verify the Content Manager URIs are identical on both servers
In Cognos Configuration on both prod01 and prod02, under Environment, the Content Manager URIs list should be exactly the same. For example.
https://cognosprod01:9300/p2pd/servlet
https://cognosprod02:9300/p2pd/servlet
Same order, same protocol, same host names that match the certificates.

3.Make sure both servers share the same Cognos encryption keys
It is not enough that the HTTPS server certificates trust each other. The Cognos "internal" crypto keys also have to match or the dispatcher will not register in the content store.

On the server that starts cleanly (cognosprod01):
Stop the Cognos service.
Open Cognos Configuration.
Use Tools > Export encryption keys (or similar wording in 12.0.4) and create the keys ZIP file with a deployment password.
Copy that ZIP to cognosprod02.

On cognosprod02:
Stop the Cognos service.
Open Cognos Configuration.
Use Tools > Import encryption keys, point to the ZIP from prod01, and enter the same deployment password.
Save the configuration.

Not sure any of that helps... but if it does great :)

-Daryl

This topic has been moved to Cognos Analytics.

https://www.cognoise.com/index.php?topic=38365.0

Hi everybody, I'm getting error related to dispatcher now. dispatcher of second server is not getting registered in content manager.

Can anybody guide what I'm missing now in configuration.

Great question. Python is definitely a good starting point, but being an "AI professional" is really about understanding a few core areas:

• Data fundamentals — how data is structured, cleaned, and prepared
• Machine learning basics — models, training, evaluation
• Prompting and LLM understanding — huge skill today
• Real-world problem framing — knowing when and why to use AI

In the real world I have found most people don't really know AI or how to apply it.  But I would suggest to start simple with what you know and what you are good at / interested in then build your skills from there...

Totally get where you're at, we see it all the time now... a lot of teams are in this exact spot where legacy Cognos content is still running the business, but nobody remembers how it was built.

A few quick tips:

• Open the existing reports in edit mode if you can. Even without full access, you can often see where the data comes from.
• Check whether the reports use Framework Manager packages or Data Modules — that tells you what you're working with.
• IBM SkillsBuild and the Cognos YouTube tutorials are great starter resources.

If you ever get stuck, feel free to ask here.
And if your org decides to clean up or migrate the environment, my team works in Cognos upgrades and BI modernization — happy to help point you in the right direction.