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

Member Login

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.

LINK TO THIS FORUM!

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

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...Over the past year I have found your site to be EXCELLENT. Never have I been able to find so many answers to such vast problems and it is an excellent service..."

Geography

Where in the world do Tek-Tips members come from?
AKATOOT (IS/IT--Management)
23 Mar 12 10:03
I am not sure what to do here or if there is anything I can do for this. This error showed up in the error log and it caused the server to miss a drive backup for drive F. I ran the TSM backup again on this F drive and it didn't commpete. I restarted the services and reconfigured the journal service.
From what I understand it is really not needed. So having this missed backup was unnessesary because if this service was not on there would have been no errors.

In the event log in applications the error was this "Unrecoverable database access error on Journal 'F:'.".
In the journal error log this is what I see.

"03/22/2012 18:36:50 ANS0361I DIAG: purgecache(): corrupt node, Invalid magic number 74006c, expected abcd.
03/22/2012 18:36:50 ANS0361I DIAG: walkTree(): fetchPage() returned -1, dbErrno: 228, "Unknown error".
03/22/2012 18:36:50 ANS0361I DIAG: dbGetList(): WalkTree(): rc = 164.
03/22/2012 18:36:50 ANS0361I DIAG: processJournalQuery(): Error performing journal query, db result code = 164.
03/22/2012 18:36:50 ANS0361I DIAG: processJournalQuery(): A database access error occurred during a journal query, journal will be restarted and placed offline."

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