[ 
https://issues.apache.org/jira/browse/DERBY-4321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Myrna van Lunteren closed DERBY-4321.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.9.0.0
         Assignee: Myrna van Lunteren

I had created DERBY-5649 to make improvements to nstest and resolved the 22003 
error for that bug. Also the XBM06 error is now reflected in the README as 
expected errors.
I looked into the 40XL1 errors and they seem normal to me - to be expected with 
the kind of operations we're doing on the tables. I added a note to reflect 
this to the README with revision 1332887.

Closing this issue.
                
> test nstest generates errors XBM06 re reencryption and 22003 re value outside 
> range for decimal/numeric
> -------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-4321
>                 URL: https://issues.apache.org/jira/browse/DERBY-4321
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.5.2.0
>            Reporter: Myrna van Lunteren
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.9.0.0
>
>
> The test nstest (both in embedded and networkserver) ran into a 
> JVM-bug-related error the last few times I tried it; but with a newer jvm I 
> notice it's generating an XBM06 error:
> XBM06: Startup failed. An encrypted database cannot be accessed without the 
> correct boot password. 
> From the test's README.txt it shows it is indeed attempting to re-encrypt, 
> but this is failing.
> The test needs to be tightened up so it doesn't show unusual errors.
> The test also generates:
> 22003: The resulting value is outside the range for the data type 
> DECIMAL/NUMERIC(5,0)
> The test's readme and comments don't indicate this is a negative test, so 
> this too should get tightened/cleaned up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to