Long time cancel process
Hello expert,
I ran a complex sql for 30 minutes, without completing, I aborted it , a message window displayed as " Cancel pending, please wait ( This may take some time)". but till now , 1:21 hrs passed, no sign to stop, will you please tell me why this cancelling process takes some much time? what can I do to get rid of this long time cancel processing?
Many Thanks.
Without knowing more details (what was the SQL doing, what application are you using, what is the application doing when you hit the cancel button, what is the database doing and waiting on, etc.), it's hard to say. Among the options
- Your SQL statement made a number of database changes that need to be rolled back and that is a generally slow process
- Your application isn't actually going to send a request to stop the execution of the SQL statement until the first rows are returned
- Your application has hung and Oracle isn't doing anything
Justin
Similar Messages
-
How to avoid the long time consuming process of settlement on periodic basi
For investment Project(purpose of capitalisation) related expenses We would like to show it Directly in Balance Sheet rather than P/L A/C.Whether it is feasible or not?as per one of consultant it will be first hit the p/L and after settlement it will only be shown in B/Sheet.So how to avoid the long time consuming process of settlement on periodic basis.
Hi, could you write down an example? And what you mean by investment project-is this an WBS?
-
CV04N takes long time to process select query on DRAT table
Hello Team,
While using CV04N to display DIR's, it takes long time to process select query on DRAT table. This query includes all the key fields. Any idea as to how to analyse this?
Thanks and best regards,
Bobby
Moderator message: please read the sticky threads of this forum, there is a lot of information on what you can do.
Edited by: Thomas Zloch on Feb 24, 2012Be aware that XP takes approx 1gb of your RAM leaving you with 1gb for whatever else is running. MS Outlook is also a memory hog.
To check Virtual Memory Settings:
Control Panel -> System
System Properties -> Advanced Tab -> Performance Settings
Performance Options -> Adavanced Tab - Virtual Memory section
Virtual Memory -
what are
* Initial Size
* Maximum Size
In a presentation at one of the Hyperion conferences years ago, Mark Ostroff suggested that the initial be set to the same as Max. (Max is typically 2x physical RAM)
These changes may provide some improvement. -
BPM Process chain takes long time to process
We have BI7, Netweaver 2004s on Oracle and SUN Solaris
There is a process chain (BPM) which pulls data from the CRM system into BW. The scheduled time to run this chain is 0034 hrs. This chain should ideally complete before / around 0830 Hrs. <b>Now the problem is that every alternate day this chain behaves normally and gets completed well before 0830 hrs but every alternate day this chain fails </b> there are almost 40 chains running daily. Some are event triggered (dependent with each other) or some run in parallel. In this, (BPM) process chain, usually there are 5 requests with 3 Delta and 2 full uploads (Master Data). The delta uploads finishes in 30 minutes without any issues with very few record transfers. The first full upload is from 0034 hrs to approximately 0130 hrs and the 2nd upload is from 0130 hrs to 0230 hrs. Now if the 1st upload gets delayed then the people who are initiating these chains, stop the 2nd full upload and continue it after all the process chains are completed. Now this entire BPM process chain sometimes takes 17 -18 hrs to complete!!!!!
No other loads in CRM or BW when these process chains are running
CRM has background jobs to push IDOCS to BW which run every 2 minutes which runs successfully
Yesterday this chain got completed successfully (well within stipulated time) with over 33,00,000 records transferred but sometimes it has failed to transfer even 12,00,000 records!!
Attaching a zip file, please refer the 21 to 26 Analysis screen shot.doc from the zip file
Within the zip file, attaching Normal timings of daily process chains.xls the name explains it .
Also within the zip file refer BPM Infoprovider and data source screen shot.doc please refer this file as the infopackage (page 2) which was used in the process chain is not displayed later on in page number 6 BUT CHAIN GOT SUCESSFULLY COMPLETED
We have analyzed:--
1) The PSA data for BPM process chain for past few days
2) The info providers for BPM process chain for past few days
3) The ODS entries for BPM process chain for past few days
4) The point of failure of BPM process chain for past few days
5) The overall performance of all the process chains for past few days
6) The number of requests in BW for this process chain
7) The load on CRM system for past few days when this process chain ran on BW system
As per our analysis, there are couple of things which can be fixed in the BW system:--
1) The partner agreement (transaction WE20) defined for the partner LS/BP3CLNT475 mentions both message types RSSEND and RSINFO: -- collect IDOCs and pack size = 1 Since the pack size = 1 will generate 1 TRFC call per IDOC, it should be changed to 10 so that less number of TRFCs will be generated thus less overhead for the BW server resulting in the increase in performance
2) In the definition of destination for the concerned RFC in BW (SM59), the Technical Setting tab says the Load balancing option = No. We are planning to make it Yes
But we believe that though these changes will bring some increase in performance, this is not the root cause of the abnormal behavior of this chain as this chain runs successfully on every alternate day with approximately the same amount of load in it.
I was not able to attach the many screen shots or the info which I had gathered during my analysis. Please advice how do I attach these files
Best Regards,Hi,
Normally index creation or deletion can take long time in case your database statistics are not updated properly, so can check stat after your data loading is completed and index generation is done, Do creation of database statistics.
Then try to recheck ...
Regards,
Satya -
Hyperion Report taking a long time to process local query
Hi All,
I am trying to run a report on Hyperion IR 9.3.1. I am facing a performance issue with this report. I am joining 13 tables using full outer join. Each table is having data about 900 rows and the final output i am getting from the local query is about 11000 rows. This local query is taking a long time to get process about 3 - 5 minutes. I suppose it should run with in 30 sec as number of rows are very few. Can anyone tell me what is the problem with this local query and how the performance of the report can be increased?
Thanks in advance.
Regards
UjjawalBe aware that XP takes approx 1gb of your RAM leaving you with 1gb for whatever else is running. MS Outlook is also a memory hog.
To check Virtual Memory Settings:
Control Panel -> System
System Properties -> Advanced Tab -> Performance Settings
Performance Options -> Adavanced Tab - Virtual Memory section
Virtual Memory -
what are
* Initial Size
* Maximum Size
In a presentation at one of the Hyperion conferences years ago, Mark Ostroff suggested that the initial be set to the same as Max. (Max is typically 2x physical RAM)
These changes may provide some improvement. -
How long time to process an application?
I have just submitted the application and label details in the iTunes Store. Approximately how long time will it take to process my application?
Maybe 10-20 minutes. It seems to vary a little, but that ought to be the range
-
IMovie taking a very long time to process anything, even open
I have 2.66ghz MacBook Pro 4GB of RAM. I figured this computer should have no problem processing and opening programs. However, when I open iMovie, it hangs for a very long time, sometimes 5 minutes. At first I thought it was just crashing but I let it go for a while and it eventually started working.
Anyone else having this issue? Is this program really so demanding that a $3000 laptop struggles to open it? Is there any fix to this?No clue why the final processes have suddenly started to take so long. Two things I'd try: a) capture from an older tape to see if some problem with the new tape is at fault. And b) check the health of your RAM and the hard drive.
The red frame sounds a bit like a glitch we used to have in OnLocation (actually in its predecessor HDV Rack) which was caused by a partial GOP. But that was a product of HDV Rack recording from the live video stream. It turned out that HDV cameras intentionally interrupt the data stream for an instant upon starting to record--specifically to avoid recording a partial GOP to tape. So my gut says that the tape has partial GOPs at the points where you stopped/started recording. -
My procedure is taking long time to process the attendance information?
Dear Experts
I have procedure which runs employees monthly attendance sorry here I am unable to post the procedure it contains 4500 lines and I am using oracle 11g R2 version on Windows 2008 R2 Server with 4 GB RAM
I have run my procedure for 1 section which have 180 employees count and procedure took 28 min of time to complete the process for 1 month and I have total 3000+ employee to run the attendance process for all the employee for 1 month.
I am Storing all the employees in Cursor then looping one by one with Dates (1st to End of the month one date for all the employees) using While Loop.
or
can you give me the suggestion how can I find at which stage procedure is taking time in the 4500 lines of code.I tried with BULK COLLECT with for loop however it takes 6 hrs 50 min to complete the process where as cursor completes it with in 25 min
Below is the type which I have used
TYPE employee_nums_t IS TABLE OF employeemaster.empno%TYPE
INDEX BY PLS_INTEGER;
l_employee_nums employee_nums_t;
select EMPM.EMPNO BULK COLLECT INTO l_employee_nums
FROM EMPLOYEEATTENDANCE EMPA,EMPLOYEEMASTER EMPM,SECTIONMASTER SEM,CATEGORYMASTER CGM
WHERE SEM.SECTIONID=EMPM.SECTIONID AND EMPM.CATEGORYID=CGM.CATEGORYID
AND EMPM.CATEGORYID!='4'
AND (P_SECTIONID IS NULL OR SEM.SECTIONID = P_SECTIONID)
AND (P_CATEGORYID IS NULL OR EMPM.CATEGORYID=P_CATEGORYID)
AND (P_EMPNO IS NULL OR EMPA.EMPNO = P_EMPNO) AND EMPA.EMPNO=EMPM.EMPNO
GROUP BY EMPM.EMPNO ORDER BY TO_NUMBER(EMPM.EMPNO);
FOR indx IN 1 .. l_employee_nums.COUNT
LOOP
----- (Here is remaining program)
END LOOP; -
Table.Join/Merge in Power Query takes extremly long time to process for big tables
Hi,
I tried to simply merge/inner join two big tables(one has 300,000+ rows after filtering and the other has 30,000+ rows after filtering) in PQ. However, for this simple join operation, PQ took at least 10 minutes (I killed the Query Editor after 10
minutes' processing) to load the preview.
Here's how I did the join job: I first loaded tables into the workbook, then did the filtering for each table and at last, used the merge function to do the join based on a same field.
Did I do anything wrong here? Or is there any way to improve the load efficiency?
P.S. no custom SQL was used during the process. I was hoping the so called "Query Folding" can help speed the process, but it seems it didn't work here.
Thanks.
Regards,
QilongHi!
You should import the source tables
in Access. This will speed up the work of
PQ in several times. -
Very long time to process big table
Hi everyone,
I have a problem with a process that computes 6 columns of a table with 260 millions of rows. At the begining the compute time was about 1.2 mins per row. wich obviously takes more than a life to finish (about 500 years).
So to improve this process naturally my first step was to partition the table. This make 64 partitions with 5 millions rows in the biggest one. My second step was to use a bulk collect with a limit of 500.000 per block, this way i have my array and next step is to compute my columns. So sadly, my first 2 columns just take 2 hours to complete for the 260 millions (Note: I need to compute all rows in the table), but the rest of columns, take 90% of total time or even more. Finally i make a bulk update with forall using the data computed on my arrays.
After all this, the compute time was reduced of 1.2 mins per row to 6 or 7 seconds per row. time wich is great, but just reduced from 500 years to 49 years.
With this scenary, my next logical step is to parallelize my query's, but if a have a degree of 8, my best shot is to take 6 years.
Now, the problem with four of six columns, is that i need to compute some values that requires make some avg and sum over data from last six months previous to the record.
So, here is my real question. ¿how i make this works?... surely i can not wait a lot of years. perhaps the company is broke before this finish.
Which is the professional way to do this real? i think out there companies have tables with lots more of rows, even billions, i have saw in others forums.
I need this, someway, somehow, this takes no more than one or two months... even less is better yet. PLEASE HELP
My DB is a 11G, running on 64bits. 32GB RAM, 6 CPU Quadcore.ok, the objective of the process is to take all the data of six years, wich is in one table only. The table is with nologging, parallel degree 8 and partitioning. and we have to update same table (six columns) and it's values are calculated with data of the same table.
Here is the DDL of the table:
create table MV_DATA_SEC
COD_EMPRESA NUMBER(3),
PERIODO VARCHAR2(6),
ID_CLIENTE VARCHAR2(14),
TIPO_CLIENTE VARCHAR2(1),
NOMBRE VARCHAR2(80),
DIRECCION VARCHAR2(100),
NCONTRATO VARCHAR2(14),
ID_TIPO_NUMERO_CONTRATO NUMBER(1),
FCONTRATO DATE,
FTCONTRATO DATE,
ATIPICA VARCHAR2(2),
SECTOR NUMBER(1),
ID_TIPO_TARIFA NUMBER(2),
ID_TIPO_CONSUMO NUMBER(2),
ID_MEDIDOR VARCHAR2(30),
VOLTAJE NUMBER(6),
KWH NUMBER(10),
LANTERIOR NUMBER(8),
LACTUAL NUMBER(8),
CONSTANTE FLOAT,
ENERGIA NUMBER(8),
LINVIERNO NUMBER(8),
EINVIERNO NUMBER(8),
PINVIERNO NUMBER(8),
PPUNTA NUMBER(8),
DPMAXIMA NUMBER(8),
PBASE NUMBER(8),
PVERANO NUMBER(8),
DPMPUNTA NUMBER(8),
DMLPPUNTA NUMBER(8),
EICINTERNAS FLOAT,
EICEXTERNAS FLOAT,
NDOCUMENTO NUMBER(12),
FDOCUMENTO DATE,
FVENCIMIENTO DATE,
CFIJO NUMBER(10),
CENERGIA NUMBER(10),
CEINVIERNO NUMBER(10),
CPINVIERNO NUMBER(10),
CPBASE NUMBER(10),
CPVERANO NUMBER(10),
CPDMAXIMA NUMBER(10),
CDCMAXIMA NUMBER(10),
CDMPUNTA NUMBER(10),
CRFPOTENCIA NUMBER(10),
CRPTRANS NUMBER(10),
CARRIENDO NUMBER(10),
CSERVICIOS NUMBER(10),
SANTERIOR NUMBER(10),
INTERESES NUMBER(10),
DESCUENTO NUMBER(10),
IVA NUMBER(10),
TOTAL NUMBER(10),
FLANTERIOR DATE,
FLACTUAL DATE,
ID_TIPO_DOCUMENTO VARCHAR2(1),
ID_TIPO_COBRO VARCHAR2(1),
SUBPRIMARIA VARCHAR2(40),
FACTURABLE NUMBER,
FACTURABLE2 NUMBER,
COD_MEDIDOR CHAR(30),
T_LECTURA NUMBER(10),
T_ESTACION CHAR(3),
LIM_INVIERNO NUMBER(10),
E_ADIC_INVIERNO NUMBER(10),
VAL_PROV_CALCULADO NUMBER(10),
PROR_CONSUMO NUMBER(10),
POT_BASE NUMBER(10)
partition by list (PERIODO)
partition PERIODO1 values ('072006')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO2 values ('082006')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO3 values ('092006')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO4 values ('102006')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO5 values ('112006')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO6 values ('122006')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO7 values ('012007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO8 values ('022007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO9 values ('032007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO10 values ('042007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO11 values ('052007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO12 values ('062007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO13 values ('072007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO14 values ('082007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO15 values ('092007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO16 values ('102007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO17 values ('112007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO18 values ('122007')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO19 values ('012008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO20 values ('022008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO21 values ('032008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO22 values ('042008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO23 values ('052008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO24 values ('062008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO25 values ('072008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO26 values ('082008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO27 values ('092008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO28 values ('102008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO29 values ('112008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO30 values ('122008')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO31 values ('012009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO32 values ('022009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO33 values ('032009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO34 values ('042009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO35 values ('052009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO36 values ('062009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO37 values ('072009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO38 values ('082009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO39 values ('092009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO40 values ('102009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO41 values ('112009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO42 values ('122009')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO43 values ('012010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO44 values ('022010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO45 values ('032010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO46 values ('042010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO47 values ('052010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO48 values ('062010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO49 values ('072010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO50 values ('082010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO51 values ('092010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO52 values ('102010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO53 values ('112010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO54 values ('122010')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO55 values ('012011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO56 values ('022011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO57 values ('032011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO58 values ('042011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO59 values ('052011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO60 values ('062011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO61 values ('072011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO62 values ('082011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO63 values ('092011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO64 values ('102011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO65 values ('112011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
partition PERIODO66 values ('122011')
tablespace SEC_SFACTURACION_DAT
pctfree 10
initrans 1
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
-- Create/Recreate indexes
create index IDX_DATA_SEC_EMP2 on MV_DATA_SEC (COD_EMPRESA)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_FACT12 on MV_DATA_SEC (FACTURABLE)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_FACT22 on MV_DATA_SEC (FACTURABLE2)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_FDOC2 on MV_DATA_SEC (FDOCUMENTO)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_MEDI on MV_DATA_SEC (ID_MEDIDOR)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 4096M
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_PER2 on MV_DATA_SEC (PERIODO)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_SUBP2 on MV_DATA_SEC (SUBPRIMARIA)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_TCOB2 on MV_DATA_SEC (ID_TIPO_COBRO)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_TDOC2 on MV_DATA_SEC (ID_TIPO_DOCUMENTO)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
create index IDX_DATA_SEC_TTAR2 on MV_DATA_SEC (ID_TIPO_TARIFA)
tablespace SEC_SFACTURACION_IDX
pctfree 10
initrans 2
maxtrans 255
storage
initial 64K
next 1M
minextents 1
maxextents unlimited
So, first i make a bulk collect.
cursor c_baseData is
select t.lactual, t.lanterior, t.energia, t.rowid, t.periodo, t.t_lectura, t.t_estacion,
t.lim_invierno, t.e_adic_invierno, t.val_prov_calculado, t.pror_consumo, t.pot_base,
t.cod_empresa, t.id_cliente, t.flactual, t.id_medidor, t.facturable, t.id_tipo_cobro,
t.flanterior, t.id_tipo_tarifa
from mv_data_sec t
where id_tipo_documento in ('B','F');
fetch c_baseData bulk collect
into v_lactual, v_lanterior, v_energia, v_rowid, v_periodo, v_lectura, v_estacion,
v_avg_verano_ins, v_ea_invierno_ins, v_val_provisorio, v_Ecalendario, v_potencia_base,
v_cod_empresa, v_id_cliente, v_flactual, v_id_medidor, v_facturable, v_id_tipo_cobro,
v_flanterior, v_id_tipo_tarifa limit 500000;
exit when c_baseData%NOTFOUND;
And i start a LOOP, because i have to process each row. Inside the loop i have to calculate the values for the six columns. We have 2 escenarios.
First one (This one, have no problem, because is calculated with data of the same row and therefore the execution time is lower than a fraction of second);
v_lectura(idx) := case when ((v_lactual(idx)<>v_lanterior(idx)) and v_energia(idx)>0) then 1 else 0 end;
v_estacion(idx) := case when (substr( v_periodo(idx), 1,2) in ('04', '05','06','07','08','09')) then 'I' else 'V' end;
Second One (This take about 1.5 second and the other 3 values takes about same time);
select nvl(avg(facturable),0), max(flactual), max(flanterior), max(lactual), max(lanterior)
into v_facturable_ant, v_flactual_ant, v_flanterior_ant, v_lactual_ant, v_lanterior_ant
from mv_data_sec
where periodo <> v_periodo(idx)
and cod_empresa = v_cod_empresa(idx)
and id_cliente = v_id_cliente(idx)
and id_medidor = v_id_medidor_consulta
and flactual = (select max(flactual)
from mv_data_sec
where cod_empresa = v_cod_empresa(idx)
and id_cliente = id_cliente
and id_medidor = v_id_medidor_consulta
and periodo <> v_periodo(idx)
and flactual < v_flactual(idx));
if ((v_flactual(idx) = v_flanterior(idx)) and (v_flactual_ant <> v_flanterior_ant)) then
v_Ecalendario(idx) := ((v_facturable_ant / (v_flactual_ant - v_flanterior_ant)) * (extract (day from last_day (v_flactual_ant)) - extract (day from (v_flactual_ant))));
end if;
if ((v_flactual_ant = v_flanterior_ant) and (v_flactual(idx) <> v_flanterior(idx))) then
v_Ecalendario(idx) := ((v_facturable(idx)/ (v_flactual(idx) - v_flanterior(idx))) * (extract (day from (v_flactual(idx)))));
end if;
if ((v_flactual(idx) <> v_flanterior(idx)) and (v_flactual_ant <> v_flanterior_ant)) then
v_Ecalendario(idx) := ((v_facturable(idx)/ (v_flactual(idx) - v_flanterior(idx))) * (extract (day from (v_flactual(idx) )))) + ((v_facturable_ant / (v_flactual_ant - v_flanterior_ant)) * (extract (day from last_day (v_flactual_ant)) - extract (day from (v_flactual_ant))));
end if;
And finally the bulk update (time is depreciable), for example the first 2 columns.
forall r in v_rowid.FIRST .. v_rowid.LAST
update mv_data_sec c
set c.t_lectura = v_lectura(r),
c.t_estacion = v_estacion(r)
where c.rowid = v_rowid(r); -
Processing document takes a long time
it takes a very long time to process a document. is anyone else experiencing this?
turns out it got completely stuck for me
-
Message processing taking a too long time
Hi,
I'm sending messages for a external party and a few days ago these messages are getting too long time do process.
Any idea where i can analyse ?
Regards,
GustavoHi Prado,
Request you to check the statistics for few days in Performance monitoring and analyse if the messages are taking long time only for this interface or it is happening for other interfaces as well.
check below link for performance monitoring
SAP PI 7.1 Performance Monitoring
1. if you are facing the issue with only this interface then you need to check the design and and analyse where and in which step it is taking time.
2. if you are facing issue with other interfaces as well then you need to tune the system..here you might need basis team help.
check below link for performance tuning
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70c8bdb7-6fe0-2e10-5b86-a33fdb53ffcd?QuickLink=index&…
Regards,
Naveen -
Data load to DSO takes long time to finish
Dear All,
We have a data load from data source to std DSO.The data load takes 5 hours to complete 6000 records in single data package which is long time.
Process monitor shows yellow status at one of the step for long time "No message :Transformation End" and after 5 hours approx it completes successfully.
Please find the snapshot of process monitor(Attached File Process monitor.png).
There is an end routine and the transformation is having direct mapping except for a target object exchage rate which is master data look up of DSO (Attached FIle : Transformation rule.png)
The look up DSO /BI0/AFIGL_DS00 in the below code is having DOCNUM as a primary key but not the POSKY. Since one of the field is not a primary key,secondary index is created for the look up DSO.But,still it takes huge time to finish the last step as mentioned in the snapshot.
Setting for parallel process is 1
DTP--> Update tab-->Error handling-->No update,no reporting.But there is a error DTP present which I believe that there is no use when "No update,No reporting" option is chosen.
Can you please suggest the reason for the such long time.Also,Please suggest how to find the exact place where it consumes lot of time.
End routine Logic:
IF NOT RESULT_PACKAGE IS INITIAL.
REFRESH IT_FIG.
SELECT DOCNUM POSKY DEBCRE LOCC
FROM /BI0/AFIGL_DS00 INTO TABLE IT_FIG
FOR ALL ENTRIES IN RESULT_PACKAGE
WHERE DOCNUM = RESULT_PACKAGE-BILNO AND
POSKY = '02'.
LOOP AT RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
READ TABLE IT_FIG INTO WA_FIG WITH KEY
DOCNUM = <RESULT_FIELDS>-BILNO.
IF SY-SUBRC EQ 0.
<RESULT_FIELDS>-DEB = WA_FIG-DEBCRE.
<RESULT_FIELDS>-LOC_CURRC2 = WA_FIG-LOCC.
ENDIF.
ENDLOOP.
ENDIF.
Thanks in advance
Regards
PradeepHi,
below code check it and try to load the data.
IF RESULT_PACKAGE IS NOT INITIAL.
SELECT DOCNUM
POSKY
DEBCRE
LOCC
FROM /BI0/AFIGL_DS00 INTO TABLE IT_FIG
FOR ALL ENTRIES IN RESULT_PACKAGE
WHERE DOCNUM = RESULT_PACKAGE-BILNO AND
POSKY = '02'.
LOOP AT RESULT_PACKAGE ASSIGNING <RESULT_FIELDS>.
READ TABLE IT_FIG INTO WA_FIG WITH KEY
DOCNUM = <RESULT_FIELDS>-BILNO.
IF SY-SUBRC EQ 0.
<RESULT_FIELDS>-DEB = WA_DOCNUM.
<RESULT_FIELDS>-DEB = WA_POSKY.
<RESULT_FIELDS>-DEB = WA_FIG-DEBCRE.
<RESULT_FIELDS>-LOC_CURRC2 = WA_FIG-LOCC.
ENDIF.
ENDLOOP.
ENDIF.
if your are getting any error please let us know
1.decrease the data packet size in DTP like 10,000 or 20,000.
2.increase the parallel process at DTP level.
Thanks,
Phani. -
Long time taken to fetch data from Database Table
Moved to correct forum by moderator.
I had a requirement where i need to fetch records from table A912 for the matching entries in an internal table and satisfying some conditions.
The Internal Table(it_out) has 1,206 entries, while Databse table(A912) has 9,758,234 entries.
The Structure of Internal Table and Select Query are,
TYPES : BEGIN OF ty_a912,
matnr LIKE a912-matnr, "Material
kunwe LIKE a912-kunwe, "Ship-to party
datbi LIKE a912-datbi, "Validity end dt
datab LIKE a912-datab, "Validity start
knumh LIKE a912-knumh, "Cond rec no.
END OF ty_a912.
TYPES : BEGIN OF ty_out,
erdat LIKE vbak-erdat, "Date
vbeln LIKE vbak-vbeln, "Sales document
posnr LIKE vbap-posnr, "Item
kunnr LIKE vbpa-kunnr, "Customer
fkdat LIKE vbkd-fkdat, "Billing Date
ndc LIKE zndc-zndc, "EAN/UPC
matnr LIKE vbap-matnr, "Material
zr00p LIKE konv-kbetr, "ZR00 Price
zcarp LIKE konv-kbetr, "ZCAR Price
zrfcp LIKE konv-kbetr, "ZRFC Price
ctrnr TYPE char80, "Contract#
ctrnm TYPE char80, "Contract Name
a912p TYPE konv-kbetr,
END OF ty_out.
SELECT
matnr kunwe datbi datab knumh
FROM a912
INTO TABLE t_a912
FOR ALL ENTRIES IN t_out
WHERE matnr EQ t_out-matnr
AND kunwe EQ t_out-kunnr
AND datbi GE t_out-fkdat
AND datab LE t_out-fkdat.
It takes very long time to process this select query, is there any alternate way?
Please suggest some valid solution for this issue.
Edited by: Matt on Dec 3, 2008 10:08 AMPrabhakar Manoharan wrote:>
> Moved to correct forum by moderator.
>
> I had a requirement where i need to fetch records from table A912 for the matching entries in an internal table and satisfying some conditions.
> The Internal Table(it_out) has 1,206 entries, while Databse table(A912) has 9,758,234 entries.
>
Hi,
can you give us an SQL trace in ST05? The SQL Trace (ST05) Quick and Easy
The FAE will be processed in a special way: see https://forums.sdn.sap.com/click.jspa?searchID=-1&messageID=6630311
If an index is NOT supported the FAE part will take forever...
if t_out is filled by another table you may go for a join? But again, index support is the key
bye
yk
Edited by: YukonKid on Dec 4, 2008 10:31 AM -
Configuration command take long time to display
When I shutdown the primary ACS service, the authentication and accounting take a long time to process. Is it normal? Whenever new command is enter, it take sometime to display after the command authorization. The time toke almost the same as timeout configure.
The primary ACS is working fine without any delay if it's up and running.
Anything that I can do to fine tune?
Here are the configuration that I have :
aaa new-model
aaa group server tacacs+ ACSSE
server-private 192.168.128.28 key abcacs01
server-private 192.168.136.35 key abcacs01
ip tacacs source-interface bvi1
aaa authentication login default group ACSSE line
aaa authentication enable default enable
aaa authorization exec default group ACSSE if-authenticated
aaa authorization commands 15 default group ACSSE if-authenticated
aaa authorization config-commands
aaa accounting update newinfo
aaa accounting exec default start-stop group ACSSE
aaa accounting commands 15 default start-stop group ACSSE
aaa accounting connection default start-stop group ACSSE
aaa accounting system default start-stop group ACSSE
tacacs-server timeout 10
The software version :
c2800nm-adventerprisek9-mz.124-11.T3.binChee
Your description of the issue sounds like your router is sending its request to the first TACACS sever and is waiting for a response but it does not receive a response. So it waits for the timeout and when the first request times out it sends the request to the second server.
If the router received an immediate answer or if it could not establish a connection to the primary server then you would not have the delay. You might be able to confirm this by running debug tacacs authentication or debug tacacs accounting. I believe that you will see your router send a request to the primary and then not receive a response (or it may receive some response which it does not interpret as not available).
If you want to tune this you could adjust the timeout value to a shorter value. But I believe that a better solution would be to figure out why the server is not sending any response.
HTH
Rick
Maybe you are looking for
-
The mail application on my I-Mac dates all emails, in or out, as 5th (of whatever month it is). It seems to get the time right. The computer clock is fine. I have no problem with my MacBook - just with the I-Mac. Any ideas, please?
-
I installed a second hard drive to my Mac Mini. After installing the operation system on it the mac will boot up on the second hard drive. How do switch back to the first drive? Thank you.
-
URGENT: Rest web service with get method works fine in browser but not with java client(Android)
Hi , I have created one REST web service which accepts two parameters send back JSON results. I tested the it in browser with URL as http://+Inteernal server+/ords/utimes/login_info?p1=+first_param+&p2=+second_para+ Web service URL : http://+Inteern
-
LDAP network users/automount points doesn't work after power failure
Hi, I have a lab of about a dozen Mac Mini clients that boot to their own local HDs and pull their user accounts from a MacPro tower running Mac OS X Server 10.4.9. Last week there was a power outage. The power was restored a couple hours later, but
-
Getting ORA-06512: at "APPS.FND_MSG_PUB", line 279 error in Oracle Sourcing
Hi, We have recently applied Sourcing Rollup 2 J patch in our instance. After this, when the users change their timezone, the system behaves weirdly. The Server timezone and Client timezone are set to Dubai timezone (GMT+4) at site level. If the user