Trigger no fire on SuSe80

My platform is SuSe Linux 80 and Developer Suite 9i.
My forms compile fine, but triggers no fire.
When I make : unset NLS_LANG - everything is fine - triggers fire.
Where is problem ?
NLS_LANG is my national setting, not AMERICAN_AMERICA...

the actual requirement is like this:
i have 2 tables one is having data about the total capacity of rooms in resort. that is refer by the one which is used to keep the record of booked rooms. and that trigger or scheduler is to reclaim the rooms capacity when time ends as you know room is booked for hourly basis. and this is just a simple example theres more of this type where one thing is booked and reclaimed again.Rahul,
I according to this logic - i don't think job is useful in this regard.
Question is why?
Just follow your current proposed solution ->
You say whenever room booked you will start the job though trigger to see whether you can reclaims that room or not.
Now, how do you get to know - the room is free or not? For that there must some other transaction will be taken place by any front end (or by any other application) which is validating inside in your procedure and your job continuously check that value through procedure. Am i right?
So, your job is not sufficient alone to decide that main issue whether it is ready to reclaim the room or not, except if you want to display this information to the owner about the probable available rooms after a specific time? In that case, you need this job. But, this will not show the actual available room. Correct me if i'm wrong - up to this explanation.
As a result, if we can tap that transaction which will ultimately taken place by any front end (or some other application to ensure that) then we can reclaim the room, and can directly put our trigger into that transaction without the job, thus reducing the overhead and complexity of the current logic.
I may be wrong - or not understood or missed some important place of your logic. So, please share your thought in this regard.
Regards.
Satyaki De.
Edited by: Satyaki_De on Oct 12, 2008 1:46 AM

Similar Messages

SEVERE: An error occured while scanning for the next trigger to fire

Hi All,
I followed below steps to configure Oracle BI publisher scheduler on oracle 10g database.
1.Log in to BI Publisher as a user with Administrator privileges and select the Admin tab.
2.Under System Maintenance, select Scheduler Configuration.
3.Enter the database connection information for the target Oracle database and user.
Database Type: 10g
Connection String: jdbc:oracle:thin://<hostname>:<port#>:<oracle SID>
Username/Password for the database user
Database Driver Class: oracle.jdbc.driver.OracleDriver
4.Click the Test Connection button to make sure the connection information is valid.
5.Click the Install Schema button to install the scheduler tables.
6.Restart the BI Publisher application.
The Schema installed successfully.
But when I am starting the weblogic server I am getting below error and BI publisher application is not getting up.
INFO: Handling 6 triggers that missed their scheduled fire-time.
23-Dec-2011 05:29:38 org.quartz.core.ErrorLogger schedulerError
SEVERE: An error occured while scanning for the next trigger to fire.
org.quartz.JobPersistenceException: Couldn't acquire next trigger: Couldn't retrieve trigger: Invalid column name [See nested exception: org.quartz.JobPersistenceException: Couldn't retrieve trigger: Invalid column name [See nested exception: java.sql.SQLException: Invalid column name]]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1773)
at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
* Nested Exception (Underlying Cause) ---------------
org.quartz.JobPersistenceException: Couldn't retrieve trigger: Invalid column name [See nested exception: java.sql.SQLException: Invalid column name]
at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1126)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1759)
at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
* Nested Exception (Underlying Cause) ---------------
java.sql.SQLException: Invalid column name
at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java:3372)
at oracle.jdbc.driver.OracleResultSetImpl.findColumn(OracleResultSetImpl.java:2009)
at oracle.jdbc.driver.OracleResultSet.getBinaryStream(OracleResultSet.java:668)
at org.apache.commons.dbcp.DelegatingResultSet.getBinaryStream(DelegatingResultSet.java:233)
at org.quartz.impl.jdbcjobstore.oracle.OracleDelegate.getObjectFromBlob(OracleDelegate.java:154)
at org.quartz.impl.jdbcjobstore.StdJDBCDelegate.selectTrigger(StdJDBCDelegate.java:2382)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.retrieveTrigger(JobStoreSupport.java:1115)
at org.quartz.impl.jdbcjobstore.JobStoreSupport.acquireNextTrigger(JobStoreSupport.java:1759)
at org.quartz.impl.jdbcjobstore.JobStoreTX.acquireNextTrigger(JobStoreTX.java:1176)
at org.quartz.core.QuartzSchedulerThread.run(QuartzSchedulerThread.java:233)
23-Dec-2011 05:30:55 org.quartz.core.ErrorLogger schedulerError
The system details are as below :
BI Publisher version : 10.1.3.4
Oracle DB : 10 G
Weblogic server :10.3.2
Please suggest to resolve this issue.
Thanks,
Sachin

Hi,
This errors occurs if you have configured some schema for the scheduler and configured it on BIP, but the configured schema is no longer available.
That is why I am suggesting you to replace the current quartz.properties file with the original file that exits during installation.
Then try to start the server, and see if the server starts without error.
After that you can try to configure the scheduler from BIP console.
thanks,
sandeep

Return Key doesn4t make my defined KEY-ENTER trigger to fire.

I4ve found that the trigger that fires when I press Return is KEY-NEXT-ITEM,but this doesn4t resolve my problem,because the tab key also fires this trigger.
I want to navigate within textitems with the tab key and that when I press return key make an action on the values entered in the items.
mila, PJR

You have to perform key mapping to get the Key-Enter trigger to work.
Open your forms90\fmrweb.res file in a text editor. Find the line:
10 : 0 : "Return" : 27 : "Return"
Change it to:
10 : 0 : "Return" : 75 : "Return"
Save the file and run the form again. The key-enter trigger should then fire when you press the Return key, but not when you press the Tab key.

Trigger should fire on Mouse Selection from List

Hi,
I have two list item type boxes in which first one is populated on when-new-block-instance trigger I want to populate second on the basis of first list item selection which trigger should I use b/c I already tried mouse-click but it fires on just clicking on list box not provide the selection of individual item and also mouse double click and mouse enter both are suffice the requeirement.
One thing more I have defined key-next-item trigger on the above first list item but once I click on this list item the key-next-item trigger will be disabled automatically or not fired.
Thanks and regards
Message was edited by:
skhawar03

Hi,
When-mouse-click as I understand you can't use in case of poplist b/c if you click on poplist this trigger will fire and does not allow you to do anything, regarding when-mouse-enter this trigger doesn't work I have used this trigger but how it fires I don't understand, if anyone know tell me, thanks.

How can I force a database trigger to fire only if there is an update not when insert

Hi
Could you help me please. I have a data base trigger that need
to fire only when there is an update in some columns in a table
But the trigger is firing eventhough they only do an insert.
here is the begining of the trigger.
create or replace trigger alpha_HZ_LOCATIONS_AUR
after update of address1,address2,city,state
,postal_code,county,province,country,attribute20
on hz_locations
for each row
DECLARE
v_cust_account_id hz_cust_acct_sites_all.cust_account_id%type;
v_cust_acct_site_id hz_cust_acct_sites_all.cust_acct_site_id%
type;
v_org_id hz_cust_acct_sites_all.org_id%type;
-- cursor; all sites for this customer address
cursor sc is
select
s.site_use_id site_use_id
,s.attribute15 frk_addr_number
from
ra_site_uses_all s
where s.address_id = v_cust_acct_site_id
and s.site_use_code in ('BILL_TO','SHIP_TO');
rowcnt number;
v_system_code varchar2(15);
v_ora_cust_num varchar2(30);
v_frk_cust_num varchar2(15);
v_insert_update_flag varchar2(1);
BEGIN
v_insert_update_flag := 'U';
-- get cust_acct_site_id (address_id)
begin
select acct_site.cust_account_id,
acct_site.cust_acct_site_id, acct_site.org_id
into v_cust_account_id, v_cust_acct_site_id, v_org_id
from
hz_party_sites party_site
,hz_cust_acct_sites_all acct_site
where acct_site.party_site_id = party_site.party_site_id
and party_site.location_id = :new.location_id;
Thank you much
alpha

Thanks for the response. My trigger is firing when I update the
table trough a form. Also when the uses go into the oracle apps
and create a new customer they get an error saying
ora-01403 no data found
ora-06512 at'the trigger name' and gives line number
ora-04088 error during execution of trigger.
Note: and I looked trigger it's really ok.
If you can please help

Trigger which fire on a specific time ?

Hello expert,
my requirement is to automatically cancel requisition's which are older than 3 day's.
for this i have to create some trigger. i created a trigger on database startup , but if i do not restart my server than
it will not work.
i also have create dml trigger but may be it will fire unnecessarily. so suggest me some process which check on some specific time in database
and cancel the requisition.
Thanks
yash

>
i create procedure and create a job by scheduler. and its working.
but i did not understand the dbms_scheduler.create_schedule .
i used dbms_scheduler.create_job to create a job with procedure to called.
but how to attach procedure with dbms_scheduler.create_schedule ???
>
You don't need to. You can just specify the repeat_interval like the example in the link shows
BEGIN
DBMS_SCHEDULER.create_job (
    job_name        => 'test_full_job_definition',
    job_type        => 'PLSQL_BLOCK',
    job_action      => 'BEGIN my_job_procedure; END;',
    start_date      => SYSTIMESTAMP,
    repeat_interval => 'freq=hourly; byminute=0; bysecond=0;',
    end_date        => NULL,
    enabled         => TRUE,
    comments        => 'Job defined entirely by the CREATE JOB procedure.');
END;
/That example shows that the job will run every hour on the hour. You need to decide how often your job and procedure should run. The procedure should check for cancellations.
You also need to start revisiting your previous 155 (81 unresolved) threads and mark them ANSWERED as appropriate.

When new record instance trigger at Fire Enter Query event is throwing erro

HI
I have the following code on when new record instance which is set to fire at Enter Query Mode
IF :SYSTEM.BLOCK_STATUS <> 'QUERY' THEN
rec_num:=Get_Block_Property( 'MASTER', CURRENT_RECORD);
GO_ITEM('DETAIL.ITEM_NAME');
CLEAR_BLOCK(NO_VALIDATE);
GO_BLOCK('MASTER');
GO_RECORD(rec_num);
END IF;
But this is throwing error when I am querying record on master block.
It says 'Function not allowed.Please see a list of keys or functions'
Thanks in advance.

hi,
GO_ITEM( ) procedure is resctricted procedure.It can not be used in Enter Query mode to navigate to an item in a different block.
You can check wheter rest of the procedures are Enter Query Mode -Yes/No thourgh forms help window.
Message was edited by:
Manish.Sharma

Triggers no fire on SuSe80 Linux

My platform is SuSe Linux 80 and Developer Suite 9i.
My forms compile fine, but triggers no fire.
When I make : unset NLS_LANG - everything is fine - triggers fire.
Where is problem ?
NLS_LANG is my national setting, not AMERICAN_AMERICA...

Sorry, folks. Forgot the obvious. Compiling on the destination architecture fixed the problems.

What trigger can fire when execute_query occurs?

I have a form where the new form instance trigger calls execute_query (parameters bring the query
field info). I need the code in some when-radio-changed triggers to execute when execute_query occurs
as well. What is the easiest way to do this? (I do not find when-new-item-instance firing at execute_query).
forms 11.1.1.4
Is the only way to do this to put each when-radio-changed in its own procedure and call each explicitly?
(since you can't call a when-radio-changed trigger by name with execute_trigger (why?)).
Well since I wrote that I did put the triggers in procedures and call them and that does work.
Seems to me in forms6i the when new item instance trigger would've fired. This is definitely a whole
new ballgame it seems.
Edited by: lake on Jun 16, 2011 12:28 PM

write the code in the POST-QUERY trigger for this purpose.

Db trigger that fires when new user created?

I need to set up a trigger so that whenever a new user is created in our application, user info should be inserted into an application table.
So I assumed that a trigger on CREATE DDL event will do the trick. But when I looked up trigger syntax, it asks me the schema name on which I want to define the trigger.
Is it possible to do it at all?

create or replace trigger create_user_trigger
after create on database
begin
if ora_dict_obj_type = 'USER' then
-- action
end if;
end;
/

If any body logon to oracle any trigger will fire???

Hai,
Just i would like to know that if any body logon to oracle his terminal name and username will be noted in v$session, But i want to refuse particular user when ever user logon to oracle. i mean just like triggers on tables is there any event like that.
And also i want to execute some script when ever user logon to oracle.
If possible please give me answer.
Thanks
null

Check event triggers for details in
http://technet.oracle.com/docs/products/oracle8i/doc_library/817_doc/appdev.817/a76939/adg14evt.htm#999369

Which trigger fires when i press cancel query button in oracle d2k forms.

hi all,
i have simply press then enter query but didn't enter anything in form and then press the cancel query. so i just want to know that what trigger will fire when i press the cancel query button in d2k form.
Regards,
kam.

Why not ask into Forms<br>
<br>
Nicolas.

Timer fires during trigger processing on web

I was looking for a way to augment the default behaviour
of a hierarchical tree. The trouble is clicking in a tree can fire various combinations of WHEN-MOUSE-CLICK, WHEN-TREE-NODE-SELECTED, WHEN-TREE-NODE-EXPANDED,
WHEN-TREE-NODE-ACTIVATED, WHEN-MOUSE-DOUBLE-CLICKED. I wanted to trigger some action after they had finished firing but as I didn't know which would fire last, where to put the code ?
The solution I found was to start a 1 ms timer in WHEN-MOUSE-CLICK (which always fires first), gather information from the other triggers into a variable, and do my processing in WHEN-TIMER-EXPIRED. This worked fine on client/server but when I deployed it on the web I found the timer expired between WHEN-MOUSE-CLICK and WHEN-TREE-NODE-SELECTED (triggered by a single click).
My understanding of timers is that, however short their duration, they should not expire during trigger processing. Have I got this wrong or is this a bug ?
It seems to work OK with 5 ms but I would like to know what is going on.
(f6i patch 7)

All,
as promised, here's an answer from development. Duncan said it already, but here's the long version
1). Regarding timers in general. 1ms timers fire on the server (effectively,
at the time the timer is created in a trigger, we put a timer macro on the
stack so that that next time we go for input (after we've processed all
of the events we've already gotten at that point), it will act as if the timer
has expired. This, as you know, prevents us from doing round-trips to the
client when people are simply creating a timer to get around some of the
restricted built-in/trigger issues. Any timer of longer than 1ms will get
created on the client and thus cause round-trips. We have no plans to
bump that threshhold up, so people could use 2ms timers if they wanted...
2). Regarding timers expiring during trigger processing. It is true in both
client/server and web that we will not expire a timer while a trigger is
firing. However, the order in which the user will see events (and thus
which triggers will fire in) can vary. In the example that was given,
the user (double)clicks on a node in the tree on the client. The first
mouse click causes a message/event to be sent immediately to the
server, which ends up causing the when-mouse-clicked trigger to fire.
As soon as that message is sent, the server starts processing that
trigger. In the meantime, the client may decide that it needs to send
other messages (such as when-node-selected, etc.). However, until
the server sends a return-message to the client asking for more input,
this won't get sent. Now, the server fires the when-mouse-click trigger,
and as part of it a timer gets created. There are two possible scenarios
here.
In the first scenario, the timer is 1ms, and thus is handled on the
server. Thus, when the trigger ends, the server sees if there is any more
input to be processed, and sees that the timer has expired (because, as
I explained above, this gets put directly onto the macro stack). Thus, the
timer expired trigger fires. After that trigger fires, the server sees that it
has no more input waiting, and sends a message to the client telling it to
send more input. At that point, the client can send whatever other events
it has queued up (such as the when-node-selected) and we carry on.
In the second scenario, the timer is more than 1ms long. In this case, when
the trigger says to create a timer, the server queues up a message to send
to the client telling it to create a timer. When the rest of the trigger is complete
and the server sees that it has no more events to process, it sends this timer
creation message to the client at the same time it asks the client to give it
more events. The client sends the when-node-selected event, the server
processes it, and eventually asks the client for more input. By then, the
timer has expired and then the timer message gets sent to the server.
In neither of these cases does the timer trigger fire in the middle of
another trigger that is already firing, it is simply that the separate triggers
might fire in a different order because of the order that the underlying
events are processed. In client/server, the process is effectively the same
as the 2nd scenario above, because the timer is handled by the toolkit, just
like the other events, and thus the message for the timer expiring will get
sent to Forms after any of the events related to the mouse click. But again,
the rule about timers firing during trigger processing is not violated, it is just
that there is a break between triggers that can allow a 1ms timer to fire
'sooner' on the web than in client/server.
Fran

How to fire a schema trigger from outside the schema

A user is using an ad hoc tool similar to SQL Developer called PeopleSoft Application Designer.
He creates a connection to the db, then issues an alter session set current_schema = 'restricted_schema'. The connected user does not have direct privileges on the "restricted_schema" which they call SYSADM.
After changing the schema context in that manner he creates objects in SYSADM. A schema trigger is then fired and grants privileges on the new objects created in SYSADM. Doing the same in either SQL Plus or SQL Developer does not fire the schema trigger.
I think SQL Plus and SQL Dev are working as they should. Altering the session like that does not change your identity - just the schema context. But, when you examine v_$session, the connection with this other tool looks exactly the same as one from SQL Plus or SQL Dev when changing the schema context in the session.
Instead of trying to figure out what this other tool is doing, is there any way for that schema trigger to fire when using this process from one of our tools?

>
A user is using an ad hoc tool similar to SQL Developer called PeopleSoft Application Designer.
He creates a connection to the db, then issues an alter session set current_schema = 'restricted_schema'. The connected user does not have direct privileges on the "restricted_schema" which they call SYSADM.
After changing the schema context in that manner he creates objects in SYSADM. A schema trigger is then fired and grants privileges on the new objects created in SYSADM. Doing the same in either SQL Plus or SQL Developer does not fire the schema trigger.
>
The user CANNOT create objects in any schema without the proper privileges.
Setting the current_schema parameter does not confer ANY additional privileges to a user. See ALTER SESSION in the SQL language doc
http://docs.oracle.com/cd/E14072_01/server.112/e10592/statements_2013.htm
>
CURRENT_SCHEMA
Syntax:
CURRENT_SCHEMA = schema
The CURRENT_SCHEMA parameter changes the current schema of the session to the specified schema. Subsequent unqualified references to schema objects during the session will resolve to objects in the specified schema. The setting persists for the duration of the session or until you issue another ALTER SESSION SET CURRENT_SCHEMA statement.
This setting offers a convenient way to perform operations on objects in a schema other than that of the current user without having to qualify the objects with the schema name. This setting changes the current schema, but it does not change the session user or the current user, nor does it give the session user any additional system or object privileges for the session.
>
If the user connects and sets SYSADM as the current schema and creates objects in SYSADM the user already had privileges to create objects in the SYSADM schema; setting the current schema has nothing to do with it.
So your issue is that the user has privileges to create objects in the SYSADM schema; you need to revoke those privilges (or the role that grants them) to solve your problem.

Insert 50 rows, fire trigger once

Is there a way to create a trigger that fires once after several inserts, instead of firing for each inserted row.
I want the trigger to fire once for a transaction.

An easier way is to use the after update trigger and leave out the "for each row". The trigger will only fire once for each update statement, even if the statement altered a million rows.

Trigger no fire on SuSe80

Similar Messages

Maybe you are looking for