We're here to help!

Error : DDC creation on this host cannot continue. It is possible that dbvctl is not installed.

Follow

This issue is encountered when using the GUI to create a new standby with a new installation of Dbvisit on Primary and Standby. RAC to RAC using action scripts.

When selecting the Source Host on the Create New Configuration page, the following error appears :

An unspecified error has occurred - DDC creation on this host cannot continue. It is possible that dbvctl is not installed.

Problem Details

Problem Statement

This issue is encountered when using the GUI to create a new standby with a new installation of Dbvisit on Primary and Secondary. When selecting the Source Host on the Create New Configuration page, the following error appears.

Applicable Error Code

An unspecified error has occurred - DDC creation on this host cannot continue. It is possible that dbvctl is not installed. 

Affected Versions

v8,v9

Affected Platforms

All


Description

This issue is encountered when using the GUI to create a new standby with a new installation of Dbvisit on Primary and Secondary. When selecting the Source Host on the Create New Configuration page, the following error appears.

Solution

1. Determine the PID of the dbvagent process

ps -ef|grep dbv

2. Run the following command to get the relevant process environment list for the dbvagent PID on Primary. 

xargs --null --max-args=1 < /proc/<pid>/environ
3. Capture the output into a text file - here's an example
$ xargs --null --max-args=1 < /proc/26762/environ
__CLSAGFW_TYPE_NAME=ora.cvu.type
_CRS_CRS_CSS_NODENAME=oralab01
XDG_SESSION_ID=2368
HOSTNAME=oralab01.fullspectrum.net
ORA_CRS_HOME=/u01/app/11.2.0/grid
_CRS_LOAD=1
SHELL=/bin/bash
TERM=vt100
_CRS_AGENT_FILENAME=/u01/app/11.2.0/grid/bin/scriptagent
HISTSIZE=1000
__CRSD_CONNECT_STR=(ADDRESS=(PROTOCOL=IPC)(KEY=CRSD_IPC_SOCKET_11))
NLS_LANG=AMERICAN_AMERICA.AL32UTF8
_CRS_CRS_HOME=/u01/app/11.2.0/grid
_CRS_ACL=owner:oracle:rwx,pgrp:oinstall:rwx,other::r--
CRF_HOME=/u01/app/11.2.0/grid
OLDPWD=/u01/dbvisit_shared_home/dbvisit8/dbvagent
_CRS_ID=dbvagent 1 1
_CRS_ENABLED=1
_CRS_DEGREE_ID=1
_CRS_CARDINALITY_ID=1
_CRS_ACTION_SCRIPT=/u01/dbvisit_shared_home/dbvisit8/dbvagent/action-script.scr
ORA_DAEMON_TRACING_LEVELS=AGENT=0,AGFW=0,CLSFRAME=0,CLSVER=0,CLUCLS=0,COMMCRS=0,COMMNS=0,CRSAPP=0,CRSCCL=0,CRSCEVT=0,CRSCOMM=0,CRSD=0,CRSEVT=0,CRSMAIN=0,CRSOCR=0,CRSPE=0,CRSPLACE=0,CRSRES=0,CRSRPT=0,CRSRTI=0,CRSSE=0,CRSSEC=0,CRSTIMER=0,CRSUI=0,CSSCLNT=0,SuiteTes=0,UiServer=0,OCRAPI=1,OCRCLI=1,OCRSRV=1,OCRMAS=1,OCRMSG=1,OCRCAC=1,OCRRAW=1,OCRUTL=1,OCROSD=1,OCRASM=1
GIPCD_PASSTHROUGH=false
_CRS_SERVER_POOLS=
_CRS_RESTART_ATTEMPTS=3
_CRS_NOT_RESTARTING_TEMPLATE=
_ORA_AGENT_ACTION=TRUE
__CRSD_AGENT_NAME=/u01/app/11.2.0/grid/bin/scriptagent_oracle
_CRS_PROFILE_CHANGE_TEMPLATE=
USER=root
__CRSD_MSG_FRAME_VERSION=2
...
...
For some reason, there's an issue with how the resource is started from the cluster. 
 
4. Edit your dbvagent action script and add the following line
case "$1" in
    'start')
            export USER=oracle
          ./dbvagent -d start
          RET=0
          echo "Running start dbvagent resource with return code $RET"
    ;;
...
...
5. Restart the dbvagent resource and try to create the new DDC
 
Have more questions? Submit a request

Comments