![]() Then, from client machines, always access the database with the syntax This will ensure that the database is started only on the server machine and that server processes and shared memory segments are present only on the server machine.Įnsuring that a database directory is visible only to the server machine will prevent this problem altogether, because it would make it necessary that all client machines access the database with syntax.Ġ007 VSL_SHM_BUSY Shared memory is in useĠ008 VSL_SHM_ERM Unable to remove shared memoryĠ009 VSL_CLK_ESTART Timer already startedĠ011 VSL_CLK_ESYNC Timer out of synchronizationĠ013 VSL_CLK_ETIMDAT Unable to obtain time of dayĠ018 VSL_PR_EXEC Process execution failedĠ019 VSL_PR_NEXIST Process does not existĠ021 VSL_PR_EWAIT Error waiting for processĠ022 VSL_PR_TBLBUSY Process control block is in useĠ025 VSL_SEM_EGNCNT Unable to get wait countĠ031 VSL_SEM_ECREATE Error creating latch In the case of the above example where db1 is already running on host1 when you try to make a connection from host2, you could successfully make a connection if you used the syntax but your connection would fail if you used the syntax db1 or general, you should always assign ownership of a database to a particular machine, typically configured as a server. If a database is in a directory visible to two machines, you can start it on either machine, as long as it has not already been started on the other machine. ![]() Now, if you try to connect to it from host2, you will get this error, because host2 will try to start db1 on host2, even though it is already running on host1. Next, suppose that db1 has been started by a connection from host1, which has created a server process, cleanup process, and a page cache in shared memory on host1. If the database has been started by one machine and then you try to connect to it using another machine, you will get this error.įor example, suppose that a database named db1 is visible on both machine host1 and machine host2. You can get this error when trying to connect with a database if the database is located on an NFS mounted directory visible to two different machines. Otherwise you need to reconfigure your kernel so that it can allocate more shared memory resources on demand.Ġ005 VSL_SHM_ACCESS Cannot access shared memoryĠ006 VSL_SHM_ELOCAT Cannot locate shared memory If there are multiple databases running on this machine, shut one or more down (if possible), which will free the shared memory used by these databases. VERSANT cannot find enough shared memory for the server page cache. ![]() The format of the error code documentation is:Ġ003 VSL_BLKNO_INVAL Invalid block numberĠ004 VSL_SHM_ALLOC Cannot allocate shared memory This chapter is a reference to VERSANT error codes for all interfaces. Chapter 7 of VERSANT Database Administration, Release 5.2 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |