Dbvisit Standby on Windows - Bad File Descriptor – Dbvisit Support

Read our docs Dbvisit commands return error both in command line and GUI in windows

Problem Details

Problem Statement

Dbvisit commands on standby

Applicable Error Code

Return code = 802

Affected Versions

Standby Version 7.0

Affected Platforms

Windows

Problem Description

When using Dbvisit Standby on Windows it is possible to get an error: Bad file descriptor.... when running any Dbvisit Standby commands (GUI or Command Line). Below is just one example where the DDC file was modified to look like this:

PATH = C:\Windows;C:\Windows\system32
PATH = C:\Win

When we then try and get the status of the database we see the Bad file descriptor error:

C:\Program Files (x86)\Dbvisit\Standby>dbv_oraStartStop.exe status testdb
=============================================================
Dbvisit Standby Database Technology (7.0.24.13223) (pid 728)
dbv_oraStartStop.exe started on DBVWIN101: Tue Dec  2 21:49:26 2014 ()
=============================================================

201412022149 Bad file descriptor- Cannot connect: D:\app\oracle\product\11.2.0\db_1\bin\sqlplus.exe (/no
              Dbvisit Standby terminated.
Return code = 802

(Tracefile required if contacting Dbvisit Standby support: C:\Program Files (x86)\Dbvisit\standby\trace\
  No Mail sent as SEND_MAIL_FLAG_DR = N

Solution

This is due to the PATH variable in the DDC file not being set to the correct values. Backup the current PATH value in the DDC file and modify it to ensure it looks like the following:

PATH=C:\Windows;C:\Windows\system32

Once the PATH variable in the Dbvisit Standby DDC file is updated, retry the failed operation.

Anton Els December 03, 2014 09:46

We're here to help!

Dbvisit Standby on Windows - Bad File Descriptor

Comments