Not sure But the response of Completed comes from the fact that the script
is completed. I get a completed status from my TDP's as long as the script
completes, even if no tablespaces were backed up.

Lawrie

-----Original Message-----
From: Kolbeinn Josepsson [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2003 01:21
To: [EMAIL PROTECTED]
Subject: Oracle scheduler fails if started in background


Hi everyone,

We have strange behavior on TDP Oracle backup (TSM scheduled), we installed
exactly same configuration on another Solaris box where the scheduled
backup (in backround) completed sucessfully, as far as I know the only
difference is Solaris version 8.

All comments are welcome.

TSM Server 5.1.5.2 on W2K platform
TSM BA Client 5.1.5.0 and TDPO 5.1.5 on Solaris 2.6

 If we start the scheduler in foreground, the backup completes whithout
error. We use this command:
/opt/tivoli/tsm/client/ba/bin/dsmc sched -se=tsm1_sched

If we start the scheduler in background, the backup fails, but Q EVENTS
says Completed, RMAN dos not start (no records in the RMAN Log). We use the
"at" command to start the scheduler in background:

at now
/opt/tivoli/tsm/client/ba/bin/dsmc sched -se=tsm1_sched
"ctrl-D"

Following are records from actlog, schedlog and  q events, when backup
fails (shedule started in background). Also the dsm.sys file.

actlog:

                          08-01-2003 04:20:00 for node E450_ORA completed
                          successfully at 08-01-2003 04:58:51.
08-01-2003 04:58:51      ANR0403I Session 1401 ended for node E450_ORA (SUN

dsmsched.log:

Executing scheduled command now.
01/08/03   04:58:39 Node Name: E450_ORA
01/08/03   04:58:39 Session established with server TSM1: Windows
01/08/03   04:58:39   Server Version 5, Release 1, Level 5.2
01/08/03   04:58:39   Server date/time: 01/08/03   04:58:51  Last access:
01/08/03   03:27:51

01/08/03   04:58:39
Executing Operating System command or script:
   /u01/app/oracle/local/bin/hotrman.sh
01/08/03   04:58:39 Finished command.  Return code is: 1
01/08/03   04:58:39 ANS1909E The scheduled command failed.
01/08/03   04:58:39 ANS1512E Scheduled event 'DAYLY_ORA' failed.  Return
code = 1.
01/08/03   04:58:39 Sending results for scheduled event 'DAYLY_ORA'.
01/08/03   04:58:39 Results sent to server for scheduled event 'DAYLY_ORA'.

q event:

08-01-2003 04:20:00      08-01-2003 04:58:51      DAYLY_ORA
E450_ORA          Completed

dsm.sys:

SERVERNAME  tsm1_ba
   nodename           e450
   commmethod         TCPIP
   tcpport            1500
   tcpserveraddress   tsm1.zzz.is
   tcpbuffsize        32
   tcpnodelay         yes
   tcpwindowsize      1023
   largecommbuffers   yes
   schedlogname       /var/log/tivoli/ba/dsmsched.log
   schedlogretention  10,d
   errorlogname       /var/log/tivoli/ba/dsmerror.log
   errorlogretention  10,d
   passwordaccess     generate

SERVERNAME  tsm1_ora
   nodename           e450_ora
   commmethod         TCPIP
   tcpport            1500
   tcpserveraddress   tsm1.zzz.is
   tcpbuffsize        32
   tcpnodelay         yes
   tcpwindowsize      1023
   largecommbuffers   yes
   schedlogname       /var/log/tivoli/ora/dsmsched.log
   schedlogretention  10,d
   errorlogname       /var/log/tivoli/ora/dsmerror.log
   errorlogretention  10,d
   passwordaccess     prompt

SERVERNAME  tsm1_sched
   nodename           e450_ora
   commmethod         TCPIP
   tcpport            1500
   tcpserveraddress   tsm1.zzz.is
   tcpbuffsize        32
   tcpnodelay         yes
   tcpwindowsize      1023
   largecommbuffers   yes
   schedlogname       /var/log/tivoli/ora/dsmsched.log
   schedlogretention  10,d
   errorlogname       /var/log/tivoli/ora/dsmerror.log
   errorlogretention  10,d
   passwordaccess     generate

Best regards,
Kolbeinn Josepsson 7 Systems Engineer
www.nyherji.is

Reply via email to