DBvisit suppport gave me an answer.

It works if you build it yourself and then start dbvisit standby

Once you have created the standby database manually using RMAN, configure Dbvisit Standby to automatically send and apply logs to standby database.

1) Install latest Dbvisit Standby software on both primary and standby servers.
Please download the latest release (7.0.60) here:http://www.dbvisit.com/products/download_standby/
Please refer here for the installation guide:https://dbvisit.atlassian.net/wiki/pages/viewpage.action?pageId=19005551

2) Configure DDC file, AMM, and Database repository by running ./dbvisit_setup executable on primary. Choose option 1 from the menu to configure them.

Options:
       1) New Dbvisit Database setup (combines options 2,3,4)

Ref:https://dbvisit.atlassian.net/wiki/display/UGDS7/Initial+Dbvisit+Standby+Configuration

Once done, you should have now a DDC file created on primary that will automatically be transferred to standby server.

3) You can then try sending and applying of logs manually to test if everything is running fine. Please refer below link.
Ref: https://dbvisit.atlassian.net/wiki/pages/viewpage.action?pageId=28508276

4) Once send and apply of logs are fine, you can then schedule Dbvisit default commands (ship and transfer). You have two options here - either via GUI (if you are running dbvserver GUI) or via cron. Please refer below links for more details.
https://dbvisit.atlassian.net/wiki/display/UGDS7/Dbvisit+Standby+Scheduling+-+Linux
https://dbvisit.atlassian.net/wiki/pages/viewpage.action?pageId=19005746