HELP: Not enough memory to increase memory! 
Author Message
 HELP: Not enough memory to increase memory!

Hi everybody,

I screwed my Sybase server (version 4.9.2 on Solaris 2.3) and I can't figured
out how to recover.  I increased the "user connections" parameter without
increasing "memory" at the same time.

Now every stored procedure (including sp_configure!) abort with:

        Msg 701, Level 17, State 3:
        Procedure 'sp_configure', Line 338:
        There is insufficient system memory to run this query.

I tried to update sysconfigures to go back to the previous user connections
value but it tells me:

        1> update sysconfigures set value = 25 where config = 103
        2> go
        00: 95/06/15 16:37:31.35 server: WARNING: memory usage in procedure headers (12)
        does not match memory usage count in Pss (1) for server process id 1.Msg 259, Level 16, State 2:
        Line 1:
        Ad-hoc updates to system catalogs not enabled. System Administrator must
        reconfigure system to allow this.

The manual tells me that I have to run sp_configure "allow updates" before
I can modify the system tables -- which I can't.  I tried

        update syscurconfigs set value = 1 where config = 102

but I get the same message.  So how can I "allow updates" without running
sp_configure???

Cheers, and thanks on advance for any pointers.



Mon, 01 Dec 1997 03:00:00 GMT
 HELP: Not enough memory to increase memory!

Quote:

> Hi everybody,
> I screwed my Sybase server (version 4.9.2 on Solaris 2.3) and I can't figured
> out how to recover.  I increased the "user connections" parameter without
> increasing "memory" at the same time.

> Now every stored procedure (including sp_configure!) abort with:

>    Msg 701, Level 17, State 3:
>    Procedure 'sp_configure', Line 338:
>    There is insufficient system memory to run this query.

No sweat.

Run the buildmaster utility with the -r option and every configuration
variable will be set to its default value without disturbing any
databases or anything else in any way.

Refer to the chapter buildmaster on pg 4-17 in the
Command Reference Manual

Hope this helps
Martin



Tue, 02 Dec 1997 03:00:00 GMT
 HELP: Not enough memory to increase memory!
|>
|> Hi everybody,
|>
|> I screwed my Sybase server (version 4.9.2 on Solaris 2.3) and I can't figured
|> out how to recover.  I increased the "user connections" parameter without
|> increasing "memory" at the same time.
|>
|> Now every stored procedure (including sp_configure!) abort with:
|>
|>   Msg 701, Level 17, State 3:
|>   Procedure 'sp_configure', Line 338:
|>   There is insufficient system memory to run this query.
|> [stuff deleted]
|>
|> The manual tells me that I have to run sp_configure "allow updates" before
|> I can modify the system tables -- which I can't.  I tried
|> but I get the same message.  So how can I "allow updates" without running
|> sp_configure???

Check out "buildmaster -r" in the manual on SQL-Server Utilities.  "This
option changes the configuration variables to their default values without
rebuilding the master database.  Use this option when the value of a
configuration variable is set so high that SQL Server cannot start."

                                Good Luck
                                Teresa Larson

+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
| Teresa A. Larson  ------  Hughes Information Technology Corporation  |
| NASA/GSFC Code 933.0                         voice:  (301) 286-7867  |
| Greenbelt, Maryland  20771                   fax:    (301) 286-1777  |

+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~+
                        Standard disclaimer ...



Tue, 02 Dec 1997 03:00:00 GMT
 HELP: Not enough memory to increase memory!

Quote:

> Hi everybody,

> I screwed my Sybase server (version 4.9.2 on Solaris 2.3) and I can't figured
> out how to recover.  I increased the "user connections" parameter without
> increasing "memory" at the same time.

Use buildmaster (like other folks have mentioned) but don't do -r
(unless you really have to)... use -y"all" to list all the parameters
of the master device:

%buildmaster -d/dev/rdsk/dks0d3s0 -yall
.
.
.

then to change user connections:

%buildmaster -d/dev/rdsk/dks0d3s0 -y"cusrconnections=10"

or something...

Pablo Sanchez              | Ph # (415) 390.3812        Fax # (415) 390.2821

===============================================================================
"I am accountable for my actions." "Remember that a failure to plan ahead ...
   - pablo                          is rarely considered a crisis by anyone
                                    except the person who erred." - vjs



Tue, 02 Dec 1997 03:00:00 GMT
 HELP: Not enough memory to increase memory!

Quote:

>I screwed my Sybase server (version 4.9.2 on Solaris 2.3) and I can't figured
>out how to recover.  I increased the "user connections" parameter without
>increasing "memory" at the same time.

>Now every stored procedure (including sp_configure!) abort with:

>    Msg 701, Level 17, State 3:
>    Procedure 'sp_configure', Line 338:
>    There is insufficient system memory to run this query.

You might try using the buildmaster utility to change the user connections
value.  As sybase or root, run the following command:

        $SYBASE/bin/buildmaster -d <master device> -ycusrconnections=<new value>

where <master device> is the device name of your master and <new value> is what
you want the user connections set to. (The database must be shut down in order
for you to do this.)  If this does not work, try the following command:

        $SYBASE/bin/buildmaster -d <master device> -r

This will change all configuration variables to their default values.  Then
restart the database.

Mary Shawhan
Network Administrator
AT&T Bell Labs



Tue, 02 Dec 1997 03:00:00 GMT
 HELP: Not enough memory to increase memory!

|> I screwed my Sybase server (version 4.9.2 on Solaris 2.3) and I can't figured
|> out how to recover.  I increased the "user connections" parameter without
|> increasing "memory" at the same time.
|>
|> Now every stored procedure (including sp_configure!) abort with:
|>
|>   Msg 701, Level 17, State 3:
|>   Procedure 'sp_configure', Line 338:
|>   There is insufficient system memory to run this query.

You need to run buildmaster -ymemory big_value -dmaster_dev. I don't think this is documented, so you may want to check with Sybase tech support about the details before doing it. You probably ought to be calling them anyway.



Fri, 05 Dec 1997 03:00:00 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Not enough memory/Virtual memory error from large query

2. Memory issue (Not enough storage is available to complete this operation )

3. Not enough memory to complete query

4. Error Message "Not Enough Memory"

5. Not enough memory error

6. Mesg 17155 : initblkmem: not enough memory for MEMMAP structures

7. not enough memory to run this procedure

8. MSMail32 won't run - not enough memory???

9. Error message "Not Enough Memory"

10. There is not Enough Memory to Update the Display

11. Not enough memory error.

12. ERROR: 17803 - not enough memory


 
Powered by phpBB® Forum Software