DAC : Login Error - Couldn't Store Login Data

Sometime we used to get an error after installation of DAC when we are trying to login to DAC.
It shows like - "Couldn't Store Login Data"

Reason for this error is : The cwallet.sso file does not have the full permissions for these DAC user.

Solution : Check the permissions and give Full Permissions to this file to all your DAC Users.

(Path of cwallet.ssp file: C:\dac11g\dac\conf\security\cwallet.sso )


Enjoy and stay well !! :)


  

OBIEE 11g : Create New Domain

Here, today we will discuss how to create a new domain when we have already installed one. Sometime its required to do this also to resolve some of the unpredictable issue. J

Before starting the process make sure that all BI server components (weblogic , Node Manager, Managed Server and OPMN) are down.

Step 1: You need to create a new repository schema with a new prefix. Initially if you would have create a RCU schema with DEV_BIPLATFORM & DEV_MDS, then now it will be like DEV1_BIPLATFORM & DEV1_MDS.

Step 2: Go to OBIEE MW Home >> Oracle_BI1 >> Bin. There you will be having a file called ‘config.sh’ or ‘config.bat’ . Run the file as per your BI server environment (Linux/Windows). Note that, you need to remove the $ORACLE_HOME path before starting the creation of domain.

Step 3: Once the new domain has been created, you can verify the same.  Go to OBIEE MW Home >>  instances , here two instances will be there (instance1 & instance2). Then go to OBIEE MW Home >>  user_projects >> domains, here also two domains will be there (bifoundation_domain & bifoundation_domain1).

Step 4: Restart all the BI server components.

 

Enjoy and Stay well !! :)
 

OBIEE Weblogic User Login Issue

There could be n number of reasons when Weblogic user is not able to login to BI analytics.  Some of the possible reasons are given below:

1.  Credential mapping issue for BISytemUser. For more details click  here.

2.  GUID mismatch of Weblogic User. For more details  click here.

3.  BI System Application Role got deleted. For more details click here.

4.  If SSO is enabled in BI please check the below points:

         a. Password for BISytemUser account is same in IDAM and BI.

         b. Check whether BISytemUser account has expired or not which has been created in IDAM to communicate with BI. 

 5. Need to check whether BI metadata schema ( BIPLATFORM & MDS ) has expired or not .

 6. Packages for BI metadata schema ( BIPLATFORM & MDS ) can be corrupted. Need to take care of that also.  

7. If none of the above solution work out then you can go ahead with creating a new domain.
For more details click here

Enjoy and Stay Well !! :)