My Oracle Support Banner

404 accessing APEX in DBCS OCI Classic - Database Partially Available (Doc ID 2553548.1)

Last updated on AUGUST 13, 2019

Applies to:

Oracle Database Cloud Service - Version N/A and later
Oracle Application Express (APEX) - Version 5.0 and later
Oracle SQL Developer - Version 3.0 and later
Information in this document applies to any platform.

Symptoms

On :Oracle Cloud Infrastructure -Classic (OCI-C)  DBCS

When attempting to access APEX or SQL Developer Web in a new instance (non default character set) the following error occurs.



ERROR: 404 Not Found "The request could not be mapped to any database. Verify if the URL of the request is correct and if the URL for the database mappings have been configured correctly "

In ords.log in one can see:

...

2019-06-07 22:03:37.266:INFO:oejs.Server:main: Started @22952ms
2019-06-08 02:32:22.568:WARN:oejh.HttpParser:qtp1393931310-18: Illegal character 0x5 in state=START for buffer HeapByteBuffer@bc0f24[p=1,l=4,c=8192,r=3]={\x05<<<\x02\x00\x01>>>/1.1 403 !Secure\r...\x00\....\x00}
2019-06-08 02:32:23.028:WARN:oejh.HttpParser:qtp1393931310-17: Illegal character 0x4 in state=START for buffer HeapByteBuffer@bc0f24[p=1,l=9,c=8192,r=8]={\x04<<<\x01\x00P\xC6\xFfbK\x00>>>403 !Secure\r\nDate...\x00\....\x00}
2019-06-08 10:35:34.842:WARN:oejh.HttpParser:qtp1393931310-16: Illegal character 0x1 in state=START for buffer HeapByteBuffer@bc0f24[p=1,l=256,c=8192,r=255]={\x01<<<\x02\x03\x04\x00\...\x00>>>GYWxzZQ==12.act|'...\x00\...\x00}
2019-06-09 05:49:49.740:WARN:oejs.HttpChannel:qtp1393931310-19: /user/register
org.eclipse.jetty.http.BadMessageException: 400: Unable to parse URI query
at org.eclipse.jetty.server.Request.getParameters(Request.java:405)

...
Caused by: java.lang.IllegalArgumentException: Not valid encoding '%6h'
at org.eclipse.jetty.util.UrlEncoded.decodeHexByte(UrlEncoded.java:889)
...
2019-06-09 20:56:14.009:WARN:oejh.HttpParser:qtp1393931310-18: Illegal character 0xAD in state=METHOD for buffer HeapByteBuffer@bc0f24[p=6,l=173,c=8192,r=167...
2019-06-10 01:16:01.350:WARN:oejh.HttpParser:qtp1393931310-19: Illegal character 0x16 in state=START for buffer HeapByteBuffer@bc0f24[p=1,l=149,c=8192,r=148]={\...

...

NOTE: This problem can happen with a newly create database / container or an existing database / container. 


STEPS

The issue can be reproduced at will with the following steps:
1. Create a DBCS (On OCI Classic) and select charset WE8MSWIN125


2. Test https://<PUBLIC_IP>/ords/<pdb_name>/

 

Changes

A new DBCS - Classic instance with a character set different from the default one
OR
The database was started in a restricted mode for patching or other DBCS activities.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.