![]() The upgrade can take some time, depending on the speed of your server. This will create a new schema called “APEX_040200”. ![]() Make sure the “apex” folder is writeable!Īpexins.sql needs 4 parameters: the name of the tablespace for the APEX user (in my case: APEX), the name of the tablespace for the FLOWS_FILES user (in my case: APEX), the name of the TEMP tablespace (in my case: TEMP) and the name of the virtual image directory (which is “/i/”). You need to connect as SYS as SYSDBA with the oracle software owner (mine is called “oracle”). To upgrade the APEX software, you need to run the “apexins.sql” sql script from within the “apex” folder that you extracted above. The APEX Listener should now be stopped on your GlassFish instance. – select the “apex” application and select “Disable” from the “More Actions” drop down list. – click on Standalone Instances => Applications. – connect to the GlassFish administration console (by default this is port 4848 using SSL). To stop the APEX Listener under GlassFish, you can do it as follows: You need about 275MB of free space in the APEX tablespace (mine is called “APEX”) and 100MB of free space in the SYSTEM tablespace.īefore you start with the upgrade, you need to stop the APEX Listener to make sure no one is using the software during the upgrade. I usually keep this folder on my server in a permanent location, for example /u01/app/apex. Now copy and extract the apex_4.2.1.zip file to your server. Please use a more recent version of APEX (5.1, 18.x, 19.x). Update: APEX 4.2.1 is no longer available from the Oracle website. This blog post explains how you can upgrade your Application Express installation from version 4.1.1 to version 4.2.1, with the APEX Listener deployed under GlassFish.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |