Skip to Content
avatar image
Former Member

Modifying .PRM file for user defined database functions


Currently we have the BOXI 3.1.8 Universe in oracle database and we are planning to migrate to SQL server 2008.And the universe contains few oracle functions and user defined functions in the universe objects.

In the way of migration we are planning to have both Oracle and SQL Server database connecting to single universe. To make the universe generic we have identified the objects using user defined functions and trying to push it to the database.

Since there are a few differences in the way oracle and SQL Server functions are invoked, we have decided to edit the .PRM files available in the path D:\Business Objects\BusinessObjects Enterprise 12.0\win32_x86\dataAccess\connectionServer\jdbc , so that we have a common way of invoking the functions.

Invoking functions:


SQL Server : <SchemaName>.<function>

Oracle: <function>

1.Is there any problem if I edit the .PRM?

2.Whether these changes will work fine?

3.Whether the reports will run fine if I use those objects in the reports?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Jan 09, 2012 at 01:53 PM

    Hi Lavanyaa,

    The PRM files actually state the functions that are normally available in a database, including the standard format.

    They are what drives the list of functions available when you build the SELECT definition or CONDITION definitions in Information designer... The fact that a function needs aggregation or/not is also determined in there.


    The SQL that you provide in the universe is what will be sent to the database and that must be 'understood' by the database.

    So it's not as simple as changing the PRM file and you will be able to speak 'universal' SQL in your universes.


    That complexity is taken away from you when you create a multisource database.

    You will speak 'data federator' SQL in the universe. Data federator will take care of translating it to the right syntax for each database. Notice you will probably need some customization to determine how a SQL will be handled when you need to query two databases, as the default is not automatically the best way performance wise.

    Hope this helps,


    Add comment
    10|10000 characters needed characters exceeded