Home   |   Register   |   Rules   |   Calendar   |   Get Daily   |     |  
 


If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > Database Server Software > DB2 > Better way to DROP Database ??

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-18-10, 10:59
sarbjitsinghgill sarbjitsinghgill is offline
Registered User
  
Join Date: Dec 2007
Posts: 4
Better way to DROP Database ??
Friends,

[ DB2 v9.5.5 on Win2K3 ]

While restoring backups to Mirrors, I have been dropping the target DB before restoring new copy overnight. Our Mirror servers host 2 DBs in one instance. So I need to force applications selectively to keep other DB intact while restorin the one.

I use following logic to Drop DB

Code:
CONNECT TO GAMING


   Database Connection Information



 Database server        = DB2/NT64 9.5.4

 SQL authorization ID   = RESTORE

 Local database alias   = GAMING




Sat 12/18/2010- 2:15:29.66-0
QUIESCE DB IMMEDIATE FORCE CONNECTIONS

DB20000I  The QUIESCE DATABASE command completed successfully.



Sat 12/18/2010- 2:15:30.00-0
UNQUIESCE DB

DB20000I  The UNQUIESCE DATABASE command completed successfully.



Sat 12/18/2010- 2:15:30.23-0
CONNECT RESET

DB20000I  The SQL command completed successfully.



Sat 12/18/2010- 2:15:30.47-0
DEACTIVATE DB GAMING
DB20000I  The DEACTIVATE DATABASE command completed successfully.



Sat 12/18/2010- 2:15:39.33-0
DROP DB GAMING
SQL1137W  The database manager was unable to remove the database path or some 

of the containers when dropping database "GAMING".  Cleanup is required.



Sat 12/18/2010- 2:15:41.50-4
===================================
Sat 12/18/2010- 2:15:41.50-4---Drop DB Fail
Sat 12/18/2010- 2:16:00.51-0---ReTry Drop DB
===================================
CONNECT TO GAMING
SQL1031N  The database directory cannot be found on the indicated file system. 

SQLSTATE=58031
But recently the I have come across the issue above. Seems that some application is holding some files related to GAMING at system level.

Can some one suggest me a better way to DROP DB before RESTOREing.

Or Can I do REPLACE EXISTING without dropping GAMING ??

Regards

Sarbjit Singh Gill
Last edited by sarbjitsinghgill; 12-18-10 at 15:27.
Reply With Quote
  #2 (permalink)  
Old 12-18-10, 14:31
JAYANTA_DATTA JAYANTA_DATTA is offline
Registered User
  
Join Date: Oct 2004
Location: DELHI INDIA
Posts: 336
you should practically use " REPLACE EXISTING" only while restoring. Thats simple and straight and DB2 provides this feature.
__________________

Jayanta Datta
DB2 UDB DBA
IBM India, Global Delivery
New Delhi
Reply With Quote
  #3 (permalink)  
Old 12-18-10, 15:22
sarbjitsinghgill sarbjitsinghgill is offline
Registered User
  
Join Date: Dec 2007
Posts: 4
Well, I will try that.


Logically, what does DB2 do with connected applications while restoring without dropping.
Further if DB2 fails to DROPping DB; doesn't this imply that DB2 will fail while REPLACEing.

I will try tonight skipping the DROP DB command in the script and let you know.

Thanks

Sarbjit Singh Gill
Last edited by sarbjitsinghgill; 12-18-10 at 15:27.
Reply With Quote
  #4 (permalink)  
Old 12-18-10, 21:29
db2girl db2girl is offline
∞∞∞∞∞∞
  
Join Date: Aug 2008
Location: Toronto, Canada
Posts: 1,816
Why don't you do something similar to the following:

deactivate db ...
connect to ...
quiesce db immediate force connections
connect reset
<you can add equivalent of "sleep <seconds>" on windows to give force enough time to terminate existing connections>
restore db ... without prompting
connect to ...
unquiesce db
connect reset
Reply With Quote
  #5 (permalink)  
Old 12-18-10, 22:27
sarbjitsinghgill sarbjitsinghgill is offline
Registered User
  
Join Date: Dec 2007
Posts: 4
Alright, and thanks.

I will do this. I may have to double check if any one can connect to quiesced database.

Regards
Reply With Quote
  #6 (permalink)  
Old 12-19-10, 05:57
sarbjitsinghgill sarbjitsinghgill is offline
Registered User
  
Join Date: Dec 2007
Posts: 4
Can someon suggest me how to suppress this warning ??

Code:
RESTORE DATABASE GAMING INCREMENTAL AUTOMATIC FROM 'H:\daily_backup\Image' TAKEN AT 20101218013005 TO D: LOGTARGET H:\daily_backup\logs WITH 20 BUFFERS BUFFER 512 replace existing WITHOUT PROMPTING 
SQL2540W  Restore is successful, however a warning "2539" was encountered during Database Restore while processing in No Interrupt mode.
This warning causes return code of value 1 which causes my script to send a warning e-mail to myself and my manager.

Warning "2539" is
Quote:
SQL2539W Warning! Restoring to an existing database that is the same as
the backup image database. The database files will be deleted.

Explanation:

The database aliases, names and seeds of the target database and
database image are the same, indicating these are the same databases.
The current database will be overwritten by the backup version.

User response:

Return to the utility with the callerac parameter indicating processing
to continue or end.
I just want to avoid this warning. REPLACE EXISTING and WITHOUT PROMPTING are already there to indicate that I want to replace an existing database.

Any idea or work around ??

thanks
Reply With Quote
Reply

« Previous Thread | Next Thread »
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes
Linear Mode Linear Mode

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


 
 
 
Home  |   Register  |   Get New  |   FAQ's  |   Sitemap

Powered by vBulletin
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.