Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

java.lang.ArrayIndexOutOfBoundsException: 0 on remote select after restore from backup #3662

Closed
rinatio opened this issue Feb 25, 2015 · 2 comments
Assignees
Milestone

Comments

@rinatio
Copy link

rinatio commented Feb 25, 2015

Hello guys,

I'm testing backup/restore with built in GratefulDeadConcerts database and getting a java.lang.ArrayIndexOutOfBoundsException: 0 error on select * from written_by with remote connect after restore

Here're steps to reproduce:

# ./orientdb/bin/console.sh
orientdb> connect plocal:/opt/orientdb/databases/GratefulDeadConcerts admin admin
orientdb {db=GratefulDeadConcerts}> backup database /opt/orientdb/backup.zip
orientdb {db=GratefulDeadConcerts}> drop database
# sudo /etc/init.d/orientdb.sh start
orientdb> create database remote:127.0.0.1/GratefulDeadConcerts root password plocal
# /etc/init.d/orientdb.sh stop
orientdb {db=GratefulDeadConcerts}> connect plocal:/opt/orientdb/databases/GratefulDeadConcerts admin admin
orientdb {db=GratefulDeadConcerts}> restore database /opt/orientdb/backup.zip
orientdb {db=GratefulDeadConcerts}> quit
# /etc/init.d/orientdb.sh start
# ./orientdb/bin/console.sh
orientdb> connect remote:127.0.0.1/GratefulDeadConcerts admin admin
orientdb {db=GratefulDeadConcerts}> select * from written_by

Error: com.orientechnologies.orient.core.exception.OCommandExecutionException: Error on execution of command: sql.select * from written_by

Error: java.lang.ArrayIndexOutOfBoundsException: 0

Note: with local connect query doesn't throw this exception

@rinatio
Copy link
Author

rinatio commented Mar 7, 2015

Is it safe to use backups with such exception? Will it be possible to restore the DB from such backup files once this issue is resolved?

@lvca lvca added bug labels Mar 8, 2015
@lvca lvca modified the milestones: 2.0.5, 2.0.6 Mar 8, 2015
tglman added a commit that referenced this issue Mar 13, 2015
tglman added a commit that referenced this issue Mar 20, 2015
@tglman
Copy link
Member

tglman commented Mar 20, 2015

merged in 2.0.x closing

@tglman tglman closed this as completed Mar 20, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants