Topic
  • 9 replies
  • Latest Post - ‏2013-03-27T06:53:37Z by Darell1
matt.devine
matt.devine
7 Posts

Pinned topic SQL1219N Error: Not letting me drop database

‏2008-05-19T16:19:05Z |
So I'm trying to drop my database and I get the following error, I can't really figure out what's going wrong. The systems has plenty of available memory, so much that it won't all get utilized. Any Ideas?

OS: Windows Server 2003 R2 Enterprise Edition
Memory: 16 GB

SQL1219N The request failed because private virtual memory could not be allocated.

Explanation: The instance was unable to allocate enough private virtual memory to process the request. This may be a result of shared memory allocations made in other (unrelated) processes.

User Response: The problem may be corrected by:

* Stopping other applications running on the machine, especially those that use large amounts of shared memory.

sqlcode: -1219

sqlstate: 57011

Matt Devine
Updated on 2013-03-27T06:53:37Z at 2013-03-27T06:53:37Z by Darell1
  • Saurabh.Jain
    Saurabh.Jain
    35 Posts

    Re: SQL1219N Error: Not letting me drop database

    ‏2008-05-19T17:50:23Z  
    Did you check the diag log? What error does it say? If possible, I would suggest to raise a PMR.

    -Saurabh
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: SQL1219N Error: Not letting me drop database

    ‏2008-07-31T14:01:41Z  
    Matt,

    did you solve this problem? I have the same sing here. (Windows XP SP 3, DB2 9.5, 4 GB RAM)

    Frank Steimke
  • wifo
    wifo
    2 Posts

    Re: SQL1219N Error: Not letting me drop database

    ‏2008-08-26T12:13:49Z  
    Matt,

    did you solve this problem? I have the same sing here. (Windows XP SP 3, DB2 9.5, 4 GB RAM)

    Frank Steimke
    Hi,

    in my case it depends to the envirónment variable DB2_EXTSECURITY=YES. In the db2diaglog i get an

    2008-08-26-11.00.05.396000+120 E984H419 LEVEL: Error (OS)
    PID : 2072 TID : 3208 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    EDUID : 3208 EDUNAME: db2ipccm
    FUNCTION: DB2 UDB, oper system services, sqloImpersonateLocalSystem, probe:20
    MESSAGE : ZRC=0x83000005=-2097151995
    CALLED : OS, -, OpenProcessToken
    OSERR : 5 "Zugriff verweigert"

    in the db2 command center i get the sql1219n.

    after setting the variable to NO the error does not occur anymore.

    hope that helps.

    wifo
  • Renee_Fisher
    Renee_Fisher
    2 Posts

    Re: SQL1219N Error: Not letting me drop database

    ‏2009-04-02T20:31:40Z  
    Try adding your db2admin user to the Administrator's group, that got rid of the error for me.
  • Ragav86
    Ragav86
    1 Post

    Re: SQL1219N Error: Not letting me drop database

    ‏2010-11-21T14:25:32Z  
    i got the same error when i add the client database.

    i changed the SHARED_MEMORY option to AUTOMATIC in dbm cfg file. then its works fine.
  • BeethovenLira
    BeethovenLira
    1 Post

    Re: SQL1219N Error: Not letting me drop database

    ‏2011-03-04T14:05:16Z  
    • Ragav86
    • ‏2010-11-21T14:25:32Z
    i got the same error when i add the client database.

    i changed the SHARED_MEMORY option to AUTOMATIC in dbm cfg file. then its works fine.
    change the services DB2 to systemaccount. works fine
  • hemantsohoni
    hemantsohoni
    1 Post

    Re: SQL1219N Error: Not letting me drop database

    ‏2011-09-29T07:32:05Z  
    change the services DB2 to systemaccount. works fine
    Hi, I was also seing this error:

    the request failed because private virtual memory could not be allocated. sqlstate=57011

    setting the parameter: DB2_EXTSECURITY=YES

    cmd:
    db2set DB2_EXTSECURITY=YES

    Has resolved the problem.
  • SystemAdmin
    SystemAdmin
    5837 Posts

    Re: SQL1219N Error: Not letting me drop database

    ‏2012-02-17T18:29:16Z  
    Hi, I was also seing this error:

    the request failed because private virtual memory could not be allocated. sqlstate=57011

    setting the parameter: DB2_EXTSECURITY=YES

    cmd:
    db2set DB2_EXTSECURITY=YES

    Has resolved the problem.
    TSM 6.2.3 on Windows server
    Also got SQL1219N after a reboot, server would not start either as a service or in the foreground.

    Not exactly the same problem, turned out someone had removed the instance owner id from the administrators group. Error occurred even though the instance owner was still part of the DB2ADMNs group, and the TSM server service was running as system.

    Adding it back to the administrator group fixed the problem.

    Writing here just to confirm that this error likely indicates a permissions problem.
  • Darell1
    Darell1
    1 Post

    Re: SQL1219N Error: Not letting me drop database

    ‏2013-03-27T06:53:37Z  
    TSM 6.2.3 on Windows server
    Also got SQL1219N after a reboot, server would not start either as a service or in the foreground.

    Not exactly the same problem, turned out someone had removed the instance owner id from the administrators group. Error occurred even though the instance owner was still part of the DB2ADMNs group, and the TSM server service was running as system.

    Adding it back to the administrator group fixed the problem.

    Writing here just to confirm that this error likely indicates a permissions problem.
    for me, The DB2_EXTSECURITY was already set to YES

    And the db2admin was in the Administrator's group.

    But still had the issue.

    It got resolved when i manually stopped and started db2 services.