Discussions
Categories
- 196.8K All Categories
- 2.2K Data
- 238 Big Data Appliance
- 1.9K Data Science
- 450.2K Databases
- 221.7K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 31 Multilingual Engine
- 550 MySQL Community Space
- 478 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3K ORDS, SODA & JSON in the Database
- 544 SQLcl
- 4K SQL Developer Data Modeler
- 187K SQL & PL/SQL
- 21.3K SQL Developer
- 295.8K Development
- 17 Developer Projects
- 138 Programming Languages
- 292.5K Development Tools
- 107 DevOps
- 3.1K QA/Testing
- 646K Java
- 28 Java Learning Subscription
- 37K Database Connectivity
- 154 Java Community Process
- 105 Java 25
- 22.1K Java APIs
- 138.1K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 17 Java Essentials
- 160 Java 8 Questions
- 86K Java Programming
- 80 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 204 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 436 LiveLabs
- 38 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 171 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 232 Portuguese
Receive "Issues with the configuration of the Static Files" error after ORDS 18 install and configur
Answers
-
Hello,
I have my Oracle components in the following folders:
C:\app\product\18.0.0
C:\app\product\apex
C:\app\product\ords
C:\app\product\sqldeveloper
Is there anything inherently wrong with this folder structure?
I installed the components in this order
XE 18C
Apex 18.2 (using SQLPLUS> @apexins SYSAUX SYSAUX TEMP /i/
Once installed, using SQLPlus I executed:
- @apxchpwd
- alter session set "_ORACLE_SCRIPT"=true;
- ALTER USER APEX_PUBLIC_USER ACCOUNT UNLOCK;
- ALTER USER APEX_PUBLIC_USER IDENTIFIED BY new_password;
- @apex_rest_config.sql
- @apex_epg_config.sql C:/app/product (This accesses the subordinate APEX/IMAGES directory)
- Alter User Anonymous Account Unlock;
From File Explorer I used Extract All on ords.3.0.7.253.09.40.zip to the folder C:\app\product\ords
From and elevated command prompt I ran java -jar ords.war install advanced
- When prompted for Configuration Data I supplied C:\app\product\ords
- The install program responded with:
- Your database connection is to a CDB. ORDS common user ORDS_PUBLIC_USER will be created in the CDB. ORDS schema will be installed in the PDBs.
- Root CDB$ROOT - create ORDS common user
- PDB PDB$SEED - install ORDS 18.4.0.r3541002 (mode is READ ONLY, open for READ/WRITE)
- PDB XEPDB1 - install ORDS 18.4.0.r3541002
- I started in standalone mode, changed the port to 9090
- When prompted for the Apex Static Resources Location I responded with C:\app\product\apex\images
It seems that ORDS_PUBLIC_USER is created in the CDB and the ORDS schema is created in the PDB. I don't seem to have much control over that choice. Would you change any of the installation steps I used?
Thanks again for looking at this.
-
These were the steps I took.
create a tnsnames.ora entry for the pluggable database.
test the pluggable tnsnames.ora entry OUTSIDE of the server using the SYS account.
XE 18C
sqlplus / as sysdba
alter session set container=pluggable_db_name
e:\apex18.2\apex directory - using SQLPLUS> @apexins SYSAUX SYSAUX TEMP /i/
Verify apex install:
select status from dba_registry where comp_id='APEX';
@apxchpwd.sql
ALTER USER APEX_PUBLIC_USER IDENTIFIED BY password ACCOUNT UNLOCK;
ALTER USER anonymous ACCOUNT UNLOCK;
ALTER USER xdb ACCOUNT UNLOCK;
ALTER USER flows_files ACCOUNT UNLOCK;
Rem ALTER system SET shared_servers=5 scope=both;
@apex_rest_config.sql
@apex_epg_config.sql E:\apex182 (apex installation home - my images are at: E:\apex182\apex\images)
commit; (may or may not be needed)
create the ords.war file at this point.Good practice is to install the ORDS in its own home (E:\ords for example).
I see a lot of folks on this forum that recommend this approach.Test out all of your accounts used/unlocked too.
Note that I did an alter session set container before I ran all of .sql scripts
above. Use the pluggable passwords in the
ORDS.WAR INSTALL ADVANCED command.
You can also validate the ords install and look for any issues:java -jar E:\ords\ords.war validate
-
Thanks very much Thompson. It's now working perfectly. I had not set the container to XEPDB1 prior to installing APEX. That made all the difference. It seems that the users associated with APEX and ORDS must be in the same PDB container (e,g, XEPDB1). The install documentation for Apex 18.2 doesn't show the statement alter session set container=XEPDB1 as an example or option. I got an error with @apex_rest_config when I had the APEX and other installs set to the default container (CDB$ROOT).
Just like you suggested, after installing Apex 18.2 from the same SQLPlus (set to container=XEPDB1) I ran:
@apex_epg_config.sql C:\app\product
When I installed ORDS I used
Configuration Data = C:\app\product
Database Service Name = XEPDB1
Apex Static Resource Location = C:\ app\product\ apex\images
I should mention that after installing XE 18C I adjusted the TNSNAMES.ORA file:
XEPDB1 =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = localhost)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = xepdb1)
)
)
Thanks again for all your help!
-
I've tried to figure this out for 2 months. This worked perfectly; thank you!