restore database gives error UnsupportedOperationException - orientdb

I'm following this less than precise tutorial Data Mining The City
I've create the database from the studio and it shows in my
databases folder as "soufun_db".
I downloaded the soufun.zip file into the directory db that I
created in the orientdb folder
Then I connect to the"soufun_db" database from the console
"CONNECT remote:localhost/soufun_db admin admin"
Then I run my restore database command
"RESTORE DATABASE /home/mustafa/Desktop/orientdb-community-2.1.0/db/soufun.zip
Output is:
"Restoring database database /home/.../soufun.zip
Error: java.lang.UnsupportedOperationException: restore"

BACKUP and RESTORE operations are supported only via plocal connection.
http://orientdb.com/docs/last/Console-Command-Restore.html

Related

Why am I receiving "error connected to db server: no reachable servers" after importing GZipped Archive file(.agz) to Studio 3T?

I have my database running on a docker container and I want to upload data stored in GZipped Archive file (.agz) to Studio 3T using Mongodump import. However, when I click execute it returns an error: "Import mongodump archive error connecting to db server: no reachable servers".
I have tried unzipping file, re-establishing local connection to docker container, dropping collection before importing, and all the other types of imports.
After trying the "Another Collection" import, importing the file appears to be successful with a green checkmark but logs 0 files uploaded. Every other import gives the
Import mongodump archive error connecting to db server: no reachable servers
Does anyone have any experience with this?

Does Enterprise DB can be migrated to Cloud SQL from Google Cloud?

I'm currently trying to migrate from a SQL dump file from an EnterpriseDB server to Cloud SQL Product from Google Cloud.
While searching in logs i got these messages:
"FATAL: pg_hba.conf rejects connection for host "201.xxx.xx.xxx", user "postgres", database "cloudsqladmin", SSL off"
Also:
"ERROR: unrecognized configuration parameter "edb_redwood_date""
The file i'm trying to import is a EnterpriseDB PostgreSQL file (version 9.6.6.11) and wanted to migrate to Cloud SQL Postgres (9.6).
As far as i know pg_hba.conf is a configuration file in the EnterpriseDB server, what does this file has to do with ? Do I need some normal Postgres file to migrate?
Thanks in advance.

Orient db import data

I am trying to do export/import in orient db 1.7.4 community edition between to different orient db servers running same version.
I did export database dbone which created dbone.json.gz file.
connected to other server created a new database and ran import database dbone.json.gz
it terminated with below error.
Error on importing database 'dbthree' from file: dbthree.json.gz
Error while removing cluster '10'
E:\Installs\orientdb-community-1.7.4\orientdb-community-1.7.4\databases\dbthree\e.0.ocl: The process cannot access the file because it is being used by another process.
This exception:
The process cannot access the file because it is being used by another process.
Means you've a console or server open that locks the database.

Google Cloud MySql Instance An unknown error occurred when importing

I created a mysql instance and everything is running on it. I used the process outlined in the cloud sql import to create a mysqldump file from my local production mysql instance running on windows.
mysqldump --databases xxxxx -uroot -p --hex-blob --default-character-set=utf8 > d:\database_file_feb2_2014.sql
Uploaded the file to the cloud storage and every time I try to import I get a Unknown error.
Things I have checked.
1) Made sure the USE database; command was in the file after the
CREATE DATABASE IF NOT EXISTS databasename;
command.
2) Made sure i was using the --hex-blob command.
created a export of smaller test db which was only 4.5MB instead of the 6GB file i was trying to import. Ran the first few lines from the sql prompt which ran fine.
Still unable to isolate at which line the import is breaking or Why
When I try to view the log from the old console, I get "An error has occurred. Please retry later."
I have dumped the whole instance and recreated the instance and still get the same error.
Origin OS: Windows Server 2003 R2
Running Mysql 5.1
Any advise on how I can troubleshoot this and move forward.
Thank you

DB2: not able to restore from backup

I am using command
db2 restore db S18 from /users/intadm/s18backup/ taken at 20110913113341 on /users/db2inst1/ dbpath on /users/db2inst1/ redirect without rolling forward
to restore database from backup file located in /users/intadm/s18backup/ .
Command execution gives such output:
SQL1277W A redirected restore operation is being performed. Table space
configuration can now be viewed and table spaces that do not use automatic
storage can have their containers reconfigured.
DB20000I The RESTORE DATABASE command completed successfully.
When I'm trying to connect to restored DB (by executing 'db2 connect to S18'), I'm getting this message:
SQL0752N Connecting to a database is not permitted within a logical unit of
work when the CONNECT type 1 setting is in use. SQLSTATE=0A001
When I'm trying to connect to db with db viewer like SQuireL, the error is like:
DB2 SQL Error: SQLCODE=-1119, SQLSTATE=57019, SQLERRMC=S18, DRIVER=3.57.82
which means that 'error occurred during a restore function or a restore is still in progress' (from IBM DB2 manuals)
How can I resolve this and connect to restored database?
UPD: I've executed db2ckbkp on backup file and it did not identified any issues with backup file itself.
without rolling forward can only be used when restoring from an offline backup. Was your backup taken offline? If not, you'll need to use roll forward.
When you do a redirected restore, you are telling DB2 that you want to change the locations of the data files in the database you are restoring.
The first step you show above will execute very quickly.
Normally, after you execute this statement, you would have one or more SET TABLESPACE CONTAINERS to set the new locations of each data file. It's not mandatory to issue these statements, but there's no point in specifying the redirect option in your RESTORE DATABASE command if you're not changing anything.
Then, you would issue the RESTORE DATABASE S18 COMPLETE command, which would actually read the data from the backup image, writing it to the data files.
If you did not execute the RESTORE DATABASE S18 COMPLETE, then your restore process is incomplete and it makes sense that you can't connect to the database.
What I did and what has worked:
Executed:
db2 restore db S18 from /users/intadm/s18backup/ taken at 20110913113341 on /<path with sufficient disk space> dbpath on /<path with sufficient disk space>
I got some warnings before, that some table spaces are not moved. When I specified dbpath to partition with sufficient disk space - warning has disappeared.
After that, as I have an online backup, I issued:
db2 rollforward db S18 to end of logs and complete
That's it! Now I'm able to connect.