Gc quiesce wait event on creating an index

Hi,
We're running Oracle 10.2.0.3 in a 2-node RAC.
Today we encountered something strange:
On creating an index on an empty table the session ended up in the 'waiting' state. The event was: 'gc quiesce wait'.
In an attempt to solve it we stopped 1 instance. This didn't help a bit.
Killing the session and restarting the index creation had the same result.
Eventually we bounced the database and then things went fine.
Can anyone explain what might have caused this? I've tried to find an explanation on the internet but can’t really find anything on this wait event.
I’m a newbie on RAC and would like to learn from this…
Regards,
René

Mladen Gogala wrote once:
To "quiesce" database means to suspend it for a brief period of time.
In RAC context, GC quiesce probably means to quiesce a resource Database.
This is an educated guess, only. If this table is heavily in use,
the instance you're inserting into may be pulling huge numbers of
blocks from the other nodes and becoming their master. You are waiting
for remastering. Make sure that all inserts are being done on the same
instance.
Look at the list of bugs in the heavenly patchset, the one that will be
released week after the judgment day, 10.2.0.4. The list of bug fixes is
available in the doc id: 401436.1.
Also, dump systemstate, level 12 when you observe such waits, send it to
Oracle Corp. and work with them. Using HANGANALYZE might not be a bad idea
in this situation.
K. Gopalakrishnan, the author of the RAC book might be having to say about
that, as well. I don't have his book right here and I can't look into it.
I looked into Gopal and Kirti's "Oracle10g Wait Event" book, but there is
nothing in there.
Mladen Gogala
http://mgogala.freehostia.com

Similar Messages

Wait Events "log file parallel write" / "log file sync" during CREATE INDEX

Hello guys,
at my current project i am performing some performance tests for oracle data guard. The question is "How does a LGWR SYNC transfer influences the system performance?"
To get some performance values, that i can compare i just built up a normal oracle database in the first step.
Now i am performing different tests like creating "large" indexes, massive parallel inserts/commits, etc. to get the bench mark.
My database is an oracle 10.2.0.4 with multiplexed redo log files on AIX.
I am creating an index on a "normal" table .. i execute "dbms_workload_repository.create_snapshot()" before and after the CREATE INDEX to get an equivalent timeframe for the AWR report.
After the index is built up (round about 9 GB) i perform an awrrpt.sql to get the AWR report.
And now take a look at these values from the AWR
                                                                   Avg
                                             %Time Total Wait    wait     Waits
Event                                 Waits -outs    Time (s)    (ms)      /txn
log file parallel write              10,019     .0         132      13      33.5
log file sync                           293     .7           4      15       1.0
......How can this be possible?
Regarding to the documentation
-> log file sync: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3120
Wait Time: The wait time includes the writing of the log buffer and the post.-> log file parallel write: http://download.oracle.com/docs/cd/B19306_01/server.102/b14237/waitevents003.htm#sthref3104
Wait Time: Time it takes for the I/Os to complete. Even though redo records are written in parallel, the parallel write is not complete until the last I/O is on disk.This was also my understanding .. the "log file sync" wait time should be higher than the "log file parallel write" wait time, because of it includes the I/O and the response time to the user session.
I could accept it, if the values are close to each other (maybe round about 1 second in total) .. but the different between 132 seconds and 4 seconds is too noticeable.
Is the behavior of the log file sync/write different when performing a DDL like CREATE INDEX (maybe async .. like you can influence it with the initialization parameter COMMIT_WRITE??)?
Do you have any idea how these values come about?
Any thoughts/ideas are welcome.
Thanks and Regards

Surachart Opun (HunterX) wrote:
Thank you for Nice Idea.
In this case, How can we reduce "log file parallel write" and "log file sync" waited time?
CREATE INDEX with NOLOGGINGA NOLOGGING can help, can't it?Yes - if you create index nologging then you wouldn't be generating that 10GB of redo log, so the waits would disappear.
Two points on nologging, though:
<ul>
it's "only" an index, so you could always rebuild it in the event of media corruption, but if you had lots of indexes created nologging this might cause an unreasonable delay before the system was usable again - so you should decide on a fallback option, such as taking a new backup of the tablespace as soon as all the nologging operatons had completed.
If the database, or that tablespace, is in +"force logging"+ mode, the nologging will not work.
</ul>
Don't get too alarmed by the waits, though. My guess is that the +"log file sync"+ waits are mostly from other sessions, and since there aren't many of them the other sessions are probably not seeing a performance issue. The +"log file parallel write"+ waits are caused by your create index, but they are happeninng to lgwr in the background which is running concurrently with your session - so your session is not (directly) affected by them, so may not be seeing a performance issue.
The other sessions are seeing relatively high sync times because their log file syncs have to wait for one of the large writes that you have triggered to complete, and then the logwriter includes their (little) writes with your next (large) write.
There may be a performance impact, though, from the pure volume of I/O. Apart from the I/O to write the index you have LGWR writting (N copies) of the redo for the index and ARCH is reading and writing the completed log files caused by the index build. So the 9GB of index could easily be responsible for vastly more I/O than the initial 9GB.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
To post code, statspack/AWR report, execution plans or trace files, start and end the section with the tag {noformat}{noformat} (lowercase, curly brackets, no spaces) so that the text appears in fixed format.
"Science is more than a body of knowledge; it is a way of thinking"
Carl Sagan

Library Cache Pin Wait Event (within the context of APEX)

Hello,
Firstly -
Oracle Version: 10.2.0.4.0
Apex Version: 3.0.1.00.08
Okay, my colleague (no really! This isn't one of those "Ahem ... A friend of mine has contracted something nasty +downstairs+..."-type questions) is having problems compiling a package (using TOAD incidentally, but it's the same in SQL Developer).
I've searched the forum and the web for a bit of help on what's maybe happening here and it appears to be related to a concurrency conflict with the package definition - from what I can understand it's a case of the package is in use by another session, therefore another session cannot alter it at the same time (which makes sense)
"What does this have to do with APEX?"... well, he is working on this package using the following methodology:
1. Compile the package body/spec (as necessary - body more often obviously)
2. run an apex page which uses the code in a process, which may or may not result in the error page being displayed
3. Making changes to the package body/spec
repeat steps 1-3 ad nauseum...
He is the only user directly accessing the schema (and the only user accessing the page via APEX too, although I appreciate this isn't quite the same thing).
I was wondering if, due to the architecture of APEX (the use of session pools etc), the state of a package might be being retained in some manner, thus resulting in this library cache pin wait event? If so, is there anything I can do to mitigate against this occurring?
p.s. the only difference I can see between this particular package and any other package in the schema is that this one interacts with blobs (including making references to the wwv_flow_files view) - with blobs being passed as parameters between procedures (thus potentially creating temporary blobs which may or may not being closed).
Any ideas?
p.p.s. there are also no DBMS_SCHEDULER jobs or anything that might potentially be running the code incidentally...
Edited by: Joel_C on 11-Nov-2011 11:58
We got our DBAs to run a bit of code to identify the blocking session:
select
         decode(lob.kglobtyp, 0, 'NEXT OBJECT', 1, 'INDEX', 2, 'TABLE', 3, 'CLUSTER',
                      4, 'VIEW', 5, 'SYNONYM', 6, 'SEQUENCE',
                      7, 'PROCEDURE', 8, 'FUNCTION', 9, 'PACKAGE',
                      11, 'PACKAGE BODY', 12, 'TRIGGER',
                      13, 'TYPE', 14, 'TYPE BODY',
                      19, 'TABLE PARTITION', 20, 'INDEX PARTITION', 21, 'LOB',
                      22, 'LIBRARY', 23, 'DIRECTORY', 24, 'QUEUE',
                      28, 'JAVA SOURCE', 29, 'JAVA CLASS', 30, 'JAVA RESOURCE',
                      32, 'INDEXTYPE', 33, 'OPERATOR',
                      34, 'TABLE SUBPARTITION', 35, 'INDEX SUBPARTITION',
                      40, 'LOB PARTITION', 41, 'LOB SUBPARTITION',
                      42, 'MATERIALIZED VIEW',
                      43, 'DIMENSION',
                      44, 'CONTEXT', 46, 'RULE SET', 47, 'RESOURCE PLAN',
                      48, 'CONSUMER GROUP',
                      51, 'SUBSCRIPTION', 52, 'LOCATION',
                      55, 'XML SCHEMA', 56, 'JAVA DATA',
                      57, 'SECURITY PROFILE', 59, 'RULE',
                      62, 'EVALUATION CONTEXT',
                     'UNDEFINED') object_type,
         lob.KGLNAOBJ object_name,
         pn.KGLPNMOD lock_mode_held,
         pn.KGLPNREQ lock_mode_requested,
         ses.sid,
         ses.serial#,
         ses.username
    FROM
       x$kglpn pn,
       v$session ses,
       x$kglob lob,
       v$session_wait vsw
WHERE
   pn.KGLPNUSE = ses.saddr and
   pn.KGLPNHDL = lob.KGLHDADR
   and lob.kglhdadr = vsw.p1raw
   and vsw.event = 'library cache pin'
order by lock_mode_held descresults as follows (I've changed some object names to protect the ignorant):
OBJECT_TYP OBJECT_NAME                   LOCK_MODE_HELD LOCK_MODE_REQUESTED        SID    SERIAL# USERNAME
PACKAGE    PKG_FOOBAR                             2                   0        356      21694 HTMLDB_PUBLIC_U
                                                                                                  SER
PACKAGE    PKG_FOOBAR                             0                   3        463      22309 FOOHTMLDB_PUBLIC_USER is the apex user incidentally. The session is marked in the v$session table as "inactive", the last statement being
Begin
   Dbms_session.reset_package;
End;Edited by: Joel_C on 11-Nov-2011 14:39

bump
No-one?
The problem seems to have 'resolved itself' over the weekend incidentally (although I don't believe anything truly resolves itself in this manner - something must have changed).

Tuning row lock contention wait events

Hello everyone,
Working on 10g/windows
Top 5 events
EVENT TOTAL_WAITS TIME_WAITED AVG_MS PERCENT
CPU 9462339 48
enq: TX - row lock contention 12531 3660728 2921.34 18
control file parallel write 1300731 3088079 23.74 16
log file parallel write 1510503 1264080 8.37 6
log file sync 1072553 968007 9.03 5
Distribution of row lock wait during the last 4 days in the database server
END_INTERVAL_TIME TOTAL_WAITS TIME_WAITED_MICRO AVG_WAIT_MS
2008-04-01 16:00:58 909 2721008230 2993.41
2008-04-01 15:00:27 50 149941140 2998.82
2008-03-31 12:00:42 193 575595397 2982.36
2008-03-29 23:00:13 172 513058700 2982.9
2008-03-29 22:00:37 164 483940046 2950.85
2008-03-27 22:00:35 565 1667120838 2950.66
2008-03-26 18:00:59 348 1042918982 2996.89
My analysis:
It's obvious that the row lock contention wait time is huge, and this direct me to find out SQL stmt, causing this.
all the SQL statement was SELECT ....... FOR UPDATE stmt.
I was also able to find out locked tables.
My tuning idea:
1. I'm thinking to reorganize hot tables as well as their indexes, but by instinct it seems to not give so much value to avoid the huge row lock wait time.
2. I'm also seeing if I can reduce the number of rows per block, by increasing PCTFREE and diminishing PCTUSED, so the contention will spread over many blocks instead of one heavy block.
Question
As SQL stmt related to those locked tables are select ... for update, how could I tune this kind of stmt?
Does someone have other idea to come up with this row lock contention?
Tanks for your effort and help

Taking another look at your suggested function based index, it depends on the data type of the DEV.POS_FOLIO_ID.POS_FOLIO_ID column. If the column is defined as a number, and it is a primary key, there will already be a usable index on that column.
Yesterday, I wrote this: "Once I understood why or how the sessions were trying to insert duplicate primary key values, I would try to determine why the average number of seconds for the wait event is almost 3 seconds (maybe a timeout)."
After fixing the formatting of the top 5 wait events (total duration unknown):
EVENT                        TOTAL_WAITS TIME_WAITED   AVG_MS PERCENT
CPU                                         94,623.39             48
enq: TX - row lock contention     12,531    36,607.28 2921.34    18
control file parallel write    1,300,731    30,880.79    23.74    16
log file parallel write        1,510,503    12,640.80     8.37     6
log file sync                  1,072,553     9,680.07     9.03     512,531 * 3 second time out = 37,593 seconds = 10.44 hours.
What if the reason for the 3 second average wait time is due to a timeout. I performed a little experiment... I changed a row in a test table and then made a pot of coffee.
In session 1:
CREATE TABLE T1 (
C1 NUMBER(10),
C2 NUMBER(10),
PRIMARY KEY (C1));
INSERT INTO T1
SELECT
ROWNUM,
ROWNUM*10
FROM
DUAL
CONNECT BY
LEVEL<=1000000;
COMMIT;I now have a test table with 1,000,000 rows. I start monitoring the changes in the wait events roughly every 60 seconds, and V$SESSION_WAIT and V$LOCK roughly 4 times per second.
Back in session 1:
UPDATE
T1
SET
C1=-C1
WHERE
C1<=100;I have now modified the first 100 rows that were inserted into the table, time to make the pot of coffee.
In session 2, I try to insert a row with a primary key value of -10:
INSERT INTO T1 VALUES (
-10,
10);Session 2 hangs.
If I take the third 60 second snap of the system wide wait events as the zero point, and the 11th snap as the end point. There were 149 waits on ENQ: TX - ROW LOCK CONTENTION, 148 time outs, 446.62 seconds of total time in the wait event, with an average wait time of 2.997450 seconds.
Rolling down to the session level wait events, SID 208 (my session 2) had 149 waits on ENQ: TX - ROW LOCK CONTENTION, for a total time of 446.61 seconds with an average wait time of 2.997383 seconds. All of the 149 waits and the wait time was in this one session that was locked up for the full duration of this time period because session 1 was making a pot of coffee.
Rolling down to V$SESSION_WAIT (sampled roughly 4 times per second): At the start of the third time interval, SID 208 has been in the ENQ: TX - ROW LOCK CONTENTION wait event for 39 seconds and is actively waiting trying to execute SQL with a hash value of 1001532423, the wait object is -1, wait file is 0, wait block is 0, wait row is 0, P1 is 1415053316, P2 is 196646, P3 is 4754.
At the end of the 11th time interval: , SID 208 has been in the ENQ: TX - ROW LOCK CONTENTION wait event for 483 seconds and is actively waiting trying to execute SQL with a hash value of 1001532423, the wait object is -1, wait file is 0, wait block is 0, wait row is 0, P1 is 1415053316, P2 is 196646, P3 is 4754.
Rolling down to V$LOCK (sampled roughly 4 times per second): I see that SID 214 (session 1) is blocking SID 208 (session 2). SID 214 has a TX lock in mode 6 with ID1 of 196646 and ID2 of 4754. SID 208 is requesting a TX lock in mode 4 with ID1 of 196646 and ID2 of 4754.
So, it seems that I need a faster coffee pot rather than an additional index on my table. It could be that the above process would have found that the application associated with SID 214 was abandoned or crashed and for some reason the lock was not released for a long period of time, a little less than 10.44 hours in your case.
Charles Hooper
IT Manager/Oracle DBA
K&M Machine-Fabricating, Inc.

Wait event problem

I have problem with enq: TM – contention wait events.
From ASH report in Top Event P1/P2/P3 I find problematic object – table T1. It has two columns C1 and C2. There are PK and FK constraints on these two columns.Table T1 has one UNIQUE INDEX - index_name(C1, C2).
With this:
SELECT * FROM (
SELECT c.table_name, cc.column_name, cc.position column_position
FROM   user_constraints c, user_cons_columns cc
WHERE c.constraint_name = cc.constraint_name
AND    c.constraint_type = 'R'
MINUS
SELECT i.table_name, ic.column_name, ic.column_position
FROM   user_indexes i, user_ind_columns ic
WHERE i.index_name = ic.index_name
+)+
ORDER BY table_name, column_position;
I find unindexed Foreign Key constraints, and show me that no index on C2 column.
Can I create new index on this C2 column: CREATE INDEX index_name_c2 ON T1(C2) because I have index on C1 and C2 columns ?
In ASH report in Top DB Objects I see another indexes and table with enq: TM – contention event. Whey Oracle show me this objects?

Based on what you've written I see nothing that should stop you from creating an index but I would recommend you do so in dev or test before production.
As to why Oracle is showing it to you? Likely because it thinks there is a potential issue there.
Remember always that the best designed database in the world is going to have a top 5 or top 10 list too. The only way to not have events reported is with shutdown abort.

Workflow error in fork step, process control, wait event

I am using fork step in workflow which has 2 parallel branches. In 1st branch i have a user decision step followed by a task for posting PO document in case of approval. In the 2nd branch of fork step I have a wait step to wait for an event followed by the same task for posting document with a process control step after that in the end to cancel the workitem(workitem generated by user decision step in the 1st branch of fork). I created the event by using a custom BOR object.
After the fork step is triggered, i have both a wait event running and workitem generated. When i raise the wait event from SWUE by entering the event, object key etc it works fine i.e., the workitem in the other branch is set of logically deleted and workflow ends.
But if the wait event is triggered from the program i.e., using FM SWW_WI_CREATE_VIA_EVENT, both get an error message in workflow log(SWIA). The message is: Error when executing the binding between work item 000000XXXXXX and flow item 000000XXXXXX where workitem number is the workitem id of the posting document task and flow item id is the workflow parent id

hi,
message is self explanatory.
Activate the event trace SWELS, then do the event with SWUE and within your program (als please use SAP_WAPI function modules).
Now compare the 2 events in SWEL to see what the differences are .
Kind regards, Rob Dielemans

Wait events - how to read it

Hi frnds,
As, I'm beginner to performance tuning I dont know
What action do i need to take?
I mean how to read the output which I given below.
this is the output suffering buffer busy waits.
Could anyone please tell me
CLASS TOTAL_WAITS TOTAL_TIME
data block 93303 58711
unused 0 0
system undo header 12 232
undo header 7847 6636
3rd level bmb 0 0
save undo header 0 0
bitmap index block 0 0
file header block 0 0
free list 0 0
undo block 68 207
segment header 422 399
extent map 0 0
2nd level bmb 0 0
system undo block 0 0
sort block 0 0
save undo block 0 0
1st level bmb 1 17
bitmap block 0 0
Thanks, Muhammed Thameem. S

Hello,
"Buffer busy waits" is contention for a buffer (representing a specific
version of a database block) within the Buffer Cache. So, in essence
it is block contention and thus it is most likely something to do with
the design of the tables and indexes supporting the application. A
built-in bottleneck. On indexes, it could be the age-old problem of
insertions into an index on a column with a monotonically-ascending
data value (i.e. timestamps or sequence numbers) which tends to cause
contention on the highest leaf node of the index. On tables, it might
have to do with many concurrent insertions into a table in a
freelist-managed tablespace where the table has only one freelist. It
could also be due to a home-grown implementation of sequence-number
generators (i.e. small table with one row, one column in which contains
the "last value" of a sequence, etc) which lots of people use to avoid
not being "portable across databases" which they think means not using
Oracle sequences (yadda yadda yadda).
I'd look for any SQL statement in the "SQL sorted by Elapsed Time"
section of the AWR report which exhibits high elapsed time but
relatively low CPU time, indicating a lot of wait time. Of course,
there are something like 800 possible wait events in current releases
of Oracle, of which "buffer busy waits" is only one, so this is just
inference and not a direct causal connection to your problem. But,
once I find such statements I'd check to see if they are
accessing/manipulating tables within the CUBS_DATA tablespace, and then
use "select * from table(dbms_xplan.display_awr('sql-id'))" to
get the execution plan(s), and then look for something ineffective
within the execution plan. You might find the script "sqlhistory.sql" helpful
here as well, to get a "historical perspective" on the execution of the
SQL statements over time, in case the buffer busy waits peaked at some
point in the past
Please refer to:
http://www.pubbs.net/201003/oracle/51925-understanding-awr-buffer-waits.html
Also
http://www.remote-dba.net/oracle_10g_tuning/t_buffer_busy_waits.htm
kind regards
Mohamed

Enq: TX - row lock contention in TOP 5 wait event

DB version:11.1.0.7.0
I am having enq: TX - row lock contention in top 5 wait event.
AWR analyze period - 9-10(pm). During this time only one sql loader is running to insert the data. No other job are running. So there is no chance of other session blocking this session. is there any chance of row lock contention happen by same session.
SQL> SELECT INDEX_NAME,INDEX_TYPE,UNIQUENESS FROM DBA_INDEXES WHERE TABLE_NAME='DATA_DATA';
INDEX_NAME INDEX_TYPE UNIQUENES
CIDX BITMAP NONUNIQUE
VIDX BITMAP NONUNIQUE
Thanks.

SQL> SELECT INDEX_NAME,INDEX_TYPE,UNIQUENESS FROM DBA_INDEXES WHERE TABLE_NAME='DATA_DATA';
INDEX_NAME INDEX_TYPE UNIQUENES
CIDX BITMAP NONUNIQUE
VIDX BITMAP NONUNIQUEYou have bitmap indexes here on a table being inserted into. Bitmap Indexes are another source of lock(and deadlock) in OLTP application. You said that the SQLloader was the unique active program but may be you are also triggering another procedure after the load. Procedure in which you might be using also automomous transactions and so on...
Check first if your table is subject to DML operation in a a multi-user concurrent accesss and in which case you have to get rid of those bitmap indexes
http://hourim.wordpress.com/2011/03/14/deadlock-%e2%80%93-part-1-bitmap-index/
Best regards
Mohamed Houri
www.hourim.wordpress.com

Find the Wait events for an objects.

Hi Gurus.
I need you help to find out the wait events for a particular table and index when batch export job running from the application. I have done some work around to to find out, but i am not able to figure out the issue or what are the wait events. i am working on linux 4node rac 11gR2.
Below are the steps i have done.
1. find object_id for a table finding the wait events to that object_id.
SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='ACCOUNT_DETAIL_DENORM';
DATA_OBJECT_ID
82646
88518
84184
SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=82646;
no rows selected
SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=88518;
no rows selected
SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=84184;
no rows selected
2. find the object id for the index of that table and finding the wait events to that object_id.
SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='XAK2ACCOUNT_DETAIL_DENORM';
DATA_OBJECT_ID
88655
SID EVENT WAIT_CLASS WAIT_CLASS#
1 rdbms ipc message Idle 6
2 heartbeat monitor sleep Idle 6
3 rdbms ipc message Idle 6
4 wait for unread message on broadcast channel Idle 6
6 SQL*Net message from client Idle 6
7 SQL*Net message from client Idle 6
8 SQL*Net message from client Idle 6
9 SQL*Net message from client Idle 6
10 SQL*Net message from client Idle 6
11 SQL*Net message from client Idle 6
12 SQL*Net message from client Idle 6
13 SQL*Net message from client Idle 6
1876 SQL*Net message from client Idle 6
1877 VKTM Logical Idle Wait Idle 6
1878 rdbms ipc message Idle 6
1879 rdbms ipc message Idle 6
1880 rdbms ipc message Idle 6
1881 SQL*Net message from client Idle 6
3200 SQL*Net message from client Idle 6
3210 SQL*Net message from client Idle 6
3212 db file sequential read User I/O 8
3213 SQL*Net message from client Idle 6
3214 SQL*Net message from client Idle 6
3216 SQL*Net message from client Idle 6
3751 rdbms ipc message Idle 6
3752 gcs remote message Idle 6
3754 rdbms ipc message Idle 6
3756 SQL*Net message from client Idle 6
3757 SQL*Net message from client Idle 6
1326 SQL*Net message from client Idle 6
1876 Streams AQ: waiting for time management or cleanup tasks Idle 6
1877 VKTM Logical Idle Wait Idle 6
1878 rdbms ipc message Idle 6
1879 rdbms ipc message Idle 6
1880 rdbms ipc message Idle 6
1882 SQL*Net message from client Idle 6
3751 rdbms ipc message Idle 6
3752 gcs remote message Idle 6
3754 rdbms ipc message Idle 6
3756 rdbms ipc message Idle 6
3758 SQL*Net message from client Idle 6
3759 PX Deq: Execution Msg Idle 6
3200 SQL*Net message from client Idle 6
3210 SQL*Net message from client Idle 6
3212 db file sequential read User I/O 8
3213 SQL*Net message from client Idle 6
3214 SQL*Net message from client Idle 6
3216 SQL*Net message from client Idle 6
3751 rdbms ipc message Idle 6
3752 gcs remote message Idle 6
3754 rdbms ipc message Idle 6
3756 SQL*Net message from client Idle 6
3757 SQL*Net message from client Idle 6
3786 SQL*Net message from client Idle 6
3787 SQL*Net message from client Idle 6
1 heartbeat monitor sleep Idle 6
2 wait for unread message on broadcast channel Idle 6
314 rdbms ipc message Idle 6
315 Streams AQ: qmn coordinator idle wait Idle 6
627 pmon timer Idle 6
628 rdbms ipc message Idle 6
629 Streams AQ: waiting for messages in the queue Idle 6
940 Streams AQ: waiting for time management or cleanup tasks Idle 6
941 VKTM Logical Idle Wait Idle 6
942 rdbms ipc message Idle 6
1253 rdbms ipc message Idle 6
1254 rdbms ipc message Idle 6
1256 Space Manager: slave idle wait Idle 6
1566 DIAG idle wait Idle 6
1567 rdbms ipc message Idle 6
1568 Streams AQ: qmn slave idle wait Idle 6
1879 rdbms ipc message Idle 6
1880 smon timer Idle 6
1881 rdbms ipc message Idle 6
2192 PING Idle 6
2193 rdbms ipc message Idle 6
2194 rdbms ipc message Idle 6
2505 rdbms ipc message Idle 6
2506 rdbms ipc message Idle 6
2818 rdbms ipc message Idle 6
2819 rdbms ipc message Idle 6
2821 PX Deq: reap credit Other 0
3131 DIAG idle wait Idle 6
3132 jobq slave wait Idle 6
3444 rdbms ipc message Idle 6
3445 jobq slave wait Idle 6
3757 ges remote message Idle 6
3758 rdbms ipc message Idle 6
3759 VKRM Idle Idle 6
4070 gcs remote message Idle 6
4072 rdbms ipc message Idle 6
4383 gcs remote message Idle 6
4385 PX Deq: Execution Msg Idle 6
4696 rdbms ipc message Idle 6
4697 rdbms ipc message Idle 6
1 rdbms ipc message Idle 6
2 heartbeat monitor sleep Idle 6
3 rdbms ipc message Idle 6
4 wait for unread message on broadcast channel Idle 6
6 SQL*Net message from client Idle 6
From this output, what are the waits events i need to take into consideration.
Is this the right approach to follow?
Please let me know.
Thanks in advance.

user13162661 wrote:
Hi Gurus.
I need you help to find out the wait events for a particular table and index when batch export job running from the application. I have done some work around to to find out, but i am not able to figure out the issue or what are the wait events. i am working on linux 4node rac 11gR2.
Below are the steps i have done.
1. find object_id for a table finding the wait events to that object_id.
SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='ACCOUNT_DETAIL_DENORM';
DATA_OBJECT_ID
82646
88518
84184
SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=82646;
no rows selected
SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=88518;
no rows selected
SYS@ccmintpt1 SQL>select w.sid,w.event,w.wait_class,w.wait_class# from gv$session s,gv$session_wait w where s.row_wait_obj#=84184;
no rows selected
2. find the object id for the index of that table and finding the wait events to that object_id.
SYS@ccmintpt1 SQL>select data_object_id from dba_objects where object_name='XAK2ACCOUNT_DETAIL_DENORM';
DATA_OBJECT_ID
88655
SID EVENT WAIT_CLASS WAIT_CLASS#
1 rdbms ipc message Idle 6
2 heartbeat monitor sleep Idle 6
3 rdbms ipc message Idle 6
4 wait for unread message on broadcast channel Idle 6
6 SQL*Net message from client Idle 6
7 SQL*Net message from client Idle 6
8 SQL*Net message from client Idle 6
9 SQL*Net message from client Idle 6
10 SQL*Net message from client Idle 6
11 SQL*Net message from client Idle 6
12 SQL*Net message from client Idle 6
13 SQL*Net message from client Idle 6
1876 SQL*Net message from client Idle 6
1877 VKTM Logical Idle Wait Idle 6
1878 rdbms ipc message Idle 6
1879 rdbms ipc message Idle 6
1880 rdbms ipc message Idle 6
1881 SQL*Net message from client Idle 6
3200 SQL*Net message from client Idle 6
3210 SQL*Net message from client Idle 6
3212 db file sequential read User I/O 8
3213 SQL*Net message from client Idle 6
3214 SQL*Net message from client Idle 6
3216 SQL*Net message from client Idle 6
3751 rdbms ipc message Idle 6
3752 gcs remote message Idle 6
3754 rdbms ipc message Idle 6
3756 SQL*Net message from client Idle 6
3757 SQL*Net message from client Idle 6
1326 SQL*Net message from client Idle 6
1876 Streams AQ: waiting for time management or cleanup tasks Idle 6
1877 VKTM Logical Idle Wait Idle 6
1878 rdbms ipc message Idle 6
1879 rdbms ipc message Idle 6
1880 rdbms ipc message Idle 6
1882 SQL*Net message from client Idle 6
3751 rdbms ipc message Idle 6
3752 gcs remote message Idle 6
3754 rdbms ipc message Idle 6
3756 rdbms ipc message Idle 6
3758 SQL*Net message from client Idle 6
3759 PX Deq: Execution Msg Idle 6
3200 SQL*Net message from client Idle 6
3210 SQL*Net message from client Idle 6
3212 db file sequential read User I/O 8
3213 SQL*Net message from client Idle 6
3214 SQL*Net message from client Idle 6
3216 SQL*Net message from client Idle 6
3751 rdbms ipc message Idle 6
3752 gcs remote message Idle 6
3754 rdbms ipc message Idle 6
3756 SQL*Net message from client Idle 6
3757 SQL*Net message from client Idle 6
3786 SQL*Net message from client Idle 6
3787 SQL*Net message from client Idle 6
1 heartbeat monitor sleep Idle 6
2 wait for unread message on broadcast channel Idle 6
314 rdbms ipc message Idle 6
315 Streams AQ: qmn coordinator idle wait Idle 6
627 pmon timer Idle 6
628 rdbms ipc message Idle 6
629 Streams AQ: waiting for messages in the queue Idle 6
940 Streams AQ: waiting for time management or cleanup tasks Idle 6
941 VKTM Logical Idle Wait Idle 6
942 rdbms ipc message Idle 6
1253 rdbms ipc message Idle 6
1254 rdbms ipc message Idle 6
1256 Space Manager: slave idle wait Idle 6
1566 DIAG idle wait Idle 6
1567 rdbms ipc message Idle 6
1568 Streams AQ: qmn slave idle wait Idle 6
1879 rdbms ipc message Idle 6
1880 smon timer Idle 6
1881 rdbms ipc message Idle 6
2192 PING Idle 6
2193 rdbms ipc message Idle 6
2194 rdbms ipc message Idle 6
2505 rdbms ipc message Idle 6
2506 rdbms ipc message Idle 6
2818 rdbms ipc message Idle 6
2819 rdbms ipc message Idle 6
2821 PX Deq: reap credit Other 0
3131 DIAG idle wait Idle 6
3132 jobq slave wait Idle 6
3444 rdbms ipc message Idle 6
3445 jobq slave wait Idle 6
3757 ges remote message Idle 6
3758 rdbms ipc message Idle 6
3759 VKRM Idle Idle 6
4070 gcs remote message Idle 6
4072 rdbms ipc message Idle 6
4383 gcs remote message Idle 6
4385 PX Deq: Execution Msg Idle 6
4696 rdbms ipc message Idle 6
4697 rdbms ipc message Idle 6
1 rdbms ipc message Idle 6
2 heartbeat monitor sleep Idle 6
3 rdbms ipc message Idle 6
4 wait for unread message on broadcast channel Idle 6
6 SQL*Net message from client Idle 6
From this output, what are the waits events i need to take into consideration.
Is this the right approach to follow?
Please let me know.
Thanks in advance.what actual problem are you trying to solve?
post SQL & results that have you concerned about wait events

How to identify what are all the events are created in background jobs?

Hi all,
how to identify what are all the events are created for background jobs. And what events gets triggered for a particular job.
thanxs
haritha

Hi Haritha,
JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
Use
As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
About Events:
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
Types of Events:
There are two types of events:
1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
1. Immediate
2. Date & Time
3. After event.
4. After job.
5. At Operation mode.
In case you want to view the job logs go to sm37.
Also Pls check DB02 for database performance and ST03 for workload .
Analyse u will have an idea ,
*pls assign points,if info is useful**
Regards
CSM reddy
null

Streams cannot create an index

HI All,
     I am currently implementing an Oracle Streams setup to stream a schema from one database to another database. While I have been able to overcome most problems so far, I currently have an issue where the streams apply process cannot create an index in the destination.
     I have effectively disabled VPD on the destination, and granted every privilege I can think of directly to the streams administrator, but still the transaction returns "ORA-00942: table or view does not exist". No other errors are listed - none about prilileges, open cursors or other possible problems
     I have searched Metalink, and found two notes (264477.1 and 276805.1), however neither really describe the problem, nor do their solutions help.
     Environment details are Oracle 11.1.0.7 on Red Hat Enterprise Linux Server release 5.3 (Tikanga)
     I have created a script which summarises attempted solutions, whose output is included below - appologies for the length.
Thanks in advance for any suggestions
Gavin
@ SQL>
@ SQL> connect / as sysdba
Connected.
SYS@TGFLXRD SQL> -- grant sysdba
SYS@TGFLXRD SQL> grant sysdba to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.01
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> -- For VPD
SYS@TGFLXRD SQL> grant exempt access policy to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.01
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> -- Object priv
SYS@TGFLXRD SQL> -- from Metalink ORA-942 ORA-1000 While Adding a New Table to 10g Streams Replication [ID 264477.1]
SYS@TGFLXRD SQL> grant dba to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.00
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> grant create any index to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.00
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> column grantee format a15
SYS@TGFLXRD SQL> column table_name format a25
SYS@TGFLXRD SQL> column owner format a15
SYS@TGFLXRD SQL> column grantor format a15
SYS@TGFLXRD SQL> column privilege format a20
SYS@TGFLXRD SQL> select *
2 from dba_tab_privs
3 where table_name = 'SHIPMENT_STOP_DEBRIEF'
4 order by grantee, privilege;
GRANTEE OWNER TABLE_NAME GRANTOR PRIVILEGE GRANTABLE HIERARCHY
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DELETE NO NO
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT NO NO
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT NO NO
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE NO NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT YES NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER REFERENCES NO NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT YES NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE YES NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ALTER NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DEBUG NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DELETE NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER FLASHBACK NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INDEX NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ON COMMIT REFRESH NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER QUERY REWRITE NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER REFERENCES NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ALTER NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DEBUG NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DELETE NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER FLASHBACK NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ON COMMIT REFRESH NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER QUERY REWRITE NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE NO NO
28 rows selected.
Elapsed: 00:00:00.02
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> connect glogowner/xxxxxx
Connected.
GLOGOWNER@TGFLXRD SQL> grant all on SHIPMENT_STOP_DEBRIEF to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.01
GLOGOWNER@TGFLXRD SQL>
GLOGOWNER@TGFLXRD SQL>
GLOGOWNER@TGFLXRD SQL> connect strmadmin/xxxxxx
Connected.
STRMADMIN@TGFLXRD SQL> -- ensure object can be seen
STRMADMIN@TGFLXRD SQL> create or replace synonym SHIPMENT_STOP_DEBRIEF for glogowner.SHIPMENT_STOP_DEBRIEF;
Synonym created.
Elapsed: 00:00:00.01
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> -- from Metalink ORA-942 & ORA-1000 from an Apply Process After Adding a New Table to a Streams Environment [ID 276805.1]
STRMADMIN@TGFLXRD SQL> column privilege format a40
STRMADMIN@TGFLXRD SQL> COLUMN APPLY_NAME HEADING 'Apply Process Name' FORMAT A20
STRMADMIN@TGFLXRD SQL> COLUMN APPLY_CAPTURED HEADING 'Type of Events Applied' FORMAT A15
STRMADMIN@TGFLXRD SQL> COLUMN APPLY_USER HEADING 'Apply User' FORMAT A30
STRMADMIN@TGFLXRD SQL> SELECT APPLY_NAME,
2 DECODE(APPLY_CAPTURED,
3 'YES', 'Captured',
4 'NO', 'User-Enqueued') APPLY_CAPTURED,
5 APPLY_USER
6 FROM DBA_APPLY;
Apply Process Name Type of Events Apply User
TGF_APP Captured STRMADMIN
OTM_APP Captured STRMADMIN
Elapsed: 00:00:00.00
STRMADMIN@TGFLXRD SQL> --select * from session_privs order by 1;
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> -- print_transaction from Oracle doco at
STRMADMIN@TGFLXRD SQL> -- http://download.oracle.com/docs/cd/B28359_01/server.111/b28321/strms_apmon.htm#CHDFBEFC
STRMADMIN@TGFLXRD SQL> set serveroutput on
STRMADMIN@TGFLXRD SQL> exec print_transaction('10.3.2694');
---- Local Transaction ID: 10.3.2694
---- Source Database: TGFLXD
----Error in Message: 1
----Error Number: 942
----Message Text: ORA-00942: table or view does not exist
--message: 1
type name: SYS.LCR$_DDL_RECORD
source database: TGFLXD
owner: GLOGOWNER
object: IX_SSD_ITEM_GID
is tag null: Y
ddl: CREATE INDEX GLOGOWNER.IX_SSD_ITEM_GID ON SHIPMENT_STOP_DEBRIEF(ITEM_GID) TABLESPACE INDX
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.01
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> CREATE INDEX GLOGOWNER.IX_SSD_ITEM_GID ON SHIPMENT_STOP_DEBRIEF(ITEM_GID) TABLESPACE INDX;
Index created.
Elapsed: 00:00:00.02
STRMADMIN@TGFLXRD SQL> drop index GLOGOWNER.IX_SSD_ITEM_GID;
Index dropped.
Elapsed: 00:00:00.05
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> -- let's try now...
STRMADMIN@TGFLXRD SQL> desc SHIPMENT_STOP_DEBRIEF
Name Null? Type
SHIPMENT_GID NOT NULL VARCHAR2(101)
STOP_NUM NOT NULL NUMBER(3)
ACTIVITY NOT NULL VARCHAR2(1)
SEQUENCE_NO NOT NULL VARCHAR2(10)
S_SHIP_UNIT_GID VARCHAR2(101)
S_SHIP_UNIT_LINE_NO NUMBER(10)
ITEM_PACKAGE_COUNT NUMBER(10)
PACKAGING_UNIT_GID VARCHAR2(101)
PACKAGING_UNIT_COUNT NUMBER(10)
TRANSPORT_HANDLING_UNIT_GID VARCHAR2(101)
TRANSPORT_HANDLING_UNIT_COUNT NUMBER(10)
ITEM_GID VARCHAR2(101)
NON_CONF_REASON_CODE_GID VARCHAR2(101)
SHIP_UNIT_GID VARCHAR2(101)
S_EQUIPMENT_GID VARCHAR2(101)
MATCH_TYPE VARCHAR2(20)
ORDER_RELEASE_LINE_GID VARCHAR2(101)
DOMAIN_NAME NOT NULL VARCHAR2(50)
INSERT_USER NOT NULL VARCHAR2(128)
INSERT_DATE NOT NULL DATE
UPDATE_USER VARCHAR2(128)
UPDATE_DATE DATE
STRMADMIN@TGFLXRD SQL> select count(*) from SHIPMENT_STOP_DEBRIEF;
COUNT(*)
0
Elapsed: 00:00:00.00
STRMADMIN@TGFLXRD SQL> select count(*) from glogowner.SHIPMENT_STOP_DEBRIEF;
COUNT(*)
0
Elapsed: 00:00:00.01
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> set serveroutput on
STRMADMIN@TGFLXRD SQL> begin
2 dbms_apply_adm.execute_error(
3 local_transaction_id => '10.3.2694',
4 execute_as_user => false,
5 user_procedure => null);
6 end;
7 /
begin
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 151
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 265
ORA-06512: at "SYS.DBMS_APPLY_ADM", line 467
ORA-06512: at line 2
Elapsed: 00:00:00.03
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> connect / as sysdba
Connected.
SYS@TGFLXRD SQL> revoke sysdba from strmadmin;
Revoke succeeded.
Elapsed: 00:00:00.07
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> spool off
-------------------------------------------------------------------------------------------------------------

HI All,
     I am currently implementing an Oracle Streams setup to stream a schema from one database to another database. While I have been able to overcome most problems so far, I currently have an issue where the streams apply process cannot create an index in the destination.
     I have effectively disabled VPD on the destination, and granted every privilege I can think of directly to the streams administrator, but still the transaction returns "ORA-00942: table or view does not exist". No other errors are listed - none about prilileges, open cursors or other possible problems
     I have searched Metalink, and found two notes (264477.1 and 276805.1), however neither really describe the problem, nor do their solutions help.
     Environment details are Oracle 11.1.0.7 on Red Hat Enterprise Linux Server release 5.3 (Tikanga)
     I have created a script which summarises attempted solutions, whose output is included below - appologies for the length.
Thanks in advance for any suggestions
Gavin
@ SQL>
@ SQL> connect / as sysdba
Connected.
SYS@TGFLXRD SQL> -- grant sysdba
SYS@TGFLXRD SQL> grant sysdba to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.01
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> -- For VPD
SYS@TGFLXRD SQL> grant exempt access policy to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.01
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> -- Object priv
SYS@TGFLXRD SQL> -- from Metalink ORA-942 ORA-1000 While Adding a New Table to 10g Streams Replication [ID 264477.1]
SYS@TGFLXRD SQL> grant dba to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.00
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> grant create any index to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.00
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> column grantee format a15
SYS@TGFLXRD SQL> column table_name format a25
SYS@TGFLXRD SQL> column owner format a15
SYS@TGFLXRD SQL> column grantor format a15
SYS@TGFLXRD SQL> column privilege format a20
SYS@TGFLXRD SQL> select *
2 from dba_tab_privs
3 where table_name = 'SHIPMENT_STOP_DEBRIEF'
4 order by grantee, privilege;
GRANTEE OWNER TABLE_NAME GRANTOR PRIVILEGE GRANTABLE HIERARCHY
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DELETE NO NO
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT NO NO
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT NO NO
APP_USER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE NO NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT YES NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER REFERENCES NO NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT YES NO
REPORTOWNER GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE YES NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ALTER NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DEBUG NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DELETE NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER FLASHBACK NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INDEX NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ON COMMIT REFRESH NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER QUERY REWRITE NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER REFERENCES NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT NO NO
STRMADMIN GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ALTER NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DEBUG NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER DELETE NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER FLASHBACK NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER INSERT NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER ON COMMIT REFRESH NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER QUERY REWRITE NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER SELECT NO NO
STRMADMIN_ROLE GLOGOWNER SHIPMENT_STOP_DEBRIEF GLOGOWNER UPDATE NO NO
28 rows selected.
Elapsed: 00:00:00.02
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> connect glogowner/xxxxxx
Connected.
GLOGOWNER@TGFLXRD SQL> grant all on SHIPMENT_STOP_DEBRIEF to strmadmin;
Grant succeeded.
Elapsed: 00:00:00.01
GLOGOWNER@TGFLXRD SQL>
GLOGOWNER@TGFLXRD SQL>
GLOGOWNER@TGFLXRD SQL> connect strmadmin/xxxxxx
Connected.
STRMADMIN@TGFLXRD SQL> -- ensure object can be seen
STRMADMIN@TGFLXRD SQL> create or replace synonym SHIPMENT_STOP_DEBRIEF for glogowner.SHIPMENT_STOP_DEBRIEF;
Synonym created.
Elapsed: 00:00:00.01
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> -- from Metalink ORA-942 & ORA-1000 from an Apply Process After Adding a New Table to a Streams Environment [ID 276805.1]
STRMADMIN@TGFLXRD SQL> column privilege format a40
STRMADMIN@TGFLXRD SQL> COLUMN APPLY_NAME HEADING 'Apply Process Name' FORMAT A20
STRMADMIN@TGFLXRD SQL> COLUMN APPLY_CAPTURED HEADING 'Type of Events Applied' FORMAT A15
STRMADMIN@TGFLXRD SQL> COLUMN APPLY_USER HEADING 'Apply User' FORMAT A30
STRMADMIN@TGFLXRD SQL> SELECT APPLY_NAME,
2 DECODE(APPLY_CAPTURED,
3 'YES', 'Captured',
4 'NO', 'User-Enqueued') APPLY_CAPTURED,
5 APPLY_USER
6 FROM DBA_APPLY;
Apply Process Name Type of Events Apply User
TGF_APP Captured STRMADMIN
OTM_APP Captured STRMADMIN
Elapsed: 00:00:00.00
STRMADMIN@TGFLXRD SQL> --select * from session_privs order by 1;
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> -- print_transaction from Oracle doco at
STRMADMIN@TGFLXRD SQL> -- http://download.oracle.com/docs/cd/B28359_01/server.111/b28321/strms_apmon.htm#CHDFBEFC
STRMADMIN@TGFLXRD SQL> set serveroutput on
STRMADMIN@TGFLXRD SQL> exec print_transaction('10.3.2694');
---- Local Transaction ID: 10.3.2694
---- Source Database: TGFLXD
----Error in Message: 1
----Error Number: 942
----Message Text: ORA-00942: table or view does not exist
--message: 1
type name: SYS.LCR$_DDL_RECORD
source database: TGFLXD
owner: GLOGOWNER
object: IX_SSD_ITEM_GID
is tag null: Y
ddl: CREATE INDEX GLOGOWNER.IX_SSD_ITEM_GID ON SHIPMENT_STOP_DEBRIEF(ITEM_GID) TABLESPACE INDX
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.01
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> CREATE INDEX GLOGOWNER.IX_SSD_ITEM_GID ON SHIPMENT_STOP_DEBRIEF(ITEM_GID) TABLESPACE INDX;
Index created.
Elapsed: 00:00:00.02
STRMADMIN@TGFLXRD SQL> drop index GLOGOWNER.IX_SSD_ITEM_GID;
Index dropped.
Elapsed: 00:00:00.05
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> -- let's try now...
STRMADMIN@TGFLXRD SQL> desc SHIPMENT_STOP_DEBRIEF
Name Null? Type
SHIPMENT_GID NOT NULL VARCHAR2(101)
STOP_NUM NOT NULL NUMBER(3)
ACTIVITY NOT NULL VARCHAR2(1)
SEQUENCE_NO NOT NULL VARCHAR2(10)
S_SHIP_UNIT_GID VARCHAR2(101)
S_SHIP_UNIT_LINE_NO NUMBER(10)
ITEM_PACKAGE_COUNT NUMBER(10)
PACKAGING_UNIT_GID VARCHAR2(101)
PACKAGING_UNIT_COUNT NUMBER(10)
TRANSPORT_HANDLING_UNIT_GID VARCHAR2(101)
TRANSPORT_HANDLING_UNIT_COUNT NUMBER(10)
ITEM_GID VARCHAR2(101)
NON_CONF_REASON_CODE_GID VARCHAR2(101)
SHIP_UNIT_GID VARCHAR2(101)
S_EQUIPMENT_GID VARCHAR2(101)
MATCH_TYPE VARCHAR2(20)
ORDER_RELEASE_LINE_GID VARCHAR2(101)
DOMAIN_NAME NOT NULL VARCHAR2(50)
INSERT_USER NOT NULL VARCHAR2(128)
INSERT_DATE NOT NULL DATE
UPDATE_USER VARCHAR2(128)
UPDATE_DATE DATE
STRMADMIN@TGFLXRD SQL> select count(*) from SHIPMENT_STOP_DEBRIEF;
COUNT(*)
0
Elapsed: 00:00:00.00
STRMADMIN@TGFLXRD SQL> select count(*) from glogowner.SHIPMENT_STOP_DEBRIEF;
COUNT(*)
0
Elapsed: 00:00:00.01
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> set serveroutput on
STRMADMIN@TGFLXRD SQL> begin
2 dbms_apply_adm.execute_error(
3 local_transaction_id => '10.3.2694',
4 execute_as_user => false,
5 user_procedure => null);
6 end;
7 /
begin
ERROR at line 1:
ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 151
ORA-06512: at "SYS.DBMS_APPLY_ERROR", line 265
ORA-06512: at "SYS.DBMS_APPLY_ADM", line 467
ORA-06512: at line 2
Elapsed: 00:00:00.03
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL>
STRMADMIN@TGFLXRD SQL> connect / as sysdba
Connected.
SYS@TGFLXRD SQL> revoke sysdba from strmadmin;
Revoke succeeded.
Elapsed: 00:00:00.07
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL>
SYS@TGFLXRD SQL> spool off
-------------------------------------------------------------------------------------------------------------

PX Deq: Execute Reply - Wait event

I am seeing PX Deq: Execute Reply wait event for a query which returns no data. From metalink I see this can be ignored.
Any suggestion is appreciated.

I am attaching explain plan. Not sure if this helps. Another prod database which has similiar plan works fine.
Execution Plan
0 SELECT STATEMENT Optimizer=CHOOSE (Cost=205424 Card=1 Bytes=
142)
1 0 TABLE ACCESS* (BY INDEX ROWID) OF 'STG_TRD_SWAP_CF' (Cost= :Q804383
4 Card=1 Bytes=82) 001
2 1 NESTED LOOPS* (Cost=205424 Card=1 Bytes=142) :Q804383
001
3 2 HASH JOIN* (Cost=59005 Card=146419 Bytes=8785140) :Q804383
001
4 3 NESTED LOOPS* (Cost=3 Card=1 Bytes=25) :Q804383
000
5 4 VIEW (Cost=2 Card=1 Bytes=13)
6 5 SORT (AGGREGATE)
7 6 INDEX (FULL SCAN (MIN/MAX)) OF 'T_HUB_CONTROL_
TRADE_HDR_PK' (UNIQUE) (Cost=2 Card=579 Bytes=2316)
8 4 TABLE ACCESS (BY INDEX ROWID) OF 'T_HUB_CONTROL_TR
ADE_HDR' (Cost=1 Card=1 Bytes=12)
9 8 INDEX (UNIQUE SCAN) OF 'T_HUB_CONTROL_TRADE_HDR_
PK' (UNIQUE)
10 3 PARTITION RANGE* (ALL) :Q804383
001
11 10 PARTITION LIST* (ALL) :Q804383
001
12 11 TABLE ACCESS* (FULL) OF 'T_HUB_TRD_MAIN' (Cost=5 :Q804383
9002 Card=84630120 Bytes=2962054200) 001
13 2 INDEX* (RANGE SCAN) OF 'STG_TRD_SWAP_CF_PK' (UNIQUE) ( :Q804383
Cost=3 Card=1) 001
1 PARALLEL_COMBINED_WITH_CHILD
2 PARALLEL_TO_SERIAL SELECT /*+ ORDERED NO_EXPAND USE_NL(A2) INDE
X(A2 "STG_TRD_SWAP_CF_PK") */ A1.C0,
3 PARALLEL_COMBINED_WITH_PARENT
4 PARALLEL_FROM_SERIAL
10 PARALLEL_COMBINED_WITH_PARENT
11 PARALLEL_COMBINED_WITH_PARENT
12 PARALLEL_COMBINED_WITH_PARENT
13 PARALLEL_COMBINED_WITH_PARENT

No wait events info in trace file?

A very good day to all experts,
I am tracing a session using the below procedure.
dbms_system.set_ev(12,13,EV=>10046,LE=>12,NM=>'');
I am just displaying the following information in trace file.Trace file is not displaying any wait events even when i am doing level 12 tracing.How i can see the wait event information in trace files?
call count cpu elapsed disk query current rows
Parse 1 0.00 0.00 0 0 0 0
Execute 1 0.01 0.01 0 0 0 0
Fetch 2 0.00 0.05 2 2 0 1
total 4 0.01 0.07 2 2 0 1
Misses in library cache during parse: 1
Optimizer mode: CHOOSE
Parsing user id: 55
Rows Row Source Operation
1 TABLE ACCESS BY INDEX ROWID aaa_USERS (cr=2 pr=2 pw=0 time=58806 us)
1 INDEX UNIQUE SCAN SYS_C004271 (cr=1 pr=1 pw=0 time=42773 us)(object id 47506)
Thank you....

Your post is without version information up to 4 digits.
You post tkprof output.
Not all version of Oracle have tkprof post wait event info.
IIRC. this started in Oracle 9iR2.
You would need to look in the raw trace file to find out whether this information is actually available. You will find it is.
This could likely being caused by using 8i, which doesn't have this facility.
But as you don't post a version, your question can not be answered.
Sybrand Bakker
Senior Oracle DBA

CPU Time Wait Event

I am running perfstat in Oracle9i Enterprise Edition Release 9.2.0.4.0. When I create a perfstat report using the standard scripts I see a wait event called "CPU time." I don't understand what this means. The OEM server monitoring tool does not indicate that the CPU is being used more than 50%, often more like 20%. The top 5 wait events is below.
What does "CPU time" time mean?
the following top 5 wait events:
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
CPU time 2,200 61.88
db file sequential read 113,042 639 17.96
control file parallel write 9,345 471 13.24
log file sync 4,722 122 3.44
db file scattered read 13,375 67 1.87

Hi,
Below is part of my Statspack
```````
Snap Id Snap Time Sessions Curs/Sess Comment
Begin Snap: 13805 26-Mar-08 08:00:03 85 173.2
End Snap: 13806 26-Mar-08 09:00:05 98 154.4
Elapsed: 60.03 (mins)
Cache Sizes (end)
~~~~~~~~~~~~~~~~~
Buffer Cache: 1,024M Std Block Size: 8K
Shared Pool Size: 400M Log Buffer: 2,048K
Load Profile
~~~~~~~~~~~~ Per Second Per Transaction
Redo size: 183,878.75 16,898.36
Logical reads: 61,602.61 5,661.25
Block changes: 1,255.54 115.38
Physical reads: 7,370.56 677.35
Physical writes: 55.64 5.11
User calls: 341.11 31.35
Parses: 56.26 5.17
Hard parses: 0.32 0.03
Sorts: 56.43 5.19
Logons: 0.80 0.07
Executes: 712.67 65.49
Transactions: 10.88
% Blocks changed per Read: 2.04 Recursive Call %: 82.56
Rollback per transaction %: 9.29 Rows per Sort: 1043.63
Instance Efficiency Percentages (Target 100%)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Buffer Nowait %: 99.98 Redo NoWait %: 100.00
Buffer Hit %: 88.06 In-memory Sort %: 100.00
Library Hit %: 99.96 Soft Parse %: 99.42
Execute to Parse %: 92.11 Latch Hit %: 99.95
Parse CPU to Parse Elapsd %: 69.60 % Non-Parse CPU: 99.64
Shared Pool Statistics Begin End
Memory Usage %: 89.25 89.26
% SQL with executions>1: 40.51 39.68
% Memory for SQL w/exec>1: 29.05 29.45
Top 5 Timed Events
~~~~~~~~~~~~~~~~~~ % Total
Event Waits Time (s) Ela Time
CPU time 9,272 43.73
db file sequential read 5,203,772 7,027 33.14
db file scattered read 2,198,721 1,547 7.30
log file parallel write 20,935 1,126 5.31
log file sync 10,277 759 3.58
``````````````````
From my observation I found that it seems CPU is bottneck on this Server. I have gathered few SQLs to find out whether any scope for tuning but still I believe that by reducing the cache size also I can divide the load or can say transfer the load from CPU to I/O. Am I correct or do I need to look over else ?
Thanks
MJ

Wait Event Step

Greetings Friends...
Im having this little trouble with this Step at my Workflow (WS9000000004).
In my Workflow Template I got step "Wait Event" for BUS2105 (ZBUS2105) to Event "ZPROCESSED".
At some BADI for ME41, I'm using FM SWE_CREATE_EVENT for BUS2105, Event "ZPROCESSED".
(Using "BUS2105" as object, "ZPROCESSED" as Event and "EBELN" (quotation nº) as Object-Key)
At Swel, when someone creates (saves) a new Quotation, it shows that this Event is triggered properly.
(But doesnt have any receiver, but I think this is correct, as I'm not using this event to Start a Workflow)
But all my flows from WS90000000004, (that is still processing) are stuck waiting, for event ZPROCESSED.
Am I missing something?
Att,
José Junior
PS: "ZPROCESSED" isnt the starting event from WS900000004. It is just a Step Event. The Starting event is "ZCREATE' who is working properly when a new Purchase Requisition is created. (Again, using SWE_CREATE_EVENT at some Exit in ME51N).

What is the option that you have used to wait I mean
Wait for event
Wait for Local Event
Wait for Condition etc.
Wait for Event
can you please let us know.
If you have used wait for condition check whether the conditon is satisfied or not
Yes... I mean. I am waiting the event to get the new Quotation Number Created.
So I can check if the Quotation have itens of the particular Purchase Requisition.
If yes, check the PR status, if all itens were "quotated", Status receives S. Then exits Loop.
Or by "Condition Check" you mean another thing, like somekind of the Step configuration itself?
If you are using wait for event trigger the event by using EVENT CREATOR step
Nope.... This Event is getting (actually should have been) triggered by SWE_EVENT_CREATOR at
BADI in ME41. This FM is working properly, as I can see him at SWEL. (ZPROCESSED for BUS2105
after Request for Quotation is created.)

Gc quiesce wait event on creating an index

Similar Messages

Maybe you are looking for