Recommended backup set name when using VERITAS NetBackup (tm) for Oracle

Article:TECH20615  |  Created: 2002-01-11  |  Updated: 2011-04-07  |  Article URL http://www.symantec.com/docs/TECH20615
Article Type
Technical Solution


Environment

Subject

Problem



When using VERITAS NetBackup (tm) for Oracle, backup occasionally fails with RMAN error ORA-27016.


Error



ORA-27016, 00000, "skgfcls: sbtinfo returned error"
ORA-27192: skgfcls: sbtclose2 returned error - failed to close file
 


Solution



In an Oracle RMAN script there is a "format" parameter.  This is used as a template by Oracle Recovery Manager to create a name for the backup file it creates.

The NetBackup recommended backup set name format is:

"bk_%s_%p_%t"

1. %s  is the backup set number
2. %p is the backup piece number
3. %t  is the backup set stamp

When you use the recommended format in the RMAN script, Oracle creates a backup set name that NetBackup can decipher into a valid date.  NetBackup then uses this date as a base date to create a date range to use in the search of the catalog database.

If you deviate from this format, NetBackup usually can tell that the last ten bytes of the backup set name does not contain date information and then uses a default date range in the search of the catalog database.

Sometimes, however the backup set name consists of a numeric format that NetBackup may misinterpret to be a valid date.

This is when the following error occurs as shown in the dbclient log:

(Please note the Start Time = 06/10/99 and End Time = 06/12/99 for this backup which took place August 13, 2000.)  The backup then fails with "sbtinfo: No media found".

17:10:54 [8663] <4> get_bfs_date_range: entering get_bfs_date_range.
17:10:54 [8663] <4> get_bfs_date_range: RMAN file name = i0h_CATAPRD24055367827021
17:10:54 [8663] <4> get_bfs_date_range: bfs_time=367827021,start_time=257126400,end_time=405537054
17:10:54 [8663] <4> get_bfs_date_range: yr=11, p=353548800, s=14278221, m=5
17:10:54 [8663] <4> get_bfs_date_range: adjust secs this year = 345600
17:10:54 [8663] <4> get_bfs_date_range: after adjusted for DST = 349200
17:10:54 [8663] <4> get_bfs_date_range: after adjusted for prev years = 349200
17:10:54 [8663] <4> get_bfs_date_range: after adjusted for leap years = 349200
17:10:54 [8663] <4> get_bfs_date_range: final bfs_time = 929099421
17:10:54 [8663] <4> get_bfs_date_range: Start range check: bfs_time=929099421, start=819936000, end=966287454
17:10:54 [8663] <4> get_bfs_date_range: Start Time = 06/10/99 07:10:21
17:10:54 [8663] <4> get_bfs_date_range: End Time = 06/12/99 07:10:21
17:10:54 [8663] <4> dbc_GetMediaListByName: entering dbc_GetMediaListByName.
17:10:54 [8663] <4> BuildBprdRequest: entering BuildBprdRequest.
17:10:54 [8663] <4> BuildBprdRequest: request_string=<3.2GA jx1ap034-bu jx1ap034-bu *NULL* 4 929013021 929185821 /i0h_CATAPRD24055367827021>
17:10:54 [8663] <4> dbc_GetMediaListByName: Request String = <3.2GA jx1ap034-bu jx1ap034-bu *NULL* 4 929013021 929185821 /i0h_CATAPRD24055367827021>
17:10:54 [8663] <4> getOwnerName: entering getOwnerName.
17:10:54 [8663] <2> getsockconnected: host=jx1ap009-bu service=bprd address=10.241.3.24 protocol=tcp non-reserved port=13720
17:10:55 [8663] <2> bind_for_connect: bound to port 0
17:10:55 [8663] <2> bprd_connect: no authentication required
17:10:55 [8663] <16> sbtinfo: No media found

For consistent results, VERITAS recommends the "backup set name" format statement should end with:   _%t




 


Legacy ID



248105


Article URL http://www.symantec.com/docs/TECH20615


Terms of use for this information are found in Legal Notices