Skip to Main Content
Forums

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

Integrating ORDS 19.2 with EBS 12.2 using a pdb

James DieblingAug 4 2020 — edited Aug 4 2020

Hi,

We upgraded our version of EBS to 12.2 on a 19c database and during the process a PDB was created using a lowercase name ("pdb1).   While installing ORDS, I enter the service name for access to the PDB but I get the following error:

2020-08-04T14:55:34.076Z WARNING ORA-65011: Pluggable database pdb1 does not exist.

It seems the installation expects the PDB name to be uppercase.  The DB initialization parameter _pdb_name_case_sensitive is set to TRUE (the default for this EBS version).

Has anyone had luck in connecting an ORDS installation to a 19c PDB in lowercase?  

Any help is appreciated

Comments

Even creating a pdb in lowercase, it's still created as uppercase, and my listener service names are all lowercase...

CREATE PLUGGABLE DATABASE "pdb3" FROM "PDB2"

gives me -

pastedImage_0.png

listener status -

Service "pdb3" has 1 instance(s).

So i'm not sure how to reproduce your scenario/problem...

James Diebling

Thanks for your reply...

What is the setting for parameter "_pdb_name_case_sensitive" in your database?    The default is FALSE but in EBS the value is set to TRUE.

I was told that controls if a lowercase value can be used.

Jim

ahhhh

i won't be able to easily test this

in the installer, what you you using, tns or the basic connect info?

TNS might get you around the problem, but this could cause issues further down the line...

if basic, did you try "dbname" vs dbname ?

James Diebling

I did try both suggestions, the use of TNS and using quotes around the name but got the same results

Jim

user4352244

The SOLUTION is create a new service from pdb1 in lower case, and validate ords with new service name:
SQL> exec DBMS_SERVICE.CREATE_SERVICE('pdb1lowcase','pdb1lowcase');
SQL> exec DBMS_SERVICE.START_SERVICE('pdb1lowcase');
SQL> SELECT NAME FROM V$ACTIVE_SERVICES;
run now:
$java -jar ords.war validate advance
Introduce database servicename: pdb1lowcase
and it works.

1 person found this helpful
User442369

So we tried the above but with no much luck.

[accadpch@mt64-027 ords_214]$
[accadpch@mt64-027 ords_214]$ java -jar ords.war install advanced --logDir $HOME/ords/ords_214/log
Specify the database connection type to use.
Enter number for [1] Basic [2] TNS [3] Custom URL [1]:1
Enter the name of the database server [localhost]:ccoap26.xxxxxxx.com
Enter the database listen port [1521]:9261
Enter 1 to specify the database service name, or 2 to specify the database SID [1]:1
Enter the database service name:ords
Enter 1 if you want to verify/install Oracle REST Data Services schema or 2 to skip this step [1]:1
Enter the database password for ORDS_PUBLIC_USER:
Confirm password:
Requires to login with administrator privileges to verify Oracle REST Data Services schema.

Enter the administrator username:sys
Enter the database password for SYS AS SYSDBA:
Confirm password:
Connecting to database user: SYS AS SYSDBA url: jdbc:oracle:thin:@//ccoap26.xxxxxxx.com:9261/ords

Retrieving information.
2022-04-15T15:37:53.806Z WARNING ORA-65011: Pluggable database CCOAP26 does not exist.

Enter the default tablespace for ORDS_METADATA [SYSAUX]:

1 - 6

Post Details

Added on Aug 4 2020
6 comments
1,914 views