nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Impact of changing Call Interface and Connection Script in Connection Pool.

Manoj Dixit

Hi,

We are on OBI EE 10.1.3.4.2.

We have an RPD developed by a third party (which I assume is same out of the box for their clients).

The connection pools' call interface is based on ODBC 3.5 drivers. Dashboards are in use based on standard prompts and requests.

If I were to change the call interface to Oracle OCI and call an execute on connect script (for example, alter session set nls_date_format = "YYYY-MM-DD"), I would like to know impact of these changes on the existing OBI EE dashboards.

Could someone help me in analysing the impact of the above changes or give some pointers, please?

Thank you.

Regards,

Manoj.

Find more posts tagged with

Accepted answers

All comments

Joel Acha

Your question in my opinion throws more questions than answers in my humble opinion - Why 10g? Have you tested the changes to see what the impact is? The only thing that springs to mind is that there will be a slower log in time as these pre login scripts need to execute first so it really depends on what these scripts are to do.

Manoj Dixit

Thanks Joel.

With regards to 10g, the decision makers are someone else.

I have not tested the changes system wide yet (please see below 'Additional details') but I would like to prepare for testing the changes.

The script changes the date format in an Oracle 11g database to 'YYYY-MM-DD'.

Additional details.-

I have created a prototype based on a session variable and SCD type 2 dimension. It involves a new database (in the RPD) and new subject area. The new database's connection pool is based on an Oracle OCI (instead of ODBC 3.5) call interface and also has the nls date format setting command.

A request on a dashboard page accepts a date value and based on that value, relevant row is fetched from the SCD type 2 dimension. If I do not have the connection script in the connection pool, OBI EE (the database) is throwing 'ORA-01861: literal does not match format string' error. Having the connection script resolves that issue.

I have also noticed that the date format of the prompt remains the same. So the connection script does not change the date format in the UI, which is good.

Apparently, it looks like there can be a slight delay while logging in.

Would the call interface change matter (from ODBC 3.5 to Oracle OCI)?

Regards,

Manoj.

[Deleted User]

First question: Why ODBC when you have an Oracle database? That in itself in extremely questionable and should never be done.

Manoj Dixit

Hi Christian,

(I am saying to myself: OMG, questions from OBIEE experts, questions from DBAs, questions from architects, questions from PMs, questions from PLs, questions from vendors, questions from colleagues ....).

I don't know why it's based on ODBC, probably the Vendors created it generic for their clients. Although I am keen to change it.

Kind regards,

Manoj.

(PS: Probably all those questions are fine compared to questions from wife.)

Joel Acha

1st thing would be to change it to Oracle OCI instead of ODBC.

[Deleted User]

Definitely change it for OCI. Check the settings for the DB and the NQSConfig.ini so that the date format is correct.

Manoj Dixit

Closing this as "Assumed Answered", as now I need to start working on making the actual changes (I am convinced but now I need to answer internal questions like what is the impact, etc..)