Upgrade APEX 4.1.1 to 4.2.1 on Oracle Linux with GlassFish
==============================================
Steps:
1) download the software
You can download APEX 4.2.1 here. I downloaded the “all languages” zip file. Please note that the documentation is no longer included with the software. You can download the documentation separately here.
2) copy and extract the software
Now copy and extract the apex_4.2.1.zip file to your server. I use “unzip” to unzip the zip file. This will create a folder named “apex”. I usually keep this folder on my server in a permanent location, for example /u01/app/apex.
3) check the tablespace requirements
You need about 275MB of free space in the APEX tablespace (mine is called “APEX”) and 100MB of free space in the SYSTEM tablespace.
4) stop the APEX Listener
Before you start with the upgrade, you need to stop the APEX Listener to make sure no one is using the software during the upgrade.
To stop the APEX Listener under GlassFish, you can do it as follows:
– connect to the GlassFish administration console (by default this is port 4848 using SSL).
– log in with the “admin” user.
– click on Standalone Instances => Applications.
– select the “apex” application and select “Disable” from the “More Actions” drop down list.
The APEX Listener should now be stopped on your GlassFish instance.
5) start the upgrade
To upgrade the APEX software, you need to run the “apexins.sql” sql script from within the “apex” folder that you extracted above. You need to connect as SYS as SYSDBA with the oracle software owner (mine is called “oracle”). Make sure the “apex” folder is writeable!
apexins.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/”).
$ su - oracle
$ cd /u01/app/apex
$ sqlplus /nolog
SQL*Plus: Release 11.2.0.3.0 Production on Thu Jan 3 11:21:39 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> @apexins.sql APEX APEX TEMP /i/
The upgrade will now start. This will create a new schema called “APEX_040200”. The upgrade can take some time, depending on the speed of your server. On my server (with fairly recent hardware), it took about 17 minutes. After the upgrade, check the installation log file (in the same folder where you exectuted the apexins.sql file) to make sure no errors were encountered during the process.
6) verify the installation
I always verify my APEX installation after a upgrade by querying dba_registry:
$ sqlplus /nolog
SQL*Plus: Release 11.2.0.3.0 Production on Thu Jan 3 12:06:21 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> conn / as sysdba
Connected.
SQL> select status from dba_registry where comp_id='APEX';
STATUS
-------------------------------------------------------
VALID
Ref:
====
https://matthiashoys.wordpress.com/tag/apexins-sql/
https://community.oracle.com/thread/2328355?tstart=0
==============================================
Steps:
1) download the software
You can download APEX 4.2.1 here. I downloaded the “all languages” zip file. Please note that the documentation is no longer included with the software. You can download the documentation separately here.
2) copy and extract the software
Now copy and extract the apex_4.2.1.zip file to your server. I use “unzip” to unzip the zip file. This will create a folder named “apex”. I usually keep this folder on my server in a permanent location, for example /u01/app/apex.
3) check the tablespace requirements
You need about 275MB of free space in the APEX tablespace (mine is called “APEX”) and 100MB of free space in the SYSTEM tablespace.
4) stop the APEX Listener
Before you start with the upgrade, you need to stop the APEX Listener to make sure no one is using the software during the upgrade.
To stop the APEX Listener under GlassFish, you can do it as follows:
– connect to the GlassFish administration console (by default this is port 4848 using SSL).
– log in with the “admin” user.
– click on Standalone Instances => Applications.
– select the “apex” application and select “Disable” from the “More Actions” drop down list.
The APEX Listener should now be stopped on your GlassFish instance.
5) start the upgrade
To upgrade the APEX software, you need to run the “apexins.sql” sql script from within the “apex” folder that you extracted above. You need to connect as SYS as SYSDBA with the oracle software owner (mine is called “oracle”). Make sure the “apex” folder is writeable!
apexins.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/”).
$ su - oracle
$ cd /u01/app/apex
$ sqlplus /nolog
SQL*Plus: Release 11.2.0.3.0 Production on Thu Jan 3 11:21:39 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> connect / as sysdba
Connected.
SQL> @apexins.sql APEX APEX TEMP /i/
The upgrade will now start. This will create a new schema called “APEX_040200”. The upgrade can take some time, depending on the speed of your server. On my server (with fairly recent hardware), it took about 17 minutes. After the upgrade, check the installation log file (in the same folder where you exectuted the apexins.sql file) to make sure no errors were encountered during the process.
6) verify the installation
I always verify my APEX installation after a upgrade by querying dba_registry:
$ sqlplus /nolog
SQL*Plus: Release 11.2.0.3.0 Production on Thu Jan 3 12:06:21 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> conn / as sysdba
Connected.
SQL> select status from dba_registry where comp_id='APEX';
STATUS
-------------------------------------------------------
VALID
Ref:
====
https://matthiashoys.wordpress.com/tag/apexins-sql/
https://community.oracle.com/thread/2328355?tstart=0
No comments :
Post a Comment