hi, thanks a lot ... you are right, but the problem is i changed the duration to 2 days (48 hours) and i still got the sam message ... the preschedulecmd works fine but in the mean time this error pops out from nowhere ...
# cat dsmerror_sdb.log 07/05/06 10:50:04 ANS1092W No files matching search criteria were found 07/05/06 10:50:14 ANS1092W No files matching search criteria were found 07/06/06 10:10:24 ANS1092W No files matching search criteria were found 07/06/06 12:04:15 ANS1814E Unable to start the scheduled event 'SDB_EXP_SCHED01' 07/06/06 12:04:15 ANS1815E Either the window has elapsed or the schedule has been deleted 07/09/06 05:37:49 ANS1814E Unable to start the scheduled event 'SDB_EXP_SCHED01' 07/09/06 05:37:49 ANS1815E Either the window has elapsed or the schedule has been deleted why is he trying to start scheduled event which has already been started ? can it be something with communication ? if the preschedulecmd lasts for 35 hours i presume the duration of 48 hours is okay ? or ... i'm really confused here dsmsched.log 7/07/06 18:01:24 Scheduler has been started by Dsmcad. 07/07/06 18:01:24 Querying server for next scheduled event. 07/07/06 18:01:24 Node Name: SDB 07/07/06 18:01:24 Session established with server TSM01: AIX-RS/6000 07/07/06 18:01:24 Server Version 5, Release 3, Level 3.1 07/07/06 18:01:24 Server date/time: 07/07/06 18:05:25 Last access: 07/07/06 15:33:44 07/07/06 18:01:24 --- SCHEDULEREC QUERY BEGIN 07/07/06 18:01:24 --- SCHEDULEREC QUERY END 07/07/06 18:01:24 Next operation scheduled: 07/07/06 18:01:24 ------------------------------------------------------------ 07/07/06 18:01:24 Schedule Name: SDB_EXP_SCHED01 07/07/06 18:01:24 Action: Incremental 07/07/06 18:01:24 Objects: /db/sdb11/backup01/backup/ 07/07/06 18:01:24 Options: -su=yes -preschedulecmd="su - oracle -c /db/sdb11/backup01/backup/sdb1_do_bkup.sh" 07/07/06 18:01:24 Server Window Start: 17:43:00 on 07/07/06 07/07/06 18:01:24 ------------------------------------------------------------ 07/07/06 18:01:24 Executing scheduled command now. 07/07/06 18:01:24 Executing Operating System command or script: su - oracle -c /db/sdb11/backup01/backup/sdb1_do_bkup.sh 07/09/06 05:37:48 Finished command. Return code is: 0 07/09/06 05:37:49 Session established with server TSM01: AIX-RS/6000 07/09/06 05:37:49 Server Version 5, Release 3, Level 3.1 07/09/06 05:37:49 Server date/time: 07/09/06 05:41:49 Last access: 07/09/06 05:04:05 07/09/06 05:37:49 ANS1814E Unable to start the scheduled event 'SDB_EXP_SCHED01' 07/09/06 05:37:49 ANS1815E Either the window has elapsed or the schedule has been deleted 07/09/06 05:37:49 Querying server for next scheduled event. 07/09/06 05:37:49 Node Name: SDB 07/09/06 05:37:49 Session established with server TSM01: AIX-RS/6000 07/09/06 05:37:49 Server Version 5, Release 3, Level 3.1 07/09/06 05:37:49 Server date/time: 07/09/06 05:41:50 Last access: 07/09/06 05:41:49 07/09/06 05:37:49 --- SCHEDULEREC QUERY BEGIN 07/09/06 05:37:49 --- SCHEDULEREC QUERY END 07/09/06 05:37:49 Next operation scheduled: 07/09/06 05:37:49 ------------------------------------------------------------ 07/09/06 05:37:49 Schedule Name: SDB_EXP_SCHED01 07/09/06 05:37:49 Action: Incremental 07/09/06 05:37:49 Objects: /db/sdb11/backup01/backup/ 07/09/06 05:37:49 Options: -su=yes -preschedulecmd="su - oracle -c /db/sdb11/backup01/backup/sdb1_do_bkup.sh" 07/09/06 05:37:49 Server Window Start: 17:43:00 on 07/11/06 07/09/06 05:37:49 ------------------------------------------------------------ 07/09/06 05:37:49 Scheduler has been stopped. 07/09/06 13:37:51 Scheduler has been started by Dsmcad. 07/09/06 13:37:51 Querying server for next scheduled event. ----- Original Message ----- From: "Bos, Karel" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, July 12, 2006 10:51 AM Subject: Re: schedule problem ? Hi, Queryschedperiod will not make the "07/09/06 05:37:49 ANS1815E Either the window has elapsed or the schedule has been deleted" go away. As the message says, look at the duration of your backup schedule, and update them as needed: DURation Specifies the number of units that define the length of the startup window of the scheduled operation. This parameter is optional. This value must be from 1 to 999. The default is 1. Use this parameter with the DURUNITS parameter to specify the length of the startup window. For example, if you specify DURATION=20 and DURUNITS=MINUTES, the schedule must be started within 20 minutes of the start date and start time. The default length of the startup window is 1 hour. The duration of the window must be shorter than the period between windows. This value is ignored if you specify DURUNITS=INDEFINITE. DURUnits Specifies the time units used to determine the duration of the window in which the schedule can start. This parameter is optional. The default is HOURS. Use this parameter with the DURATION parameter to specify how long the startup window remains open to process the schedule. For example, if DURATION=20 and DURUNITS=MINUTES, the schedule must be started within 20 minutes of the start date and start time. The schedule may not necessarily complete processing within this window. If the schedule needs to be retried for any reason, the retry attempts must begin before the startup window elapses, or the operation does not restart. The default value for the length of the startup window is 1 hour. Possible values are: Minutes Specifies that the duration of the window is defined in minutes. Hours Specifies that the duration of the window is defined in hours. Days Specifies that the duration of the window is defined in days. INDefinite Specifies that the startup window of the scheduled operation has an indefinite duration. The schedule can run any time after the scheduled start time, until the schedule expires. You cannot specify DURUNITS=INDEFINITE, unless you specify PERUNITS=ONETIME. The INDEFINITE value is not allowed with enhanced schedules. Regards, Karel -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of goc Sent: woensdag 12 juli 2006 10:45 To: [email protected] Subject: Re: schedule problem ? hmm, i think i know the solution i changed QUERYSCHED to 48 any ideas please ? ----- Original Message ----- From: "goc" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Monday, July 10, 2006 9:53 AM Subject: schedule problem ?
hi all, i have an schedule problem whitch includes a very long preschedulecmd command, (35 hours) Executing scheduled command now. 07/07/06 18:01:24 Executing Operating System command or script: su - oracle -c /db/sdb11/backup01/backup/sdb1_do_bkup.sh 07/09/06 05:37:48 Finished command. Return code is: 0 07/09/06 05:37:49 Session established with server TSM01: AIX-RS/6000 07/09/06 05:37:49 Server Version 5, Release 3, Level 3.1 07/09/06 05:37:49 Server date/time: 07/09/06 05:41:49 Last
access:
07/09/06 05:04:05 07/09/06 05:37:49 ANS1814E Unable to start the scheduled event 'SDB_EXP_SCHED01' 07/09/06 05:37:49 ANS1815E Either the window has elapsed or the
schedule
has been deleted 07/09/06 05:37:49 Querying server for next scheduled event. 07/09/06 05:37:49 Node Name: SDB 07/09/06 05:37:49 Session established with server TSM01: AIX-RS/6000 07/09/06 05:37:49 Server Version 5, Release 3, Level 3.1 07/09/06 05:37:49 Server date/time: 07/09/06 05:41:50 Last
access:
07/09/06 05:41:49 07/09/06 05:37:49 --- SCHEDULEREC QUERY BEGIN 07/09/06 05:37:49 --- SCHEDULEREC QUERY END 07/09/06 05:37:49 Next operation scheduled: 07/09/06 05:37:49 ------------------------------------------------------------ 07/09/06 05:37:49 Schedule Name: SDB_EXP_SCHED01 07/09/06 05:37:49 Action: Incremental 07/09/06 05:37:49 Objects: /db/sdb11/backup01/backup/ 07/09/06 05:37:49 Options: -su=yes -preschedulecmd="su
-
oracle -c /db/sdb11/backup01/backup/sdb1_do_bkup.sh" 07/09/06 05:37:49 Server Window Start: 17:43:00 on 07/11/06 07/09/06 05:37:49 ------------------------------------------------------------ 07/09/06 05:37:49 Scheduler has been stopped. the script does an export of an big db every tuesday, friday at 17:43 , the time limit which the scheduled operation must start is 2 days can anyone help me please ? server AIX 5.2-06 tsm 5.3.3.1 client HPUX 11.11 with tsmc 5.3.0.0 TIA PS: i have the similar one which lasts for more than 20 hours ... and it works fine 07/06/06 00:21:29 --- SCHEDULEREC QUERY BEGIN 07/06/06 00:21:29 --- SCHEDULEREC QUERY END 07/06/06 00:21:29 Next operation scheduled: 07/06/06 00:21:29 ------------------------------------------------------------ 07/06/06 00:21:29 Schedule Name: BSCS_OLB_SCHED01 07/06/06 00:21:29 Action: Incremental 07/06/06 00:21:29 Objects: /db/bscs81/olb/bscs8/ 07/06/06 00:21:29 Options: -preschedulecmd="su -
oracle -c
/db/bscs81/olb/bscs8/doob" -su=yes 07/06/06 00:21:29 Server Window Start: 00:25:00 on 07/06/06 07/06/06 00:21:29 ------------------------------------------------------------ 07/06/06 00:21:29 Executing scheduled command now. 07/06/06 00:21:29 Executing Operating System command or script: su - oracle -c /db/bscs81/olb/bscs8/doob 07/06/06 20:56:55 Finished command. Return code is: 0 07/06/06 20:56:56 Session established with server TSM01: AIX-RS/6000 07/06/06 20:56:56 Server Version 5, Release 3, Level 3.1 07/06/06 20:56:56 Server date/time: 07/06/06 21:00:56 Last
access:
07/06/06 00:25:30 07/06/06 20:56:56 --- SCHEDULEREC OBJECT BEGIN BSCS_OLB_SCHED01
07/06/06
00:25:00 07/06/06 20:56:56 Incremental backup of volume
'/db/bscs81/olb/bscs8/'
