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.
Pinned topic SQL1219N Error: Not letting me drop database
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-03-27T06:53:37Z at 2013-03-27T06:53:37Z by Darell1
wifo 120000NXU32 Posts
Re: SQL1219N Error: Not letting me drop database2008-08-26T12:13:49ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
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.
Ragav86 270002BKMF1 Post
Re: SQL1219N Error: Not letting me drop database2010-11-21T14:25:32ZThis is the accepted answer. This is the accepted answer.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.
hemantsohoni 270000X05N1 Post
Re: SQL1219N Error: Not letting me drop database2011-09-29T07:32:05ZThis is the accepted answer. This is the accepted answer.
- BeethovenLira 270003GUKW
the request failed because private virtual memory could not be allocated. sqlstate=57011
setting the parameter: DB2_EXTSECURITY=YES
Has resolved the problem.
SystemAdmin 110000D4XK5837 Posts
Re: SQL1219N Error: Not letting me drop database2012-02-17T18:29:16ZThis is the accepted answer. This is the accepted answer.
- hemantsohoni 270000X05N
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 270000BY4U1 Post
Re: SQL1219N Error: Not letting me drop database2013-03-27T06:53:37ZThis is the accepted answer. This is the accepted answer.
- SystemAdmin 110000D4XK
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.