I have a java app, which acts as an oracle client/bridge between a mobile app ( data visualisation) and oracle database. The java app is capable to multithread if more than one request is made at a time.
No issues here, all works fine. The aim was to refrain from plugin mobile devices to the db.
Apart from the mobile app side, it's possible to run queries against the db on a scheduler i.e. every 5 mins and keep results in a buffer.
Anyway, In a production environment, my app was connected to a client database for a couple of weeks and suddenly the below error stopped the oracle form working causing a massive issue to the customer of mine.
ORA-01034: ORACLE not available ORA-27102: out of memory Linux-x86_64 Error: 12: Cannot allocate memory
Obviously, suspicion is that my product caused the Oracle problem. Apparently, oracle ran out of "accessible memory" ( whatever that means - it wasn't techy guy who talked to me)
...so my question to you is if running queries against DB can cause any memory issues?
As far as I know, a bad sql ( there wasn't any in this case) can cause long-running queries/sessions, which can consume a lot of CPU and indeed can slow oracle down...
what's your view on this, please ?