Hi Steve, DROPping a TABLE or a DBSPACE is a 2 stages process. The database manager would first drop the description of the DBSPACE ( that is why you see 8 NOT symbols in the DBSPACENAME field). Then an entry is entered into the SYSTEM.SYSDROP table. The 2nd stage of the DROP is actually removing all the objects. After all removing of objects are successful completed and is COMMIT, the entries from the SYSTEM.SYSDROP will be removed and the NOT symbols in the SYSTEM.SYSDBSPACES table will be removed too. Only then, that DBSPACE can be reACQUIREd.
Looks like you have some problem to complete the DROP process. We know of a work around to resolve this problem: ACQUIRE a DBSPACE, COMMIT, DROP it and COMMIT. This will force the database manager to go thru the SYSTEM.SYSDROP to complete those uncompleted DROPs.
Please give it a try.
By the way, "STARTUP mode P and SYSMODE S" is used to release "empty pages". It would not force the database manager to complete those uncompleted DROPs.
I hope this help.
Steve_Domarski/[EMAIL PROTECTED] wrote:
DBSPACENO TABID QUALF
--------- ------ -----
378 227 S
386 227 S
394 227 S
407 227 S
411 227 S
412 227 S
413 227 S
418 227 S
421 227 S
422 227 S
424 227 S
Steve Domarski 352-368-8350
"Roland P.
Chung" To: IBMVM@LISTSERV.UARK.EDU
<[EMAIL PROTECTED]
gers.com> Subject: Re: DB2 VM Deleted DBSPACES marked with NOT symbol
Sent by: The IBM
z/VM Operating
System
<[EMAIL PROTECTED]
UARK.EDU>
06/28/2006 12:58
PM
Please respond
to The IBM z/VM
Operating System
Hi Steve, please do a SELECT * FROM SYSTEM.SYSDROP and post the output.
Thanks.
Steve_Domarski/[EMAIL PROTECTED]
wrote:
I recently had a pool fill up leaving only 20 pages left. I decided to
move
some of the DBSpaces to another pool. All went well but the DBSpaces I
moved were not cleared in the "SELECT * FROM SYSTEM.SYSDBSPACES" list for
the pool I took them from. The DBSpaces dropped now have eight NOT symbols
as the owner name and 5 leading spaces and the DBSpaces number as a
DBSpace
name. They are no-longer accessible for use. I was able to resolve the
space problem by adding another extent to the pool but the DBSpaces are
still inaccessible.
I found the DBSPNUM startup parm in the Operations guide that indicated
that I needed to use STARTUP mode P and SYSMODE S. I did that for DBSPNUM
=
* as well as specific DBSpace numbers no relief.
Does anyone have any other ideas.
Steve Domarski 352-368-8350
Property Appraisers Office Marion County Florida USA
"Great minds discuss Ideas.
Average minds discuss events.
Small minds discuss people. " - Admiral Hyman Rickover
With best regards,
...Roland Chung
Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)
MAXC Consultants Inc.
Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268)
197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6
** Life is short. Stop once in a while and smell the roses. **
