Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
Backing Up Oracle - Computing at Cornell
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>Up</strong>on successful install<strong>at</strong>ion of the scheduler service, the scheduler service<br />
will autom<strong>at</strong>ically start and connect to the TSM server to retrieve any<br />
associ<strong>at</strong>ed schedules. The dsmsched.log for the scheduler service will show<br />
whether a schedule was retrieved from the TSM server. Our dsmsched.log<br />
shows th<strong>at</strong> the c:\oracle\admin\scripts\autorman backup_offline_beach will be<br />
executed in 2 minutes.<br />
04/05/2001 23:06:09 Querying server for next scheduled event.<br />
04/05/2001 23:06:09 Node Name: JAMAICA_ORACLE<br />
04/05/2001 23:06:09 Session established with server BRAZIL: AIX-RS/6000<br />
04/05/2001 23:06:09 Server Version 4, Release 1, Level 2.0<br />
04/05/2001 23:06:09 Server d<strong>at</strong>e/time: 04/05/2001 21:07:36 Last access: 04/05/<br />
2001 21:05:30<br />
04/05/2001 23:06:09 --- SCHEDULEREC QUERY BEGIN<br />
04/05/2001 23:06:09 --- SCHEDULEREC QUERY END<br />
04/05/2001 23:06:09 Next oper<strong>at</strong>ion scheduled:<br />
04/05/2001 23:06:09 ------------------------------------------------------------<br />
04/05/2001 23:06:09 Schedule Name: BACKUP_OFFLINE<br />
04/05/2001 23:06:09 Action: Command<br />
04/05/2001 23:06:09 Objects: c:\oracle\admin\scripts\autorman back<br />
up_offline_beach<br />
04/05/2001 23:06:09 Options:<br />
04/05/2001 23:06:09 Server Window Start: 21:06:13 on 04/05/2001<br />
04/05/2001 23:06:09 ------------------------------------------------------------<br />
04/05/2001 23:06:09 Command will be executed in 2 minutes.<br />
We checked the dsmsched.log and it said th<strong>at</strong> the command failed. We<br />
checked the backup_offline_beach.log file and it gave us this message:<br />
RMAN-00554: initializ<strong>at</strong>ion of internal recovery manager package failed<br />
RMAN-04005: error from target d<strong>at</strong>abase: ORA-01017:<br />
invalid username/password; logon denied<br />
Th<strong>at</strong> message would lead you to believe th<strong>at</strong> the password in the<br />
AUTORMAN.CMD file was incorrect. However, we had previously run it<br />
manually and it was successful. The most common cause of a scheduled<br />
action failing when the manual action works in Windows is th<strong>at</strong> the scheduler<br />
service is running as an account th<strong>at</strong> does not have sufficient rights. We<br />
stopped the scheduler service:<br />
net stop “TSM Scheduler <strong>Oracle</strong>”<br />
Then, using Administr<strong>at</strong>ive Tools -> Services, we changed the logon type for<br />
the scheduler service from system account to the Administr<strong>at</strong>or account. You<br />
should be able to use any account th<strong>at</strong> is successful in running the command<br />
manually.<br />
Chapter 11. Day-to-day monitoring on Windows 2000 175
Change language