Hi, While running reconfig.sh it was triggering error like “UPGWLS-03503: The domain configuration file(0) is not valid” . Cause :- Reconfiguring a domain to 12.1.2 fails if a custom authenticator provider is configured in the 11g domain. Defect 16881772 Workaround :- * 1. Took backup of 12.1.1 domain directory, opened config file (DOMAIN_HOME/config/config.xml file ) OAM Identity Asserter REQUIRED * 2. In the 12.1.1 domain, deleted the above custom authentication provider entirely. * 3. Ran the reconfig.sh script After following above steps we have upgraded obiee 12.2.1.0 to 12.2.1.2 successfully. However, we noticed "BISQLGroupProvider" is not running. Do we need to apply any patch to setup BISQLGroupProcider ? Thanks

If yes then I am not sure about the location because there is no folder inside new domain(Oracle_home1).

Hi, It was working perfectly before upgrade but triggering error now. I am assuming that we need to move ODBC.ini in new oracle home ( Oracle_home1). Thanks

Hi, Normally : we have to comment the section during upgrade and uncomment it after upgrade. it will work. 1) can you chekc if you have datasource to read data in Console ? if not I will just suggest you to create BISQLgroup prover from scratch in new version. It hardly takes 30 minutes Thanks Venkat

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

After upgrading OBIEE 12.2.1.0 to 12.2.1.2 .. BISQLGroupProvider is not working

SaQ-Orcl

Hi,

While running reconfig.sh it was triggering error like “UPGWLS-03503: The domain configuration file(0) is not valid” .

Cause :-

Reconfiguring a domain to 12.1.2 fails if a custom authenticator provider is configured in the 11g domain. Defect 16881772

Workaround :-

1. Took backup of 12.1.1 domain directory, opened config file (DOMAIN_HOME/config/config.xml file )

<sec:authentication-provider xmlns:ext="http://www.bea.com/ns/weblogic/90/security/extension" xsi:type="ext:oam-identity-asserterType">
<n1:name xmlns:n1="http://www.bea.com/ns/weblogic/90/security">OAM Identity Asserter</n1:name>
<n2:control-flag xmlns:n2="http://www.bea.com/ns/weblogic/90/security">REQUIRED</n2:control-flag>
</sec:authentication-provider>

2. In the 12.1.1 domain, deleted the above custom authentication provider entirely.
3. Ran the reconfig.sh script

After following above steps we have upgraded obiee 12.2.1.0 to 12.2.1.2 successfully. However, we noticed "BISQLGroupProvider" is not running.

Do we need to apply any patch to setup BISQLGroupProcider ?

Thanks

Find more posts tagged with

Accepted answers

All comments

[Deleted User]

1. We cant see nonpublic bugs so that isnt helpful

2. Why do you reference an 11g to 12c bug when you state that you go from 12.2.1.0.0 to 12.2.1.2.0 ?

3. In general I configure the custom auths manually again when moving from A to B because it's pretty much no effort and I can have full control over what happens

SaQ-Orcl

Hi @Christian Berg

Thanks for reply.

2. Reason: we had migrated from 11g to 12.2.1.0 six month back in parallel instance(Dev), and now we are upgrading from 12.2.1.0 to 12.2.1,2

3.Thanks for this option. Will search document to config it manually. It would be helpful if you can share any reference document.

Thanks

Syedsalmancs110

First things first, check whether adapter created/configured for BISQLGroupProvider still exists or not after upgrade, you can check same executing below command.

a) make sure your Admin Server is up and running.

b) Launch wlst.cmd | wlst.sh (as per your environment) from following location <ORACLE HOME>\oracle_common\common\bin

c) Connect to Online Mode executing below command

Syntax: connect('<ADMIN USER>','<ADMIN PASSWORD>','t3://myserver:port')

Example: connect('weblogic','weblogic','t3://myserver:9500')

d) Execute below command to list adapters configured for WLS

listAdapters()

Verify if your BISQLGroupProvider adapter still exists or not.

If you are going to reconfigure BISQLGroupProvider again as it is already not working then its better to drop previous created BISQLGroupProvider adapter and then proceed with creation of new adapter.

e) Execute below command to drop an adapter.

Syntax: deleteAdapter(adapterName='<AdapterName>')

Example: deleteAdapter(adapterName='userGroupAdapter1')

For BISQLGroupProvider you can refer to below mentioned link from OBIEE 12c Product document

Configuring Oracle Business Intelligence to Use Alternative Authentication Providers

SaQ-Orcl

Appreciate it.

Will check and let you know.

Thank you very much.

[Deleted User]

Syem gave you an outline and the documentation link already.

Here's a real life example that Mark explains in drtail:https://www.rittmanmead.com/blog/2012/03/obiee-11g-security-week-connecting-to-active-directory-and-obtaining-group-memb…

SaQ-Orcl

What if we install the fresh 12.2.1.2 ? Will it come with installation or need to configure manually ?

.....

Will follows the steps which you mentioned.

Syedsalmancs110

No external LDAP(Active Directory,Oracle Internet Directory,BISQLGroupProvider,ReadOnlySQLAuthenticator etc..) configuration comes out of the box(for an fresh install environment) you need configure the same once the software is installed and configured, the only LDAP which comes configured in Default LDAP which is embedded within the system.

SaQ-Orcl

Hi,

Thanks for comment. I have implemented it successfully.

After upgrade, I have observed error in few dashboards as below ( Do we need to move odbc.ini in new oracle home1 ? )

Error Codes: OPR4ONWY:U9IM8TAC:U9IM8TAC:U9IM8TAC:U9IM8TAC:OI2DL65P

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)

State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. (HY000)

State: HY000. Code: 43119. [nQSError: 43119] Query Failed: (HY000)

State: HY000. Code: 16001. [nQSError: 16001] ODBC error state: IM003 code: 0 message: [DataDirect][ODBC lib] Specified driver could not be loaded. (HY000)

Thank in advance

Syedsalmancs110

odbc.ini is present under DOMAIN_HOME\config\fmwconfig\bienv\core, if after upgrade you have a new DOMAIN_HOME then yes you would need to copy odbc.ini to new location

SaQ-Orcl

Thank you very much for your reply.

I have copied it in new home (Oracle_home1), but still triggering error. Do you need to copy it at any specific location ?

Thanks