Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login




Remember Me
Forgot Password?
Join Us!

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Donate Today!

Do you enjoy these
technical forums?
Donate Today! Click Here

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.
Jobs from Indeed

Link To This Forum!

Partner Button
Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Urgent Need - NBU dbclient log issueHelpful Member! 

Threedot (TechnicalUser) (OP)
9 Jul 08 10:32
I am seeing the following in my dbclient logs on one of my servers:

04:35:30.019 [27642] <2> int_logDateRange: INF - Start Time = 12/25/95 19:00:00
04:35:30.019 [27642] <2> int_logDateRange: INF - End Time = 07/10/08 04:35:30

End time is correct, start time is hosed...

Other than the festive nature, does anyone know why the start time of every job in the log is Christmas 1995?  

I have an irritated DBA who is insisting that this be resoloved. I have gone to the Google alter, and this error even appears in log samples in Symantec Tech Notes!

- and yes, that does make me chuckle...
smicro (MIS)
10 Jul 08 13:51
What version of netbackup and db2?  Feel bad you have to deal with a dba thats punishment in itself, at least the ones we have.
Helpful Member!  Threedot (TechnicalUser) (OP)
29 Jul 08 9:29
Got it resolved!

In reality, this log entry is not a start time as I was thinking of it.  
 
This is the default date where the NBU backup process begins its search of the image database.  Since it doesn't see the Oracle timestamp in the file name (Established in the RMAN script with the "FORMAT" line by the %t value), it defaults to 12/25/95 as the "Start Time".  Not the start time of the job, but rather the starting point of a date range it will use for the image search it performs as part of the backup process.  It has nothing to do with the start time of the backup.
 
The reality is that this is in fact reporting correctly - It is starting at 12/25/95 when it searches the image database, and ending at the "End Time" shown.
 

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close