Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 16 Oracle Analytics Lounge
- 216 Oracle Analytics News
- 43 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 79 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
OBIEE 12c: datamodel.sh updateconnectionpool doesn't work properly
Hello Experts
We are facing strange problems, we have automated RPD deployment and we are using following command post deployment to update the connection pools online.
datamodel.sh updateConnectionpool -C masterpassword.json -SI ssi -U weblogic -P ****** -N 9502
We are mainly facing 2 issues
Issue 1: This issue occurs less frequent though, but it occurs. At times it fails to update password of one specific connection pool in our RPD.
Issue 2: If we have an RPD with less connection pools than mentioned in masterpassword.json then again one particular connection pools password is not updated correctly. As an example we have 14 connection pools in masterpassword.json, but the RPD which we are trying to deploy has say 12 connection pools only then it somehow fails to update one of the connection pool and this happens regularly and every time for one particular connection pool.
Does anyone of you have faced such scenario? If yes do we have a solution. I have raised SR with oracle support but so far they are clueless.
Please help and thanks in Advance.
Environment details:
OS: AIX 7.1
Clustered: Yes
OBIEE Version: 12.2.1.2.171017
Answers
-
Obvious point: what is that "one particular" connection pool and what makes it special?
And re master with more pools than in the RPD: I never do that. The json always contains exactly what needs to be updated. Not more.
0 -
1. That's the curiosity we have. Need to figure out why only one why not others.
2.And re master with more pools than in the RPD: I never do that. The json always contains exactly what needs to be updated. Not more - Oracle confirmed that their in-house results are fine but I highly doubt that since I gave them a demo of it happening in our environment
0 -
I think I got what's happening. Developers are re-creating the connection pool and hence UID changes for that connection pool which causes it to fail when we deploy it in next environment where UID generated was of the earlier RPD
0 -
Facepalm...
0