Status code 6 and 199 (DESPERATE HELP NEEDED!)
Guys, I've been battling for serveral months now a pesky problem related to SC 6 and 199 for two schedules of the same policy. Basically, every Saturday at around 5:30AM, one of my schedules fails invariably with SC 199, while the other completes successfully the first time, but fails about 12 min later with SC 6. I'm running 6.5.3.1 on my master, and the client is Solaris 9.
This is how it looks like (pm**** is the client, pb***** is the master):
root@pb*******:/ # bpdbjobs | grep hdb-rman | more
339027 Backup Done 199 hdb-rman archivelogs_app pm****** 02/25/12 05:42:32
339024 Backup Done 199 hdb-rman archivelogs_app pm***** 02/25/12 05:31:32
339023 Backup Done 0 hdb-rman archivelogs pm***** pb***** 6141 02/25/12 05:30:00 02/25/12 05:31:02
339021 Backup Done 6 hdb-rman archivelogs pm***** pb***** 6698 02/25/12 05:41:43 02/25/12 05:42:52
Notice the hours the two start schedules: 5:30AM for archivelogs and 5:31AM for archivelogs_app. I have already tried to implement the convoluted and unintelligible advice given for SC 199, to no avail. First I had tried to modify the schedule and it failed. Then I tried deleting the schedule altogether and recreate it manually, obviously that didn't do the trick either...
When I'm looking on the client (pm***) I notice this in the RMAN logs:
released channel: t1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on t1 channel at 02/25/2012 05:31:41
ORA-19506: failed to create sequential file, name="arch_15502_1_776151085", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
VxBSACreateObject: Failed with error:
Server Status: operation not allowed during this time period
Recovery Manager complete.
RMAN command failure
Resetting exit status to 6
Sat Feb 25 05:31:42 GMT 2012 ------------End of Script-------------
In the past, I've also separated the schedules about 3 hours apart, absolutely nothing happened, it continued to pop up those errors...I've attached the detailed description of the policy, in case that helps.
I would be very grateful if you could show me what to do next. Thanks.
- I am assuming that thus an application agent backup from the details - oracle So as well as your schedule it should have a default application schedule When your schedule kicks in it effectively tells the client to run a script that performs what is almost a user backup For that to run in needs the default application schedule in the policy and that schedule needs a window that is always open - so from midnight Sunday to midnight Sunday as a single window See http://www.Symantec.com/docs/tech27133 Hope this helps (6.5 has strange application schedules so just check it has a single Window