OAS 6.4 REDSHIFT DATA CONNECTION SENDING ROGUE SQL TO DB

Prajna

when we connect to redshift SQl query is not generating has Teradata connection. its splitting physical query in the session log

Gabby Rubin-Oracle

Can you clarify? It sounds like it might require a support ticket and not an 'idea'

Prajna

https://community.oracle.com/products/oracleanalytics/discussion/19089/oas-6-4-redshift-data-connection-sending-rogue-sql-to-db

Backend Query Document.docx

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. 

Alan Lee - Oracle-Oracle

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?

User_GB0X1

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