|
|
sybperl-l Archive
Up Prev Next
From: Steve Cable <cable dot steve at tci dot com>
Subject: Re: SQL/BackTrack Job Hung
Date: Nov 12 1997 11:42PM
Katherine Kratter wrote:
> Every night I backup 20 databases using SQL/BackTrack. SQL/BT is called
> from a wrapper program written in perl. The name of the wrapper is
> dtsbackup. The wrapper has been running for several weeks and this is
> the first time this problem has occurred. The backup is initiated from
> cron in AIX 3.2.5.1.
>
> I'm running SQL-BackTrack Sybase Backup Utility (DTSBACKUP) Version
> 3.0.1, serial number BT-00126892-4474, and the version of the SQL Server
> is SQL Server/10.0.2.4/P/RS6000/AIX3.2/EBF 5591 Rollup/OPT/Fri Dec 8
> 23:57:23 PST 1995.
>
> The problem is that a backup started at 22:40 last night and has not
> completed. The backup of this database usually takes about 25 minutes.
> The backup is written to disk and there is no backup file on disk. I've
> collected info below which may be helpful. I can be reached by phone at
> (212) 854-1362 or email. Thank you for looking into this.
>
> Kathy Kratter
>
> sybase id Crontab Entry:
>
> 40 22 * * 1-6 /usr/local/dba/bin/dtsbackup sis >/dev/null 2>&1
>
> Command Issued by Wrapper (from wrapper log):
>
> 11/11/97 22:40:17 : dtsbackup command:
> /usr/local/datatools/sbacktrack/bin/dtsbackup
> /usr/local/datatools/sbackups.physical/SYBASE@CUAIX06/sis -verbose
> -noprompt -tasks 3 -options ' -contents -no_logical_header '
>
> From dtwatch:
>
> Active:
> Tue 22:40 dtsbackup 21673: Backing up 1 control file.
> Tue 22:40 dtsdump 16555: SYBASE@CUAIX06 sis: 1.60M B/s: 49.5% 604,000 Of 1,220,779 blocks unloaded.
> Tue 22:40 obsi/disk 23980: Written 392.75M bytes to /usr/lcl/sybase/backup/sis/sis-0.11-11-1997.22:40-23980
> Tue 22:40 dtdumpcmd 22701: DUMP DATABASE command active.
> Tue 22:40 dtstripe2 19378: SYBASE@CUAIX06 sis: 640K B/s: 46.8% 571,360 Of 1,220,779 blocks unloaded.
> Tue 22:40 obsi/disk 20659: Written 370.25M bytes to /usr/lcl/sybase/backup/sis/stripe0/sis-0.11-11-1997.22:40-20659
>
> From ps -ef command:
>
> sybase 22158 11405 0 22:40:00 - 0:02 perl -wT /dev/fd/3//usr/local/dba/bin/dtsbackup sis
> sybase 23720 22158 0 22:40:17 - 0:00 sh sh sh
> sybase 21673 23720 0 22:40:17 - 0:33 /usr/local/datatools/sbacktrack/bin/dtsbackup /usr/local/datatools/sbackups.phys
> sybase 16555 21673 0 22:40:18 - 9:57 dtsdump -physical -server SYBASE@CUAIX06 -database sis -contents -no_logical_hea
> sybase 22701 16555 0 22:40:34 - 0:04 dtsdump -physical -server SYBASE@CUAIX06 -database sis -contents -no_logical_hea
> sybase 19378 16555 0 22:40:38 - 9:17 dtsdump -physical -server SYBASE@CUAIX06 -database sis -contents -no_logical_hea
> sybase 23980 21673 0 22:40:25 - 0:20 disk
> sybase 20659 21673 0 22:40:39 - 0:18 disk
>
> From SQL Server sp_who command:
>
> 1> sp_who
> 2> go
> spid status loginame hostname blk
> dbname cmd
> ------ ------------ ------------------------------ ---------- -----
> ------------------------------ ----------------
> 1 recv sleep sa 0
> master AWAITING COMMAND
> 6 sleeping NULL cuaix06 0
> sis DUMP DATABASE
>
> From SQL Server sysprocesses table:
>
> 1> select * from sysprocesses where spid = 1
> 2> go
> spid kpid enginenum status suid hostname program_name
> 1 49152017 0 recv sleep 1 dtsbackup
> hostprocess cmd cpu physical_io memusage
> 22158 AWAITING COMMAND 2 2 1
> blocked dbid uid gid
> 0 1 1 0
> tran_name
> NULL
> time_blocked network_pktsz
> NULL 512
> (1 row affected)
> 1> select * from sysprocesses where spid = 6
> 2> go
> spid kpid enginenum status suid hostname program_name
> 6 49414180 0 sleeping 0 cuaix06 SQL-BackTrack
> hostprocess cmd cpu physical_io memusage
> 22701 DUMP DATABASE 0 299 14
> blocked dbid uid gid
> 0 7 1 0
> tran_name
> NULL
> time_blocked network_pktsz
> NULL 512
> (1 row affected)
Kathy,
Did you try bouncing the SQLBacktrack open server?
Is the output device full and waiting for more space?
Steve
|
