Search This Blog

Sunday, 13 January 2013

oracle 11g data base instalation on wnidows 8

Give mail id and enter
Click on I want to     
And next
Create and config
Desk top class and next
Pass word yours choice
Click on finish
Allow access

Click on ok

Tuesday, 8 January 2013

Variables available in OBIEE

Variables available in OBIEE

ScopePresentation VariableExample
systemproductVersionsystem.productVersion = (Build 090619.0110.000)
systemcurrentTimesystem.currentTime = 6/29/2009 7:35:59 PM
sessionlocalesession.locale = en-us
sessionlanguagesession.language = en
sessionrtlsession.rtl = false
This indicates whether the language selection in the Login page is a right to left language. For example, if the language selection is Hebrew, then this variable returns true.
sessiontimeZonesession.timeZone = (GMT-06:00) Central America = (GMT-06:00) Central America
This returns a value that is not localized. = (GMT-06:00) Central America
This returns a localized value.
sessiontimeZone.valuesession.timeZone.value = (GMT-06:00) Central America
This returns a localized value.
sessionloginTimesession.loginTime = 6/29/2009 7:12:01 PM
sessionlogoutTimesession.logoutTime = 6/29/2009 8:02:01 PM
sessionlastAccessTimesession.lastAccessTime = 6/29/2009 7:35:59 PM
sessioncurrentUsersession.currentUser = Administrator = $ English - United States
sessioncurrency.symbolsession.currency.symbol = $
sessioncurrency.userPreferencesession.currency.userPreference = Global Currency 2 = Administrator
userdisplayNameuser.displayName = Administrator
userhomeDirectoryuser.homeDirectory = /users/administrator
dashboardcurrentPagedashboard.currentPage = page 1
dashboardxmldashboard.xml = the dashboard XML = Euro
dashboarddashboard.currency.symboldashboard.currency.symbol = $
dashboarddashboard.currency.userPreferencedashboard.currency.userPreference = Global Currency 1
dashboarddashboard.pathdashboard.path = /users/administrator/_portal/Sales
This returns the path in the catalog. = MyDashboard
dashboarddashboard.captiondashboard.caption = Sales
This returns the localized name of the dashboard.
dashboarddashboard.locationdashboard.location = Dashboard&PortalPath=/users/administrator/_portal
This returns the URL for the location.
dashboarddashboard.descriptiondashboard.description = Sales by region and district = Administrator = Sales page 1
dashboard.currentPagedashboard.currentPage.pathdashboard.currentPage.path = /users/administrator/_portal/Sales/page 1
dashboard. current Pagedashboard.currentPage.currency.namedashboard.currentpage.currency.
name = USD
dashboard.current Pagedashboard.currentPage.currency.symboldashboard.currentPage.currency.
symbol = USD
dashboard. current Pagedashboard.currentPage.currency.userPreferencedashboard.currentPage.currency.userPreference = Global Currency 2 = $ English - United States
analysisreport.currency.symbolreport.currency.symbol = $
analysisreport.currency.userPreferencereport.currency.userPreference =
Global Currency 2

Obiee 11g Bi Scheduler Gives Error Nqserror: 75005

Obiee 11g Bi Scheduler Gives Error Nqserror: 75005

when running Agent (iBot), the following error message is seen:

Failed to send AUTH command. 5.7.3 Authentication unsuccessful

The above error message is seen if the BI scheduler cannot ping the mail server specified in the scheduler configuration. In this case, customer is able to ping and telnet the mail server.

The other scenario where the error message is seen is if Username and password are specified in the scheduler configuration.

To view this setting, log in to enterprise manager > Business Intelligence > Coreapplication > Deployment > Mail and you will notice Username, password. If the values are specified for Username and password then Failed to Send Auth Command error is seen.

In this case, Username and password for the scheduler configuration have values.

Once the values are entered, these values cannot be deleted from the EM. In order to delete the values for Username and Password specified in mail configuration, log in to enterprise manager > Weblogic Domain > Right click on bifoundation_domain > Security > Credentials > Expand > Highlight mail.server and delete.

After deleting the credential, customer was able to run the agents successfully



When using Evaluate Function in OBIEE 11g

Error : Formula syntax is invalid
[nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. EVALUATE_SUPPORT_LEVEL inside NQSConfig.INI is not set to support EVALUATE. (HY000)

SQL Issued: SELECT EVALUATE('LEAST(%1,%2)', 1, 2) FROM "Disclosures - Encumbered Assets"


Change the setting in the nqsconfig.INI

location of File : $MW_HOME/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1

Edit nqsconfig.INI and Change the setting to 2

# 1: evaluate is supported for users with manageRepositories permssion
# 2: evaluate is supported for any user.
# other: evaluate is not supported if the value is anything else.


Save changes and Restart the OPMN Services

--Start Services

$MW_HOME/instances/instance1/bin/opmnctl stopall

--Stop Services

nohup $MW_HOME/instances/instance1/bin/opmnctl startall

OBIEE Writeback setup

OBIEE Writeback setup

Detailed Write Back steps in OBIEE

Krishna M

Step 1

Amend the instanceconfig.xml and add the LIghtWriteback entry as shown below with in the server instance tags

The instanceconfig.xml file is located in $MW_HOME/instances/instance1/config/OracleBIPresentationServicesComponent
/coreapplication_obips1 directory

Add the LightWriteback tag just above the /ServerInstance tag as in above example.


Restart the OPMN services for the instanceconfig amendment above to take effect

Login to Analytics


Set privileges within Administration screen

Add roles or users to the Write back privileges above

Step 2

Create a table used to store the write back table and import it into the physical layer in RPD

Ensure the connection pool user has required privileges to insert / update data on this table

Step 3











In Business Model, switch on the Writable property for all required columns

This completes the one time setup required to carry out write back functionality. Following steps are required for setting up an actual write back

Step 4

Create a new analysis with the required columns

Select the Column Properties using the drop down arrow on each column

Choose the column property and Tick the Enable Write Back check box on the Write Back tab for the required column. In my case, I have enabled only for USD Amount.

Note: If the ‘Writable’ flag is not enabled in RPD then this check box also cannot be enabled

Step 5











Note that only the USD_AMT column is displayed as editable

Choose the Edit Table View option and click on Table View Properties











Tick the Enable Write Back on enter a Template Name. I entered ‘RPA’ and this can be any user given name. Note this name is case sensitive. Below you will see how to create this template called RPA used here

Step 6

Click on the advanced tab of the analysis

Here under the Analysis XML box we want to note down all the columnID's that we will be using to populate the Writeback table with

Make a note of the columnIDs for the required columns. These will be used in the next step

Step 7



Create XML file as below and place it in

/analyticsRes/customMessages directory if the analytics res directory has been deployed.

Please see the Deploying analyticsRes for custom Messages post that we have created that wont ever get overwritten by Oracle Patches etc

If you dont want to use the analyticsRes custom messages folder then you can use the seeded folder

If the directory ‘customMessages’ does not exist then create one in the path mentioned


--------Start of XML--------

<?xml version="1.0" encoding="utf-8" ?>

<WebMessageTables xmlns:sawm="">

   <WebMessageTable lang="en-us" system="WriteBack" table="Messages">

      <WebMessage name="RPA">


            <writeBack connectionPool="Writeback">


                <update>update encumbered_rpa set usd_amt = @{cbe48633dbeb2bda8},update_date = sysdate,updated_by = '@{cb26f41933b0c7d7c}' where product_id = @{c9c0a2069f38dda8c}</update>








Within the update tags have the update statement that gets executed in the database using the columnIDs picked from the Advanced tab

Save the XML as RPA.xml
Bounce the OPMN service for this XML to be loaded and available for use



Step 8



Run the report that was created in Step 4

If all the steps are carried as they should be then you will see two buttons as in the above screen shot. The Update functionality is ready.

Amend the value of any editable field and hit the Update button then the change is carried out in the database and the screen gets refreshed with the new value. The statement that is given in the XML template between the update tags gets executed.

Revert button is used to undo any changes that are not yet sent to the database.

If you have noticed, the insert statement is left blank. But the same XML can be amended to provide the functionality of insert. If the amended record exists in DB, then the update statement is issued and if the amended record does not exist in DB then the insert statement is issued.

You don’t necessarily have a insert statement with the insert tags. You can use a function call here or you can issue an update statement to a different table. Using this base functionality you can deliver tailor made solutions fit for purpose.