Scheduled refresh of Discoverer Portlet is failed

Hello Experts,
I am now facing an issue while refreshing the Oracle Discoverer Portlets. thay are scheduled to run at specific intervals.
I am getting the following errors
Main Error for some portlets
5014> Element not found for: {cn=cf_a104, wbf=1, fm=xml, nlsl=en-us, aow=false, eul=EULNAME, arq=false}
For some other portlets.
5004> Attempt 1. CORBA protocol : 0 of 1 processes started.
Other portlets
5015>
I searched in the google but didn;t find any solution for this.
Please let me know if you have any inputs on this issue.
Thanks & Regards
Salih KM
Message was edited by:
kmsalih

Thanks for your input.
I got one document from Metalink.oracle.com
Note ID is 266540.1
I will post a reply if required.
Thanks & Regards
Salih KM
Message was edited by:
kmsalih

Similar Messages

Refresh all Discoverer Portlets at once

I have 20 Discoverer Portlets and 10 users (they are using private connections). My objective is to run the refresh of portlets at once automatically.
Any suggestions?

You can set the scheduled refresh to occur at your chosen time automatically. It works pretty good compared to manual refresh even with parameter based portlets.
For example if you want to refresh every week on Monday @ 7AM type in may 12, 2008 and also 7:00AM and say refresh weekly.
Hope this helps,
-Esther

Scheduled refresh - Test connections settings validation failed: one or more connections did not pass the test

I copied a workbook that has a working scheduled refresh
modified the data model, added some new reports
added a new source (PQ from azure market place)
uploaded workbook to new powerbi location.
get the following error when i try to turn on scheduled refresh - this is even if i just select one data source that is still identical to the original (working) workbook
Test connections settings validation failed: one or more connections did not pass the test
Technical Details ▼
Correlation ID: ddcab6b8-ff2c-4881-9d8e-eeabbd23dff2
Date and Time: 12/12/2014 06:13:06 AM (UTC)
what's the problem?
Jakub @ Adelaide, Australia Blog

Still a problem and not just for me but other users going by the threads on here...
https://social.technet.microsoft.com/Forums/en-US/eb8682f4-9b40-456a-a7f1-45627a0f4ff0/cannot-schedule-refresh?forum=powerbiforoffice365#eb8682f4-9b40-456a-a7f1-45627a0f4ff0
Applies to all worksheets that utilise a PQ connection registered in the gateway. (my gateway is on an azure VM)
Existing worksheets receive this warning. New workbooks that utilise these connections also receive this warning
Adding a new PQ to the gateway and a new workbook that uses the new connection also receives this warning.
Every PQ connection I have receives this warning. My PQ connections are all to web resources. Most are to the workflowmax.com API, and one is to the Azure Marketplace to retrieve data for a date dimension.
Note: this does not prevent me from scheduling or triggering a refresh, and the refresh itself completes successfully. It's just a weird warning that caused confusion as it sounds like the actual refresh will fail as well seeing as the connection test failed.
Jakub @ Adelaide, Australia Blog

Cannot find discoverer portlet in portlet repository (9iAS rel2)

I would like to use discoverer portlet in my portal page. I have already install 9iAS 9.0.2.0.1 + 9iAS discoverer patch (9.0.2.5.3) and also patch 9iDS Discoverer to the same version (all products on Windows 2000). Then register the discoverer provider, it was successfully. But when I tried to add discoverer portlet from my portal page, I cannot find discoverer portlet provider in the repository. This happen without any errors. Any suggestion ?

Try to refresh your Discoverer Portlet Provider. It should do the trick.
Peter

Discoverer Graph on portlet not appearing after portlet scheduled refresh

Hi,
We have discoverer portlets that shows the graphs created with D40. We've recently implemented in the production environment and everything has been displayed correctly even after its overnight scheduled portlet refresh.
Today, I finally was able to refresh the cube but 2 of our portlet graphs is now displaying an error on "The data has insufficient number of rows" and
"The data has insufficient number of columns" error messages on the space for the graph. But when I click on the Analyze button, the data is complete. After I click on the "Save and Return" to portal, the graph is displayed properly. However, the saving is only for my access and the rest of the users will see the error.
How do I resolve this problem? Need help please.

Hi Keith,
For some bizzare reason, the graph is appearing now. I tried switching between 2 public connections for the past 1hour with no luck. Then now its all back. The weird thing about it was that it didn't happen to the other graphs although the other graphs were created from different cubes. There must be a cache somewhere, yet again, it should have been true to all the graphs.
I will observe this in the next few days then I will raise another SR to Oracle.
Thanks.

The last scheduled refresh failed. Click for details

Hi,
I have Discoverer scheduled results published in Portal via portlet.
The scheduled job is set to run everyday in Discoverer.
In Portal while publishing the results I set it up to refresh every day.
Though the discoverer scheduled job runs without any error I see in Portal the portlet is not refreshed.
It gives error "The last scheduled refresh failed. Click for details".
The details shows something like this
An error occurred while getting requested worksheet. BIB-10306 Object with name SWB:_LIBRARYEXECDIV_FORMAT/148142/1 could not be found.
or like
WWC-50003 - Object not found.
Cause:
The specified path to the given object does not exist.
Action:
Check that the path is valid. Path names are case-sensitive.
Can anyone help me with this
Thanks
Jay

Hi.
I don't know any real solutiion, but why don't you try to delete that potrlet and create a new one.
It's a simple and fast way and it will usually help in simmilar situations. Only if the new portlet also fails, it's a time for deeper investigation...
Jakub

Refreshing Discoverer Portlets

Using 9iAS R2, we have set up discoverer portlets on our intranet and have serveral scheduled worksheets which display within portlets.
On one report I have scheduled it to run once an hour and I have also set the Discoverer worksheet porlet to refresh on an hourly basis - which it seems to do.
However, the data is not updating at all. It is only when we actually open the worksheet using Discoverer Plus and save that data in the Portlet refreshes.
When users click on the 'view worksheet' link and open Discoverer Viewer the correct data appears
Perhaps I have missed something . . is there another way to ensure that the data shown in the portlets is refreshed?

I believe that the refresh is set as a DBMS_JOB in the database, however, I have no clue where this is set, obviously somewhere in the product and/or identity metadata database depending on your configuration. Something that might be an easier solution is use something like HTTPClient from the Apache Foundation (http://jakarta.apache.org/commons/httpclient/) and write a small app that logs into portal as an administrator and then calls each portlet's refresh URL in order. It know its a workaround, however, it should work, that being said I've never tried it. I don't know if I'll get time to write it, but if someone gets a chance to write it before I do please shoot me the code :P
Matt Topper
TUSC, The Oracle Experts

Discoverer Portlets - Refresh Job

Hello Everybody,
I have a clarification related to the Discoverer Reports Portlets.
The Refresh of Discoverer Reports Portlets can be Scheduled to run as job.
I would like to know where can i find the information of the refresh of portlets jobs.
I am currently looking into the Portal Schema to find the table.
Thanks & Regards
Salih KM

You can set the scheduled refresh to occur at your chosen time automatically. It works pretty good compared to manual refresh even with parameter based portlets.
For example if you want to refresh every week on Monday @ 7AM type in may 12, 2008 and also 7:00AM and say refresh weekly.
Hope this helps,
-Esther

How to change Refresh Time in a Discoverer Portlet?

Hi,
I have added a discoverer portlet to my main portal page. The minimum refresh time for the discoverer page i could set is 1 hour. Is there any way i could change it to 1 min as this is getting real time data in the database which i would like to display immediately.
Any help/suggestion is most welcome. Thanks in advance.
Regards
Goutam

Hi, i have the same problem.
i have searched both metalink and here but found nothing .. doesnt anybody know how to change the discoverer portlets refresh time interval anything other than 1 hour,1day,1week etc. (they are the only options available)
Any help would be appreciated.

Failed scheduled refresh

Hi,
We are getting sporadic failures on scheduled refresh, see the details bellow:
1.
Correlation ID: acd4ab73-37d9-4832-9d47-3fac01e26baf
start: 11/04/2014 at 01:31 AM
end: 11/04/2014 at 01:32 AM
error message: Sorry, something went wrong. Please try again.
2.
Correlation ID: 5b606360-8545-4c56-90da-1acb6881e1c3
start: 11/02/2014 at 04:15 PM
end: 11/02/2014 at 04:15 PM
error message: Sorry, something went wrong. Please try again.
can you provide more detailed error details? why was it failed?
Thanks,
Nadia

Nadia, is this still an issue?
Can you also submit it via the Smile/Frown button in the UI?
Thanks!
Ed Price, Azure & Power BI Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Discoverer Portlet Refresh Date

I have a Discoverer Portlet on a Portal page. Is there any way I can hide or not show the Last Refresh Date and Next Refresh Date from Discoverer Portlet?
Here's an example:
Graph or Gauge displayed and then at bottom there is:
Last Refresh Date 3/31/06 10:46 AM
Next Refresh Date 4/1/06 9:01 AM
Thanks in advance,
-- asit

If anyone's interested, i found a blog that shows how to remove it.
UIX Hack 2 Remove the Last Refresh Date from Discoverer Portlets
http://oraclebi.blogspot.com/2005/09/uix-hack-2-remove-last-refresh-date.html
Thanks Abhinav,
-- asit

Discoverer Portlet fails with ora-01017

This is about OAS 10gR2
Middle tier version: 10.1.2.0.2
Discoverer version: 10.1.2.48.18
I've manually changed password for Discoverer EUL Owner schema (using "alter user blablabla identified by blablabla" statement, in sqlplus) and now I can't register discoverer portlet provider.
It fails with the following message:
"Error!
BaseException is ... ORA-01017: invalid username/password; logon denied
Recognizing component versions...
ptlshare.jar version: 10.1.2.0.2
pdkjava.jar version: 10.1.2.0.0"
I make no idea what was the password for discover5 schema before and that was the reason i changed it.
Already have redeployed discoverer.ear file in OAS administration, but it didn't change a thing.
I've tried the Discoverer Forum but no one there answered my question.
Any ideas of what could bring this kind of issue?
TIA
Marcos

Solved!
The problem was that when I changed user password in database, i did not synchronized Database user with OID attributes.
Step by step solution:
Reset Password for DB user in sqlplus with
"Alter user XXXX identified by YYYYYY;"
Enter OID (Oracle Directory Management) as the "superuser" (ORCLADMIN);
Navigate to
-> Entry Management
-> cn=OracleContext
-> cn=Product
-> cn=IAS
-> cn=IAS InfraStructure Databases
-> cn=orclReferenceName=appsdb.ecovias.com.br
-> OrclResourceName=DISCOVERER5
Alter orclPasswordattribute for the user, using the same password you have resetted in Sqlplus.
Bounce OAS middle tier instance (ompnctl startall/stopall or using Application Server Control).
Touché, it's done!
Alternativelly, you can keep geniuses away from altering passwords...
Thanx y'all...
Marcos

Discoverer Portlet - where is refresh information stored?

Hi again
When specifying refresh information in a Discoverer Portlet (step 6 I think) where is this information stored?
I would like to programatically change the "next run time" depending on the refresh completion of our data warehouse but I simply cannot figure out in which tables the refresh information is stored...
Can anyone help me here?
Claus Jessing

I have some problems like that
I have a page is created form two porlet : Simple Parameter Form & Discoverer Worksheet . Then i have created parameter for them and add some information like : Company, Center , Type, From_date, ..... Final I have a page like this photo .
http://www.albumtown.com/data/99d86f4ed61dbbb54fe8caef653f8498/47650_p682099.jpeg
But when i change the information from simple Parameter such as : From_date, To_date.... the Discoverer Worksheet is changed like this :
http://www.albumtown.com/data/99d86f4ed61dbbb54fe8caef653f8498/47650_p682100.jpeg
Refreshing Portlet
The portlet is refreshing. There is no estimate available for the time it will take to refresh. Click the link below to refresh the page and check if the portlet is refreshed.
Refresh Page
I must click the link "Refresh Page" until Discoverer Worksheet shows the information .
I want to know "when refresh page finish " , and how i can rewrite a porlet which can relike when refresh page finish then automatic show information and users don't need click refresh Page.
Please help me .
Thanks in Advance.
John Henry

Scheduling workbooks in discoverer desktop

I'm trying to figure out how to schedule workbooks to run and export the output to a folder in Discoverer Desktop, I see in many posts that it can be done easily, I just can't figure it out, can anyone help?
I did confirm with my DBA that we do have the DBMS_Job package installed.
When I click on schedule as a user I get the following message:
A workbook cannot be scheduled for the following reason(s) - summary refresh 'job_queue_processes' parameter is 0
I would appreciate any help you can offer.
Thanks,
Janet
email: [email protected]

Hi Janet
You do not need to have DBA privilegs to schedule workbooks and any user should be able to do this. Here is an article from my notes:
Setting up Workbook Scheduling
The workbook scheduling feature in Discoverer uses native features in the Oracle DBMS, and is therefore only available when running against the Oracle database. This feature uses the same highly scalable and reliable processing procedures ithin the kernel, since the summary management capability and the setup for both features is similar. These procedures use standard packages in the DBMS called DBMS_JOB.
To enable the processing procedures for workbook scheduling in Discoverer, follow these steps:
A. Grant Schedule Workbook Privilege to the user.
B. Confirm that DBMS_JOBS has been installed.
C. Specify result set storage.
D. Set the time period at which the process kicks in.
These procedures are described in the following sections:
A. Grant Schedule Workbook Privilege to the User
The user must be granted the Schedule Workbooks privilege in the Privileges dialog. Connect to the Administration Edition, and grant the Schedule Workbooks privilege in Tools->Privileges dialog.
B. Confirming that DBMS_JOBS is Installed
1. Log onto SQL*Plus as the Administrator, and execute the following SQL statement:
SQL> select * from all_objects where object_name='DBMS_JOB' and
object_type = 'PACKAGE';
If the statement returns no rows, use SVRMGRL to create the necessary packages.
2. From Windows XP or NT, select Start->Run.
3. Type in one of the following:
SVRMGRL
4. When in the DBA facility, type CONNECT INTERNAL.
5. Execute the following SQL statement:
SQL> start <ORACLE_HOME>/rdbms/admin/dbmsjob.sql;
SQL> start <ORACLE_HOME>/rdbms/admin/prvtjob.plb;
C. Specifying Result Set Storage
When a scheduled workbook is run, the results are stored in database tables
within the database. Result set data created as part of the workbook
scheduling process may be stored in one of two areas:
the user's own schema or a centralized schema.
User's Schema
In order to enable workbook scheduling in the user's own database schema,
the user requires the following database privileges:
Create Procedure
Create Table
Create View
To grant these privileges, do the following:
1. Log onto SQL*Plus or SQLDBA as the Database Administrator.
2. Type the following:
SQL> Grant CREATE PROCEDURE to <USER>;
SQL> Grant CREATE TABLE to <USER>;
SQL> Grant CREATE VIEW to <USER>;
SQL> Grant EXECUTE ANY PROCEDURE to <USER>;
SQL> Grant SELECT on SYS.DBMS_JOB to <USER>;
SQL> Grant EXECUTE on SYS.V$_PARAMETER to <USER>;
where <USER> is the userid of the person who is to be allowed to schedule
workbooks.
These privileges must be granted directly to the user and not to a database
role.
Advantages: A database limit can be specified on the maximum amount of data a
user can store in the database. If the result set is stored under the user's
schema, then you keep control over the maximum amount of space one individual
user can fill with result sets. If the user creates a scheduled workbook that
fills that space, it affects only his/her own scheduled workbook.
Disadvantage: The user is required to have the above privileges in the database.
Repository User's Schema
In order to enable workbook scheduling using a centralized repository user's
schema, the SQL script batchusr.sql must be run in SQL*Plus or SQLDBA as a
database administrator (such as, SYSTEM). This script creates a new user that
is granted the above privileges.
In addition, the administrator of the EUL must change the user so that the
Repository User property is pointing to the repository user's schema just
created. The centralized repository user's schema may be customized by the
database administrator for space management purposes and underlying data access.
NOTE: SELECT ANY TABLE access is given by the script batchusr.sql,
but this may be limited provided the repository user's schema is
granted access to the underlying data that will be accessed for
workbook scheduling.
The repository user created will not be able to directly schedule a workbook
through the User Edition.
Advantages: Each user does not need DML procedures to run scheduled workbooks.
Disadvantages: One user can potentially run a scheduled workbook that fills the
available result set space, preventing other scheduled workbooks from running
until it is cleared.
D. Setting the Start Time for Workbook Processing
The workbook processes run within the database on the server, and are
controlled by parameters in the initialization file of the Oracle DBMS
- the INIT<SID>.ORA file.
To limit the number of processing requests that can run simultaneously:
The parameter job_queue_processes specifies the number of concurrent processes to use to process DBMS_JOB. It controls the number of processing requests that can be handled simultaneously. The default value is zero, which means processing requests will not be created. You should set it to a minimum of 2 or more if you have any other applications that use DBMS_JOB.
You need more than one job queue process, because if one job fails for any reason, it may keep getting re-submitted, and thus, prevent everything else in the queue from being completed. If you want to have 10 simultaneous processing requests handled, then you will need to set this to 10.
The INIT<SID>.ORA parameter job_queue_interval is the time in seconds that controls how often the job processes wake up to process pending jobs. The default is 60, which is quite frequent. What you set this to depends on how frequently you want the process to wake up and serve the requests that have been made. Oracle recommends that you update the 60 seconds default to at least 10 minutes (a value of 600).
NOTE: This parameter also affects summary management.
To enable these parameters:
1. Locate the INIT<SID>.ORA file.
For example, on Personal Oracle7 the INIT<SID>.ORA file is held in
<ORACLE_HOME>\database. Its default name is INITORCL.ORA where ORCL is
the <SID> name.
2. Enter 2 lines into the file. For example:
job_queue_processes = 2
job_queue_interval = 600 (equivalent to 10 minutes)
NOTE: The summary management and workbook scheduling features both use this scheduling capability within the Oracle DBMS. The interval you specify and the number of concurrent requests affect both features.

BPC 10.0 Input Schedule refresh : investigating performance issues on frontend side

Hello,
We are running SAP BPC NW 10.0 SPS8.
We recieve a lot of complaints regarding performance issues.
More specifically BPC Input Schedule refresh takes ages (11 minutes actually)
I am a SAP Basis Administartor with some solid BW experience, but very linited BPC knowledge.
So raf we have tried the following :
* BPC Full and light ptmimize of the BPC Cubes.
* Updating Oracle Statistics
* Activating ABAP/SQL traces*
* Checking USJTAT Logs
Then it rutned out that the perfromance problems werre not caused by the backend SAP BW server (only 9 seconds of bakend processing are displayed in UJSTAT).
The overwhelming majority of the processing is spent on the frontend side : on the computer of the user.
We really would like to know what is happening on BPC Frontend side, but are really lacking any investigative method .....
other that checking memory/CPU usage o nthe frontend computer.
From your experience, is there any tool/method to allow to conduct some investigation on what is going on the frontend side, when a BPC Input Schedule is refreshed ?
Thank you for your attention.

Hello Vadim,
We still need to get confirmation from the external consultants who developed the BPC solution, but as far as I can understand it :
We do not use use member formulas
We are indeed talking about EPM (without EPMRetrieveData functions)
The perfromance problems occur in DEV and QAS , after a restore of the BPC environment (backup from PRD)
We already had the problem in the past, but we never knew precisely how to solve it, it is as if there was some missing links between the restored BPC environment from PRD and the DEV/QAS system
One additional information, we checked the EPM CLient Log , and here are the errors displayed while refreshing the input schedule :
The thing is that I have no idea what it means ...
?FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2
RECORD_SEPARATOR:35
COLUMN_SEPARATOR:124
COLUMNS:Time|Severity|Category|Method|User|DSRRootContextID|DSRTransactionID|DSRConnectionID|DSRCounter|Thread|Text
SEVERITY_MAP:DEBUG|Debug|INFO|Information|VERBOSE|Verbose|WARNING|Warning|ERROR|Error|FATAL|Fatal
HEADER_END
2014-04-18 08:41:17,446|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,613|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,630|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,648|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:18,731|ERROR|ReportManagement|FPMXLClient.Office.EPMExcelReportManagerRepository.GetReportManager|BPCUSER|||||1|Unable to get the Object property of the OLEObject class#
2014-04-18 08:41:37,171|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 1#
2014-04-18 08:41:39,348|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 08:41:39,474|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 08:41:39,536|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 08:41:39,597|ERROR|ReportManagement|FPMXLClient.ReportManagement.DynamicReport.Load|BPCUSER|||||1|bytes = 0#
2014-04-18 09:00:22,088|ERROR|Dataservice|FPMXLClient.BPCProxy.MetaData_Data.DataServiceHelper.ExecuteReportAsStream|BPCUSER|||||ServerCallThread_666f378d-d824-4a8a-bf38-0da8493e2382|An error has occured on the server#
2014-04-18 09:00:22,252|ERROR|BPC10Connection|FPMXLClient.Connection.RESTConnection.ExecuteReport|BPCUSER|||||ServerCallThread_666f378d-d824-4a8a-bf38-0da8493e2382|An error has occured on the server#
2014-04-18 09:00:22,268|ERROR|OfficeWrappers|FPMXLClient.Office.EPMReportManager.ExecuteReport|BPCUSER|||||1|An error has occured on the server#
2014-04-18 09:00:22,317|ERROR|OfficeWrappers|FPMXLClient.Office.EPMExcelReportManager.RefreshReports|BPCUSER|||||1|An error has occured on the server#
2014-04-18 09:00:22,447|ERROR|AnalyzerOne|FPMXLClient.AddIn.RefreshSheetWithScan|BPCUSER|||||1|Execution of Report Default Report failed : #
2014-04-18 09:00:22,537|ERROR|Automation|FPMXLClient.EPMAddInAutomation.RefreshActiveSheet|BPCUSER|||||1|Execution of Report Default Report failed : #

Scheduled refresh of Discoverer Portlet is failed

Similar Messages

Maybe you are looking for