Hello, You were right, as soon as I changed the encoding, it is now opening the orientDB Web UI. But when I open the "GratefulDeadConcerts" database with any username, I am getting the following errors on z/OS...
2014-02-13 07:03:29:550 WARN Sun Unsafe direct memory implementation is going to be used, this implementation is not stable so please use JNA version instead. [Class] 2014-02-13 07:03:29:666 SEVE Internal server error: com.orientechnologies.orient.core.exception.OStorageException: Cannot open local storage '/###/orientdb-community-1.6.3/databases/GratefulDeadConcerts' with mode=rw --> com.orientechnologies.orient.core.exception.OSerializationException: Cannot load database's configuration. The database seems to be corrupted. --> com.orientechnologies.common.io.OIOException: You cannot access outside the file size (626 bytes). You have requested portion 4-665 bytes. File: File: database.ocf os-size=1650, stored=626, filled=626, max=0 [ONetworkProtocolHttpDb] I did not even touch the database so it is not corrupted. Also I tried to run it on AIX, since z/OS and AIX use the same Java version (IBM Java) and I observed these errors... 2014-02-13 06:22:09:149 WARN Sun Unsafe direct memory implementation is going to be used, this implementation is not stable so please use JNA version instead. [Class] 2014-02-13 06:22:10:156 SEVE Database's schema is empty! Recreating the system classes and allow the opening of the database but double check the integrity of the database [OSchemaShared$12] 2014-02-13 06:22:10:325 SEVE Internal server error: com.orientechnologies.orient.core.exception.OQueryParsingException: Error on parsing query at position #6: Error on parsing query Query: OUser where name = 'admin' limit 1 -----------^ --> com.orientechnologies.orient.core.exception.OCommandExecutionException: Class 'OUSER' was not found in current database [ONetworkProtocolHttpDb] Also to check if this was a JNA issue, I removed the linux-* folders from the jna-4.0.0.jar and repacked it and ran it on Redhat on which it was working properly...then I get this Warning in the server console but no errors like the ones above and I can still log into the database. 2014-02-13 06:52:04:149 WARN Sun Unsafe direct memory implementation is going to be used, this implementation is not stable so please use JNA version instead. [Class] Would rebuilding JNA on z/OS and AIX fix these issues? I just want a confirmation so that I can try. On Thursday, 13 February 2014 15:24:18 UTC+5:30, Artem Orobets wrote: > > Hi, > > It seems that server uses another encoding then your client app. Client > writes database name to the network but server reads with other encoding. > > Try following, add -Dfile.encoding=ISO8859-1 parameter to server and > client JVM. > You can add this parameter to OrientDb server in server.sh > > Best regards, > Artem Orobets > > *Orient Technologies the Company behind OrientDB* > > > 2014-02-12 13:47 GMT+02:00 Dante <[email protected] <javascript:>>: > >> Hi Artem, >> >> I downloaded the Multiplatform binary for OrientDB 1.6.3 version. I faced >> some problems in extracting it into a proper format first, since >> conventional methods won't work on USS(on z/OS). I did that using pax >> utility and it somehow extracted the product but the xml files (like >> orientdb-server-config.xml) had a tag ^M attached to it wherever a new-line >> character is there. Then I did some manipulation to remove those and >> changed the xml encoding to ISO-1047(EBCDIC), and it finally ran(without >> the encoding, it throws JAXBMarshaller exceptions). But when I accessed the >> database using the following line in my Java Code. >> >> new OrientGraph("remote:<myserver>/GratefulDeadConcerts", "admin", >> "admin"); >> >> It throws a long list of exceptions and the root of it is not being able >> to find the above database with a changed text, >> >> Caused by: >> com.orientechnologies.orient.core.exception.OConfigurationException: >> Database 'åÊ/ÈÁÃÍ%àÁ/Àä?>ÄÁÊÈË' is not configured on server >> >> Same is observed if it is a JDBC connection. I am new to USS so I am not >> at all sure what is happening. Even the Web-UI is giving response but it >> gives junk characters on the page if the server is running. This is some >> sort of encoding issue I think. Will building the JNA for z/OS resolve this >> error? >> >> Thanks, >> Dante >> >> On Tuesday, 11 February 2014 19:59:53 UTC+5:30, Artem Orobets wrote: >> >>> Hi, >>> >>> z/OS is supported platform by OrientDB. The only inconvenience that >>> there is no JNA distribution for this os, so you should build them by >>> yourself from sources >>> (https://github.com/twall/jna<https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Ftwall%2Fjna&sa=D&sntz=1&usg=AFQjCNEvsae_ZnZ6xpTlIs_li7Z10Z4ASg> >>> ). >>> >>> >>> >>> Best regards, >>> Artem Orobets >>> >>> *Orient Technologies the Company behind OrientDB* >>> >>> >>> 2014-02-11 15:12 GMT+02:00 Dante <[email protected]>: >>> >>>> Hi, >>>> >>>> If it runs, then how to handle the EBCDIC to UTF-8 or vice-versa >>>> encodings? >>>> >>>> Thanks, >>>> Dante >>>> >>>> -- >>>> >>>> --- >>>> You received this message because you are subscribed to the Google >>>> Groups "OrientDB" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> >>>> For more options, visit https://groups.google.com/groups/opt_out. >>>> >>> >>> -- >> >> --- >> You received this message because you are subscribed to the Google Groups >> "OrientDB" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
