Using Octo on Yottadb Replicated DB

[Agostino Nigro]

Hello all,

My next project is trying to use Octo for reporting on data within my VistA Instance. So far I have done the following:

1. Configured replication from servers vistaprod --> vistaro and confirmed it is functioning appropriately
   
2. Ensured that both servers have the same scripts and systemd configurations, but on the vistaro server, disabled the systemd for Taskman/Filers and CPRS GUI so that Tasman doesn't try to spin up since it is replicating to this server. Additionally on the VistARO and VistAPROD servers have configured a cron job to keep only 15 days of journals so not to use too much space
3. I have tried now on the vistaro server to configure access via octo and then rocto, but when I attempt it, I get the following error:

gtmuser@vistaro:~$ $ydb_dist/plugin/bin/octo

[ERROR]: ERR_YOTTADB: YottaDB error: 150378098,(SimpleAPI),%YDB-E-SCNDDBNOUPD, Database Updates not allowed on the secondary

Any assistance with this would be greatly appreciated! Thanks!

[Sam Habiel]

Agostino,

I am traveling and can’t type much. 

YottaDB has two kinds of replication: BC (Read-Only), and SI (Write allowed). You need to use SI for Octo. 

—Sam

--
--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/hardhats/bd96d461-f55e-401b-a6aa-2ff2d6ee4987n%40googlegroups.com.

[Agostino Nigro]

Thanks for that Sam! I have It working now!

[Sam Habiel]

Bravo! It’s not easy. 

—Sam

To view this discussion visit https://groups.google.com/d/msgid/hardhats/9028d5bc-6ee3-42a2-b116-044c041ca0fdn%40googlegroups.com.

[Agostino Nigro]

Thanks Sam! Safe travels and appreciate your help with this! Have already got Rocto configured and setup so lots of fun to be had!

[Nancy Anthracite]

If this is a production system in the United States, I would advise you hold
on to Journals in a separate place for more time.

--
Nancy Anthracite

On Saturday, August 15, 2026 11:38:01 AM Eastern Daylight Time Agostino Nigro
wrote:

> Hello all,
>
> My next project is trying to use Octo for reporting on data within my VistA
> Instance. So far I have done the following:
>

> 1. Configured replication from servers vistaprod --> vistaro and

> confirmed it is functioning appropriately

> 2. Ensured that both servers have the same scripts and systemd

> configurations, but on the vistaro server, disabled the systemd for
> Taskman/Filers and CPRS GUI so that Tasman doesn't try to spin up since
it
> is replicating to this server. Additionally on the VistARO and VistAPROD
> servers have configured a cron job to keep only 15 days of journals so not
> to use too much space

> 3. I have tried now on the vistaro server to configure access via octo

> and then rocto, but when I attempt it, I get the following error:
>

> *gtmuser@vistaro*:*~*$ $ydb_dist/plugin/bin/octo

[Agostino Nigro]

Hi Nancy! It is not a full production system, just running in my homelab (just is named that for ease of understanding which one is running which services).

I did though just adjust it to be 30 days - thanks!

[Nancy Anthracite]

My concern was that it was a production system with patient data. You could
just not journal at all if it isn't something like that.

--
Nancy Anthracite

On Sunday, August 16, 2026 11:10:48 AM Eastern Daylight Time Agostino Nigro
wrote:

> Hi Nancy! It is not a full production system, just running in my homelab
> (just is named that for ease of understanding which one is running which
> services).
>
> I did though just adjust it to be 30 days - thanks!
>
> On Sunday, August 16, 2026 at 11:02:04 AM UTC-4 Nancy Anthracite wrote:
>
> > If this is a production system in the United States, I would advise you
> > hold
> > on to Journals in a separate place for more time.
> >
> >

[K.S. Bhaskar]

Journaling is like brushing teeth. Only brush those teeth that you want to keep. Journal only those database regions that you don't want to delete and start over after a crash! Any database region with data you care about must be journaled.

Regards

- Bhaskar

[iq100]

Use only dentists that do not crash. Competent care givers create systems that do not crash. :-)