Problems with Creating Service Instances

You might experience problems when creating services.

In the process of creating a service, the operation failure becomes visible in the following way:

  1. The service instance appears in the Services list in the Oracle Java Cloud Service Console.

  2. An In progress... message appears in the service instance details.

  3. When the creation process fails, a Failed message is displayed and a red exclamation mark appears on the service instance's icon.

  4. The service instance is listed in the Instance Create and Delete History section.

  5. Click on Details to view progress and error messages.

    You can locate additional error messages using the procedure in Find Status Messages for Oracle Java Cloud Service Instances.

The most common sources of failure when creating a service instance include:

  • Timeout errors

  • SSH connection isssues

  • Incorrect credentials

  • Database listener down

The following solutions apply to problems creating service instances for Oracle Java Cloud Service.

I cannot create an Oracle Java Cloud Service — Virtual Image instance when I choose a Oracle Database Cloud Service — Virtual Image database deployment

A failure will occur when you attempt to create an Oracle Java Cloud Service instance with a Oracle Database Cloud Service — Virtual Image database deployment.

To prevent this failure, you must first configure the Oracle Database Cloud Service — Virtual Image environment. See Use a Database Cloud Service - Virtual Image Database Deployment.

I receive a database connectivity error message

You might not be able to create an Oracle Java Cloud Service instance because the oracle user does not have a password on Oracle Database Cloud Service instances. To modify the properties of the oracle users so that the password does not expire, see Problems Creating Deployments in Administering Oracle Database Cloud Service.

I cannot create a service when I have many service instances

Your account might not have enough compute quota to create the service instance.

If you have instances you do not need, delete them. If you need all your service instances, contact Oracle Sales and Services to buy more quota for your account.

I cannot create a service instance, even after waiting for an hour

If service creation fails after one hour, the system might be experiencing a heavy load, and resources are not yet available.

Wait before you try again to create the service. If the problem persists, contact Oracle Support Services.

I cannot create a service instance when the service instance name is not unique

Oracle Java Cloud Service instance creation can fail if the name you choose for the new service instance is identical to the name of another service instance, including a failed service instance. Also, the Oracle Java Cloud Service instance name cannot be the same as the name of an Database Cloud Service instance.

After an attempt to create an Oracle Java Cloud Service instance fails, Oracle Java Cloud Service may require some time to remove items that were created during the attempt. If the new and failed service instance names are identical, a naming conflict may occur and the attempt to create the new service instance may fail.

Note:

As a best practice, always ensure that your Oracle Java Cloud Service instance names are unique.

I can create a service instance but the Coherence Data Tier failed to create

Delete the service instance. Wait before you try again to create the service instance. If the problem persists, contact Oracle Support Services.

I receive an error message stating that no database service is available

If you attempt to create an Oracle Java Cloud Service using an Oracle Database Cloud Service database deployment that does not have backups enabled (Destination=None), then provisioning will fail and issue the following error message:

There are no Oracle Database Cloud Service instances available for Service Level: 
Oracle Java Cloud Service

Create a new database deployment with backups enabled and specify this database deployment when you create a new Oracle Java Cloud Service instance.

I encounter Intermittent provisioning failures for clustered instances based on WebLogic Server 12.2.1

Your attempt to create an Oracle Java Cloud Service instance based on WebLogic Server release 12.2.1 can fail if you create an instance containing a large number of cluster members.

The cause of the problem is that an exclusive configuration lock acquired by one process is released by another process that successfully acquires another exclusive lock.

This problem is intermittent, so try again to provision a service instance. Alternatively, provision a smaller cluster and then scale out your nodes. See Scale Out a Cluster.

I encounter a database connection error when creating an Oracle Java Cloud Service instance

In the process of creating an Oracle Java Cloud Service Instance while using the Service Instance Creation Wizard, you may receive the following error message: Failed to connect to DBaaS Service.

To help identify the problem, confirm that the user name and password are correct by connecting to the database via sqlplus. Also, confirm that you have the correct privileges. For more information, see About Database Cloud Service Roles and Users in Administering Oracle Database Cloud Service.

If you have done these checks and do not see any issues, the problem might be that the oracle password has expired on the database node.

You can change the properties of the oracle user so that the password does not expire. See Problems Administering Deployments in Administering Oracle Database Cloud Service.

Provisioning fails when infrastructure database creation times out

Infrastructure database creation times out and instance provisioning fails if the recycle bin size exceeds its threshold or if the infrastructure database size approaches the maximum database size.

Find the following information in the job file:

  • Database recycle bin objects count
  • Database recycle bin size
  • Database maximum DB size
  • Database current DB size

Look for the following messages:

  • Recycle bin size has exeeded 50% of current DB Size. Consider purging the recycle bin.
  • DB usage size has exeeded 75% of Max DB Size.

Oracle recommends that you purge the database recycle bin if the size exceed its limit. Clean up the database if the database usage size approaches the maximum database size.

I cannot select my Autonomous Transaction Processing database or Oracle Cloud Infrastructure Database from the web console

Your Autonomous Transaction Processing database or Oracle Cloud Infrastructure Database will not appear on the Database Instance Name dropdown field as an infrastructure schema database choice unless you specify the following policies:

For an Autonomous Transaction Processing database:

Allow service PSM to inspect autonomous-database in compartment compartment_name

For an Oracle Cloud Infrastructure Database:

Allow service PSM to inspect database-family in compartment compartment_name

For information on creating policies, see Creating the Infrastructure Resources Required for Oracle Platform Services.