Results 1 to 3 of 3
  1. #1
    Join Date
    Aug 2014

    Red face Unanswered: context allocation routine failed - Invalid context version

    The backups failed this am and we are not sure what the next steps will be. Hoping that a major upgrade is not required yet.

    Here is the message:

    The context allocation routine failed.
    Physical backup of XXXX on server XXX started at
    Friday, August 1, 2014
    The context allocation routine failed.
    The following problem caused the failure:
    Invalid context version.
    SQL-BackTrack Sybase Backup Utility (DTSBACKUP).
    Copyright (c) 1995-2011, BMC Software, Inc.
    Version (32bit binary)
    (SunOS XXXX 5.10 Generic_147440-15 sun4u)

    *** control directory is /usr/datatools/sbackups.physical/XXX/XXXXXX
    BMCBKS5709511F: Error 'FILE_OPEN_ERROR in Directory:/usr/datatools/tmp/:PERMISSION DENIED' : while trying to lock the control file '/usr/datatools/sbackups.physical/XXX/XXXXXX' for the current task.

  2. #2
    Join Date
    Jan 2012
    Provided Answers: 1

    Probably the backup of the day before the 01, did not complete ok, and is hanging.

    '/usr/datatools/sbackups.physical/XXX/XXXXXX' - locked by another process. So your new backup wont be able to use it.

    look for other sbactrack processes
    ps -ef | grep sbac ( smth like this )

    You will see older processes with more days.... that should not be running.
    Kill them and try again it should be fine.


  3. #3
    Join Date
    Aug 2014

    Thumbs up

    Thanks, Catarrunas for responding. That will be something to remember for the future.

    Since posting, it was discovered that the Pax used to unpack data after a transfer didn't preserve the directory and file ownership and assigned all permissions to the root. All but one of the permissions had been changed. The last one has been fixed.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts