"[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..

Happy blogging.. :)

Important Path Directories in OBIEE 11g

Wondering about the configuration files in OBIEE 11g.?? Here's some of the main Configuration/Log file locations.

OBIEE Configuration file Path :-

Catalog Path:
C:\Middleware\instances\instance1\bifoundation\OracleBIPresentationServicesComponent\coreapplication_obips1\catalog

Repository Path:
C:\Middleware\instances\instance1\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository

Instanceconfig.xml:
C:\Middleware\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1

NQSConfig.INI:
C:\Middleware\instances\instance1\config\OracleBIServerComponent\coreapplication_obis1

Start-up / Stop Issues :-

You have to check the below logs if you have any start-up issues for any of your OBIEE components.
The first step is to check the status of all components using,

C:\Middleware\instances\instance1\bin>opmnctl status -l

If any of the component status is down, go to the corresponding log file for more information.
To individually start components for an example to start the presentation services you would use the below command,

opmnctl startproc ias-component=coreapplication_obips1

Similarly to start other components replace the coreapplication_obips1 with correct names.

OBIEE System Component Log Locations :-

Presentation Services:
OBIEE_HOME\instances\instance1\diagnostics\logs\OracleBIPresentationServicesComponent\coreapplication_obips1

sawlogo.log - Fro any issues related to Presentation Services start/stop

BI Server Component:
OBIEE_HOME\instances\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1

nqquery.log - For any issues related OBIEE Analysis & RPD issues
nqserver.log - For any issues related to Server Component start/stop

BI Scheduler Component:
OBIEE_HOME\instances\instance1\diagnostics\logs\OracleBISchedulerComponent\coreapplication_obisch1

nqscheduler.log - For any issues related to Scheduler Component start/stop

BI Cluster Component:
OBIEE_HOME\instances\instance1\diagnostics\logs\OracleBIClusterControllerComponent\coreapplication_obiccs1

nqcluster.log - For any issues related to Cluster Component start/stop

Java host Component:
OBIEE_HOME\instances\instance1\diagnostics\logs\OracleBIJavaHostComponent\coreapplication_obijh1

jh.log - For any issues related to Java Host Component start/stop

Weblogic Server Log Locations :-

BI Managed Server:
C:\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server1\logs

bi_server1.out - For any issues related to bi_server1

Admin Server:
OBIEE_HOME\user_projects\domains\bifoundation_domain\servers\AdminServer\logs

AdminServer.log - For any issues related to AdminServer

[nQSError: 38107] Not all four columns are defined for closure table

Problem: [nQSError: 38107] Not all four columns are defined for closure table

In OBIEE 11g, while dealing with Parent-Child Hierarchy, you can get the error saying,
[nQSError: 38107] Not all four columns are defined for closure table 'D51 Sales Rep Parent Child'. (HY000)

The BI Consistency Check will be fine. But when you are going to test your results in Analysis, the error report would through this error.
[nQSError: 38107] Not all four columns are defined for closure table ....

The root cause of this error is Parent-Child setting in hierarchy can't be set up properly while modifying repository in online mode.

Solution: 

• To fix this issue, make your all BI Services down.
• Open your repository in offline mode.
• Set the Parent-Child settings properly.
• Save and take your repository online.
• Test your result now.

Happy BI. ;-)

Unauthorized Access: Either you do not have the privilege, or you have not signed in.

While getting started with Oracle BI Publisher, you may face this problem saying
"Unauthorized Access: Either you do not have the privilege, or you have not signed in." even if you have logged in as weblogic user.

This is because, the weblogic user is not having permission to access root folders bisystemuser and My Folders. So, we are modifying the permission of those folders as below.

1. Stop all BI Services.
2. Open Catalog Manager in offline mode.
3. Select User Folders.
4. Right click on bisystemuser  and give full control to weblogic user.
5. Right click on My Folders and give full control to weblogic user.
6. Restart the BI Services.
7. You are the in to BI Publisher.

nQSErrors: Cause and Actions

Hi intelligent folks......

I always wondered with every nQSError i have faced soo far.. Every time i need to ask for solutions to our most favorite GOOGLE uncle.. But we are independent now. ;-)
Yes, here's the link from Oracle Corporation, to list out every possible error that can occur while dealing with Siebel Analytics.

Please have your own copy of this all-in-one doc.
http://download.oracle.com/otndocs/products/bi/bi-ee/docs/784/AnyMsg.pdf

Happy blogging. :-)

nQSError: 37005 Transnational Update Failed

This issue was there since version 11.1.1.3.x. It will appear if you edit an OBIEE repository in online mode.The administrator tool for editing the RPD is unable sometimes to acquire an exclusive lock on the objects, that in turn causes the error message.Checking in the changes on a regular basis will reduce the occurrence of this error.

• One more thing you can try for this bug is,

Failures that trigger this error are normally written to the NQServer.log file located in C:\Middleware\instances\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1

Check this file for errors like "has name with leading or trailing space(s)". Fix that, check for consistency and save. Then restart the services.

As per my knowledge, this should be the most preferable solution.

• As a temporary solution, the following workaround can be used.

1. After you click on the Check-in button, do Consistency Check.
2. Click ‘Save’ button.It will display the ‘nQSError: 37005 Transnational Update Failed’ error.
3. Click ‘Save’ one more time despite the error.
4. Click the ‘Close’ button.You will get a prompt, Do you want to check in the changes?
5. Select ‘Yes’, you will get the error again.
6. Click the ‘Close’ button again.Then you will get a prompt, Do you want to check in the changes?
7. Select ‘No’.Then the RPD will close.
8. If the RPD says ‘your changes will get saved’ then it means that your changes will be there when you re-open the repository.

• To permanently resolve this Bug 9884975, apply patch number 12909840 to your OBIEE platform. Oracle Support released a patch for the [nQSError: 37005] Transaction update failed error.
  Remember that you have to ask the patch password (by opening a new SR) in order to download it.