Discussions
Categories
- 381.9K All Categories
- 2.1K Data
- 207 Big Data Appliance
- 1.9K Data Science
- 447.5K Databases
- 220.8K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 24 Multilingual Engine
- 516 MySQL Community Space
- 464 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 473 SQLcl
- 3.9K SQL Developer Data Modeler
- 186K SQL & PL/SQL
- 20.9K SQL Developer
- 292.7K Development
- 7 Developer Projects
- 125 Programming Languages
- 289.5K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 23 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.8K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 143 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 243 LiveLabs
- 35 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
ORDS 19.4 to 19.4.6 causes massive concurrency in the database
Hello everyone,
I'm running into this issue in our current test instance where during ORDS upgrade process, it would cause a massive concurrency in the database. Eventually
Eventually, it errored out with the following error message in the ords_upgrade log.
ORA-20103: Cannot revoke EXECUTE on SYS.DBMS_UTILITY from ORDS_PUBLIC_USER. ORA-04021: timeout occurred while waiting to lock object
I've never run into this issue before during the previous ORDS upgrade. (We have been running our ORDS inside a docker containers since ORDS 18.2 (we upgraded to 19.4 with no issue).
Has anyone had this issue with a 19.4.6 upgrade on non-docker instance, also?
Best Answer
-
Have you tried upgrading to ORDS 20.2? There is a very similar issue that was fixed in ORDS 20.2 and this issue could potentially be fixed as well.
https://www.oracle.com/tools/ords/ords-relnotes-202.html
Answers
-
are you an oracle employee?
are you doing a container (multitenant) install?
-
I'm not an Oracle Employee.
are you doing a container (multitenant) install?
No, My ORDS installation is on tomcat server that is running inside a docker.
Our RDMBS version is 12.1.0.2, APEX 20.1, and ORDS 19.4.
UPDATE: During ORDS upgrade from 19.4 to 19.4.6 the concurrency issue in the database was so bad that we can't even access the EBS instance anymore. Since it was non-production instance, I also tried doing ORDS upgrade with EBS front-end shutdown. Massive concurrencies still occurred in the database activity during the ORDS upgrade and eventually error out with ORA-20103: Cannot revoke EXECUTE on SYS.DBMS_UTILITY from ORDS_PUBLIC_USER. ORA-04021: timeout occurred while waiting to lock object.
-
Have you tried upgrading to ORDS 20.2? There is a very similar issue that was fixed in ORDS 20.2 and this issue could potentially be fixed as well.
https://www.oracle.com/tools/ords/ords-relnotes-202.html
-
Thank you, I supposed I could tried ORDS 20.2.0 instead. Thank you and will let you know.
-
I don't see the same concurrency issue in the database when going from 19.4 to 20.2.0. Thank you.
-
Hello,
We just ran into the same issue, but with
20.4.3.r0501904ORA-20103: Cannot revoke EXECUTE on SYS.DBMS_UTILITY from ORDS_PUBLIC_USER. ORA-04021: timeout occurred while waiting to lock objectThe SYS session is waiting on "Revoke: get object" while running the revoke.
At the same time we see many other sessions suddenly getting blocked on cursor: pin S wait on X. This is a 2 node RAC on rdbms 19.11
I guess we will have to request downtime to upgrade to this new ORDS.
regards