Monitor and Troubleshoot a Resource

Inspect the executing server’s NoSQL runtime. Configuration can exist before the first provider runtime is created.

Inspect Runtime Metrics

Use the server-runtime tree of the relevant target server. This WLST example reads server-local resource state and failures.

serverRuntime()
service = cmo.getNoSQLServiceRuntime()
if service is not None:
    resource = service.lookupNoSQLSystemResourceRuntime('personNoSqlResource')
    if resource is not None:
        print(resource.getState())
        print(resource.getActiveRuntimeCount())
        print(resource.getFailedRuntimeCreationCount())
        print(resource.getLastFailureTime())
        print(resource.getLastFailureMessage())

A connection to the Administration Server shows that server’s local runtime tree. Connect to the relevant Managed Server or use the domain-runtime hierarchy to inspect every target member. An Administration Server connection alone does not establish the state of cluster members.

Additional attributes report provider/type identity, descriptor filename, successful creation count, close count, and last creation time. Counts describe provider lifecycle, not query throughput or connection-pool capacity.

A construction failure reports FAILED and increments the failure count. Later successful creation can return the state to ACTIVE. The last failure message is sanitized.

Diagnose Configuration and Application Failures

The following table connects symptoms to the relevant checks and recovery.

Symptom	Check	Recovery
Activation rejected	Provider/type, properties, path, targets, complete edit	Correct the proposed configuration
Deployment rejected	Declaration, scope, mapping, JNDI uniqueness, local target	Correct the effective binding
SecurityException	Current subject, policy, ownership, authorization availability	Restore intended authorization/context
First database use fails	Failure metrics, endpoint, database, credential input	Correct provider settings and retry as applicable
Retained capability rejected after replacement	Originating configuration generation	Reacquire it from the current handle
Rejection continues after resource recovery	Terminal deployment invalidation	Fully redeploy
Cluster members differ	Applied configuration, connectivity, local metrics	Correct the affected member’s conditions

Collect sanitized messages and timestamps. Avoid credential-bearing property dumps and raw encrypted values. No JDBC-style testPool operation is implied.