Showing posts with label Obiee. Show all posts
Showing posts with label Obiee. Show all posts

Wednesday, February 1, 2017

OBIEE platform DBUSER password reset

Often you may find that when you come to start and OBIEE environment, it may fail with errors relating to the fact the OBIEE platform and mds accounts are either locked, or the stored passwords within the OBIEE configuration are out of step with whats held in the database.  You may see errors in the bi_server.log file such as :-
creating connection for pool “rtd_datasource”: ORA-28000: the account is locked
<BEA-001129> <Received exception while creating connection for pool “mds-owsm”: ORA-28001: the password has expired
When querying the DBA_USERS table within the database, you may discover the accounts are locked/expired :-
SQL> select username,account_status from dba_users where username like ‘DEV%';
USERNAME                    ACCOUNT_STATUS
—————————— ——————————–
DEV_BIPLATFORM  EXPIRED
DEV_MDS                        EXPIRED
If you do know the password, you can get away with reseting the account with the same password i.e.
alter user DEV_MDS identified by <original_password>;
alter user DEV_BIPLATFORM identified by <original_password>;     

You may not know the password, so you may end up having to reset the password as listed below.

alter user DEV_MDS identified by DEV_MDS;
alter user DEV_BIPLATFORM identified by DEV_BIPLATFORM;

Once reset, you will beable to test via a SQL * Plus connection.
However the various connections configured within OBIEE will need to be reset before you can successfully restart the OBIEE environment. The following steps below take you through the areas you will need to reset the DEV_MDS and DEV_BIPLATFORM password if you have had to reset the password with a new password in the steps above
Login to the Web Logic Console i.e. http://hlcdb01:7001/console
navigate to bifoundation_domain –> Services –> Data Sources. Check each data source for where the passwords are storeed typically you will need to modify these :-
bip_datasource > connection pool tab, reset the password for DEV_BIPLATFORM
EPMSystemRegistry > connection pool tab, reset the password for DEV_BIPLATFORM
mds_owsm > connection pool tab, reset the password for DEV_MDS
Click save and apply, a full restart will be required once all steps are performed.
Next step is to Login to the OBIEE Enterprise Manager Console i.e. http://hlcdb01:7001/em. You will need to reset the stored password for the NQS Scheduler, otherwise the service will fail to start
  • Expand “Business intelligence” menu on the left;
  • Click the “Deployment” tab;
  • Click the “Scheduler” tab under deployment;
  • Click “Lock and Edit Configuration” button;
  • Set the password and hit “Apply”;
  • Click the “Activate Changes” button;
Once all new passwords have been applied, a full restart, and all services should now start successfully

Monday, January 30, 2017

Invalid identifier at OCI call OCIStmtExecute (1)

 Invalid identifier at OCI call OCIStmtExecute (1)


Problem: Error when editing initialization block
Screenshot:
Invalid identifier
Screenshot text:
[NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 17001] Oracle Error code: 904, message: ORA-00904: [IDENTIFIER]: invalid identifier at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed.
Possible solution:
  • edit the SQL statement
  • change the part that is using [IDENTIFIER] to a part that is not using [IDENTIFIER]
  • save the statement
The error message is not displayed anymore.

Wednesday, January 25, 2017

[39018] The object is not available for query by any user due to permission setup

[39018] The object is not available for query by any user due to permission setup

 

Issue in OBIEE 11g, Presentation Layer object permission issue in 11g

 

Hi All,
I found a common issue in OBIEE 11g while consistency check, all presentation objects are set with no access permissions initially, if rpd is created newly in 11g.
We can go ahead for each object properties then change it’s permissions to Read, but this is manual and time consuming process.
I’ve a tip for this, but may have better & proper solution than this. I’ll definitely get back if I found as such, till the time we can use this as temporary solution which has no issues..

1.       Copy (Ctrl + C) entire Subject Area from presentation layer to any editor, which is UDML content..

2.       Now, find this text: PRIVILEGES ( NONE)

3.       Replace above text with: PRIVILEGES ( READ)

4.       Now, Copy entire content then paste it back to presentation layer.
Note: Above operation will override the existing subject area with permissions turned to be Read.
With the above approach in a single-shot we can suppress the consistency warnings related to permissions issue.

 

Tuesday, January 24, 2017

"[nQSError: 36010] server version 325 can not read the newer version 326 of the repository."

"[nQSError: 36010] server version 325 can not read the newer version 326 of the repository."



When you are trying to open the latest version repository using lower version of Admin Tool, you will be getting the error saying "[nQSError: 36010] server version 326 can not read the newer version 325 of the repository."

To overcome this issue, we need to downgrade the repository.

In OBIEE, we use nqgenoldverrpd.exe utility of the Admin Tool.

You can find this file on the following path,

If your are using default Admin Tool that comes with the OBIEE installation,
C:\Middleware\Oracle_BI1\bifoundation\server\bin

If you have installed BI Admin client saperately on your Windows machine,
C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client Tools\oraclebi\orahome\bifoundation\server\bin

For this purpose of practice, we are using BI Admin client path as my OBIEE server is on Linux environment.

The parameters that nqgenoldverrpd.exe uses are as follows,

-P: Repository password
-I: Repository name along with the full path that you want to downgrade.
-O: Repository path and new name of the rep you want to name for the downgraded version.
-V: Version you would like to downgrade.

Please make sure that the database types and call interface types in the repository are allowed in the specified version.
If not, change them to the nearest types before you run this utility. Otherwise, these types will be changed to the default type(ODBC 2.0) in the generated repository.

The downgrade process,
  • Open command prompt and poing to the one of the above mentioned path, i.e.
    cd C:\Program Files\Oracle Business Intelligence Enterprise Edition Plus Client Tools\oraclebi\orahome\bifoundation\server\bin

  • The downgrade command will be as follows,
    nqgenoldverrpd.exe -P Admin123 -I D:\Sample\HandsOn.rpd -O D:\Sample\HandsOn_325.rpd -V 325
  • Once you get Done!!! message,
In output path, there will be a newly created repository having your mention version (downgraded).
Also, you can find a log file of this process in a path mentioned in -O parameter of the command.

Now try to open that repository using your lower version of Admin Tool, surely you will be in..

Downgrade an OBIEE RPD Version

An RPD file saved by one version of the OBIEE Administration Tool cannot be opened by an older version of the OBIEE Administration Tool or be applied to an older version of an Oracle BI Server. For  this example we’re looking at an RPD created with version 349 of the Administration Tool (that’s the first release of OBIEE 11.1.1.9) and we’re trying to apply it to a server expecting version 326 (that’s the latest patched release of OBIEE 11.1.1.7.150120)
You can check the version of the tool you’re currently using by going to Help > About in the menu and look at the Repository Version line.
About-Oracle-BI-Administration-Tool
You’ll get an nQSError 36010 from the Administration tool if the tool is not of a high enough version:
Luckily there is a way round it! For certain versions you’ll be able to downgrade your RPD file so that you’re able to open it in the older version of the Admin tool. This isn’t true for all version, but from my test the below major versions worked for the downgrade process:
  • 11.1.1.6 > 11.1.1.5 (318 > 308)
  • 11.1.1.9 > 11.1.1.7 (349 > 326)
To downgrade the RPD file you’ll need to use an Admin Tool version that can open the file. Carrying on our example, we’ll need to use the 11.1.1.9 Admin Tool. You will need the nqgenoldverrpd utility which is part of the Administration Tool installation and can be found in the below path:
The utility has a few switches which you’ll need to enter to tell it what it needs to know to downgrade the RPD file.
  • -P – is the RPD password of the source RPD you wish to downgrade.
  • -I –  is the source RPD you wish to downgrade.
  • -O – is the target name and path for the downgraded RPD
  • -V – is the RPD version to downgrade to.
There is also a -F which will force the downgrade process to clear any expressions that cannot be downgraded.
The following example will downgrade an RPD on your desktop with password Admin123 and save it to a new RPD file on your desktop. The downgraded version will be 326 which is OBIEE 11.1.1.7.
First of all, open a CMD prompt in Windows and navigate to the above path, or the path where your Administration Tool is installed.
And execute the nqgenoldverrpd command and substitute your values.
You’ll see the below message once it’s complete:

nqgenoldverrpd File Paths

You can find the nqgenoldverrpd utility installed as part of the OBIEE Admin Tool or under an OBIEE installation on Windows.
  • On Client under : [CLIENT_FOLDER]\oraclebi\orahome\bifoundation\server\bin\nqgenoldverrpd.exe
  • On Server under : $MW_HOME\bifoundation\server\bin\nqgenoldverrpd

How To Fix Hive – Partition Table Query Failed When Stored As Parquet

This article is about the bug in Hive filtering option, when the partition table query stored as parquet. Big data developers will help y...