Memory problems. . . 
Author Message
 Memory problems. . .

I am trying to increase the amount of memory Informix can use.  So far I have h
ad no luck.  I attempted to create a new dbspace and a new chunk, but now for s
ome inexplicable reason I get the following errors:
    529:  Cannot attach to shared memory
    123:  ISAM error: no shared memory

What am I doing wrong?  Is this even the right way to go about increasing memor
y?  (I need more for a large database.)  If not, how do I increase the amount o
f memory ISQL has?
Thanks in advance.

Michael Gibson



Sat, 08 Jun 1996 22:25:44 GMT
 Memory problems. . .

Quote:

>Subject: Memory problems. . .
>Date: Tue, 21 Dec 93 14:25:44 EST
>X-Informix-List-Id: <news.5156>

>I am trying to increase the amount of memory Informix can use.  So far I
>have had no luck.  I attempted to create a new dbspace and a new chunk,
>but now for some inexplicable reason I get the following errors:
>    529:  Cannot attach to shared memory
>    123:  ISAM error: no shared memory

>What am I doing wrong?  Is this even the right way to go about increasing
>memory?  (I need more for a large database.)  If not, how do I increase
>the amount of memory ISQL has?

There seems to be some confusion here between disk space and memory space.

Adding a new chunk in a new dbspace provides more disk storage.  To use the
new dbspace, you will need to create one or more tables (or databases)
which use the new dbspace.  Otherwise it will sit there, unused.  If you
are trying to provide more space for an existing table or database, then
you should probably drop the new, unused dbspace, and then add the chunk
again as extra space in the existing dbspace which has run out of space.

On the other hand, your errors indicate that you have a problem with shared
memory.  The errors you give are unusual -- normally you get other, less
informative, error messages when you try to attach to a non-existent chunk
of shared memory, so I wonder if they mean what they say.  Can you run
tbstat?  This should allow you to determine whether your OnLine system is
up and it is just ISQL that has problems, or whether the OnLine system is
down so anything and everything will have problems.  Assuming OnLine is up,
what is the value of SHMBASE in your tbconfig file?  If it is 0x100000 (1
MB), you should probably increase it, to 0x400000 or 0x800000 (4MB or 8MB).
Note: this is not the size of the shared memory, just the address to which
it will be mapped.  If you change SHMBASE, remember to take OnLine off-line
and then bring it back up again.  I'd do it using "tbmode -ky; tbinit"; you
may prefer to use tbmonitor.  After doing this, check that you can run
tbstat.  If not, then there is a basic configuration problem; if you can,
then the chances are that ISQL will now work.

If none of the above applies, then you'll need to be clearer about what
your problem is, and you should provide hardware and software version
information.

Happy Christmas.

Yours,



Tue, 11 Jun 1996 01:08:04 GMT
 
 [ 2 post ] 

 Relevant Pages 

1. Suspect Memory Problem about SQL Server

2. Memory Problem!!!

3. SQL Server memory problems

4. Memory Problems with MMC.EXE and Novell Client

5. SQL Memory problem

6. SQLCE and MEMORY Problems

7. Win98 clients having severe memory problems in w/SQL connectivity

8. Memory Problem in SQL Cluster

9. Win98 Clients experiencing severe memory problems attaching to SQL2k

10. tempdb memory problem

11. RAM Memory Problem

12. memory problems


 
Powered by phpBB® Forum Software