You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Suresh Thalamati (JIRA)" <de...@db.apache.org> on 2005/08/20 00:25:54 UTC
[jira] Created: (DERBY-523) Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
--------------------------------------------------------------------------------------------------------------------------
Key: DERBY-523
URL: http://issues.apache.org/jira/browse/DERBY-523
Project: Derby
Type: Bug
Components: Store
Reporter: Suresh Thalamati
once the log archive mode that is required for roll-forward recoveryis enabled all the operations are logged including the operations that are not logged normally like create index.But I think the currently derby does not handle the case where correctly . non-logged operations that were started before log archive mode is enabled
This issue was discussed along with real time online backup (derby-239) on the list. Conclusing was to block the existing system procedure if the non-logged opeation were in progress while enabling the log archive mode. and add a new system procedures that will take extra parameters to deceide whethere to block /fail.
--
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
[jira] Updated: (DERBY-523) Non logged operation that starts before
the log archive mode is enabled can not be recovered during rollforward
recovery.
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-523?page=all ]
Kathey Marsden updated DERBY-523:
---------------------------------
Fix Version: 10.2.0.0
> Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-523
> URL: http://issues.apache.org/jira/browse/DERBY-523
> Project: Derby
> Type: Bug
> Components: Store
> Reporter: Suresh Thalamati
> Assignee: Suresh Thalamati
> Fix For: 10.2.0.0
>
> once the log archive mode that is required for roll-forward recoveryis enabled all the operations are logged including the operations that are not logged normally like create index.But I think the currently derby does not handle the case where correctly . non-logged operations that were started before log archive mode is enabled
> This issue was discussed along with real time online backup (derby-239) on the list. Conclusing was to block the existing system procedure if the non-logged opeation were in progress while enabling the log archive mode. and add a new system procedures that will take extra parameters to deceide whethere to block /fail.
--
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
[jira] Assigned: (DERBY-523) Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-523?page=all ]
Suresh Thalamati reassigned DERBY-523:
--------------------------------------
Assign To: Suresh Thalamati
> Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-523
> URL: http://issues.apache.org/jira/browse/DERBY-523
> Project: Derby
> Type: Bug
> Components: Store
> Reporter: Suresh Thalamati
> Assignee: Suresh Thalamati
>
> once the log archive mode that is required for roll-forward recoveryis enabled all the operations are logged including the operations that are not logged normally like create index.But I think the currently derby does not handle the case where correctly . non-logged operations that were started before log archive mode is enabled
> This issue was discussed along with real time online backup (derby-239) on the list. Conclusing was to block the existing system procedure if the non-logged opeation were in progress while enabling the log archive mode. and add a new system procedures that will take extra parameters to deceide whethere to block /fail.
--
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
[jira] Resolved: (DERBY-523) Non logged operation that starts
before the log archive mode is enabled can not be recovered during
rollforward recovery.
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-523?page=all ]
Suresh Thalamati resolved DERBY-523:
------------------------------------
Resolution: Fixed
This issue is fixed along wiith latest online backup patches(DERBY-239. . Backup is not allowed, if there are any pending unlogged operations.
svn commits:
r370530, r357269, r354898
> Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-523
> URL: http://issues.apache.org/jira/browse/DERBY-523
> Project: Derby
> Type: Bug
> Components: Store
> Reporter: Suresh Thalamati
> Assignee: Suresh Thalamati
>
> once the log archive mode that is required for roll-forward recoveryis enabled all the operations are logged including the operations that are not logged normally like create index.But I think the currently derby does not handle the case where correctly . non-logged operations that were started before log archive mode is enabled
> This issue was discussed along with real time online backup (derby-239) on the list. Conclusing was to block the existing system procedure if the non-logged opeation were in progress while enabling the log archive mode. and add a new system procedures that will take extra parameters to deceide whethere to block /fail.
--
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
[jira] Closed: (DERBY-523) Non logged operation that starts before
the log archive mode is enabled can not be recovered during rollforward
recovery.
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-523?page=all ]
Suresh Thalamati closed DERBY-523:
----------------------------------
> Non logged operation that starts before the log archive mode is enabled can not be recovered during rollforward recovery.
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-523
> URL: http://issues.apache.org/jira/browse/DERBY-523
> Project: Derby
> Type: Bug
> Components: Store
> Reporter: Suresh Thalamati
> Assignee: Suresh Thalamati
> Fix For: 10.2.0.0
>
> once the log archive mode that is required for roll-forward recoveryis enabled all the operations are logged including the operations that are not logged normally like create index.But I think the currently derby does not handle the case where correctly . non-logged operations that were started before log archive mode is enabled
> This issue was discussed along with real time online backup (derby-239) on the list. Conclusing was to block the existing system procedure if the non-logged opeation were in progress while enabling the log archive mode. and add a new system procedures that will take extra parameters to deceide whethere to block /fail.
--
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