db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Assigned: (DERBY-1240) creating /restoring a db from backup using createFrom with log at different location copies the log from backup to the db dir also.
Date Thu, 05 Oct 2006 23:56:20 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1240?page=all ]

Suresh Thalamati reassigned DERBY-1240:
---------------------------------------

    Assignee: Suresh Thalamati

> creating /restoring a db from backup using createFrom with log at different location
copies the log from backup to the db dir also.
> -----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-1240
>                 URL: http://issues.apache.org/jira/browse/DERBY-1240
>             Project: Derby
>          Issue Type: Bug
>          Components: Store
>    Affects Versions: 10.2.1.6, 10.1.3.0
>         Environment: WindowsXP/JDK142
>            Reporter: Suresh Thalamati
>         Assigned To: Suresh Thalamati
>            Priority: Minor
>
> creating/restoring  a database from a backup copy with exteral log location  copies the
transaction log to the default location.  db uses the external location , but there is unnessary
copy of transaction log at default location. 
> connect 'wombat;create=true';
> create table t1(a int );
> insert into t1 values(15);
> call SYSCS_UTIL.SYSCS_BACKUP_DATABASE('extinout/mybackup');
> connect 'wombat;shutdown=true';
> disconnect;
> --- create a db from the backup using a different log location.
> connect 'crwombat;createFrom=extinout/mybackup/wombat;logDevice=extinout/crwombatlog';
> select * from t1;
> --- If you loook under the "crwombat" dir  you will find the log dir , it should not
 be there because 
> --  transaction log  is place st  extinout/crwombatlog  as specified in the  connection
URL.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message