Skip to Main Content

SQL & PL/SQL

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORACLE/PLSQL: ORA-04091

gkayaDec 28 2015 — edited Dec 28 2015

Hi all,

I have a package that include a procedure. I'm using this procedure for inserting data to ps_acu_sf_tahs table if provide some conditions. But when I try to run as bellow:

begin

tahs_aktarim_.tahs_aktarim('45397','T1' );

end;

I m getting error: ORA-04091

I checked out all triggers that if effect ps_acu_sf_tahs table but there is no trigger which effect that table.


I just curious about what is the problem if there is no trigger for that table.

Is there anyone who faced similar weird problem?

Regards,

Gunce

This post has been answered by Paulzip on Dec 28 2015
Jump to Answer

Comments

jmarc
in older apex version,
the error was "Error in mru internal routine: ORA-20001: Error in MRU: row= 1, ORA-20001: ORA-20001: Current version of data in database has changed since user initiated update process" .


the message is now more elegant
but i'm the only one on this sample and i have the message each time a validation fails .


any help would be very appreciate.
jmarc
i can reproduce the problem on apex.oracle.com
for the sample tabular form,

if i change in globalization the Application Primary Language from english(en) to French(France) fr .
975525
Hello there,

I've got the same issue here, do you have any update?

Apex 4.2, Application Primary Language set to French (Canada)(fr-ca).

In my case I've done some test and here is what I've found:

In a Tabular Form with a numeric field, if there is a value with a comma (ex: 12,5) in it, any validation who triggers on any other field will cause the error "Current tabular form data is too old".
If all the numerics are whole numbers, no problem.
Also, if I change the Application Primary Language to English (United States)(en-us) everything is fine.

Same thing whith a date field, if there is a date in the field, if a validation fires, same error message. If I specify a Date Format or If I set the Application Primary Language to English (United States)(en-us) everything is fine again.

I've got the same behavior on apex.oracle.com.

Regards,
Lucien
975525
Our Apex version is 4.2.0.00.28.
Regards,
Lucien
jmarc
i have opened a SR on metalink

it's a bug # 15851176.

BUG 15851176 - TABULAR FORM ADD ROW BROKEN WHEN PRIME LANG NOT ENGLISH


fixed in 4.2.1


regards
975525
Thanks JM for the update.
Regards,
Lucien
1 - 6
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Jan 25 2016
Added on Dec 28 2015
14 comments
2,881 views