I have an Apex application on a server running Apex 19.2
I would like to import this application into a server running Apex 19.1
The import doesn't work saying that the versions are not compatible.
I tried to manully change the release date in the application sql file to "fake" the version but it still doesn't work.
Does anyone know how to solve that please ?
Thanks.
Cheers,
It is not only the release date, but release itself:
wwv_flow_api.import_begin (
p_version_yyyy_mm_dd => '2020.02.24',
p_release => '19.1.x.yy.zz' --> this
...
Did you do that as well?
Perhaps you'll be interested in reading How to import an Oracle APEX Application export file from a higher version into a lower version. There's no guarantee that it'll actually work, but - if you're desperate enough, try it.
Related
because of the interest we have in postgresql 15, my team and I would like to migrate to this new version. As we work with docker, I loaded the postgres:15 image instead of the old postgres:13 image and got it on my PC.
Now my problem is that I can't find a way to use Postgres:15 on my DataGrip IDE.
I can still write postgresql 14 code in DataGrip.
select version();
in a query console in DataGrip gets me version 15.1 version response but new commands such as MERGE can't be found by the IDE.
I found out after some research that the old version persisted in a terminal call of psql so i deleted the old cluster because they had the same port and name and now when i call psql in a terminal, I can write in postgresql 15.1 but still not on DataGrip.
There's a plan to implement it from 2023.1: https://youtrack.jetbrains.com/issue/DBE-16310
Now that, since 12.2, Oracle no longer install APEX by default, is there a way to force the APEX installation during installation of the database? It's quite a pain having to manually re-install APEX after each 12c install.
One way you can accomplish this is by creating your own Database Template which includes APEX. Mike Dietrich has an excellent blog post about database templates here.
Keep in mind, that will install the version of APEX that is in the database home, which may not always be the latest version of APEX.
Whatever you do, I advise against installing APEX common (in CDB$ROOT), and only install it locally in a PDB.
I get this error : toad invalid pointer operation , when I want to import data from excel.
Toad version : 12.1
Oracle version :Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
I ve restarted TOAD , even Computer but it does not work.
thanks in advance
I had the same problem and this was my solution (idea from https://support.quest.com/toad-for-oracle/kb/52537):
To quickly remove any hidden formulas in the spreadsheet, I copied all the range of cells with the required data and pasted it into another spreadsheet.
On the following import operation everything worked smoothly.
I'm facing an issue when trying to run or debug a package where Oracle SQL Developer doesn't display public members (procedures) that don't have input parameters.
There is a couple of procedures, some overloads, but Oracle SQL Developer doesnt display no invoke-able members.
I've tried with following versions of Oracle SQL Developer
4.1.1.19 link to article saying this version solves the issue, but it didn't
4.0.3.16 - same behavior
4.0.0.13 - same behavior
3.2.20.09 - this version actually displayed invokable members, but debugger doesnt work.
This is the Oracle version :
select * from v$version;
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
"CORE 11.2.0.4.0 Production"
TNS for IBM/AIX RISC System/6000: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production
Has anyone successfully resolved similar situation and how?
(Upgrading database is not an option atm)
A bit late, but i could help. There is a SqlDeveloper bug. What I have to do is to "Save" it before Compile it...
Hope it helps
I found 2 possible cause that may cause the no public member problem
1) SQL Developer hit some kind of bugs itself.
This can be resolved by completely close and restarting the SQL developer
2) Some keywords used in your codes (e.g. field name in SQL statements) that works fine in compiled execution , but would ruin the display of function list.
I resolved my problem by applying double quote to the entire packages where a field named “CASE” is used.
i.e.
SELECT table1.case FROM table1
change to
SELECT table1."CASE" FROM table1
Alex
Definitely late , but came across the same issue & thought of posting what helped me .
The proc was contained in a package that belong to another user
&
the grants were not provided for the user which was calling the proc .
Works when the grants are done.
I would recommend to save the stored procedure and then compile. In some cases, after saving the procedure, the table will automatically compile. But, you have to save each and every time you make changes.
I hope this helps you out.
I have a package which I've just replaced and the method being called (ASP.NET client) is raising an error about an incorrect number of parameters.
If Oracle is still running the old version, how can I get it to discard the old "compiled" version?
Oracle 10g won't run the old version of a package after you've done a CREATE OR REPLACE (I'm assuming that you did that both for the package spec and the package body).
If you were using 11.2 and explicitly asked it do, Oracle can run two different versions of a piece of code in two different editions which would let some clients continue using the old edition and gradually migrate to the new edition. Edition-based redefinition is new in 11.2 though.