db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-588) database created on zOS (os/390) cannot be used on windows
Date Tue, 02 Oct 2007 15:41:50 GMT

    [ https://issues.apache.org/jira/browse/DERBY-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12531832

Kathey Marsden commented on DERBY-588:

I wonder if this is not a JVM bug.  We use Properties.store to save the service.properties
settings and the javadoc says:
    * The stream is written using the ISO 8859-1 character encoding.
    * Characters not in Latin-1 in the comments are written as \uxxxx for their appropriate
unicode hexadecimal value xxxx.
    * Characters less than \u0020 and characters greater than \u007E in property keys or values
are written as \uxxxx for the appropriate hexadecimal value xxxx. 

So we should get a common format on all platforms.  Could you perhaps try this on a newer
JVM and see if it is still a problem?



> database created on zOS (os/390) cannot be used on windows
> ----------------------------------------------------------
>                 Key: DERBY-588
>                 URL: https://issues.apache.org/jira/browse/DERBY-588
>             Project: Derby
>          Issue Type: Bug
>          Components: Services
>    Affects Versions:
>         Environment: zOS, R6, with ibm jvm 142
>            Reporter: Myrna van Lunteren
> When a database is created on zOS, the service.properties is readable English, thus,
it is created in EBCDIC or with file.encoding Cp1047. After jar -cvf, ftp to window, jar -xvf,
the database is not accessible:
> ---------------
> ERROR XJ040: Failed to start database 'bladb2', see the next exception for details.
> ERROR XCY03: Required property 'derby.serviceProtocol' has not been set.
> --------------
> which is the error we get when something is wrong with service.properties in the database.
> After converting (native2ascii -encoding Cp1047) service.properties, the database is
usable again.
> Doing the reverse, i.e. creating and jar-ing the database on windows and ftp-ing it to
zOs, works fine. In that case, service.properties is not readable.
> If I understand correctly how this should work, Derby should not create the service.properties
on zOS in local encoding.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message