I recently installed PostgresSQL and, previously, in a former install, I was able to import CSV files using Tools/(Import/Export). This is now greyed out, along with Table icon, next to the Query tool icon.
Related
Using MySQL Workbench 6.3.8 build 1228 CE (64-bit), on Windows 10 Pro, version 1803, build 17134.112.
I want to restore my old workspaces in MySQL Workbench. If that is not possible, I will be happy with just being able to access them as text files.
I guess my laptop had an unusual power-off or reset last night. Normally I put it in Sleep mode, but when I opened it this morning it had reset itself: all applications had quit.
I re-opened Workbench, and got this error message:
saying that my workspaces could not be opened.
I can't get the full text of the error message, so I don't know exactly where Workbench is looking, but using Windows Explorer I could navigate to:
C:\Users\JamesBarton\AppData\Roaming\MySQL\Workbench\sql_workspaces
which looks right to me, and contains .workspace and .autosave directories.
I've backed up the Workbench\ directory, and then tried just removing the .autosave directories, to force the use of the .workspace directories, but when I did that, Workbench still just opened one empty tab. The first .workspace directory contains 95 files, including 45 .scratch files totalling 107kb.
Is it possible to check exactly where MySQL Workbench is looking for workspaces?
Can I force it to open a workspace directly, or at least show me why it can't open a workspace? If that is not possible, can I somehow extract the SQL from the .scratch files? Thanks.
Should be easy to recover the sql from the scratch files which are just plain text files. The sql code is not encrypted. Also you can look in the Workbench log file (see Help menu) to see if there's an error message or similar for a specific file. Could be there's some file corruption. Running the file system checker on that disk also might help.
PS: in Windows you can use the clipboard in system dialogs like this one. Just press Ctrl+C while the dialog has the focus to copy the entire text, including the button captions, to the clipboard. That will hopefully give you the full error message.
Even though my desktop has crashed several times in the past 3 years (either power-related or system) this last time was the first time MySQL Workbench had issues with a workspace (apparently the 2 I had open at the time?). When I investigated why I discovered that all the .info and .scratch files in those workspaces were written with only NUL characters so no easy recovery of my tabs is possible. Grrr.
I will have to recover everything from scratch (haha) by going through the sql_history and possibly log folders and copy/paste as necessary back into the GUI.
So SQL Developer won't show the connections tab no matter what I do.
I've tried going through the "view" tab and clicking into the "connections" and I've also tried clicking the new button. I've also tried an uninstall/reinstall, but nothing.
It's probably something simple, but I'm fairly new to it, can anyone direct me or provide any advice?
Any help is really appreciated :)
You can go to the upper tab "WINDOW" and then click "Reset Windows to factory settings".
1.) Save your current SQL connection xml file located in windows 7/8/10: C:\Users\"youruseraccount"\AppData\Roaming\SQL Developer\systemXXXXX\o.jdeveloper.db.connection.xxxxxx
2.)Now delete your SQL Developer Folder and sqldeveloper folder located in: C:\Users\"youruseraccount"\AppData\Roaming\
3.)Now delete the main sqldeveloper folder containing the actual SQL developer application files.This would be located wherever you initially unzipped the SQLDeveloper download.
4.)Download the latest version of SQL Developer and unzip wherever you like.
5.)Launch SQL developer and specify your JDK location.
6.)Copy your connections xml file to your roaming SQL Developer directory here: C:\Users\"youruseraccount"\AppData\Roaming\SQL Developer\systemXXXXXX)\o.jdeveloper.db.connection.xxxxxx
7.)Launch SQL Developer and your DBA view should now be available after selecting view -> DBA
1 ) Select the Windows Menu
2 ) Choose the option Reset Windows to Factory Settings
3 ) Oracle SQL Developer automatically closed and reopened.
Search for the file - windowinglayoutDefault.xml and delete it, and restart SQL Developer.
This file should be present inside a system folder at
windowuserPath\AppData\Roaming\SQL Developer\
I had the similar issue with SQL Developer 4.2, one fine day all the connections pane on left vanished, tried couple options unsuccessfully.
Remedy is
1) Installation of newer version of SQL Developer to the folder of your choice with newer java JDK
2) Import the preference from previous version. DID the TRICK... Good Luck
Rajarao
For me, it worked in the following way:
I just deleted the folder where I had extracted the zip folder and then re-extracted it and then ran sqldeveloper.exe
I exported all my connection to a json file. Then imported the one disappeared and it worked.
This worked for me!!, No need of recreating the connections.
I am trying to install reinstall zencart setup again on the following link:-
http://hobbystii.ro
But when i click to start the setup it shows a blank page. I am not able to understand the problem. Can please anyone help.
For my confirmation i deleted the database cleaned everything and tried reinstallation but same error showing blank screen.
I suggest you rename the install directory "install" to start with; that is the original name if i remember correct. And try replacing the folder with original one from ZIP file.
However the best option would be to do a fresh install since your existing database will be wiped during an install either way. After doing so you can simply copy your theme files across or if you have customizations attempt copying the entire code from previous install across. Make sure to keep backups of everything and replace the configuration files for both admin and user side with that of the new one.
I'm attempting to into import oracle 11gR2 using the command line tool for SqlDeveloper 4.0. The ultimate reason is we are attempting to import a lot of freetext fields that need to preserve the exact formatting. CR LF, etc for legal reasons. End users need to edit these in Excel.
SQLLoader baulks at the CR LF's, You can achieve this in SqlDeveloper by switching the formatting to UTF-8 for import / export. We are now trying to build up some scripts after discovering how to do this in the command line runtime sdcli64... BUT there doesn't appear to be an option to import from a flat file or .xlsx in that utility??
Any pointers or are we missing an obvious parameter?
(we are using the latest version of SqlDeveloper we can find, 4.03)
Cheers,
Chris
New version of Oracle developer 4.1 was released as an Early adopter today. You can run the sdcli or sdcli64 command line version with the new parameters. This will import excel files as possible in the sqlDeveloper GUI and it will preserve the formatting using the new [-utility] switch.
You can then use the scripting tool/method of choice to build scripts to do all files in a directory, etc.
With new SQL Developer 4.1 you may import XLSX file (and other formats too) via command line:
Use sdcli utility import.
You will need a config XML file. To create one, start the import in the UI, configure the columns, etc, and at the last step click the button 'Save State'. It will create an XML file you may re-use in command line.
I'm using MAMP (osx) to test my website local.
Because I recently switched to a new Macbook I took a backup from my database with phpMyAdmin.
I did this by going to phpMyAdmin and click on the export tab and selected all the databases and saved the file to localhost.sql (8,9mb).
Now when I try to import that file (going to phpMyAdmin, selecting the import tab and then browsing to the localhost.sql file) it show me this error:
1046 - No database selected
How can I import all of my databases again into phpMyAdmin?
If you select "Custom" from the Export options radio buttons, then look down to the "Object creation options" area, check the box for Add CREATE DATABASE / USE statement. This should add the proper statements to your export. Perhaps this should be the default when exporting multiple databases, but at least that will enable you to move your data around.