Troubleshooting

Use troubleshooting information to identify and address common issues that can occur when working with your Internet of Things (IoT) Platform.

Make sure you have the required permissions. An administrator grants access by creating the required policies. For more information, see Prerequisites and Policy Details for the Internet of Things (IoT) Platform.

Update your passwords

You may need to reset your database password when connecting to the database using APEX, or when connecting directly to the database using the Identity domain group.

Cause: If you are using APEX and you need to reset your password

If you configure access to view your IoT data in APEX, then two different users are created, a database user and an APEX Workspace Administrator user. These are two different users with the same user name and the same initial password. You can update the passwords for each user.

Remedy: Update your APEX database password

Only an APEX workspace administrator can change the database user's password. Initially, the APEX workspace administrator uses your APEX database password to log in, and then follows these steps to change the database password.
In APEX, log in to the IoT domain's Workspace as an administrator, using the following as the workspace name and database user name, with your current APEX database password.
Note

Notice the two underscores __WKSP.
```
<domain-short-id-from-device-host>__WKSP
```
Go to SQL Workshop, select SQL Commands.
Confirm the <iot-domain-short-id-from-device-host>__WKSP schema is selected from the top right schema drop-down menu. Notice the schema contains two underscores.

Use this SQL ALTER USER statement and the required REPLACE clause to change your database user's password:

ALTER USER <workspace-administrator-user-name> IDENTIFIED BY "<new-password>" REPLACE "<old-password>";

Select Run.
Example results showing the password update:
```
User altered.

0.24 seconds
```

Remedy: Update your APEX password

To change your APEX password:

As an APEX workspace administrator, you can change the workspace admin password. After logging into APEX as an administrator, select the Set APEX Account Password option. For more information, see Resetting your password in APEX.
As an APEX user, when you log in to the APEX application for the first time, you will be prompted to change your APEX password. After your initial log in, you can reset your password on the APEX log in page.

Note

Depending on the system you use, double quotes may be required when your password contains special characters.

Remedy: Reset the APEX workspace password using the API

As an APEX workspace administrator, you can change if the IoT APEX workspace account is locked, as an administrator you can run this ConfigureIotDomainDataAccess operation twice to reset the APEX workspace password.

POST /20250531/iotDomains/{iotDomainId}/actions/configureDataAccess
{
  "type": "APEX",
  "dbWorkspaceAdminInitialPassword": "<your-apex-initial-password>"
}

Cause: Missing authorization when connecting directly to the database

If you establish a direct connection to the database using the following CLI command, and you don't have authorization to connect directly to the database, then you can create a new database password for the Identity domain group to connect.

For example, when you use the oci iot domain configure-direct-data-access command and the required parameters to configure an IoT domain's authentication to establish a direct database connection and you can not connect.

oci iot domain configure-direct-data-access --iot-domain-id <iot-domain-OCID> --db-allow-listed-identity-group-names '["<tenancy-OCID:<identity-domain-name>/<identity-group-name>"]'

or if you use this format:

oci iot domain configure-direct-data-access --iot-domain-id <iot-domain-OCID> --db-allow-listed-identity-group-names '["<tenancy-OCID:<identity-group-name>"]'

Remedy: Update the database password for the Identity domain user

Update your IAM Identity domain user's database password. To do that, log in to your IoT tenancy, and complete the following steps:

Open the navigation menu, go to Identity & Management, select domains.
On the domain list page, select the Identity domain that you want to work with and connect to an IoT domain.
Select the User Management tab, select the user you want to update the password for. Select the Database Passwords tab, to update the password delete your current IAM database password and create a new IAM database password.

Digital Twin Models Use DTDL Specifications v3

Cause: Creating a digital twin model results in error

When you create a digital twin model if you get an error, confirm you are using only DTDL v3 specifications that are supported.

Remedy: Use only supported v3 DTDL specifications

When you define the digital twin model all DTDL v3 specifications are supported, except MQTT extensions and writable properties.

If a writable property is included in the digital twin model, it must be set to false.

Service Limits Exceeded

Troubleshoot IoT domain or IoT domain group resource service limits per region.

Cause: IoT resources limits per region

Internet of Things (IoT) Platform has limits on the number of resources per region.

If you try to create more than 2 IoT domains or more in an IoT domain group, then you may see the following error. For more information, see create an IoT domain or an IoT domain group.

The following service limits were exceeded: <resource-count>. Request a service limit increase from the service limits page in the console.

Note

Oracle restricts creating up to 2 IoT domains in each IoT domain group. The maximum number of IoT domain groups is 5 and maximum number IoT domains is 10 per region in your tenancy. To create an IoT domain your user must have read access for the associated IoT domain group.

Remedy: Upgrade and increase the limits

See Service Limits to review the limits for IoT resources. If you need to increase the limits, you can request a service limit increase.

Using quotes with OCIDs

In Oracle Cloud Infrastructure (OCI), an OCID (Oracle Cloud Identifier) is a unique ID assigned to each cloud resource. Depending on the specific scenario, when interacting with OCI through the Command Line Interface (CLI), JSON input, or API calls, you may need to quote the OCID so its interpreted as string value. Or you may need to remove quotes if a code editor you are working adds unwanted quotes.

Note

Some applications or code editors may add unwanted quotes to your values, review and remove any unwanted quotes or this can cause an error.

To conform to JSON standards and ensure correct interpretation by OCI services an OCID must be enclosed in double quotes, so that its treated as string value within JSON structures or complex inputs. When passed as direct, simple arguments to CLI commands, explicit quoting is often not required.

Not quoting OCIDs in CLI: If an OCID is a direct argument to a CLI command, you do not need to explicitly use quotes unless it's part of a larger string or a complex type that requires quoting.
This example shows using an OCID is a CLI command without quotes:
```
oci iot digital-twin-adapter create --iot-domain-id ocid1.iotdomain.oc1.example-ocid 
```
Quoting OCIDs when embedding within JSON strings: If you are passing a complex parameter to a CLI command as a JSON string with an OCID value, then the OCID within the JSON string must be enclosed in double quotes and escaped if necessary. Depending on the tool and operating system you are using, for Windows its required. For more information, see Passing Complex Input in CLI.
Quoting OCIDs in JSON objects: All string values within a JSON object must be enclosed in double quotes. If an OCID is a value in a JSON object that you are sending to OCI using an API or in a CLI command, it must be double-quoted:
```
{ "displayName": "my_resource", "compartmentId": "ocid1.compartment.oc1..<example>" } 
```
Quoting OCIDs in API Calls: In request bodies or parameters: When making API calls to OCI, if an OCID is part of the request body as a JSON payload or a query parameter, then it should be treated as a string and enclosed in double quotes within the JSON payload. Or it must be properly encoded as a string for URL parameters. The specific requirements depend on the API endpoint and the data type expected for that parameter.

In Digital Twin Instances using quotes for an external key

External key equals device username: If a digital twin instance is created with quotes embedded in the external key for example: "\"american-auto\"", then the basic authentication username in your curl request must also include the quotes, or a mismatch occurs and results in a 401 Unauthorized error.

If you use quotes in your digital twin instance external key value, then you must use the quotes when you make an API call. Or you can omit the quotes in your external key value.

To avoid quoting issues, do not use quotes in a digital twin instance's external key value. For example, this shows the --external-key CLI parameter and the corresponding value that does not use quotes:

--external-key 01-23-45-67-89-ab

In Digital Twin Adapters JSON objects must use quotes

Unquoted expressions are not supported in digital twin adapter inbound routes. For more examples, see Scenarios.

In a digital twin adapter, the inbound-route expressions are not supported as raw values without quotes, for example:

"$.speed": ${(.velocity_kph / 1.609) | floor}

In a digital twin adapter, for the inbound-route values expressions must be embedded as strings using quotes, for example:

"$.speed": "${(.velocity_kph / 1.609) | floor}"

Oracle Cloud Infrastructure Documentation