Forbidden
The requested operation is not allowed
I have created new application and getting above error while running app on local server
Old Question, but this might help others:
Seems like the friendly URL feature introduced in APEX 20.1 is causing this issue. A workaround for me is just disabling that in the Application Definition Atrributes.
I had the same problem after upgrading from Oracle Apex 19.2 to Oracle Apex 20.2. I tried everything and nothing happened. I found this:
https://docs.oracle.com/en/database/oracle/application-express/20.1/htmrn/index.html#HTMRN-GUID-175AC460-3BCB-4871-A14C-5A232EDF8CAD
I'm not sure if this is the case, but I can't find any other explanation - in section 2.1.1 Oracle Database Requirement it is said that version 20.2 is compatible with database version 11.2.0.4 and above. Mine is 11.2.0.3. Probably doesn't work for that. Check your version of the database and share if you are below the required one to know if I guess correctly. If so, and you want APEX 20.2, you may need to update your database version first, if a possible.
I hope I helped.
Related
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.
After upgrading from Oracle 11/12 to 18/19 I get this error: ORA-01036: illegal variable name/number.
The error occurred in a query like this:
SELECT * FROM (SELECT * FROM TABLE) MY_TABLE WHERE ROWNUM <= :P_ROWNUM
(Subquery + binding parameters)
The identical query works properly with the Oracle 11.2.0.4 or 12.1.0.2 client. It fails with the Oracle Client 18c or 19c.
PS: The Oracle Server is version 18c 64x for Windows.
I use Delphi 10.1.2 with ADO components (dbGO). I also tried with Delphi 13.3.3 but the behavior is the same.
It seems to be a problem in the Oracle OLE DB provider (ORAOLEDB).
If I don't use ADO but DevArt Unidac all worked as expected.
Someone can help me?
Max
Your query is fine. We ran into a similar issue when migrating from 12.1 to 19. In our case, we have a custom OLE DB provider that interfaces with OraOLEDB (and others) using the Microsoft OLE DB Provider Templates (ATL). When attempting to upgrade from 12.1.x to 19c we started seeing the strange and confusing "ORA-01036: illegal variable name/number" error for parameterized SELECT queries. The queries would succeed the first time they were executed but subsequent executions would fail when all we did was change the parameter value (the queries were executed sequentially). I went on a wild goose chase trying to diagnose the issue and finally decided it had to be an Oracle caching bug of some kind. Yesterday, I experimented with the cache-related connection string attributes and found that adding the MetaDataCacheSize attribute and setting its value to 0 (zero) resolved the issue for us. None of the current Oracle patches appear to address this issue, at least none of those that mention the ORA-01036 error.
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
A quick and simple question: has anybody used the combination of Hibernate 2.1.7 and Oracle 11gR2 database? We have a legacy app that is using Hibernate 2.1.7 (which we are not planning to update at this point in time) and our database back-end is being upgraded to Oracle 11gR2. Is there any issues we need to be aware of?
Thanks!
With jdbc driver 11.1.0.6.0 you can connect to Oracle 11gR2. No problem.
A simple issue that you might run into is the case of username and passwords. In 11g this is case sensitive, before that version it was not case sensitive.
An other nice one is that accounts now default expire. Check that with your local dba.
You should test the app during the upgrade tests. Database features change, optimizer features change, so the app behaviour could change. Technically I see no reasons why it would not work but knowing some software projects .... Test it. In many cases it does not give any problems at all. A lot depends on the quality of the code. If your app's code is working because it is based on a bug in Oracle that is now solved, you will run into an issue.
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.