OBIEE 11g Errors- nQSError: 43113, nQSError: 43126, nQSError: 37001

My Environment: Windows 2008 R2, Oracle DB 11gR2, OBIEE 11.1.1.5.0

One fine day no user even administrator was able to log in to OBI. We were receiving the following errors:

Unable to Sign In- An invalid User Name or Password was entered.
When trying to open the repository in online mode, following error messages are received:
nQSError: 43113, nQSError: 43126, nQSError: 37001

We tried everything including redeploying rpd and catalog, refreshing GUIDs, creating new users with Admin privileges, playing around with BI System User, etc. with no success.

NQServer Log:

Error Message For BISystemUser: User not authenticated.

Authentication failed: invalid user/password.

NQ Admin Tool Log:

[nQSError: 43113] Message returned from OBIS.

[nQSError: 43126] Authentication failed: invalid user/password.

[nQSError: 37001] Could not connect to the Oracle BI Server instance.

Presentation Log:

Could not create a system user connection to Oracle BI Server during start-up. Please check the error message and try again.

Authentication Failure.

Odbc driver returned an error (SQLDriverConnectW).

[nQSError: 10018] Access for the requested connection is refused.

[nQSError: 43113] Message returned from OBIS.

[nQSError: 43126] Authentication failed: invalid user/password.

After several hours of debugging we found that our DB schemas/user MDS and BIPLATFORM got locked/ expired. It was a setting in Oracle DB which makes schemas or users lock after a period of time. To check the status of account use:


SELECT USERNAME, ACCOUNT_STATUS FROM DBA_USERS;


You can use the following to unlock accounts:

ALTER USER MDS ACCOUNT UNLOCK;

ALTER USER BIPLATFORM ACCOUNT UNLOCK;

If the password has expired make sure to revert it back to the password you used during installation. Use the following:

ALTER USER MDS IDENTIFIED BY Admin123;

ALTER USER BIPLATFORM IDENTIFIED BY Admin123;

This did the trick and we were able to login to OBI Presentation Services.

Cheers!

Deepak

OBIEE 10g Migration Steps- Linux

I recently end up going back to 10g version and the following script helped me a lot during migration process between DEV/QA/PROD. Let’s assume we are migrating from QA to PROD for this post. I usually use putty to perform these steps. Following steps can be a good guideline.

1.  Start Putty and point to QA box. Shutdown OBIEE services on QA box.

./run-sa.sh stop

./run-saw.sh stop

2.  Make a new deployment directory (mmddyyyy is date of deployment this gives a versioning technique/ trackback control on deployment)

mkdir rpdcatmmddyyyy

3.  Copy Catalog & RPD into deployment directory

Change directory to the new deployment folder you created.

cd rpdcatmmddyyyy

-Copy rpd and catalog to this directory

cp -R /u01/app/obiee/OracleBIData/web/catalog/SalesCatalog .

cp /u01/app/obiee/OracleBI/server/Repository/salesrepository.rpd .

If you have made changes to configuration files, copy them over to this deployment folder as well e.g. I created a new xml file for writeback

cp /u01/app/obiee/OracleBI/web/msgdb/customMessages/writeback.xml .

4.  SCP the deployment directory to PROD box

Go back to home directory by issuing cd command and then use SCP as below

cd

scp -r rpdcatmmddyyyy obieeprod@prodboxname:/home/obieeprod

5.  Start another session of putty pointing to PROD box. Archive Catalog & RPD in target platform.

Stop BI Services in PROD box

 ./run-sa.sh stop

./run-saw.sh stop

cd /u01/app/obiee/OracleBIData/web/catalog/

mv SalesCatalog SalesCatalog.mmddyyyy

cd /u01/app/obiee/OracleBI/server/Repository/

mv SalesRepository.rpd SalesRepository.rpd.mmddyyyy                                

6.  Move Catalog & RPD to proper directories from the deployment directory you moved to PROD box

cd /u01/app/obiee/OracleBI/server/Repository/

cp /home/obieeprd/rpdcatmmddyyyy/salesrepository.rpd .

cd /u01/app/obiee/OracleBIData/web/catalog/

cp -R /home/obieeprd/rpdcatmmddyyyy/SalesCatalog .

cd /u01/app/obiee/OracleBI/web/msgdb/customMessages/

cp /home/obieeqa/rpdcatmmddyyyy/writeback.xml .

7.  Start OBIEE in QA and POD

./run-sa.sh start

./run-saw.sh start

8. If you have not pointed PROD rpd to PROD DB then do it in online mode now.

Hope someone working on OBIEE 10g will benefit from this post.

Cheers!

Deepak