when we connect to redshift SQl query is not generating has Teradata connection. its splitting physical query in the session log
Can you clarify? It sounds like it might require a support ticket and not an 'idea'
Problem Description:
Physical query for OAS reports is not generating in expected form by using redshift ODBC Advance connection.
Problem Explanation and Challenges:
While generating physical query, we are facing 3 different patterns of issues.
Problem 1: Timedifference logic is not populating in a proper executive query format. Due to which the debugging process will be challenging as the timestamp difference columns are not parsing. It is in frontend computed format.
Problem 2: For any parent and child connected reports, Teradata is generating physical queries in subquery format but using redshift, the subqueries are generating separately. The challenge here is to identify the relationship between parent and child reports, as physical query is splitting the subquery.
Problem 3: Query with multiple joining condition like an inner join or a left / right outer join, the query gets splits up into different whole query. Again, the debugging process get tricky as the columns splits up from main query.
It is still not clear what you are trying to do. What is the use case are for mixing feature sets between DBs? What is your source DB, Redshift or Teradata?
We are migrating our enterprise data warehouse from Teradata to Redshift.
In this process, our backend table structure will remain same on Redshift, and all our OAS reports will be now pointed to Redshift database.
While running OAS Reports pointing to Teradata source, OAS Generates full query that can be directly executed on backend Teradata database, it is very helpful for troubleshooting data related issues.
But Incase of Redshift as a source, OAS is splitting that query into multiple sub queries which is not in the required format that can be directly executable on Redshift database. so it is becoming more difficult to validate the data related issues.
I feel it will be a big bottleneck for any migration projects to redshift if it is not resolved. Hope problem statement is clear and looking forward for a meeting if that helps.
Thanks
Sreekanth
OAS Classic Report Results display the first 5000 rows and the OAS user needs to click the next button for the next 5000 rows and so on. The 5000 row limit is the maximum allowed to be setup in the OAS Console. OBIEE Report Results support display of the entire report results data set. Our users would like this feature in…
Background We recently identified an issue through an inconsistency in the number of records returned in an API response. This allowed us to notice, after the fact, that a fix had been applied that changed the behavior of an existing API. Problem We understand that information about resolved bugs is eventually made…
We need a way for non-admin users to view the backend/physical SQL queries executed by reports (via Session and Query Logs) without granting them full administrator access. OAC's custom Application Role model (Console > Roles and Permissions) allows selecting fine-grained permissions instead of assigning predefined roles.…
Customer would like to request that IBM DB2 12.x be added as a supported data source for Oracle Analytics Server. They hope that it will be included as a certified and supported data source in the next(Year 2027 ) OAS release. Background: The customer is currently operating a reporting and analysis platform using Oracle…
We would like to restrict the MCP to certain OAC application roles instead of all the users. Please help us to achieve this functionality.
