DBMS_SCHEDULER after insert row

Hi,
I have probably simple question..
Is there any trick to run job after insert row?? I try to find some example, but all have repeat_interval :/ Thanks for all sugestions :)

Why can't you use trigger? Or if it must be a job you can probably run job from trigger. By the way - repeat_interval is not the time when job is starting but the time between job executions. The time when job is starting can be set by start_date parameter of DBMS_SCHEDULER.CREATE_JOB procedure.

Similar Messages

How to Display a message after inserting row in table............

Hi
I want to display a message after inserting rows in table like *'you have inserted a new row successfully*'.
i am using the createinsert ADF Button to insert the rows in table.after that i am comitting it.
after commiting i want to display message for the user.for this what i need to do.
Please help me.
Sailaja.

user10860137
Can you please explain me the each line in the code briefly.
+public String saveButton_action(){+
BindingContainer bindings = getBindings();
OperationBinding operationBinding = bindings.getOperationBinding("Commit");
Object result = operationBinding.execute();
+// note "!" operator has been removed from the default code.+
+if(operationBinding.getErrors().isEmpty()){+
FacesContext ctx = FacesContext.getCurrentInstance();
FacesMessage saveMsg = new FacesMessage("Record Saved Successfully");
ctx.addMessage(null,saveMsg);
+}+
return null;
+}+
And i have requirement to show the message on favcet "status bar".not in a popup window.(from the above code the message is showing in popup window. )the Layout i am using is PanelCollection.
can you tell me what i need to do.
Thanks
Sailaja.
Edited by: sj0609 on Mar 19, 2009 8:03 AM

Update of JTable after inserting row with beans binding

I have a little problem. When i create a little app with netbeans which uses the beansbinding with a table it is not possible to get updates of the list into the table.
i use nearly the same methods as if i create a database application with the wizzard. The only difference i see (so far) is that i don't use the Swing application framework.
if i try to repaint the table or the ScrollPane, nothing happens. The list is changed but not the table....

You should be updating the TableModel, not the "list". When you update the model it will notify the table to repaint itself.

Capturing value in after insert or update row level trigger

Hi Experts,
I'm working on EBS 11.5.10 and database 11g. I have trigger-A on wip_discrete_jobs table and trigger-B on wip_requirement_operations table.When ever i create discrete job, it inserts record in both wip_discrete_jobs and wip_requirement_operations.
Note:2 tables are like master-child relation.
Trigger-A: After Insert.Row Level trigger on wip_discrete_jobs
Trigger-B:After Insert,Row Level trigger on wip_requirement_operations
In Trigger A:
I'm capturing wip_entity_id and holding in global variable.
package.variable:=:new.wip_entity_id
In Trigger B:
I'm using the above global variable.
Issue: Let's say i have create discrete job,it's wip_entity_id is 27, but the global variable is holding the previous wip_entity_id(26),not current value.It looks like before trigger A event is complete, trigger B is also in process, i think this could be the reason it's not storing the current wip_entity_id in the global variable.
I need your help how to have the current value in the global variable so that i can use that in the trigger B.
Awaiting response at the earliest.
Thanks

798616 wrote:
Hi Experts,
I'm working on EBS 11.5.10 and database 11g. I have trigger-A on wip_discrete_jobs table and trigger-B on wip_requirement_operations table.When ever i create discrete job, it inserts record in both wip_discrete_jobs and wip_requirement_operations.
Note:2 tables are like master-child relation.
Trigger-A: After Insert.Row Level trigger on wip_discrete_jobs
Trigger-B:After Insert,Row Level trigger on wip_requirement_operations
In Trigger A:
I'm capturing wip_entity_id and holding in global variable.
package.variable:=:new.wip_entity_id
In Trigger B:
I'm using the above global variable.
Issue: Let's say i have create discrete job,it's wip_entity_id is 27, but the global variable is holding the previous wip_entity_id(26),not current value.It looks like before trigger A event is complete, trigger B is also in process, i think this could be the reason it's not storing the current wip_entity_id in the global variable.
I need your help how to have the current value in the global variable so that i can use that in the trigger B.
Awaiting response at the earliest.
ThanksMy head hurts just thinking about how this is being implemented.
What's stopping you from creating a nice and simple procedure to perform all this magic?
Continue with the global/trigger magic at your own peril, as you can hopefully already see ... nothing good will come from it.
Cheers,

Updating statistics after insert

Is it possible, without creating a custom post-map process, to update statistics after inserting rows into a table. I've tried setting different parameters within OWB to no avail.
Please respond only if you have actually succeeded in updating statistics without writing code. I've already read the docs and experimented.
Thanks.
Garrett

Hi,
why do you think so? The analyze configuration
results in a procedure which calls
WB_RT_MAPAUDIT_UTIL_INVOKER for each target table
which then calls the DBMS_STATS-Package? What is
misssing for the CBO? I'm a little bit confused?!
Regards,
DetlefThanks for the info. I'm a little confused. I thought that I had the analyze table box checked in the configuration and statistics were not updated. However, when I looked again, it was not checked. My error. Ran another test and statistics were updated. Sorry for the confusion.
G.

Insert Blank row After every Row in alv report

How to insert blank row After every row in Alv report

what do you mean by a 'blank row'? ALV displays tabular data with 'any' number of columns. Now if you actually want a blank row (no columns at all, just a row), then that is just not possible. If I'm not mistaken, this question was posted before, so try to do a search on SCN. See what is says.

SQL merge and after insert or update on ... for each row fires too often?

Hello,
there is a base table, which has a companion history table
- lets say USER_DATA & USER_DATA_HIST.
For each update on USER_DATA there has to be recorded the old condition of the USER_DATA record into the USER_DATA_HIST (insert new record)
- to have the history of changes to USER_DATA.
The first approach was to do the insert for the row trigger:
trigger user_data_tr_aiu after insert or update on user_data for each rowBut the performance was bad, because for a bulk update to USER_DATA, there have been individual inserts per records.
So i tried a trick:
Instead of doing the real insert into USER_DATA_HIST, i collect the USER_DATA_HIST data into a pl/sql collection first.
And later i do a bulk insert for the collection in the USER_DATA_HIST table with stmt trigger:
trigger user_data_tr_ra after insert or update on user_dataBut sometimes i recognize, that the list of entries saved in the pl/sql collection are more than my USER_DATA records being updated.
(BTW, for the update i use SQL merge, because it's driven by another table.)
As there is a uniq tracking_id in USER_DATA record, i could identify, that there are duplicates.
If i sort for the tracking_id and remove duplicate i get exactly the #no of records updated by the SQL merge.
So how comes, that there are duplicates?
I can try to make a sample 'sqlplus' program, but it will take some time.
But maybe somebody knows already about some issues here(?!)
- many thanks!
best regards,
Frank

Hello
Not sure really. Although it shouldn't take long to do a test case - it only took me 10 mins....
SQL>
SQL> create table USER_DATA
2 (   id      number,
3      col1    varchar2(100)
4 )
5 /
Table created.
SQL>
SQL> CREATE TABLE USER_DATA_HIST
2 (   id      number,
3      col1    varchar2(100),
4      tmsp    timestamp
5 )
6 /
Table created.
SQL>
SQL> CREATE OR REPLACE PACKAGE pkg_audit_user_data
2 IS
3
4      PROCEDURE p_Init;
5
6      PROCEDURE p_Log
7      (   air_UserData        IN user_data%ROWTYPE
8      );
9
10      PROCEDURE p_Write;
11 END;
12 /
Package created.
SQL> CREATE OR REPLACE PACKAGE BODY pkg_audit_user_data
2 IS
3
4      TYPE tt_UserData        IS TABLE OF user_data_hist%ROWTYPE INDEX BY BINARY_INTEGER;
5
6      pt_UserData             tt_UserData;
7
8      PROCEDURE p_Init
9      IS
10
11      BEGIN
12
13
14          IF pt_UserData.COUNT > 0 THEN
15
16              pt_UserData.DELETE;
17
18          END IF;
19
20      END;
21
22      PROCEDURE p_Log
23      (   air_UserData        IN user_data%ROWTYPE
24      )
25      IS
26          ln_Idx              BINARY_INTEGER;
27
28      BEGIN
29
30          ln_Idx := pt_UserData.COUNT + 1;
31
32          pt_UserData(ln_Idx).id     := air_UserData.id;
33          pt_UserData(ln_Idx).col1   := air_UserData.col1;
34          pt_UserData(ln_Idx).tmsp   := SYSTIMESTAMP;
35
36      END;
37
38      PROCEDURE p_Write
39      IS
40
41      BEGIN
42
43          FORALL li_Idx IN INDICES OF pt_UserData
44              INSERT
45              INTO
46                  user_data_hist
47              VALUES
48                  pt_UserData(li_Idx);
49
50      END;
51 END;
52 /
Package body created.
SQL>
SQL> CREATE OR REPLACE TRIGGER preu_s_user_data BEFORE UPDATE ON user_data
2 DECLARE
3
4 BEGIN
5
6      pkg_audit_user_data.p_Init;
7
8 END;
9 /
Trigger created.
SQL> CREATE OR REPLACE TRIGGER preu_r_user_data BEFORE UPDATE ON user_data
2 FOR EACH ROW
3 DECLARE
4
5      lc_Row      user_data%ROWTYPE;
6
7 BEGIN
8
9      lc_Row.id   := :NEW.id;
10      lc_Row.col1 := :NEW.col1;
11
12      pkg_audit_user_data.p_Log
13      (   lc_Row
14      );
15
16 END;
17 /
Trigger created.
SQL> CREATE OR REPLACE TRIGGER postu_s_user_data AFTER UPDATE ON user_data
2 DECLARE
3
4 BEGIN
5
6      pkg_audit_user_data.p_Write;
7
8 END;
9 /
Trigger created.
SQL>
SQL>
SQL> insert
2 into
3      user_data
4 select
5      rownum,
6      dbms_random.string('u',20)
7 from
8      dual
9 connect by
10      level <=10
11 /
10 rows created.
SQL> select * from user_data
2 /
        ID COL1
         1 GVZHKXSSJZHUSLLIDQTO
         2 QVNXLTGJXFUDUHGYKANI
         3 GTVHDCJAXLJFVTFSPFQI
         4 CNVEGOTDLZQJJPVUXWYJ
         5 FPOTZAWKMWHNOJMMIOKP
         6 BZKHAFATQDBUVFBCOSPT
         7 LAQAIDVREFJZWIQFUPMP
         8 DXFICIPCBCFTPAPKDGZF
         9 KKSMMRAQUORRPUBNJFCK
        10 GBLTFZJAOPKFZFCQPGYW
10 rows selected.
SQL> select * from user_data_hist
2 /
no rows selected
SQL>
SQL> MERGE
2 INTO
3      user_data a
4 USING
5 (   SELECT
6          rownum + 8 id,
7          dbms_random.string('u',20) col1
8      FROM
9          dual
10      CONNECT BY
11          level <= 10
12 ) b
13 ON (a.id = b.id)
14 WHEN MATCHED THEN
15      UPDATE SET a.col1 = b.col1
16 WHEN NOT MATCHED THEN
17      INSERT(a.id,a.col1)
18      VALUES (b.id,b.col1)
19 /
10 rows merged.
SQL> select * from user_data_hist
2 /
        ID COL1                 TMSP
         9 XGURXHHZGSUKILYQKBNB 05-AUG-11 10.04.15.577989
        10 HLVUTUIFBAKGMXBDJTSL 05-AUG-11 10.04.15.578090
SQL> select * from v$version
2 /
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bi
PL/SQL Release 10.2.0.4.0 - Production
CORE    10.2.0.4.0      Production
TNS for Linux: Version 10.2.0.4.0 - Production
NLSRTL Version 10.2.0.4.0 - ProductionHTH
David

How to insert the new row after current row in RowIterator - Steve Muench

Hi,
Our client wants the new row to be added after current row on the front end instead of before current row.
we were using "new JUActionBinding(this,iterBinding,JUActionBinding.ACTION_CREATE_INSERT_ROW);" this code inserts the new row after current row.
I tried a lot to insert the new row after current row. Used new JUActionBinding(this,iterBinding,JUActionBinding.ACTION_LAST to move the cursor to last row in rowiterator and the used .ACTION_CREATE_INSERT_ROW but this thing inserts the new row as the second last row.
Could somebody plesae help ?
Message was edited by:
user556161

I am using JDeveloper 9.0.4.2.0 (Build 1459)

Problem with a field set to refresh after insert at Row level

hello all,
i have a problem with a field (a serial) which is set by a db trigger at insertion. The field "refresh after insert" is properly set in the Entity and everything is refreshed correctly when i insert data via an adf form in a jspx but when i want to insert programmatically nothing is refreshed. I insert data this way :
ViewObject insertVO = findViewObject("myView");
Row newRow = insertVO.createRow();
newRow.setAttribute("mandatoryAttribute1",value1);
newRow.setAttribute("mandatoryAttribute2",value2);
<more init here but not the serial since it will be set by the DB trigger>
insertVO.insertRow(newRow);
but when i want to get back the value with "newRow().getAttribute("TheSerial");" i always get a null back and not the value set by the db trigger.
One way to get the serial is to commit after each insert but i don't want to commit between inserts.
i've tried to unset the refresh after insert and override the createDef() method to setUseReturningClause(false) as it's is advised in chapter 26.5 of the ADF 4GL dev. guide but in this case i have an exception JBO-29000: JBO-26041.
How can i get the value back properly ?
thanks
-regards

The data for the newly created row doesn't get inserted into the database until the commit is executed, so the insert trigger isn't called.
If you need to get the value without committing, then you should implement the trigger programmatically and drop the trigger from the database. The code below shows how you could do this.
ViewObject insertVO = findViewObject("myView");
Row newRow = insertVO.createRow();
SequenceImpl seq = new SequenceImpl("MY_SEQ", insertVO.getDBTransaction());
Long next = (Long)seq.getData();
newRow.setAttribute("primaryAttribute", new Number(next));
...You will need to replace MY_SEQ and primaryAttribute with the correct values for your example, but this should acheive what you want.

URGENT: How to see the inserted row results in the ResultSet after an insertRow()?

I want to see the inserted row in my result set immediately after I do an insertRow(). I don't want to do another select as my table has 100,000 records. I am using TYPE_SCROLL_SENSITIVE and CONCUR_UPDATABLE resultset with 8.1.7 thin driver.
May be the driver does not support this because dbmd.ownInsertsAreVisible(ResultSet.TYPE_SCROLL_SENSITIVE)) always returns false. I just want to know is there a workaround or any solution for this problem. I would really appreciate if somebody could help me. Thanks in advance.

Okay, first execute the query reqd. Then make whatever filters, navigational changes etc that are reqd. Once you are satisfied with the view of the data that you see on the screen, then from the Bex toolbar, click the Save button (Second from left) and choose the option Save as View Global. Give it a decsription and technical name.
Hope this helps...

How do I prevent tree collapse after insert of row?

Hi,
I've got a tree with several discrattrbindings. It's a recursive tree representing a parent/child relation.
If I add a sub record to one of the children, the tree collapses. The insert is fine and the tree is ok, it's just that it completely collapses everytime I add something. How do I prevent this? This is extremely annoying for users.
(jdev9031 on win2k)
Greetings,
Ivo

I've got some additional info, which I think is a bug.
After the first record is added, the tree is collapsed, as I've said above. Now, if I reopen the tree and then try to open a node (that was previously closed) which has no subitems, then at the moment I click the '+', the entire tree collapses again. If I open a node that contains subs, it's fine, but empty nodes cause the tree to collapse.
This is only after insertion of a row. If I run the app without inserting a row, the tree remains open if I open an empty node.

Updating row after insert that causes trigger

Hi,
I have a table which one of the columns is a sequence number which each time a new row is written I want to automatically write to this sequence column the latest number (which is maintained using an Oracle sequence). I decided to use a trigger which works great:
CREATE OR REPLACE TRIGGER pre_insert_trg before insert ON INCOMING
for each row
BEGIN
SELECT INCOMING_SEQ.NEXTVAL
INTO :new.SEQ
FROM DUAL;
END;
The problem is I have many multi-threaded processes writing to this table and the sequence number gets allocated before the row is committed which means although thread 1 may write first it may commit after thread 2 which has a later sequence number which has the result that sequence number 2 may be shown before 1. The problem is much larger when dealing with many threads with 100's of messages a second and so I would prefer the seq to be added AFTER the insert (once committed), e.g.
CREATE OR REPLACE TRIGGER post_insert_trg after insert ON INCOMING
for each row
BEGIN
SELECT INCOMING_SEQ.NEXTVAL
INTO :new.SEQ
FROM DUAL;
END;
Trying to create this trigger results in a "ORA-04084: cannot change NEW values for this trigger type". Is there a way to update a column for the row which caused the trigger? If I try and remove the :new. I then get errors when inserting about mutating table (which I understand the DML locking but need a way round)
Many thanks,
John

Off hand I think the only way you can do what you say you want to do is to replace the sequence with a code table. A transaction locks the code table, gets the next value from it and unlocks the code table at the end of the transaction. This ensures that the sequence number is always assigned in transaction completion order (or rather the transactions always complete in sequence assigned order). It is basically what java does with its synchronize statement.
The only drawback with this approach is that it completely shags the performance of the sort of multi-threaded environment you've just described. :P
So you need to decide what's more important: having stuff inserted into a queue in sequence order or having a multi-threaded system running quickly. I really don't see how you can acheive what you're attempting in a genuinely concurrent environment; you'll have to introduce an artificial serialism (ie bottleneck) somewhere.
If you do crack this please tell me how: I would be interested in ordering multiple AQs in the fashion you described.
Cheers, APC

The row was not found at the Subscriber error keeps popup and stopped synchronization even after inserting missing record at subscriber - transcational replication.

The row was not found at the Subscriber error keeps popup and stopped synchronization even after inserting missing record at subscriber - transcational replication.
first error throws: Grab exact sequence number, find row and inserted at subscriber...
Start synchronizing, ran fine for a while, stopped again with error with different exact sequence number, repeat again same as step 1.......
how can we stop this and make it run without this error?
Please advise!!!

Hi,
This means that your database is out of sync. You can use the continue on data consistency error profile to skip errors. However, Microsoft recommends that you use -SkipErrors parameter cautiously and only when you have a good understanding of the following:
What the error indicates.
Why the error occurs.
Why it is better to skip the error instead of solving it.
If you do not know the answers to these items, inappropriate use of the
-SkipErrors parameter may cause data inconsistency between the Publisher and Subscriber. This article describes some problems that can occur when you incorrectly use the
-SkipErrors parameter.
Use the "-SkipErrors" parameter in Distribution Agent cautiously
http://support.microsoft.com/kb/327817/en-us
Here are two similar threads you may refer to:
http://social.technet.microsoft.com/Forums/en-US/af531f69-6caf-4dd7-af74-fd6ebe7418da/sqlserver-replication-error-the-row-was-not-found-at-the-subscriber-when-applying-the-replicated
http://social.technet.microsoft.com/Forums/en-US/f48c2592-bad7-44ea-bc6d-7eb99b2348a1/the-row-was-not-found-at-the-subscriber-when-applying-the-replicated-command
Thanks.
Tracy Cai
TechNet Community Support

:new., lob columns and after insert ... for each row trigger

I'm having this little problem with
my update/insert triggers and lob columns.
I have this little trigger:
CREATE OR REPLACE TRIGGER BLOB_DATA_INSERT
AFTER INSERT ON BLOB_DATA
FOR EACH ROW
BEGIN
INSERT INTO BLOB_DATA_CHANGE VALUES(CHANGE_SEQ.NEXTVAL, 'I', :NEW.ID,:NEW.DATA);
END;
Which works except when the DATA column
is a BLOB or CLOB (There is no data in :NEW.DATA. I even tried some of the DBMS_LOB package procedures)
The one thing that is different for the lob columns is that the application updating
the data is using a bind statement with returning, like:
INSERT INTO BLOB_DATA
VALUES(:ID,EMPTY_BLOB())
RETURNING DATA INTO :DATA;
COMMIT;
Thanks for any help

I'm having this little problem with
my update/insert triggers and lob columns.
I have this little trigger:
CREATE OR REPLACE TRIGGER BLOB_DATA_INSERT
AFTER INSERT ON BLOB_DATA
FOR EACH ROW
BEGIN
INSERT INTO BLOB_DATA_CHANGE VALUES(CHANGE_SEQ.NEXTVAL, 'I', :NEW.ID,:NEW.DATA);
END;
Which works except when the DATA column
is a BLOB or CLOB (There is no data in :NEW.DATA. I even tried some of the DBMS_LOB package procedures)
The one thing that is different for the lob columns is that the application updating
the data is using a bind statement with returning, like:
INSERT INTO BLOB_DATA
VALUES(:ID,EMPTY_BLOB())
RETURNING DATA INTO :DATA;
COMMIT;
Thanks for any help

Help me to return the primary key after insert the row

Hi
I am using JDBC, with oracle database. i have welformed normalization tables .i am inserting parent table with dynamic sequence number as primary key .after inserting i need inserted row primary key .how to get the inserted row primary key with out using select statement
please help me
Thanks in advance
Edited by: 849614 on Apr 4, 2011 5:41 AM
Edited by: 849614 on Apr 4, 2011 5:54 AM

Hello
If I undestand you, I think you should do this:
Connection conexion = dataSource.getConnection();
int idCenter=-1;
String query = "Begin Insert into CENTER (NAME_CENTER) values (?) returning ID_CENTER into ?; end";
callableStatement = conexion.prepareCall(query.toString());
     callableStatement.setString(1, "Center name");
     callableStatement.registerOutParameter(2, java.sql.Types.INTEGER);
          callableStatement.executeUpdate();
          idCenter=callableStatement.getInt(2);
This way, you have in idCenter the primary key of the line that has just been inserted.
Edited by: cris on 05-abr-2011 5:28

DBMS_SCHEDULER after insert row

Similar Messages

Maybe you are looking for