Problem DB Trigger and ADF Application for update a field.

I again,
I have a Data Base table as following :
--Solicitudes*
id number not null,
extern_code integer,
delivery_date timestamp( 6 ),
... and more fields
And a Trigger as following :
create or replace trigger update_delivery_date
before update of on Solicitudes
for each row
begin
if ( :new.extern_code = 9 ) then -- I need update the "delivery_date" to the current date and timestamp
select systimestamp into :new.delivery_date from dual;
end if;
end;
The trigger works fine in the DB, but when I update the 'Solicitudes' data base table through the ADF Application, the 'delivery_date' field is updated to different current systimestamp , for example suppose right now is : 19-JUN-*2012** 10.45.30.773000000 PM -04:00 , it field should be update to this date, but it is not update to that date, it is update to : 10-DEC-*1989* 10.45.30.773000000 PM -04:00.
Why is this ?
I put in the SQL Developer's query editor : select systimestamp from dual; and it show me the correct date and time.
That problem occurs only when I update the table through my ADF Application.

Marco,
I don't see any issue with ADF in this. Just tried with a dummy table created with similar structure and tried updating it (have a similar trigger as well). It updated with proper timestamp (tried from SQL Developer, AppModule Tester and in jspx page - all same result).
Can you check the system date on the machine where your DB is hosted. I guess you are using different database for testing the query and the app is using a different db.
If not, try creating a simple testcase (as I mentioned in the first line) and see if you are able to reproduce the issue.
-Arun
P.S : I tried this in 11.2.0.1 DB & JDev 11.1.2.0.0

Similar Messages

I'm trying to update my Photoshop CS5, but continue to receive the same problem every time. The application manager update dialogue box simply states "some updates failed to install." There's no specific error code, but a link to contact support for furth

I'm trying to update my Photoshop CS5, but continue to receive the same problem every time. The application manager update dialogue box simply states "some updates failed to install." There's no specific error code, but a link to contact support for further assistance. It doesn't take me to customer support, but does take me to a screen which states. "Error "This serial number is not for a qualifying product." I've checked my account and the product serial number is associated with my account., so I don't see any problem. I have not been able to find a resolution to this problem, so I hope that someone can point me in the right direction. Thank you!

update directly, Product updates

Problem with trigger and entity in JHeadsart, JBO-25019

Hi to all,
I am using JDeveloper 10.1.2 and developing an application using ADF Business Components and JheadStart 10.1.2.27
I have a problem with trigger and entity in JHeadsart
I have 3 entity and 3 views
DsitTelephoneView based on DsitTelephone entity based on DSIT_TELEPHONE database table.
TelUoView based on TelUo entity based on TEL_UO database table.
NewAnnuaireView based on NewAnnuaire entity based on NEW_ANNUAIRE database view.
I am using JHS to create :
A JHS table-form based on DsitTelephoneView
A JHS table based on TelUoView
A JHS table based on NewAnnuaireView
LIB_POSTE is a :
DSIT_TELEPHONE column
TEL_UO column
NEW_ANNUAIRE column
NEW_ANNUAIRE database view is built from DSIT_TELEPHONE database table.
Lib_poste is an updatable attribut in TelUo entity, DsitTelephone entity, NewAnnuaire entity.
Lib_poste is upadated in JHS table based on TelUoView
I added a trigger on my database shema « IAN » to upadate LIB_POSTE in DSIT_TELEPHONE database table :
CREATE OR REPLACES TRIGGER “IAN”.TEL_UO_UPDATE_LIB_POSTE
AFTER INSERT OR UPDATE OFF lib_poste ONE IAN.TEL_UO
FOR EACH ROW
BEGIN
UPDATE DSIT_TELEPHONE T
SET t.lib_poste = :new.lib_poste
WHERE t.id_tel = :new.id_tel;
END;
When I change the lib_poste with the application :
- the lib_poste in DSIT_TELEPHONE database table is correctly updated by trigger.
- but in JHS table-form based on DsitTelephoneView the lib_poste is not updated. If I do a quicksearch it is updated.
- in JHS table based on NewAnnuaireView the lib_poste is not updated. if I do a quicksearch, I have an error:
oracle.jbo.RowAlreadyDeletedException: JBO-25019: The row of entity of the key oracle.jbo. Key [null 25588] is not found in NewAnnuaire.
25588 is the primary key off row in NEW_ANNUAIRE whose lib_poste was updated by the trigger.
It is as if it had lost the bond with the row in the entity.
Could you help me please ?
Regards
Laurent

The following example should help.
SQL> create sequence workorders_seq
2 start with 1
3 increment by 1
4 nocycle
5 nocache;
Sequence created.
SQL> create table workorders(workorder_id number,
2 description varchar2(30),
3   created_date date default sysdate);
Table created.
SQL> CREATE OR REPLACE TRIGGER TIMESTAMP_CREATED
2 BEFORE INSERT ON workorders
3 FOR EACH ROW
4 BEGIN
5 SELECT workorders_seq.nextval
6    INTO :new.workorder_id
7    FROM dual;
8 END;
9 /
Trigger created.
SQL> ALTER SESSION SET NLS_DATE_FORMAT = 'DD-MON-YYYY HH24:MI:SS';
Session altered.
SQL> insert into workorders(description) values('test1');
1 row created.
SQL> insert into workorders(description) values('test2');
1 row created.
SQL> select * from workorders;
WORKORDER_ID DESCRIPTION                    CREATED_DATE
           1 test1                          30-NOV-2004 15:30:34
           2 test2                          30-NOV-2004 15:30:42
2 rows selected.

Re: Transactions and Locking Rows for Update

Dale,
Sounds like you either need an "optimistic locking" scheme, usually
implemented with timestamps at the database level, or a concurrency manager.
A concurrency manager registers objects that may be of interest to multiple
users in a central location. It takes care of notifying interested parties
(i.e., clients,) of changes made to those objects, using a "notifier" pattern.
The optimistic locking scheme is relatively easy to implement at the
database level, but introduces several problems. One problem is that the
first person to save their changes "wins" - every one else has to discard
their changes. Also, you now have business policy effectively embedded in
the database.
The concurrency manager is much more flexible, and keeps the policy where
it probably belongs. However, it is more complex, and there are some
implications to performance when you get to the multiple-thousand-user
range because of its event-based nature.
Another pattern of lock management that has been implemented is a
"key-based" lock manager that does not use events, and may be more
effective at managing this type of concurrency for large numbers of users.
There are too many details to go into here, but I may be able to give you
more ideas in a separate note, if you want.
Don
At 04:48 PM 6/5/97 PDT, Dale "V." Georg wrote:
I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save'button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
>
>
>
>
====================================
Don Nelson
Senior Consultant
Forte Software, Inc.
Denver, CO
Corporate voice mail: 510-986-3810
aka: [email protected]
====================================
"I think nighttime is dark so you can imagine your fears with less
distraction." - Calvin

We have taken an optimistic data locking approach. Retrieved values are
stored as initial values; changes are stored seperately. During update, key
value(s) or the entire retieved set is used in a where criteria to validate
that the data set is still in the initial state. This allows good decoupling
of the data access layer. However, optimistic locking allows multiple users
to access the same data set at the same time, but then only one can save
changes, the rest would get an error message that the data had changed. We
haven't had any need to use a pessimistic lock.
Pessimistic locking usually involves some form of open session or DBMS level
lock, which we haven't implemented for performance reasons. If we do find the
need for a pessimistic lock, we will probably use cached data sets that are
checked first, and returned as read-only if already in the cache.
-DFR
Dale V. Georg <[email protected]> on 06/05/97 03:25:02 PM
To: Forte User Group <[email protected]> @ INTERNET
cc: Richards* Debbie <[email protected]> @ INTERNET, Gardner*
Steve <[email protected]> @ INTERNET
Subject: Transactions and Locking Rows for Update
I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for
any
ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
------ Message Header Follows ------
Received: from pebble.Sagesoln.com by notes.bsginc.com
(PostalUnion/SMTP(tm) v2.1.9c for Windows NT(tm))
id AA-1997Jun05.162418.1771.334203; Thu, 05 Jun 1997 16:24:19 -0500
Received: (from sync@localhost) by pebble.Sagesoln.com (8.6.10/8.6.9) id
NAA11825 for forte-users-outgoing; Thu, 5 Jun 1997 13:47:58 -0700
Received: (from uucp@localhost) by pebble.Sagesoln.com (8.6.10/8.6.9) id
NAA11819 for <[email protected]>; Thu, 5 Jun 1997 13:47:56 -0700
Received: from unknown(207.159.84.4) by pebble.sagesoln.com via smap (V1.3)
id sma011817; Thu Jun 5 13:47:43 1997
Received: from tes0001.macktrucks.com by relay.macktrucks.com
via smtpd (for pebble.sagesoln.com [206.80.24.108]) with SMTP; 5 Jun
1997 19:35:31 UT
Received: from dale by tes0001.macktrucks.com (SMI-8.6/SMI-SVR4)
id QAA04637; Thu, 5 Jun 1997 16:45:51 -0400
Message-ID: <[email protected]>
Priority: Normal
To: Forte User Group <[email protected]>
Cc: "Richards," Debbie <[email protected]>,
"Gardner," Steve <[email protected]>
MIME-Version: 1.0
From: Dale "V." Georg <[email protected]>
Subject: Transactions and Locking Rows for Update
Date: Thu, 05 Jun 97 16:48:37 PDT
Content-Type: text/plain; charset=US-ASCII; X-MAPIextension=".TXT"
Content-Transfer-Encoding: quoted-printable
Sender: [email protected]
Precedence: bulk
Reply-To: Dale "V." Georg <[email protected]>

Problem in downloading and installing application ...

hey
m havng problem in downloading and installing application on mah x2-01 . many times i tried to dwnload whatsapp to mah phn and if the application isz downloaded thn while verifyng the no. it says error unitterupted problem in contacting the server . so knw wht shud i do . i hav also restrore mah phn thn too. plz help me

You may verify first your mobile number from this link. Make sure to sign in and under Mobile numbers, click Verify now.

TS1492 When I go to iTunes and then check for updates. I can not do this action due to the fact iTunes will not connect to the internet although the internet is working just fine, what do I do to fix this issue? Apparently I am currently using iTunes 7.0.

When I go to iTunes and then check for updates. I can not do this action due to the fact iTunes will not connect to the internet although the internet is working just fine, what do I do to fix this issue? Apparently I am currently using iTunes 7.0.

If you're really using iTunes 7.0 you are very far behind the current version - maybe it is trying to connect to a decomissioned server. In fact I am kind of surprised it will run on a Macbook Air. Are you sure you are running iTunes 7?

HT201359 Provide the version numbers of your operating system and relevant applications, for example "iOS 6.0.3" or "iPhoto 9.1.2".

Provide the version numbers of your operating system and relevant applications, for example "iOS 6.0.3" or "iPhoto 9.1.2".

What is the question?

I cant update my iphone and i tried going on my pc on itunes and clicking check for update button but it says that "itunes could not contact the iphone software update server because you are not connected to the internet".plz help

i cant update my iphone and i tried going on my pc on itunes and clicking check for update button but it says that "itunes could not contact the iphone software update server because you are not connected to the internet". But i checked my internet on both my pc and iphone and tried again but it still says the same thing. plzz plzz help

Were you definitely connected to the internet at the time? If you don't have iOS 5 on your iPhone then the only way to update it would be via iTunes, once updated to the latest version of iOS you'll be able to update your iPhone without connecting to iTunes "over-the-air".
Before updating however it goes without saying to Backup your iPhone, this should happen by default upon connecting your iPhone to iTunes.
Regards,
Steve

Error using Bapi_PO_Change for update custom fields

Dear Expert,
I have requirement for update custom field in table ekko. I used BAPI_PO_CHANGE with PO_number as a key. Then i put the value of custom field in segment TABLES - EXTENSIONIN.
But I get error : "ERROR TRANSFERING EXTENSIONIN DATA FOR ENHANCEMENT CI_EKKODB".
When I checked, I found the difference between data type the value for BAPI_PO_CHANGE (Usinf structure BAPIPAREX) and data type for custom field in table EKKO.
Data Type in BAPI_PO_CHANGE is CHAR (you can see in structure BAPIPAREX). And data type for the custom field is DECIMAL.
I found the note '1124803', but the correction note was not applicable for us because our released system is 500.
Is there any suggestion or solution for resolve our problem?
Really appreciate your help.
Thanks.

Hi Laxmikanth Bethi ,
I tried with BAPI_PO_CHANGE in level header, and SAP was support the BAPI. And also i tried to appending the same fields in MEPOHEADR & MEPOHEADERX structures, but the problem is the type of my custom fields are DECIMAL, then the type MEPOHEADR & MEPOHEADERX structures are CHARACTER. So i got the error : "ERROR TRANSFERING EXTENSIONIN DATA FOR ENHANCEMENT CI_EKKODB".
Because the types are difference.
Have you any suggestion to solve this problem?
Really appreciate for your input.

Problem with trigger and mutating table

Hello,
I have a problem with the following trigger. Everytime it starts I got an error message:
ORA-04091: table ccq_test.QW_QUALIFIER is mutating, trigger/function may not see it
ORA-06512: at "QW_AFTER_UPDATE_ALL", line 3
ORA-06512: at "QW_AFTER_UPDATE_ALL", line 10
ORA-04088: error during execution of trigger 'QW_AFTER_UPDATE_ALL'
Here is the trigger:
CREATE OR REPLACE TRIGGER qw_after_update_all
AFTER UPDATE ON ccq_test.QW_QUALIFIER FOR EACH ROW
DECLARE
     CURSOR c1 IS SELECT id AS mx FROM QW_QUALIFIER_LOG WHERE msgid = :NEW.msgid AND messagedate BETWEEN SYSDATE - (1 / (24 * 60 * 6)) AND SYSDATE AND transfer = 1;
     CURSOR c_qwprod IS SELECT value FROM ccq_test.QW_QUALIFIER WHERE msgid = :NEW.msgid AND name = 'product';
     CURSOR c_qwgesch IS SELECT value FROM ccq_test.QW_QUALIFIER WHERE msgid = :NEW.msgid AND name = 'geschaeftsfall';
     qw_rec c1%ROWTYPE;
     qw_prod c_qwprod%ROWTYPE;
     qw_gesch c_qwgesch%ROWTYPE;
BEGIN
OPEN c1;
OPEN c_qwprod;
OPEN c_qwgesch;
     FETCH c1 INTO qw_rec;
     FETCH c_qwprod INTO qw_prod;
     FETCH c_qwgesch INTO qw_gesch;
     IF c1%NOTFOUND THEN
          IF (:NEW.name = 'product') THEN
               INSERT INTO QW_QUALIFIER_LOG VALUES (QW_QUALIFIER_LOG_SEQ.NEXTVAL, :NEW.msgid, :NEW.value, qw_gesch.value, SYSDATE, 1);
          ELSE
          INSERT INTO QW_QUALIFIER_LOG VALUES (QW_QUALIFIER_LOG_SEQ.NEXTVAL, :NEW.msgid, qw_prod.value, :NEW.value, SYSDATE, 1);
     END IF;
     ELSE
          IF (:NEW.name = 'product') THEN
               UPDATE QW_QUALIFIER_LOG SET product=:NEW.value, messagedate=SYSDATE WHERE id = qw_rec.mx;
          ELSE
               UPDATE QW_QUALIFIER_LOG SET geschaeftsfall=:NEW.value, messagedate=SYSDATE WHERE id = qw_rec.mx;
     END IF;
     END IF;
CLOSE c1;
END;
Can anyone help me?

You are trying to lookup data from qw_qualifier you are currently modifying. You could see the data in a inconsistent way and Oracle is protecting you from it.
You could read here about how to program around this problem.
But: your table design seems questionable. You have two records for qw_qualifier and you are trying to log it into one qw_qualifier_log record. Maybe you could fix that, and the need for querying the same table as you are updating is removed.
Regards,
Rob.

I am having many problems with the CC 2014 application manager update

I have 2 seats. Thus I have CC 2014 installed on four computers. All four are high end desktops with Windows 7 Ultimate 64 bit installed, all four with the latest patches. All four also use high end nvidia graphics cards all with the latest drivers.
On all four, when I tried to update the application manager, only the frame of update the window was visible. Then, when I moused over the empty frame, the blue update button became visible, but nothing else. Since the common thread is nvidia drivers, it seems there may be a conflict. But one card is a Quadro FX 5800, another is 2x SLI NVIDIA GeForce GTX 285, another is an NVIDIA GeForce GTX 680 2GB, and the fourth is an NVIDIA GeForce GTX 780 3Gb. So all four have different cards.
I went ahead and installed the app mgr update and all the program updates on all four computers. All four had problems, two of them serious.
On one computer, there were problems booting up. The boot up problems went away when I restored to a prior image. I tried several times. The problem persisted. I finally gave up on updating this computer.
This boot up problem then happened on a second computer. I restored to a prior image and the problem went away here as well. I then tried the installs again. This time, the computer booted fine, but I lost the ability to send email. I use Thunderbird and have had no problems sending email ever (for at least the past 8 years). So I again restored to a prior image and the email problem went away. I then tried the installs a third time. Same result. Investigating, I was able to get an alternate outgoing mail server to work (that of my company site). But I never got the Verizon server to work. Incoming? Yes. But no outgoing.
On the third computer, I also had problems booting. But rebooting many times seems to have solved the problem. Unfortunately, Premiere crashes so often I've reverted to CC.
I realize that Adobe puts much work into making their software better. And I depend on it every day. But to be honest, I've just spent several whole days trying to fix broken computers. And my confidence in Adobe is at an all time low.
I so regret not staying with CC.

>regret not staying with CC
Previous via Cloud http://helpx.adobe.com/creative-cloud/help/install-apps.html#previous

Transactions and Locking Rows for Update

I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
[email protected]------------------

I have a problem in the application I am currently working on, which it
seems to me should be easily solvable via appropriate use of transactions
and database locking, but I'm having trouble figuring out exactly how to
do it. The database we are using is Oracle 7.2.
The scenario is as follows: We have a window where the user picks an
object from a dropdown list. Some of the object's attributes are then
displayed in that window, and the user then has the option of editing
those attributes, and at some point hitting the equivalent of a 'save' button
to write the changes back to the database. So far, so good. Now
introduce a second user. If user #1 and user #2 both happen to pull up
the same object and start making changes to it, user #1 could write back
to the database and then 15 seconds later user #2 could write back to the
database, completely overlaying user #1's changes without ever knowing
they had happened. This is not good, particularly for our application
where editing the object causes it to progress from one state to the next,
and multiple users trying to edit it at the same time spells disaster.
The first thing that came to mind was to do a select with intent to update,
i.e. 'select * from table where key = 'somevalue' with update'. This way
the next user to try to select from the table using the same key would not
be able to get it. This would prevent multiple users from being able to
pull the same object up on their screens at the same time. Unfortunately,
I can think of a number of problems with this approach.
For one thing, the lock is only held for the duration of the transaction, so
I would have to open a Forte transaction, do the select with intent to
update, let the user modify the object, then when they saved it back again
end the transaction. Since a window is driven by the event loop I can't
think of any way to start a transaction, let the user interact with the
window, then end the transaction, short of closing and re-opening the
window. This would imply having a separate window specifically for
updating the object, and then wrapping the whole of that window's event
loop in a transaction. This would be a different interface than we wanted
to present to the users, but it might still work if not for the next issue.
The second problem is that we are using a pooled DBSession approach
to connecting to the database. There is a single Oracle login account
which none of the users know the password to, and thus the users
simply share DBSession resources. If one user starts a transaction
and does a select with intent to update on one DBSession, then another
user starts a transaction and tries to do the same thing on the same
DBSession, then the second user will get an error out of Oracle because
there's already an open transaction on that DBSession.
At this point, I am still tossing ideas around in my head, but after
speaking with our Oracle/Forte admin here, we came to the conclusion
that somebody must have had to address these issues before, so I
thought I'd toss it out and see what came back.
Thanks in advance for any ideas!
Dale V. Georg
Indus Consultancy Services [email protected]
Mack Trucks, Inc. [email protected]
[email protected]------------------

Problem while deploying the ADF application in weblogic 10.3

Hi,
We did the application using ADF and EJB3.0 in JDeveloper11g relese and this application is working fine when i run in the JDeveloper release. When i try to deploy the same application in weblogic 10.3(Which I downloded and installed) i am getting following error.
shared library "adf.oracle.domain" could not be found.
Can any one tell me, what the problem is?
Thanking you,
NIRANJAN REDDY.

person with many names,
You need to configure the WLS domain for ADF.
http://download.oracle.com/docs/cd/E12839_01/install.1111/e13666/toc.htm#wls_adf
John

Language problem in Travel and Expense Application

Hi ,
We have travel and expense application currently running.
We are supporting that the user can use his browser language to view the content on the travel and expense application.
The problem occurs only on IE 7.0 and higer and also in firesfox 3.0.
We are on SP15 where sap supports IE 7.0.
When the user selects the international version of the language in IE 7.0 or IE8.0 like fr-FR or de-DE or es-ES it gives german by default for any language selected.
But if we select country specific language which like fr-CA or es-AR it works fine and shows the right language.
We have set our JCO language to be empty for using browser langauge.
We do not have user profile language enabled on the portal so users cannot set their language other than in the portal.
The links on the area group page show in right language.
The problem is seen when the user clicks on create expense report link and is in the webdynpro application.
I have opened an OSS note for this.Could anyone test the same scenario on your browsers on portal with version 7.0 having the same issue.Please make sure your browser is version IE 7.0 or higher
Regards
swathi

Dear Swati,
Got any solution for this.
If then, Please update.
Warm regards
Hari Sankar M

Problems Oracle 9iDB and ASO Configuration for Cybersafe

Oracle 9iDB installation on Solaris with ASO option
Objective
My objective is to configure Oracle 9iDB, Release 9.0.1 ASO on Solaris for external authentication using Cybersafe ActiveTRUST, which is a Kerberos, based authentication product.
Question
Getting ORA-12641: Authentication Service failed to initialize when trying to connect to Oracle 9iDB using sqlplus from a Oracle 9i Client machine, when ASO is configured for Cybersafe authentication on both Oracle 9iDB and Oracle 9i client
Can anyone help me setup Oracle 9iDB and Oracle 9i client for ASO using Cybersafe Authentication?
Environment
1. I have a Solaris box as my Oracle 9iDB server
2. I have an NT Server as my Authentication server and Oracle 9i Client.
Installation Procedure
I installed as per the steps given in the doc, Oracle Advanced Security Administrators Guide, Release 9.0.1
Authentication Server / Oracle Client setup (NT Server)
I installed on the NT Server the following
1. CyberSafe ActiveTRUST 4.0 Security Server on the NT Server, which acts as an Authentication server.
2. CyberSafe ActiveTRUST 4.0 Security Client
3. Cybersafe Application Security Toolkit (GSS runtime libraries) as needed by Oracle ASO setup procedures.
4. Oracle 9i Client, custom installations with ASO option.
Oracle 9iDB Server Setup (Solaris Server)
I installed on the Solaris Server the following
1. CyberSafe ActiveTRUST 4.0 Security Client
2. Cybersafe Application Security Toolkit (GSS runtime libraries)
3. Oracle 9iDB server, custom installation, with ASO option selected.
Installation of all the above components is successful.
Note: Installation of Oracle 9iDB server with ASO option never prompted me to choose a Authentication mechanism like Cybersafe, or Kerberos or Radius etc..,
Note: Oracle 8.1.7 DB installation on NT actually prompted for Authentication mechanism selection.
ASO Configuration:
I configured ASO on the Oracle server and client side as mentioned in chapter 5 of Oracle Advanced Security Administrators Guide, Release 9.0.1
I created an external user in Oracle, [email protected] as mentioned in http://download-uk.oracle.com/otndoc/oracle9i/901_doc/network.901/a90150/1004747
I configured the NT server, Oracle 9i client for ASO using Net8 Assistant and I have the sqlnet.ora file.
ASO Problems:
Once I have configured both Oracle 9i client and 9iDB server for ASO, I am not able to log in to the database using sqlplus /@cybr.
It returns with an error ORA-12641, saying Authentication Services Failed to Initialize.
I could not get much help from questions posted on metalink on ORA-12641.
It looks like Solaris 9iDB could not recognize cybersafe even though, Cybersafe is listed as one of the installed adapters, when I ran # $ORACLE_HOME/bin/adapters. From this, it looks like Cybersafe adapter is linked to ASO.
Oracle Server is not able to initialize authentication services and call the authentication server at all.
Can anyone help me setup Oracle 9iDB and Oracle 9i client for ASO using Cybersafe Authentication?

The problem has been resolved after providing cn=orcladmin instead of orcladmin for the OID user admin user. Now the overall sso solution is working fine with ADF applications.
Regards,
S R Prasad

Problem DB Trigger and ADF Application for update a field.

Similar Messages

Maybe you are looking for