cancel
Showing results for 
Search instead for 
Did you mean: 

Strange Issue in Oracle scheduling.

Possible
Level 6
Accredited Certified

Yearly schedule is executing on monthly basis.

Yearly schedule is exepected to run at start of the year and policy is specified in script as 

varaible defined 1st....

NB_ORA_POLICY=policyname

main clause is (vaule of variable assgined in main clause.)

RUN {
ALLOCATE CHANNEL ch00 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch01 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch02 TYPE 'SBT_TAPE';
ALLOCATE CHANNEL ch03 TYPE 'SBT_TAPE';
   send 'NB_ORA_POLICY=${NB_ORA_POLICY}';

Yearly and monthly policies are different.

I have taken a llok at http://www.symantec.com/business/support/index?page=content&id=TECH31742 but dont find it related to me.

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you checked Oracle output file/log as well as dbclient log to see if variable is interpreted correctly? 
We need to see what is sent to NBU.

Which shell is used for the script?
Possibility that $NB_ORA_POLICY and ${NB_ORA_POLICY} is different depending on the shell being used.

If you have different scripts for monthly and yearly, why not simply hardcode the policy name in the 'send' statement?

View solution in original post

6 REPLIES 6

RamNagalla
Moderator
Moderator
Partner    VIP    Certified

does it scheduled from Netbackup or any third party scheduler?

show us the output of below command for both policies..

bppllist <policyname> -L

Possible
Level 6
Accredited Certified

Its calender based scheduling from nbu...checkd no crontab or anything...

It triggers on monthly basis with yearly policy name.

policy info.

 


Policy Name:       <Policy Name>
Options:           0x0
template:          FALSE
audit_reason:         ?
Names:             (none)
Policy Type:       Oracle (4)
Active:            yes
Effective date:    01/10/2009 12:03:22
Block Incremental: no
Mult. Data Stream: no
Perform Snapshot Backup:   no
Snapshot Method:           (none)
Snapshot Method Arguments: (none)
Perform Offhost Backup:    no
Backup Copy:               0
Use Data Mover:            no
Data Mover Type:           -1
Use Alternate Client:      no
Alternate Client Name:     (none)
Use Virtual Machine:      0
Hyper-V Server Name:     (none)
Enable Instant Recovery:   no
Policy Priority:   75019
Max Jobs/Policy:   Unlimited
Disaster Recovery: 0
Collect BMR Info:  no
Keyword:           
Data Classification:       -
Residence is Storage Lifecycle Policy:    no
Client Encrypt:    no
Checkpoint:        no
Residence:         -
Volume Pool:       NetBackup
Server Group:      *ANY*
Granular Restore Info:  no
Exchange Source attributes:              no
Exchange 2010 Preferred Server: (none defined)
Application Discovery:      no
Discovery Lifetime:      0 seconds
ASC Application and attributes: (none defined)
Generation:      10
Ignore Client Direct:  no
Enable Metadata Indexing:  no
Index server name:  NULL
Use Accelerator:  no
Client/HW/OS/Pri/DMI:  <Client Info>
Include:           /usr/openv/netbackup/ext/db_ext/oracle/BackupScript.sh
Schedule:              Yearly
  Type:                FULL SObk (0)
  Calendar sched: Enabled
    Allowed to retry after run day
    SPECIFIC DATE 0 - 01/05/2014
    SPECIFIC DATE 1 - 01/05/2015
    SPECIFIC DATE 2 - 01/05/2016
    SPECIFIC DATE 3 - 01/05/2017
    SPECIFIC DATE 4 - 01/05/2018
    SPECIFIC DATE 5 - 01/05/2019
    SPECIFIC DATE 6 - 01/05/2020
    SPECIFIC DATE 7 - 01/05/2021
    SPECIFIC DATE 8 - 01/05/2022
    SPECIFIC DATE 9 - 01/05/2023
  Maximum MPX:         12
  Synthetic:           0
  Checksum Change Detection: 0
  PFI Recovery:        0
  Retention Level:     0 (35 days)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  Number Copies:       1
  Fail on Error:       0
  Residence:           <SLP Name>
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      020:00:00  029:00:00   020:00:00  029:00:00
   Monday      020:00:00  029:00:00   044:00:00  053:00:00
   Tuesday     020:00:00  029:00:00   068:00:00  077:00:00
   Wednesday   020:00:00  029:00:00   092:00:00  101:00:00
   Thursday    020:00:00  029:00:00   116:00:00  125:00:00
   Friday      020:00:00  029:00:00   140:00:00  149:00:00
   Saturday    020:00:00  029:00:00   164:00:00  173:00:00 005:00:00

Schedule:              Default-Application-Backup
  Type:                UBAK Obak (2)
  Frequency:           7 day(s) (604800 seconds)
  Maximum MPX:         15
  Synthetic:           0
  Checksum Change Detection: 0
  PFI Recovery:        0
  Retention Level:     0 (35 days)
  u-wind/o/d:          0 0
  Incr Type:           DELTA (0)
  Alt Read Host:       (none defined)
  Max Frag Size:       0 MB
  Number Copies:       1
  Fail on Error:       0
  Residence:           <SLP Name>
  Volume Pool:         (same as policy volume pool)
  Server Group:        (same as specified for policy)
  Residence is Storage Lifecycle Policy:         1
  Schedule indexing:     0
  Daily Windows:
   Day         Open       Close       W-Open     W-Close
   Sunday      000:00:00  024:00:00   000:00:00  024:00:00
   Monday      000:00:00  024:00:00   024:00:00  048:00:00
   Tuesday     000:00:00  024:00:00   048:00:00  072:00:00
   Wednesday   000:00:00  024:00:00   072:00:00  096:00:00
   Thursday    000:00:00  024:00:00   096:00:00  120:00:00
   Friday      000:00:00  024:00:00   120:00:00  144:00:00
   Saturday    000:00:00  024:00:00   144:00:00  168:00:00

 

pri3006
Level 4
Certified

As you mentioned, It triggers on monthly basis with yearly policy name, can you check the script used for the monthly policy and see if the monthly policy's name is mentioned in the 'NB_ORA_POLICY' parameter?

Possible
Level 6
Accredited Certified

Monthly policy has correct .sh mentioned in nbu and on rman it has correct NB_ORA_POLICY i.e. monthly

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Have you checked Oracle output file/log as well as dbclient log to see if variable is interpreted correctly? 
We need to see what is sent to NBU.

Which shell is used for the script?
Possibility that $NB_ORA_POLICY and ${NB_ORA_POLICY} is different depending on the shell being used.

If you have different scripts for monthly and yearly, why not simply hardcode the policy name in the 'send' statement?

View solution in original post

Possible
Level 6
Accredited Certified

Tried to forecast next year schedule with nbpemreq which proved +ve result and shown next year date.

Thanks for the info provided ; but i was still not sure as parent job was showing scheduled for this month for yearly policy. (I understand that failed backup when resterted will only show as Scheduled).