We need to know since version Oracle 12, exists the concepts of plug-gable databases and containers.
So first download oracle database and oracle apex:
Oracle APEX Release 18.2.0.00.12
Use the setup and next.
Finally we will have the URLs where we can access to the database
So, here i have some troubles to access because my listener was stopped.
The URL for access is : https://localhost:5500/em
If you have problems to access. Check using
lsnrctl status
If the listener is stopped, you can start using:
lsnrctl start
About listener :
Foro Oracle 1
Foro Oracle 2
This point is very important.
Firsts we going to check the current pdbs, connect to sqlplus as execute show pdbs, it must the display the correct mode, read only and read write.
Look this guides if is different
Guía 1
Guía 2
Beforo to start the install, we must to select the correct pdb.
ALTER SESSION SET CONTAINER = XEPDB1;
The containers since Oracle 12, is like this, for that reason before to install we need to select to correct container. This link is a resume about that.
Next, Go to directory where you have apex 18.2 uncompressed, and install,
Guide Oficial Oracle.
@apexins.sql SYSAUX SYSAUX TEMP /i/
Set the password of admin.
@apxchpwd.sql
Configure the Pl/Sql Gateway for local environment.
Use the parent directory as URL.
@apex_epg_config.sql C:\MyPc\InstallApex
Next , check the port:
SELECT DBMS_XDB.GETHTTPPORT FROM DUAL;
If is 0 we need to change with 8080, or another.
EXEC DBMS_XDB.SETHTTPPORT(8080);
If we are in both and with that mode, execute:
ALTER USER ANONYMOUS ACCOUNT UNLOCK;
Finally we can enter to Oracle Apex 18.2
http://localhost:8080/apex
http://localhost:8080/apex/apex_admin
First time enter as workspace Internal and user admin , and pass of the istallation.
References:
Oracle Database Express Edition (XE) Release 18.4.0.0.0 (18c)
Oracle APEX Release 18.2.0.00.12
Si te olvidaste de seleccionar el contenedor o tienes errores al crear el workspace
Problemas con activar el read write en los contenedores 1
Problemas con activar el read write en los contenedores 2
Guía instalacion Oracle 18c express
Guía instalacion Oracle APEX 18.2
Acerca de pluggable database
I face a weird issue on Win 10 recently, when I try to install ORDS it give Network adopter error. SQLPlus however works. Any suggestions?
ReplyDeleteIt did work perfectly on Win 7 Tomcat 9 Ords Latest though.
Hello i dont sure what could be your error, maybe you can create a post with your problem on Oracle Community https://goo.gl/cszDq2 and we can help all together.
DeleteGreat Help; thnx 4 posting!
ReplyDeleteAngel
ReplyDeleteI followed exactly all the steps in your article, but I can not access Apex. There are two issues when I try to access the browser.
1 - First the browser requests login and password in a prompt before loading the page, I try to access with the user created in the installation of Apex and with Sys, but it does not work;
2 - I get the message "" There is a problem with your environment because the Application Express files have not been loaded. Please verify that you have copied the images directory to your application server as instructed in the Installation Guide. In addition, please verify that your image is correct. Your current path is / (it should contain both starting and ending forward slashes, such as the default / i /). Use the SQL script reset_image_prefix.sql if you need to change it. ""
And I performed the installation with the command @ apex_epg_config.sql C: \, since the apex was unzipped in C: \ apex.
Could you help me with these problems?
Thank you!
The first error, is usually when you try to connect to apex, but the accounts are locked or with the password expired. try:
DeleteALTER USER ANONYMOUS ACCOUNT UNLOCK;
ALTER USER xdb ACCOUNT UNLOCK;
ALTER USER apex_public_user ACCOUNT UNLOCK;
ALTER USER flows_files ACCOUNT UNLOCK;
The second error is kind of weird make sure the path is the correct for images. I create this video for apex 5.1 but the installation its the same as 18 or 19, execpt for select the PDB data base first https://www.youtube.com/watch?v=zaWjW5OzhpE&t=391s / also you can check in the apex direcctory the log files, and see what is the error