show...
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.
On Thursday, March 2, 2023 at 4:27:13 AM UTC-5, Jens Lideström wrote:variables (which too are optional as everything has a default). So, it is a great way to use YottaDB without getting into details.
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
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
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 491 |
Nodes: | 16 (2 / 14) |
Uptime: | 121:06:32 |
Calls: | 9,687 |
Calls today: | 3 |
Files: | 13,728 |
Messages: | 6,176,629 |