JOURNAL.lgf can take too long

Hello,
We are facing an issue with the JOURNAL.lgf and I would really appreciate your feedback.
Our JOURNAL logic generates an additional record with the closing balance, however even though for most of the users, the process of this logic is instantaneously, for some users it can take up to hours to refresh the additional record that the JOURNAL logic has to generate.
I am not able to reproduce the issue because in my case, I post a journal and it generates the records instantaneously. Is there a way to track how long the logic takes? (BIF transaction, etc.)
Why could it be that this issue is only happening to few users with the same authorizations?
Has anyone faced this issue?
We are using SAP BPC 7.5 NW SP03
Many thanks in advance
Best regards
Dani
Edited by: Daniel Sobrino on Feb 1, 2011 5:13 PM
Edited by: Daniel Sobrino on Feb 1, 2011 5:35 PM
Edited by: Daniel Sobrino on Feb 1, 2011 5:35 PM

Hello,
We found out with te audit data report that for some oof the user facing this problem, the JOURNAL.lgf is not being executed until another user posts a journal and updated the previous journal.
We will create the user ID's again
Regards
Dani
Edited by: Daniel Sobrino on Feb 2, 2011 12:42 PM

Similar Messages

What can I do if I don't remember my security cuestions? And it takes too long to receive the email

Please if you can answer me I will be very thanks full

Sorry my question is what can I do if I don't remember my security questions and it takes too long to receive the email

HT204406 what if i do not want artwork for any song? they take too long to upload and I personally don't care to retain or see the "artwork". Can you diable this in itunes match?

what if i do not want artwork for any song? they take too long to upload and I personally don't care to retain or see the "artwork". Can you diable this in itunes match?

Agreed. I hope they allow this some time soon or iTunes Match will remain a big disappointment for me.

After updating my iphone 5s to 7.1 ... the keyboard is crashing and it takes too long to respond, what is the solution? if there any link from which we can download the original 7.1 firmware for A1533 Version?

After updating my iphone 5s to 7.1 ... the keyboard is crashing and it takes too long to respond, what is the solution? if there any link from which we can download the original 7.1 firmware for A1533 Version?

Restoring the iPhone will reload its firmware.
Plug the iPhone into (the current version of) iTunes on your computer.
Let it sync. Then choose "Restore" from the iPhone's summary page in iTunes.

What can I do when my iphone 4 take too long to restore? It only has 1 song on it

What can I do when my iphone 4 take too long to restore? It only has 1 song on it and 1 additional app beside the standard apps.
The circle in the middle of the phone has been spinning from after 4 yesterday afternoon until now. Please help me

I'm having the same problem. I got error message 21. I went to apple store. they are saying i have a hardware error. Really, my phone was working before the update. Asked me for $150 to get another one when I am due to get a new one and wanted to pass this one on to my child.
Help please,
I will be glad to go back to the older software update

When I back up my library, the pictures do not go to my external HD as albums/pastes, they are copied all together, so I have to arrange one by one to get all organized. It takes too long. Is there any option to organize it automatically? Thanks

When I back up my library, the pictures do not go to my external HD as albums/pastes, they are copied all together, so I have to arrange one by one to get all organized. It takes too long. Is there any option to organize it automatically? Thanks

If you backup correctly to a correctly formatted drive (Mac OS extended (journaled) )then everything can be restored exactly as it was prir to the backup
How exactly are you "backing up"?
LN

11gR2:crsctl, srvctl commands takes too long to respond

Hi,
I have successfully configured *11gR2 two node RAC on ASM on Win 2008 64bit.*
Everything work very well like connecting to database, querying database. Node restart also takes acceptable time to go down & restart the clusterware & database.
But when I execute crsctl status resource -t or srvctl status database -d db_name commands from any node takes 10-15min to give output.
They give output & everything completes successfully but takes too long to respond.
The questions are:
- If everything works fine then why crsctl, srvctl takes too long to respond?
- what could be blocking these command to gather clusterware and database status on all nodes?
- what additional info would be helpful that I can provide?

dag wrote:
I dont have this issue either. are you auto starting mpd?
that time is how long it is up in other words you opened it then closed it at that time
I'm not sure if you are referring to me or not, but in my screenshot I am timing the lag in ncmpcpp by pressing 'q' in the terminal during the delay, so it quits ncmpcpp immediately after the lag. The lag is longer for ncmpc because the interface loads before the program connects to mpd, so I have to stop it manually immediatly after it connects.
WonderWoofy wrote:I don't have this problem... if you are starting it as a systemd user service, maybe there is relevant information in the journal.
The journal did not reveal anything relevant sadly. I have now tried launching mpd without systemd, and the lag remains. I have also noticed that a small mpd programming project I am writing also experiences the same lag when it tries to connect to mpd.

Report Takes Too Long Time

Hi!
I am in troubble
following is the query
SELECT inv_no, inv_name, inv_desc, i.cat_id, cat_name, i.sub_cat_id,
sub_cat_name, asset_cost, del_date, i.bl_id, gen_desc bl_desc, p.prvcode, prvdesc, cur_loc,
pldesc, i.pmempno, pmname, i.empid, empname
FROM inv_reg i,
cat_reg c,
sub_cat_reg s,
gen_desc_reg g,
ploc p,
province r,
pmaster m,
iemp_reg e
WHERE i.sub_cat_id = s.sub_cat_id
AND i.cat_id = s.cat_id
AND s.cat_id = c.cat_id
AND i.bl_id = g.gen_id
AND i.cur_loc = p.plcode
AND p.prvcode = r.prvcode
AND i.pmempno = m.pmempno(+)
AND i.empid = e.empid(+)
&wc
order by prvdesc, pldesc, cat_name, sub_cat_name, inv_no
and this query returns 32000 records
when i run this query on reports 10g
then it takes 10 to 20 minuts to generate report
how can i optimize it...?

Hi Waqas Attari
Pls study & try this ....
When your query takes too long ...
hope it helps....
Regards,
Abdetu...

OPM process execution process parameters takes too long time to complete

PROCESS_PARAMETERS are inserted every 15 min. using gme_api_pub packages. some times it takes too long time to complete the batch ,ie completion of request. it takes about 5-6 hrs long time ,in other time s it takes only 15-20 mins.This happens at regular interval...if anybody can guide me I will be thankful to him/her..
thanks in advance.
regds,
Shailesh

Generally the slowest part of the process is in the extraction itself...
Check in your source system and see how long the processes are taking, if there are delays, locks or dumps in the database... If your source is R/3 or ECC transactions like SM37, SM21, ST22 can help monitor this activity...
Consider running less processes in parallel if you have too many and see some delays in jobs... Also indexing some of the tables in the source system to expedite the extraction, make sure there are no heavy processes or interfaces running in the source system at the same time you're trying to load... Check with your Basis guys for activity peaks and plan accordingly...
In BW also check in your SM21 for database errors or delays...
Just some ideas...

Web application deployment takes too long?

Hi All,
We have a wls 10.3.5 clustering environment with one admin server and two managered servers separately. When we try to deploy a sizable web application, it takes about 1 hour to finish. It seems that it takes too long to finish the deployment. Here is the output from one of two managerd server system log. Could anyone tell me it is normal or not? If not, how can I improve this?
Thanks in advance,
John
+####<Feb 29, 2012 12:11:03 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535463373> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_NEW to STATE_PREPARED on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:05 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <9baa7a67b5727417:26f76f6c:135ca05cff2:-8000-00000000000000b0> <1330535465664> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_NEW to STATE_PREPARED on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466493> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_PREPARED to STATE_ADMIN on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466493> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_PREPARED to STATE_ADMIN on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466809> <BEA-149059> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] is transitioning from STATE_ADMIN to STATE_ACTIVE on server Pinellas1tMS3.>+
+####<Feb 29, 2012 12:11:06 PM EST> <Info> <Deployer> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330535466809> <BEA-149060> <Module copyrequest of application copyrequest [Version=COPYREQUEST0002bb] successfully transitioned from STATE_ADMIN to STATE_ACTIVE on server Pinellas1tMS3.>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442300> <BEA-320143> <Scheduled 1 data retirement tasks as per configuration.>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320144> <Size based data retirement operation started on archive HarvestedDataArchive>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320145> <Size based data retirement operation completed on archive HarvestedDataArchive. Retired 0 records in 0 ms.>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320144> <Size based data retirement operation started on archive EventsDataArchive>+
+####<Feb 29, 2012 1:00:42 PM EST> <Info> <Diagnostics> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330538442301> <BEA-320145> <Size based data retirement operation completed on archive EventsDataArchive. Retired 0 records in 0 ms.>+
+####<Feb 29, 2012 1:10:23 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <weblogic.cluster.MessageReceiver> <<WLS Kernel>> <> <> <1330539023098> <BEA-003107> <Lost 2 unicast message(s).>+
+####<Feb 29, 2012 1:10:36 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539036105> <BEA-000111> <Adding Pinellas1tMS2 with ID -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 to cluster: Pinellas1tCluster1 view.>+
+####<Feb 29, 2012 1:11:24 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539084375> <BEA-000128> <Updating -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 in the cluster.>+
+####<Feb 29, 2012 1:11:24 PM EST> <Info> <Cluster> <entwl3t-vm.co.pinellas.fl.us> <Pinellas1tMS3> <[STANDBY] ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1330539084507> <BEA-000128> <Updating -9071779833610528123S:entwl2t-vm:[7005,7005,-1,-1,-1,-1,-1]:entwl2t-vm:7005,entwl3t-vm:7007:Pinellas1tDomain:Pinellas1tMS2 in the cluster.>+
Edited by: john wang on Feb 29, 2012 10:36 AM
Edited by: john wang on Feb 29, 2012 10:37 AM
Edited by: john wang on Feb 29, 2012 10:38 AM

Hi John,
There may be some circumstances like when there are many files in the WEB-INF folder and JPS don't use TLD.
I don't think a 1hour deployment is normal, it should be much more faster.
Since you are using 10.3.5, I suggesto you to install the corresponding patch:
1. Download patch 10118941p10118941_1035_Generic.zip
2. Uncompress the file p10118941_1035_Generic.zip
3. Copy the required files (patch-catalog_XXXXX.xml, CIRF.jar ) to the Patch Download Directory (typically, this folder is <WEBLOGIC_HOME>/utils/bsu/cache_dir).
4. Rename the file patch-catalog_XXXXX.xml into patch-catalog.xml .
5. Start Smart Update from <WEBLOGIC_HOME>/utils/bsu/bsu.sh .
6. Select "Work Offline" mode.
7. Go to File->Preferences, and select "Patch Download Directory".
8. Click "Manage Patches" on the right panel.
9. You will see the patch in the panel below (Downloaded Patches)
10. Click "Apply button" of the downloaded patch to apply it to the target installation and follow the instructions on the screen.
11. Add "-Dweblogic.jsp.ignoreTLDsProcessingInWebApp=true" to the Java options to ignore additional findTLDs cost.
12. Restart servers.
Hope this helps.
Thanks,
Cris

AME CS6 rendering with AE and Pr takes too long

Hi Guys,
Need some help here. i have rendered a 30 secs mp4 video with 1920 x 1080 HD format 25 frames w/o scripting in AME for 4 hours!
Why does it take too long? I have rendered a 2 minute video with same format w/ scripting but only spare less than 30 minutes for rendering.
Im using After Effects and Premium Pro both CS6 and using Dynamic Link in AME.
What seems to be wrong in my current settings?
Any help would be appreciated.
Thanks!

This may be a waste of time, but it won't take a minute and is something you should always do whenever things go strangely wrong ............ trash the preferences, assuming you haven't done it already.
Many weird things happen as a result of corrupt preferences which can create a vast range of different symptoms, so whenever FCP X stops working properly in any way, trashing the preferences should be the first thing you do using this free app.
http://www.digitalrebellion.com/prefman/
Shut down FCP X, open PreferenceManager and in the window that appears:-
1. Ensure that only FCP X is selected.
2. Click Trash
The job is done instantly and you can re-open FCP X.
There is absolutely no danger in trashing preferences and you can do it as often as you like.
The preferences are kept separately from FCP X and if there aren't any when FCP X opens it automatically creates new ones . . . instantly.

My Query takes too long ...

Hi ,
Env   , DB 10G , O/S Linux Redhat , My DB size is about 80G
My query takes too long , about 5 days to get results , can you please help to rewrite this query in a better way ,
declare
x number;
y date;
START_DATE DATE;
MDN VARCHAR2(12);
TOPUP VARCHAR2(50);
begin
for first_bundle in
select min(date_time_of_event) date_time_of_event ,account_identifier ,top_up_profile_name
from bundlepur
where account_profile='Basic'
AND account_identifier='665004664'
and in_service_result_indicator=0
and network_cause_result_indicator=0
and   DATE_TIME_OF_EVENT >= to_date('16/07/2013','dd/mm/yyyy')
group by account_identifier,top_up_profile_name
order by date_time_of_event
loop
select sum(units_per_tariff_rum2) ,max(date_time_of_event)
into x,y
from OLD_LTE_CDR
where account_identifier=(select first_bundle.account_identifier from dual)
and date_time_of_event >= (select first_bundle.date_time_of_event from dual)
and -- no more than a month
date_time_of_event < ( select add_months(first_bundle.date_time_of_event,1) from dual)
and -- finished his bundle then buy a new one
date_time_of_event < ( SELECT MIN(DATE_TIME_OF_EVENT)
                         FROM OLD_LTE_CDR
                         WHERE DATE_TIME_OF_EVENT > (select (first_bundle.date_time_of_event)+1/24 from dual)
                         AND IN_SERVICE_RESULT_INDICATOR=26);
select first_bundle.account_identifier ,first_bundle.top_up_profile_name
,FIRST_BUNDLE.date_time_of_event
INTO MDN,TOPUP,START_DATE
from dual;
insert into consumed1 VALUES(X,topup,MDN,START_DATE,Y);
end loop;
COMMIT;
end;

> where account_identifier=(select first_bundle.account_identifier from dual)
Why are you doing this? It's a completely unnecessary subquery.
Just do this:
where account_identifier = first_bundle.account_identifier
Same for all your other FROM DUAL subqueries. Get rid of them.
More importantly, don't use a cursor for loop. Just write one big INSERT statement that does what you want.

Query designer takes too long to save a query

Hi dear SDN friends.
I´m working with query designer in BI 7 and sometimes it takes too long to save a query, about ten minutes. Sometimes it never ends saving and some other times it saves the same query in 1 minute.
Can anybody please give an advice about this behavior of the query designer?
We have recently update BI to sp18. In query designer I have sp5 revision 529
Best regards,
Karim Reyes

Hello Karim,
I would suggest testing this again in the latest Frontend Patch available (FEP 602). In FEPs 600, 601, & 602 there were some performance and stability improvements made which may correct your issue. If the issue persists, I would suggest then opening a Customer Message via Service Marketplace.
It can be downloaded from:
http://service.sap.com/swdc
u2192Download
u2192Support Packages and Patches
u2192Entry by Application Group
u2192SAP Frontend Components
u2192BI ADDON FOR SAPGUI
u2192 BI 7.0 ADDON FOR SAPGUI 7.10
u2192 BI 7.0 ADDON FOR SAPGUI 7.10
u2192Win32
See SAP Note 1085218 for planned FEP releases.
I hope that helps.
Regards,
Tanner Spaulding
SAP NetWeaver RIG Americas, BI

OIM11g managed server startup takes too long

I am running a OIM11g managed server using weblogic on windows xp; in development mode
My managed server takes too long to startup; averaging atleast an hour at the minimum.
I am attaching the logs from the server between the time frame when it took the longest time.
Can someone please help me to improve the startup.
Edited by: 838243 on Feb 20, 2011 10:22 AM

<9:32:14 PM> <Info> <EJB><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-010008> <EJB Deploying file: iam-ejb.jar>
<9:45:06 PM> <Info> <JDBC><oim1> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-001128> <Connection for pool "mds-oim" closed.>
<9:45:07 PM> <Info> <Common><oim1> <MDSPollingThread-[oim, jdbc/mds/MDS_REPOS]> <anonymous> <BEA-000628> <Created "1" resources for pool "mds-oim", out of which "1" are available and "0" are unavailable.>
<10:00:06 PM> <Info> <JDBC><oim1> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-001128> <Connection for pool "mds-oim" closed.>
<10:00:07 PM> <Info> <Common><oim1> <MDSPollingThread-[oim, jdbc/mds/MDS_REPOS]> <anonymous> <BEA-000628> <Created "1" resources for pool "mds-oim", out of which "1" are available and "0" are unavailable.>
<10:15:11 PM> <Info> <JDBC><oim1> <[ACTIVE] ExecuteThread: '14' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-001128> <Connection for pool "mds-oim" closed.>
<10:15:41 PM> <Info> <Common><oim1> <MDSPollingThread-[oim, jdbc/mds/MDS_REPOS]> <anonymous> <BEA-000628> <Created "1" resources for pool "mds-oim", out of which "1" are available and "0" are unavailable.>
<10:30:11 PM> <Info> <JDBC><oim1> <[ACTIVE] ExecuteThread: '19' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-001128> <Connection for pool "mds-oim" closed.>
<10:30:15 PM> <Info> <Common><oim1> <MDSPollingThread-[oim, jdbc/mds/MDS_REPOS]> <anonymous> <BEA-000628> <Created "1" resources for pool "mds-oim", out of which "1" are available and "0" are unavailable.>
<10:32:44 PM> <Info> <Deployer><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-149060> <Module iam-ejb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server oim_server1.>
<10:32:44 PM> <Info> <Deployer><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-149059> <Module dataobjects-ejb.jar of application oim [Version=11.1.1.3.0] is transitioning from STATE_NEW to STATE_PREPARED on server oim_server1.>
<10:33:08 PM> <Info> <J2EE><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-160166> <References were found in deployment plan for module 'dataobjects-ejb.jar' with uri, 'META-INF/weblogic-ejb-jar.xml'. The plan was merged.>
<10:33:14 PM> <Info> <EJB><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-010008> <EJB Deploying file: dataobjects-ejb.jar>
<10:38:10 PM> <Info> <Deployer><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-149060> <Module dataobjects-ejb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server oim_server1.>
<10:38:10 PM> <Info> <Deployer><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-149059> <Module iam-async-mdb.jar of application oim [Version=11.1.1.3.0] is transitioning from STATE_NEW to STATE_PREPARED on server oim_server1.>
<10:38:10 PM> <Info> <J2EE><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-160166> <References were found in deployment plan for module 'iam-async-mdb.jar' with uri, 'META-INF/ejb-jar.xml'. The plan was merged.>
<10:38:11 PM> <Info> <J2EE><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-160166> <References were found in deployment plan for module 'iam-async-mdb.jar' with uri, 'META-INF/weblogic-ejb-jar.xml'. The plan was merged.>
<10:38:11 PM> <Info> <EJB><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-010008> <EJB Deploying file: iam-async-mdb.jar>
<10:38:13 PM> <Info> <Deployer><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-149060> <Module iam-async-mdb.jar of application oim [Version=11.1.1.3.0] successfully transitioned from STATE_NEW to STATE_PREPARED on server oim_server1.>
<10:38:13 PM> <Info> <Deployer><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-149059> <Module xlWebApp of application oim [Version=11.1.1.3.0] is transitioning from STATE_NEW to STATE_PREPARED on server oim_server1.>
<10:38:13 PM> <Info> <J2EE><oim1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <WLS Kernel> <BEA-160166> <References were found in deployment plan for module 'xlWebApp.war' with uri, 'WEB-INF/web.xml'. The plan was merged.>
Edited by: 838243 on Feb 20, 2011 10:22 AM

Drill Through reports takes too long

Hi all,
I need some suggestions/help with our drill through reports. We are using Hyperion 11.1.1.3 and the cube is ASO.
We have drill through reports set up in Essbase studio for drilling down from Essbase to Oracle database. It takes too long (like 30 mins for fetching 1000 records) and the query is simple.
What are the changes that we can do to bring down this time. Please advice.
Thanks.

Hi Glenn,
We tried optimizing the drill through SQL query but actually when we run the directly in TOAD it takes *23 secs* but when we do drill through on the same intersection
it took more than 25 mins. Following is our query structure :
(SELECT *
FROM "Table A" cp_594
INNER JOIN "Table B" cp_595 ON (cp_594.key = cp_595.key)
WHERE (Upper(cp_595.*"Dim1"*) in (select Upper(CHILD) from (SELECT * FROM DIM_TABLE_1 where CUBE = 'ALL') WHERE CONNECT_BY_ISLEAF = 1 START WITH PARENT = $$Dim1$$ CONNECT BY PRIOR CHILD = PARENT UNION ALL select Upper(CHILD) from DIM_TABLE_1 where CUBE = 'ALL' AND REPLACE('GL_'||CHILD, 'GL_IC_', 'IC_') = $$Dim1$$))
And ----same for 5 more dimensions
Can you suggest some improvement ? Please advice.
Thanks

JOURNAL.lgf can take too long

Similar Messages

Maybe you are looking for