How do I override Oracle Apex to upload files? I get the error
Erro: 413 Request Entity Too Large
I have already changed in nginx and tomcat and nothing solves this, wouldn't interface have anything to help?
Version: 19C
Related
I transferred a application from a host with apex 20.1 and Database 19.3 to another host with apex 20.1 and Database Xe 11g.
My application only use a schema that I transferred it completely with Data Pump.
1- After this transfer for each page that have intReport i see javaScript Error!
2- One of my page doesn't work, completely and show a error ( can see it here ). I Finded problem of this page that have a master detail structure!
I have a LIST ITEM in in detail intGrid. When i change it to TEXT ITEM page work correctly!!
Do you have similar problem after transfer application between hosts with same apex version?
Do you have any idea about this errors?
Oracle Database XE 11g is actually running database version 11.2.0.2.0. If you look at the section Oracle Database Requirements for APEX 20.1 you will see in the release notes:
Oracle Application Express release 20.1 requires an Oracle Database release 11.2.0.4 or later...
If you are looking to transfer your application to an XE environment, I would recommend using the latest version of the XE database which is version 18.4.0.0.0
I have Oracle Apex 20.1 Installed on Oracle Linux 6.10 Server with Oracle Database 12.2. Recently I am trying to update into Apex 20.2 but this script file (apex_epg_config.sql) is missing in zip folder.
When I load the site then giving me this error:
There is a problem with your environment because the Application Express files are not up-to-date! The
files for version 20.1.0.00.13 have been loaded, but 20.2.0.00.20 is expected. Please verify that you
have copied the images directory to your application server as instructed in the Installation Guide.
How to solve this error?
The embedded PL/SQL Gateway (EPG) along with mod_plsql are no longer supported for Oracle APEX. This deprecation was announced in APEX 20.1.
Oracle REST Data Services (ORDS) is the only supported and documented Web listener for APEX. The configuration instructions are here. ORDS includes an embedded Web server, so in addition to being supported with Apache Tomcat and WebLogic Server, you can also run ORDS standalone.
I had the same problem after upgrading from APEX 18.2 to 20.2. I solved the problem by not executing this script. It seems that it isn't needed any longer. Update succeeded without running this script.
Attention: There is a pitfall: After upgrading you must clear your browser cache (only images). When I cleared the browser cache, the error message disappeared.
I am getting error that say
ora-28040 no matching authentication protocol
when trying to connect Oracle Forms 6i with ORacle database 12c
I searched and found that this issue is because of connection restriction
that oracle 12c has while oracle Forms 6i do not
I know oracle forms 6i are really old but this is business requirements so
I have nothing to do with upgrading current software ...etc etc
So please if there is any work around for this
SQLNET.ALLOWED_LOGON_VERSION is deprecated since 12c you need to add
SQLNET.ALLOWED_LOGON_VERSION_CLIENT=8
and
SQLNET.ALLOWED_LOGON_VERSION_SERVER=8
to your sqlnet.ora, and reload the listener after you update the file
We are in the process of upgrading an application running on Oracle 10g and oracle HTTP server to Oracle 12C.
Due to mod pl/sql being deprecated we have chosen following combination.
oracle 12c + ORDS 3.0 and tomcat. (we are not using APEX)
A major functionality of our application is uploading files via website to the documents table in the database schema.
While doing that we are getting error "500 Internal Server Error" which has been experienced by others on this link https://community.oracle.com/thread/3891751
If anyone has got a sucessfull file upload into Documents table via Oracle Rest Data Services config I would like to know.
As far as I could prove, it is not possible to upload files with ORDS without having APEX installed. You will have to install APEX even if you do not use it in your application.
You can try another gateway but most are deprecated, I have started to develop one in Java without APEX dependencies. When I have it ready I will publish it in github.
You might want to have a look at the latest ORDS release as explained my own question related to this topic:
File uploads in a non-Apex PL/SQL application migrated to ORDS
I have a web app hosted on BEA Weblogic 10.x with an Oracle 10g database backend.
It works perfectly with one database, but when we make a clone of it and try to use a different WebLogic and Oracle instance we are getting this error:
ERROR - Problem initializing invocation tracking - disabling
tracking xxxxclass.BadTableMappingException: Database column
xxxxPeriodEnding in database yyyyyyy, table zzzzzzz has an
unknown type: JDBC Type 91.
We get it every time we do a query that involves a column of type DATE. There was no ORA-XXXX code in the message.
I can access the database using SQL*Plus using the same access and do selects and updates on the same tables with no errors.
The answer to this question is not just a simple description of what a type 91 error is (although that will help) but what could be causing this given the circumstances described above.
I am using ojdbc14.jar for JDBC on both instances of weblogic.
I have no idea about the error, but have you considered the jdbc jar version and more importantly if the oracle DB needs to be updated.
I faced very weird problems with oracle, and struggled for a while to find at the end that installing some patches for oracle would solve the problem.
Set oracle.jdbc.V8Compatible=true.
This remaps the oracle DATE type to a DATETIME time in JDBC. This parameter was missing on the new Weblogic server.