My Oracle Support Banner

EXACS:DB STATUS is "FAILED" in CLOUD UI (Doc ID 2908991.1)

Last updated on NOVEMBER 16, 2022

Applies to:

Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

 DB(test) showing "FAILED" in UI but the DB is actually up and running in the Domu nodes in Exacs.

/From getDatabases.out

"test1" : {
"id" : "<Agent_id>",
"dbSyncTime" : 1667927711988,
"createTime" : 1586124000000,
"updateTime" : 0,
"dbName" : "test",
"dbUniqueName" : "TEST1",
"dbDomain" : "<FQDN>.com",
"dbId" : 323355495,
"cpuCount" : 20,
"sgaTarget" : "7600MB",
"pgaAggregateTarget" : "5000MB",
"dbSize" : "1103GB",
"dbUsedSize" : "987GB",
"totalFraSize" : "14214GB",
"fraSizeUsed" : "249GB",
"dbKmsKeyOcid" : null,
"isCDB" : true,
"dbRole" : "PRIMARY",
"dbType" : "RAC",
"dbClass" : "OLTP",
"dbEdition" : "EE",
"dgEnabled" : true,
"patchVersion" : "12.2.0.1.210420",
"resourceOCIDSettings" : {
"tenancyOCID" : "<TENANCY_OCID>",
"compartmentOCID" : "<COMP_OCID>",
"resourceOCID" : "<RESC_OCID>",
"resourceID" : "<RED_ID>",
"resourceType" : "CDB",
"parentResourceID" : null
},
"dbCharacterSet" : {
"characterSet" : "WE8MSWIN1252",
"nlsCharacterset" : "AL16UTF16",
"dbTerritory" : "AMERICA",
"dbLanguage" : "AMERICAN"
},
"dbNodeLevelDetails" : null,
"pdbs" : null,
"messages" : [ {
"message" : "[FATAL] [DBAAS-60018] Unable to get patch version of oracle home '/<DB_HOME>'.",>>>>>>>>>>>>>>>>>>>
"errorCode" : "DBAAS-60018",
"cause" : null,
"action" : "Make sure that home exist and registered to central inventory.",
"extraDetails" : null,
"stackTrace" : null,
"severityLevel" : "SEVERE",
"exceptionCause" : {
"message" : "[FATAL] [DBAAS-60018] Unable to get patch version of oracle home '/<DB_HOME>'.",>>>>>>>>>>>>>>>>>>>
"errorCode" : "DBAAS-60018",
"cause" : null,
"action" : "Make sure that home exist and registered to central inventory.",
"extraDetails" : null,
"stackTrace" : null,
"severityLevel" : "SEVERE",
"exceptionCause" : {
"message" : "[FATAL] [DBAAS-60022] Command '/<DB_HOME>/OPatch/opatch lspatches|egrep -i 'DATABASE BUNDLE PATCH|DATABASE.*RELEASE|DATABASE PATCH FOR EXADATA'' execution has failed on nodes [NODE1].",
"errorCode" : "DBAAS-60022",
"cause" : null,
"action" : null,
"extraDetails" : "Result of node:lpitexacs01-57g6g1\nERRORS:\n/<DB_HOME>/OPatch/opatch: line 839: [: too many arguments\n/<DB_HOME>/OPatch/opatch: line 839: [: too many arguments\n\nExit code of the operation:1",
"stackTrace" : null,
"severityLevel" : "SEVERE",
"exceptionCause" : null

 

//From ocr

srvctl config database -d test

Database unique name: test1

Database name: test>>>>>>>>>>>>>>>>>>>>>

Oracle home: /<DB_HOME>

Oracle user: oracle

Spfile: +DATAC1/test1/spfilec0dbluc1.ora

Password file: +DATAC1/test1/PASSWORD/passwd

Domain: <FQDB>.com

Start options: open

Stop options: immediate

Database role: PRIMARY

Management policy: AUTOMATIC

Server pools:

Disk Groups: DATAC1,RECOC1

Mount point paths:

Services:

Type: RAC

Start concurrency:

Stop concurrency:

OSDBA group: dba

OSOPER group: racoper

Database instances: test1,test2

Configured nodes: Node1,Node2

CSS critical: no

CPU count: 0

Memory target: 0

Maximum memory: 0

Default network number for database services:

Database is administrator managed

 

 

//From opatch lsinventory of <DB_HOME> is failing with below error.

 

 ./opatch: line 839: [: too many arguments
./opatch: line 839: [: too many arguments
Java (1.7) could not be located. OPatch cannot proceed!>>>>>>>>>>>>>>>>>>>
OPatch returns with error code = 1

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.