Incorrect DBaaS user/pass error when creating JCS instance

user1015961

We have created a DBaaS instance, but when creating a JCS WL12.2.1 instance, the creation script fails due to the following error:
JCS-ERR-20027: Cannot establish connection using connect string 'wcddb-scan-int:1522/wcdpdn.bchtrial3.oraclecloud.internal' and userName 'sys as sysdba'. Reason: 'ORA-01017: invalid username/password; logon denied

We have confirmed that the username/password is correct and works when connecting directly. The only thing that looks out of place is that the username is 'sys as sysdba' instead of 'sys' (which is what I entered into the field).

Anyone have any tips?

In case it helps, here is the full output for the failed JCS creation:

Service provisioning attempt 1 (out of 2) has failed.

Created Compute resources for WebLogic Server...

Created security resources for the service...

Established SSH connectivity to WebLogic Administration Server...

Established SSH connectivity to Host(s) [wcs1sat__server_2] from Administration Server...

Failed to configure WebLogic Administration Server...

Configured Load Balancer...

Service Reachabilty Check (SRC) of Load Balancer timed out after 225 minutes...

operation.rollback.msg

Cleaning up resources before retrying to provision the Service...

Stopped all Compute resources...

Removed Compute resources...

Service record (WebLogic) removal complete...

Updated Load Balancer metadata...

Service provisioning attempt 2 (out of 2) has failed.

Created Compute resources for WebLogic Server...

Created security resources for the service...

Established SSH connectivity to WebLogic Administration Server...

Established SSH connectivity to Host(s) [wcs1sat__server_2] from Administration Server...

Failed to configure WebLogic Administration Server...

The provisioning errors in [wcs1sat wls 1]:

JCS-ERR-20027: Cannot establish connection using connect string 'wcddb-scan-int:1522/wcdpdn.bchtrial3.oraclecloud.internal' and userName 'sys as sysdba'. Reason: 'ORA-01017: invalid username/password; logon denied

'.

Configured Load Balancer...

Service Reachabilty Check (SRC) of Load Balancer timed out after 225 minutes...

operation.rollback.msg

Unable to provision the service. Hence rolling back...

Stopped all Compute resources...

Removed Compute resources...

Service record (WebLogic) removal complete...

Updated Load Balancer metadata...