Oracle Java Cloud Service - Learnings

The intent of this postings is to share learings in order to safe lifetime.

When creating an Oracle Java Cloud Service (11.1.1.7 - that might be needed for some Fusion Middleware Products) on OCI-Classic I would suggest:

• the Database must not be 12.2.x, it can be 12.1..0.2
• the Database name must not contain any "-"
  ( Doc ID 2214258.1 Creating new Java Cloud Service fails, if it has hyphen in DBCS name or Identity domain name.)
• Database Password must be between 8 and 30 characters with at least one lower case letter, one upper case letter, one number, one special character (_,-,#) (these 3, only!) and no white space character. It must also not contain the following keywords or their reversed form: root, sys, system, dbsnmp, oracle. Acceptable password example, Ach1z0#d) 
• The Oracle Database Cloud Service database deployment must have backups enabled, otherwise provisioning will fail(Doc ID 2268255.1 Unable To Create JCS Instance As It Says There Are No Oracle Database Cloud Service Instances Available)
• Database User used to create Java Cloud Service must have the SYSDBA role and must have DBA privileges. (Doc ID 2287399.1 Creating JCS Instance Failed)
• the Java Cloud Service - 11.1.1.7 (Version 10.3.6.1.171017) Weblogic Password must start with a lower letter
• (otherwise error "sm.create.service.request.not.validated [DBConnectionIncorrectCredentials]"
• plus Weblogic Password should not have any other special characters than ('$',''_,'#') 

Otherwise your service creastion might fail.