Screenshot
Hello, I cannot rename or remove the table after imported the data :(
What I have tried:
RENAME TABLE 'collections.csv' to 'collections'
DROP TABLE 'collections.csv'
I tried another table which is doing fine.
After restarting the docker, I reran the command, which worked this time. Not sure if it is a bug 🤔
Related
I am going to use reusable mapping in odi 12c, but there is a problem. When ever I drag and drop a table into the environment, it gives me this error:
No object could be dropped on the diagram possibly because the chosen technologies in the "Create As" dialog were incorrect. Please, try again choosing a different technology.
I got confused and I do not know what is wrong because before that I was doing the same thing but suddenly this error pops out.
I was going to develop simple reusable mapping to save that for using in my other mapping.
I got the same error message. I couldn't drag and drop any of my tables - regardless of their source.
I did not find any solution except to delete my old mapping and create a new one.
Closing the ODI and launching again should help as a workaround for this error.
Use the command:
odi -clean -initialize
This will clear the cache and launch ODI and it should negate the error until next time.
I have a very basic PostgreSql table. Despite the simple table schema, I cannot query it via PgAdmin4.
The View Data option is unresponsive; Query Tool option becomes unresponsive after a few attempts in opening and closing the panel. When the Query Tool is eventually (somehow) launched, a trivial SQL statement like
SELECT * FROM test_table
will spin forever and never display.
The diagram above shows the exact same table, which is okay under PgAdmin3.
The table was created empty. Then added with a row. But it threw errors about not having a Primary Key. Which also threw errors when I tried to set a Primary Key. So I used TeamPostgreSql to set a Primary Key. So all is good under PgAdmin3 now. Hence I'm really curious about what's going on with PgAdmin4?
I'm running pgAdmin4 v3.0 and I've put localhost as host name.
I mean, left panel > servers > create > server and then connection tab > host name
I could not query tables, clicking on view/edit data > all rows had no results (nor error log entries).
After I changed server name from localhost to 127.0.0.1, all worked as expected!
I hope it helps, because I've lost so much time on this and could not find a proper answer.
I find a way to view query result on Data Output window using the "Reset Layout" command from File menu. Save your current work (query) before as it will kind of restart pgAdmin4. Tested with pgAdmin 2.1
1) First delete the log file to get rid of older logs
2) Start pgAdmin4.
3) Try to view data again
Can you check log file for any errors & paste it here?
Linux log location: ~/.pgadmin/pgadmin4.log
Windows log location:
C:\Users\YOUR_USERNAME\AppData\Roaming\pgAdmin\pgadmin4.log
Try naming your columns with lower case letters.
Or try with a blank query and write the SQL commands manually:
SELECT * FROM “test_table”
ORDER BY “Apple” ASC
I think this is a bug. The command the pgAdmin 4 is sending, does not contain the double quotes in the order command on the column name, and if you have upper case letters, SQL is going to convert them to lower case letters, thus not finding the sorting criteria.
I had a similar problem.
For me the Query Tool did render, however I could not see the Query Tool until after I expanded the view.
Then even after expanding I was not able to see the result of the query until I ran ( File -> Reset Layout ) as Guillaume Raymond suggest.
Before Expand
After Expand
After Running Reset Layout
I fixed this by opening the connection, changing just the connection name and saving the connection.
Based on other comments, I'd say there is likely some difference in the persisted format of the connection and they need to be resaved by the new version to work.
Warning: You may need to recreate connections.
This worked for me.
1.) Shutdown pgadmin4 3.1
2.) Delete folder: C:\Users\YOUR_USERNAME\AppData\Roaming\pgAdmin
Faced a similar issue where the problem was caused by Firefox, pgADmin 4. Launching pgAdmin in Chrome solved the issue.
This problem I experienced with the internet explorer browser where the query tool was not loading at all. It just kept on spinning with a circle. I solved this issue by using chrome browser.
When you launch pgadmin4 it launches in internet explorer by deafult. it has a key attached to it like
http://127.0.0.1:57756/?key=0371aabd-b4c7-4454-8234-b1234416d7e5e.
you can just paste the above url in the browser directly and the pgadmin4 will open
and query tool works in it. Or you cna use cmd and paste the belwo command and pgadmin4 will open as a standlone application rather tahn another tab in the browser and you cna use it like old pgadmin3.
C:\windows\system32>"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --app=http://127.0.0.1:57756/?key=0371aabd-b4c7-4454-8234-b1234416d7e5e
I had the same problem (version 4.18). Only the following worked for me:
Create a new server group (!) by right-clicking on "servers" in the left-hand navigation.
In this new group I created the desired connection to the database (with host name 127.0.0.1)
After that I could finally work with it
You can remove pgadmin4, then reinstall it. It worked for me. I used Ubuntu 18.04.
Here is my command on terminal:
sudo apt autoremove pgadmin4
sudo apt install pgadmin4 pgadmin4-apache2 -y
Suddenly SQL worksheet is not displaying in my SQL Developer. When I click on 'Open SQL Worksheet' or Alt+F10 nothing will appear.
I have tried many things such as: uninstalling SQL developer; cleaned the appData; changing java version; change SQL Developer version; and so on. But nothing has worked. Help?
Try to open Sql Developer as administrator. It's weird but works for me.
While any the software - SQLDeveloper got error or something worng.
You can try to
backup whole sqldeveloper directory from C:\Users\AppData\Roaming\
then delete it.
But remember to backup your customer infomation!
Or reference this SQLDeveloper not starting
Hope this can help.
I clear folder C:\Users\AppData\Roaming\SQL Developer\SqlHistory. It works for me.
For me, it was path problem. I changed path of temp and TMP in environment variable to C:\Users\____\Appdata\Local\Temp
Then worksheet showed up again. somehow I changed this path before, that was the reason for me.
I was able to solve this by :
Closing SQL developer
Deleting the file SqlHistory.xml that is located at C:\Users\AppData\Roaming\SQL Developer\. Alternatively, you can rename it to e.g SqlHistoryOLD.xml
Now when you open SQL developer and create a new SQL worksheet, it will work :)
Update
I've just found what's causing it but couldn't solve it :
When running the project, VS copies the SDF file to bin\Debug, therefore, any changes made to it, even if only refreshing the DB will cause it to be overwritten...
I've created a quick and dirty project to test SQL CE 4.0, designed a small table and added an Update button to save entered data. So far everything works, I close and reopen the application, data is loaded and shown in the DataGridView.
There is one issue however, whenever I make any changes in Server Explorer such as just refreshing the connection,
when I launch the application again, all the data I entered is gone.
Did I miss something ?
How I created the database :
From Data Sources I've added a new data source, created a new connection, created a new database, answered yes for copying it to my project and modifying the connection.
Then from Server Explorer I created a new table, added columns
Finally, I reconfigured my data source so it recreates the data set, data table and the adapter
Here is a fix for it :
Do not copy it locally to the project folder, there won't be two versions with one overwriting the other.
for whom using QTP(Quick Test Professional) do anyone of you face this issue on data table upon savin script on QC(Quality Center).
When you try to edit "DataTable" message box says that "locked cells cannot modified" displays.
kindly see the attached snapshot.
your help and support is highly appreciated.
Thanks,
Manaysah
I have found that the following procedure corrects this problem:
Open the test in QTP
Check it out
Right-click the datatable
Select File > Export…
Browse to the location where you want to save the export file
Enter a file name for the export file
Click Save
Right-click the datatable
Select File > Import
Browse to the location where you saved the export file
Select the export file
Click OK
Datatable should now be unlocked.
If you are using QC 10.0 to store/save your QTP 10.0 scripts ,then you can try following.
Verify what patch level your QC 10.o on if you are on patch 28 then you have to apply patch 29 on QC.
Defect ID: QCCR1J 24598
Problem: An automatic job runs every fifteen minutes that cleans the database of stale sessions and locks.
A regression prevents locks from being deleted if the Quality Center client was terminated abruptly.
This causes entities to remain locked even after the LOCK_TIMEOUT and the entities cannot be edited.
A workaround existed to physically delete the locked rows from the database