We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Discovery Error - "Applicative credentials for CI type cmdb_ci_db_ora_instance are not defined" desp

Vishnu-K
Kilo Sage

Hi Everyone,

 

We are trying to retrieve the Oracle GLAS details. For this, we have created Applicative Credentials for the CI type cmdb_ci_db_ora_instance. These credentials work fine when tested in debug mode against the GLAS patterns.

 

However, when we run Discovery, we get the following error:

"Applicative credentials for CI type cmdb_ci_db_ora_instance are not defined. Please go to the Credentials page to add the appropriate Applicative Credentials."

Has anyone faced this issue before, or does anyone know what could be causing Discovery to not recognize the credentials even though they work correctly in debug mode? Any pointers on what might be missing in the configuration would be appreciated.

 

Thanks in advance

2 REPLIES 2

shubhamseth
Giga Sage

@Vishnu-K 

 

Since the credentials work in Pattern Debug, you can rule out the credential itself. The issue is most likely that Discovery is unable to resolve the Applicative Credential against a CI during runtime.

 

typically occurs when the Oracle Instance CI (cmdb_ci_db_ora_instance) has not yet been created or identified before the GLAS pattern executes.

I would check the following:

  1. Verify that the Oracle Instance Pattern successfully creates/identifies the cmdb_ci_db_ora_instance before the GLAS pattern starts.
  2. In the Pattern Debug/Discovery Log, confirm that the GLAS pattern is receiving a CI of type cmdb_ci_db_ora_instance. If the runtime context is still cmdb_ci_computer or another class, Discovery won't be able to resolve the applicative credential.
  3. Verify the Applicative Credential record:
    • Active = true
    • CI Type = cmdb_ci_db_ora_instance
    • Correct MID Server (if restricted)
    • No Domain Separation restrictions
  4. Check Credential Affinity and ensure no other credential process is overriding the applicative credential during Discovery.
  5. Review the Discovery Pattern Log (not just ECC logs) to identify the exact step where the credential lookup fails.

One question that would help narrow this down:

Are you running the GLAS pattern as part of the standard Oracle Discovery pattern, or are you executing the GLAS pattern independently?

 

If it's being executed independently, this error is expected because there is no Oracle Instance CI context available for Discovery to resolve the applicative credential.

 

 

Issue resolved? → Mark as Correct


Found value? → Mark as Helpful


Tanushree Maiti
Tera Patron

Hi @Vishnu-K 

 

Refer:

https://www.servicenow.com/community/itom-forum/setting-up-oracle-options-for-discovery/m-p/960737

Oracle pluggable database and container database discovery 

https://www.servicenow.com/community/itom-forum/oracle-database-discovery-applicative-credentials/m-...

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti