db2uext2 --> ADSM, reinvoked after ADSM failure? 
Author Message
 db2uext2 --> ADSM, reinvoked after ADSM failure?

Quote:

>> The DB2UEXT2 exit routine has the following comment in it.
>> /* ----------------------------------------------------------------- */
>> /* User Exit Supported Return Codes                                  */
>> /*    NOTE: DB2 will reinvoke the user exit for the same request     */
>> /*          after 5 minutes if return code is 4 or 8.  For other     */
>> /*          non-zero return codes, DB2 will not invoke user exit     */
>> /*          for the database until the database is shut down.        */
>> /* ----------------------------------------------------------------- */
>> Ok, so the ADSM server goes down.  That will yield a return code greater than
>> 8 and the exit routine will not be called again until DB2 is stopped.  This
>> is an unacceptable situation for our shop.  We have several DB2 servers using
>> one ADSM server.  We are constantly having tape drive problems, (the IBM 3575
>> ain't thru cookin'), that forces us to take ADSM down. I can't reboot these
>> servers everytime ADSM goes down.
>> So, if I hard code a return code of 4 when the return code is greater than 8,
>> will the exit routine be called over and over for a specific log file until
>> ADSM comes back up and yields a zero return code?  Or will the exit routine
>> only try one extra time per log file.  I can't tell from the comment in the
>> exit routine what it will do.

Good question.  DB2 will call userexit for the same file over and over
until the return code is either 0 or greater than 8.  Also, DB2 will
call userexit program to archive a new log file if it is ready for
archive.  The limitation is that there is a limit on the number of
files DB2 will remember.  I think the limit is somewhere arround 60.
That is, if your ADSM goes down for a long time, eough for DB2 to
produce about 60 log files, then DB2 will give up (treat as if return
code is > 8).

--
Roger Zheng
DB2 Development   Phone 416-448-2632  Tie Line 778-2632          



Sun, 24 Jun 2001 03:00:00 GMT
 db2uext2 --> ADSM, reinvoked after ADSM failure?

Is there probably a workaround for that.

We are working with SAP R/3 DB2 UDB5.2 and ADSM and have the
probelm that sometimes userexit db2uext2 didn't work.
We cannot stop our DB2 Database, it is 7*24. And i don't
have time to start db2uext2 manually one file after the other.

So my question once more, are you or the lab work on it.

On time we have 9 DB2 UDB5 V5.2 Server for SAP. Three DB2 for
inhouse application and until end of January a DB2 EEE working with
ADSM.

Quote:


> >> The DB2UEXT2 exit routine has the following comment in it.
> >> /* ----------------------------------------------------------------- */
> >> /* User Exit Supported Return Codes                                  */
> >> /*    NOTE: DB2 will reinvoke the user exit for the same request     */
> >> /*          after 5 minutes if return code is 4 or 8.  For other     */
> >> /*          non-zero return codes, DB2 will not invoke user exit     */
> >> /*          for the database until the database is shut down.        */
> >> /* ----------------------------------------------------------------- */

> >> Ok, so the ADSM server goes down.  That will yield a return code greater than
> >> 8 and the exit routine will not be called again until DB2 is stopped.  This
> >> is an unacceptable situation for our shop.  We have several DB2 servers using
> >> one ADSM server.  We are constantly having tape drive problems, (the IBM 3575
> >> ain't thru cookin'), that forces us to take ADSM down.       I can't reboot these
> >> servers everytime ADSM goes down.

> >> So, if I hard code a return code of 4 when the return code is greater than 8,
> >> will the exit routine be called over and over for a specific log file until
> >> ADSM comes back up and yields a zero return code?  Or will the exit routine
> >> only try one extra time per log file.  I can't tell from the comment in the
> >> exit routine what it will do.

> Good question.  DB2 will call userexit for the same file over and over
> until the return code is either 0 or greater than 8.  Also, DB2 will
> call userexit program to archive a new log file if it is ready for
> archive.  The limitation is that there is a limit on the number of
> files DB2 will remember.  I think the limit is somewhere arround 60.
> That is, if your ADSM goes down for a long time, eough for DB2 to
> produce about 60 log files, then DB2 will give up (treat as if return
> code is > 8).

> --
> Roger Zheng
> DB2 Development   Phone 416-448-2632  Tie Line 778-2632


--
Joachim Mller    | Tel.  : +49-2331-690-249
DIS               | Fax   : +49-2331-690-636

D-58099 Hagen     | www   : http://www.douglas-holding.de
                  | www   : http://www.douglas.de
Germany


Mon, 25 Jun 2001 03:00:00 GMT
 db2uext2 --> ADSM, reinvoked after ADSM failure?

Quote:
>>>>> ">" == j mueller <Joachim> writes:
>> Is there probably a workaround for that.
>> We are working with SAP R/3 DB2 UDB5.2 and ADSM and have the
>> probelm that sometimes userexit db2uext2 didn't work.
>> We cannot stop our DB2 Database, it is 7*24. And i don't
>> have time to start db2uext2 manually one file after the other.
>> So my question once more, are you or the lab work on it.

I am working on having a retry logic 1 hour after userexit failed.
You will still have to manually archive log files produced during this
time, but at least you don't have to do it after ADSM comes back.
--
Roger Zheng
DB2 Development   Phone 416-448-2632  Tie Line 778-2632          



Mon, 25 Jun 2001 03:00:00 GMT
 
 [ 5 post ] 

 Relevant Pages 

1. Problem Using ADSM to Back Up Databases

2. Integrating ADSM

3. Oracle Backup by Using ADSM

4. Oracle data files on ADSM-managed filesystems

5. EBU and ADSM

6. Backing up HP-Unix Oracle database to Mainframe via ADSM

7. RMAN & ADSM

8. Backup Oracle Databases by ADSM

9. Oracle Backup and ADSM Tools needed!

10. Using ADSM to backup Sybase DB

11. Database backup to ADSM (or other data/media management software)

12. Backup to ADSM


 
Powered by phpBB® Forum Software