Results 1 to 3 of 3
  1. #1
    Join Date
    Dec 2006
    Posts
    2

    Unanswered: Can't load database from file in tape backup ASE15.0

    I have some problem with load database from tapebackup like this
    "
    1> load database ssmdb from tape_dump with file='ssmdb063500C62F '
    2> go
    Backup Server session id is: 132. Use this value when executing the
    'sp_volchanged' system stored procedure after fulfilling any volume change
    request from the Backup Server.
    Backup Server: 6.28.1.1: Dumpfile name 'ssmdb063500C62F ' section number 1
    mounted on tape drive '/dev/rmt/0n'
    The database 'graddb' is currently not available and cannot be checked for
    cross-database encryption key references for the keys existing in database
    'ssmdb'.
    Backup Server: 4.139.2.22: [105] The 'uncompress' call failed for device
    '/dev/rmt/0n' with error number 12 (Not enough space). Refer to your operating
    system documentation for further details. Look for 'Dec 21 16:50:54 2006: A00:
    SYBMULTBUF ERROR: ' in the backup server errorlog for additional information
    from SYBMULTBUF.
    Msg 8009, Level 16, State 1:
    Server 'SYBDEVDB', Line 1:
    Error encountered by Backup Server. Please refer to Backup Server messages for
    details."
    Any can tell me how to load it please.

  2. #2
    Join Date
    Dec 2006
    Posts
    1

    Cross-database constraints and loading databases

    System Administration Guide
    Chapter 12: Backing Up and Restoring User Databases
    --------------------------------------------------------------------------------


    If you use the references constraint of create table or alter database to reference tables across databases, you may encounter problems when you try to load a dump of one of these databases.

    If tables in a database reference a dumped database, referential integrity errors result if you load the database with a different name or on a different server from where it was dumped. To change the name or location of a database when you reload it, use alter database in the referencing database to drop all external referential integrity restraints before you dump the database.

    Loading a dump of a referenced database that is earlier than the referencing database may cause consistency issues or data corruption. As a precaution, each time you add or remove a cross-database constraint or drop a table that contains a cross-database constraint, dump both affected databases.

    Dump all databases that reference each other at the same time. To guard against synchronization problems, put both databases in single-user mode for the dumps. When loading the databases, bring both databases online at the same time.

    Cross-database constraints can become inconsistent if you:

    Do not load database dumps in chronological order (for example, you load a dump created on August 12, 1997 after one created on August 13), or

    Load a dump into a database with a new name.

    If you do not load, cross-database constraints can become inconsistent.

    To remedy this problem:

    Put both databases in single-user mode.

    Drop the inconsistent referential constraint.

    Check the data consistency with a query such as:

    select foreign_key_col from table1
    where foreign_key not in
    (select primary_key_col from otherdb..othertable)

    Fix any data inconsistency problems.

    Re-create the constraint.

  3. #3
    Join Date
    Dec 2006
    Posts
    2

    Question Don't understand

    I don't understand while in ASE 12.5 can load please tell me.
    Quote Originally Posted by willemwinckel
    System Administration Guide
    Chapter 12: Backing Up and Restoring User Databases
    --------------------------------------------------------------------------------


    If you use the references constraint of create table or alter database to reference tables across databases, you may encounter problems when you try to load a dump of one of these databases.

    If tables in a database reference a dumped database, referential integrity errors result if you load the database with a different name or on a different server from where it was dumped. To change the name or location of a database when you reload it, use alter database in the referencing database to drop all external referential integrity restraints before you dump the database.

    Loading a dump of a referenced database that is earlier than the referencing database may cause consistency issues or data corruption. As a precaution, each time you add or remove a cross-database constraint or drop a table that contains a cross-database constraint, dump both affected databases.

    Dump all databases that reference each other at the same time. To guard against synchronization problems, put both databases in single-user mode for the dumps. When loading the databases, bring both databases online at the same time.

    Cross-database constraints can become inconsistent if you:

    Do not load database dumps in chronological order (for example, you load a dump created on August 12, 1997 after one created on August 13), or

    Load a dump into a database with a new name.

    If you do not load, cross-database constraints can become inconsistent.

    To remedy this problem:

    Put both databases in single-user mode.

    Drop the inconsistent referential constraint.

    Check the data consistency with a query such as:

    select foreign_key_col from table1
    where foreign_key not in
    (select primary_key_col from otherdb..othertable)

    Fix any data inconsistency problems.

    Re-create the constraint.

Posting Permissions

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