EMCC: ODA discovery errors

The ODA discovery process may occasionally fell with the mysterious error below:

“The following errors are found during discovery. Please examine the error message and the targets being discovered if any”

This error may be caused by the root password including a special character, & or $.



ADW: dbms_cloud.copy_data and record delimiter

To import via dbms_cloud.copy_data a windows file that include window CR+LF at the end of each record, specify the record delimiter as follow:

(table_name      => '<table>'
,credential_name => '<credential_name>'
,file_uri_list   => 'https://<restpoint>/<file>'
,schema_name     => '<schema>'
,format           => json_object('recorddelimiter'      value '''\\r\\n''')


An invalid specification of this delimiter would return the error below:

ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-06512: at "C##CLOUD$SERVICE.DBMS_CLOUD", line 801
ORA-06512: at "C##CLOUD$SERVICE.DBMS_CLOUD", line 782
ORA-29400: data cartridge error
KUP-00554: error encountered while parsing access parameters
KUP-01005: syntax error: found "xxx": expecting one of: "double-quoted-string, hexprefix, newline, single-quoted-string"
KUP-01007: at line 2 column 2
ORA-06512: at "C##CLOUD$SERVICE.DBMS_CLOUD", line 757
ORA-06512: at "C##CLOUD$SERVICE.DBMS_CLOUD", line 819
ORA-06512: at line 2

OCI-c: Project Fn setup

Basically following the instructions posted in the fn project page:


#1 Setup a VM running OL7.2 with 50GB

Preferably pick OL72 over OL68 as fn require docker > 17.5


#2 Setup security policy (OL7)

# setenforce permission


#3 Install docker (root)

Follow the instructions posted in the documentation.

Update /etc/yum.repos.d/public-yum-ol7.repo to enable the ol7_addons then

# yum install docker-engine wget tree
# chkconfig docker on
# yum update
# service docker start


#4 Install fn (as root)

curl -LSs https://raw.githubusercontent.com/fnproject/cli/master/install | sh



#5 Create a runtime user and add it to the docker group

# useradd -g 500 -d /home/oracle oracle
# sudo usermod -a -G docker oracle


#6 Login as oracle and start the fn server

$ fn start


#5 Login again as oracle in a second window and configure a demo project

$ mkdir project
$ cd project
$ fn init --runtime go hello
$ cd hello
$ fn run
$ fn deploy --app myapp --local
$ fn invoke myapp hello

Update the file func.go, changing Hello with bonjour, deploy and test again

$ fn deploy --app myapp --local
$ fn invoke myapp hello
{"message":"Bonjour World"}




DevCS: Storage configuration

When configuring the storage for a Developer Cloud Service, make sure that the user password is reasonable short.

If not, the error “Cannot add configuration. Check the credentials and Authorization URL” may be returned.

In addition, make sure that the Authorization URL uses the protocol https, or the other error may be returned:

Unable to authenticate. Check the Service ID and/or credentials

OCI: ORDS 18.x redirection and logging

The tips below are applicable for ORDS 18.x standalone, for example after a deployment on an OCI dbsystem.

#1 To configure the access.log, update the file standalone.properties available from the /u01/app/oracle/product/ords/config/ords/standalone/standalone.properties configuration file to add the following property


Where /tmp/ords is going to be a directory that will hold the daily logfiles. Then restart the ords standalone process.


#2 To implement some redirect for the internal ords port to be accessible from the standard https port 443, instead of the native port 8443, create the file https (for example) in /etc/xinetd.d, with the following content:

service jetty-https
disable = no
socket_type = stream
protocol = tcp
wait = no
redirect = localhost 8443
port = 443
user = nobody

Then restart the xinetd.d service

service xinetd restart

Check that the firewall and the ingress rules allow inbound access to 443.

APEX: ORA-02291: integrity constraint (APEX_180100.WWV_FLOW_FND_GU_INT_G_FK) violated – parent key not found

Getting the error ORA-02291: integrity constraint (APEX_180100.WWV_FLOW_FND_GU_INT_G_FK) violated – parent key not found while importing an apex workspace.

Issue has to do with users groups that are not part of the import. This is the bug 16781538, still unresolved with 18.1.

Solution is to edit the import file, locate the users that belong to group and change in the www_flow_fnd_user_api. create_fnd_user call(s) that create issues, for example:

  p_group_ids => '1860188076423573:1860279868423578:1860329781423578:'


  p_group_ids => ''