[ https://forge.continuent.org/jira/browse/SEQUOIA-906?page=all ]
Emmanuel Cecchet resolved SEQUOIA-906:
--------------------------------------
Resolution: Fixed
Fix Version: sequoia 2.10.10
Patch applied in 2.10 branch
> backup with MS JDBC driver for MS SQL Server 2005
> -------------------------------------------------
>
> Key: SEQUOIA-906
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-906
> Project: Sequoia
> Type: Bug
> Components: Configuration Files Parser
> Versions: Sequoia 3.0 beta2
> Environment: Version of Sequoia: 3.0 beta 2
> Database: MS SQL Server 2005 Express Edition
> OS: Windows XP SP2
> JVM version: 1.6
> Reporter: Denis Garyachy
> Assignee: Emmanuel Cecchet
> Fix For: sequoia 2.10.10
> Attachments: MSSQLBackuper ms jdbc driver.patch
>
>
> I am experiencing problems with creating backup using JDBC driver from
> Microsoft.
> I think there is a problem in parsing the connection string.
> Starting controller:
>
> 11:12:29,046 INFO controller.core.Controller Sequoia controller (3.0-beta2)
> 11:12:29,453 INFO controller.core.Controller Loading configuration file:
> xml\pcController.xml
> 11:12:29,656 INFO controller.core.Controller JMX is enabled
> 11:12:29,703 INFO controller.core.Controller Starting JMX server on host:
> 192.168.0.2:1090
> 11:12:30,859 INFO controller.backup.BackupManager Registering backuper
> MSSQLServer to handle format MSSQL raw dump
> 11:12:30,921 INFO backend.DatabaseBackend.mainPCDB Adding connection manager
> for virtual user "sa"
> 11:12:32,546 INFO controller.RequestManager.VirtualDatabase Request manager
> will parse requests with the following granularity: TABLE
> 11:12:32,578 INFO controller.virtualdatabase.VirtualDatabase Using Hedera
> properties file: /hedera_appia.properties
> 11:12:33,062 INFO appia.xml.AppiaXML Loading XML configuration from file:
> C:\sequoia\config\my_appia.xml
> 11:12:33,625 INFO continuent.hedera.appia AppiaThread: Starting Appia.
> 11:12:36,515 INFO controller.virtualdatabase.VirtualDatabase Group
> VirtualDatabase connected to Member(address=/192.168.0.2:2736, uid=
> 192.168.0.2:2736)
> 11:12:36,515 INFO controller.virtualdatabase.VirtualDatabase First
> controller in group VirtualDatabase
> 11:12:36,562 INFO sequoia.controller.recoverylog Checking recovery log
> consistency
> 11:12:36,562 INFO controller.virtualdatabase.VirtualDatabase Enabling
> backend mainPCDB from checkpoint disable
> mainPCDB-mainPCController-20070129110936296+0200
> 11:12:37,453 INFO backend.DatabaseBackend.mainPCDB Detected backend as:
> Microsoft SQL Server
> 11:12:37,531 WARN backend.DatabaseBackend.mainPCDB
> Statement.getGeneratedKeys not supported.
> 11:12:46,828 INFO controller.RequestManager.VirtualDatabase Setting new
> virtual database schema.
> 11:12:46,875 INFO controller.recoverylog.RecoverThread Starting recovery
> 11:12:47,171 INFO controller.RequestManager.VirtualDatabase All activity is
> suspended for VirtualDatabase
> 11:12:47,171 INFO controller.recoverylog.RecoverThread Recovery completed
> 11:12:47,234 INFO controller.recoverylog.RecoverThread Database backend
> mainPCDB is now enabled
> 11:12:47,250 WARN controller.virtualdatabase.VirtualDatabase No response
> while getting static metadata from remote controller
> 11:12:47,375 INFO controller.core.Controller Adding VirtualDatabase
> VirtualDatabase
> 11:12:47,390 INFO controller.core.Controller Waiting for connections on
> 0.0.0.0:25322
> 11:12:47,406 INFO controller.core.Controller Controller started on
> 2007.01.29 05 at 11:12:47 AM EET
> 11:12:47,406 INFO controller.core.Controller Controller mainPCController
> ready, listening to requests ...
>
> 1.1 Virtual Database configuration #1
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE SEQUOIA SYSTEM "C:/sequoia/xml/sequoia-3.0-beta2.dtd">
> <SEQUOIA>
> <VirtualDatabase name="VirtualDatabase">
> <Distribution>
> <MessageTimeouts/>
> </Distribution>
>
> <Backup>
> <Backuper backuperName="MSSQLServer"
> className="org.continuent.sequoia.controller.backup.backupers.MSSQLBackuper"/>
> </Backup>
>
> <AuthenticationManager>
> <AdminUser username="admin" password=""/>
> <VirtualUser vLogin="sa" vPassword="1"/>
> </AuthenticationManager>
> <DatabaseBackend name="mainPCDB"
> driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"
>
> url="jdbc:sqlserver://localhost;databaseName=VirtualDatabase"
> connectionTestStatement="SELECT 1">
> <ConnectionManager vLogin="sa"
> rLogin="sa"
> rPassword="1">
> <VariablePoolConnectionManager
> initPoolSize="10"
> minPoolSize="5"
> maxPoolSize="50"
> idleTimeout="30"
> waitTimeout="30"/>
> </ConnectionManager>
> </DatabaseBackend>
> <DatabaseSchema/>
> <RequestManager>
> <RequestScheduler>
> <RAIDb-1Scheduler level="passThrough"/>
> </RequestScheduler>
> <RequestCache>
> <MetadataCache/>
> <ParsingCache/>
> <!-- <ResultCache granularity="table"/> -->
> </RequestCache>
> <LoadBalancer>
> <RAIDb-1>
> <WaitForCompletion policy="first"/>
> <RAIDb-1-LeastPendingRequestsFirst/>
> </RAIDb-1>
> </LoadBalancer>
>
> <EmbeddedRecoveryLog/>
> </RequestManager>
> </VirtualDatabase>
> </SEQUOIA>
> 1.2 Sequoia's console output:
> admin VirtualDatabase
> admin
> Ready to administrate virtual database VirtualDatabase
> expert on
> Expert mode on
> initialize mainPCDB
> Virtual Database VirtualDatabase has been successfully initialized from
> backend
> backup mainPCDB init_dump MSSQLServer \tmp
> sa
> Backup backend mainPCDB in dump file init_dump
> Unsupported db url jdbc:sqlserver://localhost;databaseName=VirtualDatabase
> 2.1 Virtual Database configuration #2
>
> <?xml version="1.0" encoding="UTF-8"?>
> <!DOCTYPE SEQUOIA SYSTEM "C:/sequoia/xml/sequoia-3.0-beta2.dtd">
> <SEQUOIA>
> <VirtualDatabase name="VirtualDatabase">
> <Distribution>
> <MessageTimeouts/>
> </Distribution>
>
> <Backup>
> <Backuper backuperName="MSSQLServer"
> className="org.continuent.sequoia.controller.backup.backupers.MSSQLBackuper"
> options="urlHeader=jdbc:sqlserver:,driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
> "/>
> </Backup>
>
> <AuthenticationManager>
> <AdminUser username="admin" password=""/>
> <VirtualUser vLogin="sa" vPassword="1"/>
> </AuthenticationManager>
> <DatabaseBackend name="mainPCDB"
> driver="com.microsoft.sqlserver.jdbc.SQLServerDriver"
>
> url="jdbc:sqlserver://localhost;databaseName=VirtualDatabase"
> connectionTestStatement="SELECT 1">
> <ConnectionManager vLogin="sa"
> rLogin="sa"
> rPassword="1">
> <VariablePoolConnectionManager
> initPoolSize="10"
> minPoolSize="5"
> maxPoolSize="50"
> idleTimeout="30"
> waitTimeout="30"/>
> </ConnectionManager>
> </DatabaseBackend>
> <DatabaseSchema/>
> <RequestManager>
> <RequestScheduler>
> <RAIDb-1Scheduler level="passThrough"/>
> </RequestScheduler>
> <RequestCache>
> <MetadataCache/>
> <ParsingCache/>
> <!-- <ResultCache granularity="table"/> -->
> </RequestCache>
> <LoadBalancer>
> <RAIDb-1>
> <WaitForCompletion policy="first"/>
> <RAIDb-1-LeastPendingRequestsFirst/>
> </RAIDb-1>
> </LoadBalancer>
>
> <EmbeddedRecoveryLog/>
> </RequestManager>
> </VirtualDatabase>
> </SEQUOIA>
> 2.2 Sequoia's console output:
>
> admin VirtualDatabase
> admin
> Ready to administrate virtual database VirtualDatabase
> expert on
> Expert mode on
> initialize mainPCDB
> Backend mainPCDB is not in a disabled state (current state is enabled)
> backup mainPCDB init_dump MSSQLServer \tmp
> sa
> Backup backend mainPCDB in dump file init_dump
> Incorrect syntax near the keyword 'null'.
> enable mainPCDB
> Enabling backend mainPCDB from its last known checkpoint
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
