- 1. SQL-Backtrack filespace deletion. (score: 1)
- Author: Sean McNamara <mcnams AT PJM DOT COM>
- Date: Wed, 22 Dec 1999 15:33:11 -0500
- Hello All, Over the past few days we have been seeing the following error message during our nightly Oracle database backup using SQL-Backtrack: 02:31 backup of archived logs completed 02:32 backup o
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg00929.html (12,223 bytes)
- 2. Re: SQL-Backtrack filespace deletion. (score: 1)
- Author: Shawn Raymond <sraymond AT SNRGY DOT COM>
- Date: Thu, 23 Dec 1999 08:23:21 -0500
- Sean, I have seen this with SQL-Backtrack for sybase. In our case ADSM was expiring the entry in the ADSM database before SQL Backtrack, so when SQL backtrack tried to expire, it wasn't there. -- Sha
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg00963.html (12,877 bytes)
- 3. Re: SQL-Backtrack filespace deletion. (score: 1)
- Author: "France, Don (Pace)" <don.france-eds AT EDS DOT COM>
- Date: Mon, 27 Dec 1999 13:53:05 -0600
- So... the question now becomes "when you query as ROOT, are the objects marked 'inactive' ?!? If so, then it's the Sybase-Backtrack problem cited -- what's the cure?" It doesn't make sense that ROOT
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg01055.html (14,901 bytes)
- 4. Re: SQL-Backtrack filespace deletion. (score: 1)
- Author: Sean McNamara <mcnams AT PJM DOT COM>
- Date: Mon, 27 Dec 1999 15:03:23 -0500
- When I query as ROOT there are 'active' and 'inactive' versions on the server. This leads me to believe that my management class is set up improperly for the server ( i.e. all ORACLE filespaces shoul
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-12/msg01056.html (16,249 bytes)
This search system is powered by
Namazu