Friday, 13 June 2014

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