英文:
oracle apex current version 4.0 we can upgrade latest version 22.2
问题
请查看以下有关Apex的详细信息：
当前版本为：DB 11.2.0.2.0 和 APEX 版本 4.0
Linux 服务器
它是 opensuse 13.2。非常旧的版本
32GB 内存，8 核 CPU 和 2TB
在虚拟机上。
所需内容：
数据库版本 – 21c
Apex 版本 – 我们希望使用 22.2
所需内容：
数据库版本 – 21c
Apex 版本 – 我们希望使用 22.2
英文:
Please see below details for Apex:
Current is: DB 11.2.0.2.0 and APEX version 4.0
Linux server
It's opensuse 13.2. Very old version
32GB ram, 8 core CPU and 2TB
On a virtual machine.
Required
Database version – 21c
Apex version – We want to use 22.2
Required
Database version – 21c
Apex version – We want to use 22.2
答案1
得分: 1
I'm not a DBA所以我不能真正评论升级数据库11g到21c的问题。也许 - 只也许 - 如果您安装了一个全新的21c数据库，并使用导出/导入工具将现有模式移动到新数据库，可能会更简单一些。好处是：您将摆脱不再使用的模式（导出它们，以备份为目的）。缺点是：如果要移动很多模式，这将需要时间。
至于Apex本身：假设您按照上述描述操作，您将在新数据库中安装新版本。然后逐个创建工作空间，并导出/导入您想要移动的应用程序。好处是：您将摆脱旧应用程序和多年来积累的所有垃圾。缺点是：如果要移动很多应用程序，这将需要时间。
您的旧应用程序能在新的Apex中正常工作吗？如果您保持它们原样，应该可以。有一个"兼容模式"属性，允许您指定先前的4.1版本（这就是您拥有的版本）：
如果您计划升级应用程序到最新版本，那么在"工具"部分有这样一个选项。它将引导您完成整个过程 - 您将需要一步一步进行操作，并且可以选择检查（或取消检查）您想要（或不想要）升级的页面/组件。
请注意，如果进行完整升级，不是一切都能正常工作。例如，表格表单将被迁移到交互式网格，您可能会失去为表格表单编程的功能。或者，日期选择器已经发生了很大的变化，这可能会影响到流程和验证。如果我记得正确，4.0中没有动态操作，而它们代表了页面逻辑的重大改进 - 以前不能做的事情（或者可以做，但不容易）现在可以以更简单的方式重新编写。
所以 - 是的，您可以预期会遇到一些问题，需要时间来修复。如果您有很多应用程序，希望不是唯一的开发人员来处理。也许您真的应该保持那些旧应用程序的原样，让用户继续使用它们。在新的Apex版本中开发新应用程序，并在有时间慢慢仔细处理时逐个升级旧应用程序。
英文:
I'm not a DBA so I can't really comment on upgrading database 11g to 21c. Maybe - just maybe - it would be simpler if you installed a brand new 21c database and used export/import utilities to move existing schemas to a new database. Benefit: you'll get rid of schemas you don't need because nobody uses them any more (export them, though, and keep for backup purposes). Drawback: it'll take time if you have many schemas to move.
As of Apex itself: presuming you'll do as described above, you'll install new version in your new database. Then create workspaces, one-by-one, and export/import applications you want to move. Benefit: you'll get rid of old applications and all the garbage you collected through the years. Drawback: it'll take time if you have many applications to move.
Will your old applications work in new Apex? They should, if you leave them as they were. There's the "Compatibility mode" property which lets you specify pre 4.1 version (which is what you have):
If you, on the other hand, plan to upgrade applications to the most recent version, there's such an option in "Utilities" section. It'll lead you through the process - you'll have to do it step-by-step, and will be allowed to check (or uncheck) pages/components you want (or don't want) to upgrade.
Note that not everything will work properly if you do the full upgrade. For example, tabular forms will be migrated to interactive grids and you might lose functionalities you programmed for tabular forms. Or, date pickers have changed a lot which might affect processes and validations. If I remember well, there were no dynamic actions in 4.0, and they represent significant improvement to page logic - things you couldn't do (or could do, but not in an easy way) can now be rewritten in a simpler manner.
So - yes, you can expect some problems which will take time to fix. If you have a lot of applications, I hope you aren't the only developer who will be doing it. Maybe you should really leave those old applications as they are and let users work with them. Develop new applications in new Apex version, and upgrade the old ones one-by-one, when you have time to do it slowly and carefully.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论