• Disable YottaDB's Octo and AIM

    From =?UTF-8?Q?Jens_Lidestr=C3=B6m?=@21:1/5 to All on Thu Mar 2 01:27:12 2023
    When I start YottaDB for the first time it configures a number database objects for Octo and AIM, which creates database files and global directory entries.

    I would prefer our database environment to be free from any such entities for features that we don't use, to make the environment simpler and easier to understand.

    Example:

    show
    ...
    *** NAMES ***
    Global Region
    ------------------------------------------------------------------------------
    %ydbAIM* YDBAIM
    %ydbAIm* YDBAIM
    %ydbAiM* YDBAIM
    %ydbAim* YDBAIM
    %ydbOCTO* YDBOCTO
    %ydbOCTo* YDBOCTO
    %ydbOCtO* YDBOCTO
    %ydbOCto* YDBOCTO
    %ydbOcTO* YDBOCTO
    ...

    Can I disable Octo and AIM and any other extra bundled tools or features in YottaDB, so that no extra objects are created?

    I didn't find any options for this in the installation script.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From K.S. Bhaskar@21:1/5 to All on Thu Mar 2 08:11:14 2023
    On Thursday, March 2, 2023 at 4:27:13 AM UTC-5, Jens Lideström wrote:
    When I start YottaDB for the first time it configures a number database objects for Octo and AIM, which creates database files and global directory entries.

    I would prefer our database environment to be free from any such entities for features that we don't use, to make the environment simpler and easier to understand.

    Example:

    show
    ...
    *** NAMES ***
    Global Region ------------------------------------------------------------------------------
    %ydbAIM* YDBAIM
    %ydbAIm* YDBAIM
    %ydbAiM* YDBAIM
    %ydbAim* YDBAIM
    %ydbOCTO* YDBOCTO
    %ydbOCTo* YDBOCTO
    %ydbOCtO* YDBOCTO
    %ydbOCto* YDBOCTO
    %ydbOcTO* YDBOCTO
    ...

    Can I disable Octo and AIM and any other extra bundled tools or features in YottaDB, so that no extra objects are created?

    I didn't find any options for this in the installation script.

    These regions are created by sourcing the ydb_env_set file, which is intended to ensure a default installation, recovery after a crash, and manage disk space used by journal files, all with no involvement from the user beyond setting a few environment
    variables (which too are optional as everything has a default). So, it is a great way to use YottaDB without getting into details.

    Advanced users usually do their own scripting for those functions. A good way to get started is to go through the exercises in the Acculturation Guide (https://docs.yottadb.com/AcculturationGuide/).

    You can use the GDE utility (https://docs.yottadb.com/AdminOpsGuide/gde.html) to remove those regions if you don't want them. But I recommend going through the Acculturation Guide first.

    Regards
    – Bhaskar

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Sam Habiel@21:1/5 to K.S. Bhaskar on Thu Mar 2 09:53:09 2023
    On Thursday, March 2, 2023 at 11:11:16 AM UTC-5, K.S. Bhaskar wrote:
    On Thursday, March 2, 2023 at 4:27:13 AM UTC-5, Jens Lideström wrote:
    When I start YottaDB for the first time it configures a number database objects for Octo and AIM, which creates database files and global directory entries.

    I would prefer our database environment to be free from any such entities for features that we don't use, to make the environment simpler and easier to understand.

    Example:

    show
    ...
    *** NAMES ***
    Global Region ------------------------------------------------------------------------------
    %ydbAIM* YDBAIM
    %ydbAIm* YDBAIM
    %ydbAiM* YDBAIM
    %ydbAim* YDBAIM
    %ydbOCTO* YDBOCTO
    %ydbOCTo* YDBOCTO
    %ydbOCtO* YDBOCTO
    %ydbOCto* YDBOCTO
    %ydbOcTO* YDBOCTO
    ...

    Can I disable Octo and AIM and any other extra bundled tools or features in YottaDB, so that no extra objects are created?

    I didn't find any options for this in the installation script.
    These regions are created by sourcing the ydb_env_set file, which is intended to ensure a default installation, recovery after a crash, and manage disk space used by journal files, all with no involvement from the user beyond setting a few environment
    variables (which too are optional as everything has a default). So, it is a great way to use YottaDB without getting into details.

    Advanced users usually do their own scripting for those functions. A good way to get started is to go through the exercises in the Acculturation Guide (https://docs.yottadb.com/AcculturationGuide/).

    You can use the GDE utility (https://docs.yottadb.com/AdminOpsGuide/gde.html) to remove those regions if you don't want them. But I recommend going through the Acculturation Guide first.

    Regards
    – Bhaskar

    While VistA specific, https://www.hardhats.org/projects/New/InstallVistAOnGTM.html contains information on the process needed to create your own GDE file, execute it, and create databases. I am only sending it as it's comparatively short and shows the
    steps quickly.

    A word of warning: Do NOT use the default GDE settings, as settings for stuff like "key_size" are too small. You should always check what you actually need from an application, and tailor your values.

    --Sam

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)