Hi All,
After extracting and copying the 7.9.6.4 catalog to catalog folder faced an error like Destination Path too long for the destination folder.
Resolution:
Check the check box and click on skip let the process continues.
Now open the two catalog from catalog manager in offline mode.Now copy the files from neatly extracted catalog to our catalog by using catalog manager.
Keep the Catalog path in the Enterprise Manager(EM) and restart the services.
Hi All,
Oracle Business Intelligence Applications 7.9.6.4 is released.We can get the Apps Installer from the below link.
BI APPS 7.9.6.4 RPD is shared in the below location.
https://docs.google.com/file/d/0B5hhXh5H6a8CMmlTa0p0WEdnOHM/edit
BI APPS 7.9.6.4 Catalog is shared in the below location.
https://docs.google.com/file/d/0B5hhXh5H6a8CR0FRbDBWTjk3QnM/edit
Issue : Need to change View Selector to Left Side from Center.
Resolution :
Need to add
VSelSelector{padding-bottom:2px;text-align:left;}. line in views.css file from the below mentioned paths.
E:\Middleware\Oracle_BI1\bifoundation\web\app\res\s_blafp\b_mozilla_4\rtl\views.css
E:\Middleware\Oracle_BI1\bifoundation\web\app\res\s_blafp\b_mozilla_4\views.css
E:\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\s_blafp\b_mozilla_4\rtl\views.css
E:\Middleware\user_projects\domains\bifoundation_domain\servers\bi_server1\tmp\_WL_user\analytics_11.1.1\7dezjl\war\res\s_blafp\b_mozilla_4\views.css
Save the files and restart OPMNCTL then we can see View Selector changes to the Left from center.
Stream Closed Error when Click on coreapplication in Enterprise Manager in OBIEE 11g:
Recently when I tried to click on coreapplication in Enterprise Manager in OBIEE 11g, I am getting an error like Stream Closed.
Resolution:
Go to the below mentioned path
Middleware\user_projects\domains\bifoundation_domain\sysman\mds\partition1\ai\bi\mdssys\cust\user\weblogic
Here you can find instance.jspx file.
Delete this file and restart all the services then you can resolve this issue.
Error : Exceeded configured maximum number of allowed output prompts, sections, rows in OBIEE 11g.
When we are drilling from main report to detail report we are getting an error like Exceeded configured maximum number of allowed output prompts, sections, rows this is because of huge data in the report.
So in order to resolve this issue we need to add the below mentioned tags in instanceconfig.xml file which is located under
\Middleware\instances\instance1\config\OracleBIPresentationServicesComponent\coreapplication_obips1
The tags which needs to be added are
Hi All,
While Implementing Usage Tracking in OBIEE 11g,I came to know that the given default RPD and Catalog is a bug in 11.1.1.5.
So updating you all with correct RPD and Catalog for implementing Usage Tracking in OBIEE 11g.
you can get the correct RPD and catalog from here.
https://docs.google.com/open?id=0B5hhXh5H6a8CM09WZXY5czdSckNJTnVscnJLVkk3dw
https://docs.google.com/open?id=0B5hhXh5H6a8COV9OdDIwbWhRQUNrdTlmSnRHNVZxUQ
Step by Step procedure of Implementing Usage Tracking in OBIEE 11g:
Usage Tracking:
Used to monitor system and ad hoc query performance and to provide input on usage details. Used for determining user queries that are creating performance, based on query frequency and response time.Usage tracking Presentation Catalog provides prebuilt requests and a dashboard built to provide common analysis—for example, analyzing usage patterns by users, groups, and queries; daily and weekly peak usage patterns and load variance;time series comparisons to help compare current usage over previous weeks or months; and major contention points for troubleshooting, including, for example, top long-running queries.
Before implementing Usage Tracking we need to run the following scripts.
Step 1 :
Create the following sql scripts:
CREATE OR REPLACE VIEW nq_login_group AS SELECT DISTINCT user_name AS login, user_name AS resp FROM s_nq_acct;
Grant select on nq_login_group to public;
We can get the scripts from Middleware/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/sample/usagetracking/SQL_Server_Time
We can get the S_NQ_ACCT table from
Middleware/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/schema
Note : Don’t forget to commit the changes after creating the tables and inserting the data.
Step 2 : We can get the upgraded Usage Tracking RPD and Catalog from the below path after installing OBIEE 11g.
Middleware/instances/instance1/bifoundation/OracleBIServerComponent/coreapplication_obis1/sample/usagetracking/
As mentioned it is a bug so you can get the RPD and Catalog from the above mentioned links.
Step 3 : Upload the RPD and Catalog in the Enterprise Manager (EM) to make it online.
you can get how to upload RPD and Catalog in to EM from https://bidevata.wordpress.com/2011/11/23/how-to-keep-rpd-and-catalog-in-online-mode-in-obiee-11g/
Step 4 : Open the RPD in online mode and change the Usage Tracking Writer Connection Pool settings to your database credentials.
Update the row count and check whether data was populating or not.
Step 5: OBIEE 11g Usage Tracking Server Configuration:
To configure the server configuration parameters, perform the following steps:
a) Open Middleware\instances\instance1\config\OracleBIServerComponent\
coreapplication_obis1\NQSConfig.ini in Notepad and edit.
b) Next, set the usage tracking options. Scroll to the Usage Tracking section. Set Enable = Yes; to enable usage tracking.
c) In the section that lists parameters used for inserting data into a table, set the
PHYSICAL_TABLE_NAME = “OBI Usage Tracking”.”Catalog”.”dbo”.”S_NQ_ACCT” ;
d) The table name is the fully qualified name as it appears in the Physical layer of the Server Administration Tool. The general structure of this parameter depends on the type of database being used. For Oracle, the structure is PHYSICAL_TABLE_NAME = “<Database>”.”<Schema>”.”<Table>”.]
e) Set the CONNECTION_POOL parameter to specify the connection pool to use for inserting records into the usage tracking table. The setting is CONNECTION_POOL = “OBI Usage Tracking”.“Usage Tracking Writer Connection Pool”. Leave the default settings for BUFFER_SIZE, BUFFER_TIME_LIMIT_SECONDS, NUM_INSERT_THREADS, and MAX_INSERTS_PER_TRANSACTION. Your configuration file should look like this:
The connection pool name is the fully qualified name as it appears in the Physical layer of the repository.
f)Save and close the NQSConfig.ini configuration file.
Step 6 : Login to analytics http://<hostname>: <port >/analytics/ by using Administrators credentials.
Check the Usage Tracking dashboards .
We recently faced an issue while opening BI Publisher it shows only blue page,the content is not displaying.
Resolution:
Step 1 : : Login to answers page http://<hostname>: <port >/analytics/ by using the credentials.
Step 2 : Go to Administration –> Manage privileges–> Access to SOAP.
Here the permissions should be given to BI Consumer Role.
Now we are able to see the BI Publisher.
When you try to take the query from the Administration Tab we used to get an error like No Log Found.
In order to see our query we have to set the log level to 7 in RPD.
Setting Log Level in RPD:
We have to check the Logging Level in three places in RPD.
Step 1 : Open RPD by using the credentials.
Step 2 : Go to Tools–>Options–>Repository
Here set the Log Level to 7 in System Logging Level.
Step 3 : Go to Manage–>Identity–>weblogic and set the Logging level to 7 here.
Step 4 : Sometimes we used to define the Log Level in Initialization Blocks.
Go to Variables–>Session–>Initialization Blocks–Log Level.
Edit the Data Target and set the Log Level to 7.
Requirement: Rename Apply Button in OBIEE 11g:
Steps followed:
Step 1: Go to /uo1/Middleware/Oracle_BI1/bifoundation/web/msgdb/l_en/messages and locate the file viewmessages.xml.
Step 2: Edit the viewmessages.xml file and find for the tag <HTML>Apply</HTML> and replace “Apply” with “GO”.
Step 3: Restart the Services.
Step 4: Login in to verify your changes. Now we can see the Apply Button changed to GO button after successful restart.
Facing error in Agents OBIEE 11g:
Eventually succeeded, but encountered and resolved errors in Agents OBIEE 11g:
Step1: Create a new GMX account.
Go to http://www.gmx.com/ and create a new user.
Step2: Login to Enterprise Manager by using the credentials.
http://< bi server >:<7001>/em
Go to Business IntelligenceàCore ApplicationàDeploymentàMail.
Use the SMTP Server, Port, Username and Password as mentioned below.
Step3: Click Apply and Activate Changes.
Step4: Click Restart to apply recent changes.
Step5: Schedule a report.
Scheduling of report can be shown here.
https://bidevata.wordpress.com/2011/11/25/scheduling-agents-in-obiee-11g/
bi 