The previous DB2 Express-C versions were working fine over the years, but the basic commands not running on no cost Db2 Community Edition 11.5.5 (latest) .
after installing the Db2 Community Edition 11.5.5, when running the db2level command, it gives the error:
SQL1022C There is not enough memory available to process the command.
and below links didn't help:
https://www.ibm.com/support/pages/error-sql1022c-there-not-enough-memory-available-process-command-after-changing-hostname-db2-server
https://www.ibm.com/support/pages/running-db2level-db2-command-window-returning-sql1022c
Some my findings are:
db2set' not working - DBI1302E Invalid parameter detected.
'db2set -all' working - DB2_EXTSECURITY=YES
'db2level' - SQL1022C There is not enough memory available to process the command.
'db2start' not working - SQL1390C The environment variable DB2INSTANCE is not defined or is invalid.
DB2 icon not presented on taskbar
db2 get dbm cfg | find "SYSADM" - not working (no output)
db2 get dbm cfg - DB21018E A system error occurred. The command line processor could not continue processing.
db2 update dbm cfg using sysadm_group DB2ADMNS - DB21018E A system error occurred. The command line processor could not continue processing.
Followed the same recommended steps (for DB2 installation) as being following since DB2 9.7 version (on WIN 8.1 machine + RAM 8 GB).
My logged-in user is machine administrator
The supplied user is 'db2admin'
Now on the problem machine, OS is Windows 10 Pro + RAM 8 GB.
Ran the setup.exe after extracting the downloaded zip
From the DB2 Setup Launchpad > Install a Product > DB2 Version 11.5.5.0 Server Editions > Install Now > then installed with all default settings
DB2 setup installed successfully but DB2 commands not working as explained above
I had the same issue but after installing db2 with administrator privileges (starting setup.exe as an admin) the issues were gone and everything was set up as expected.
I have ubuntu version 18.04.3 running on virtual box.
I have been trying to install pintos on qemu, but when I run ./pintos run alarm-multiple my qemu is stuck on loading.
I am getting the following output:
**WARNING: Image format was not specified for '/tmp/5XpQ2ee16J.dsk' and probing guessed raw.
Automatically detecting the format is dangerous for raw images, write
operations on block 0 will be restricted.Specify the 'raw' format
explicitly to remove the restrictions.
qemu-system-x86_64: warning: TCG doesn't support requested feature:
CPUID.01H:ECX.vmx [bit 5]
PiLo hda1
Loading............
Kernel command line: run alarm-multiple
Pintos booting with**
Nothing is coming after pintos booting with
You are using an old version of pintos.
Use the latest version available here.
git://pintos-os.org/pintos-anon
I have once before mounted this same database, so I am confident that I have the correct credentials.
During the last session that I had it mounted I was experimenting with my queries, visuals etc. and the session all of a sudden crashed.
Then when I reloaded slamdata, the mount for my database was gone.
Obviously I then tried to remount the same database with the same credentials in order to continue my work. However when I did this I got an error:
There was a problem saving the mount: An unknown error ocurred: 500 ""
And then there is a never ending spin wheel that sits on the mount button. I can leave this pop up and go to the original screen, but nothing occurs. And then if I try to remount again the same error occurs.
I have verified that I can still access my db and collections using robomongo. So if anyone knows what this error message refers to please let me know! I have yet to find its meaning online.
Note: I have already tried uninstalling and reinstalling/ restarted my computer.
In SlamData 4.2.1 this bug has been identified and fixed an issue with the MongoDB connecter that would corrupt the metastore if you use the _id field in a query. The fix is available in the SlamData 4.2.2 release soon
Below is the fix:
Delete the current metastore. Below is the location of this file for each supported operating system:
Mac OS:
$HOME/Library/Application Support/quasar/quasar-metastore.db.mv.db
Microsoft Windows:
%HOMEDIR%\AppData\Local\quasar\quasar-metastore.db.mv.db
Linux (various vendors):
$HOME/.config/quasar/quasar-metastore.db.mv.db
Open a terminal and switch to the location that you stored SlamData into. You should find a quasar-web.jar file in the following location based on your installed operating system based on default installation paths:
Mac OS:
/Applications/SlamData 4.2.1.app/Contents/java/app/quasar-web.jar
Microsoft Windows:
C:\Program Files (x86)\slamdata 4.2.1\quasar-web.jar
Linux (various vendors):
$HOME/SlamData 4.2.1/quasar-web.jar
Run the following command in a terminal:
java -jar quasar-web.jar initUpdateMetaStore
This will rebuild your metastore. Once complete it will return you to your operating system prompt.
Rerun the SlamData application as you normally would
Remount your database
At this point in time you can access your saved workspaces.
NOTE: You will not want to open the workspace you were using that caused this issue as it will cause the same problem.
Once upon a time I had a Postgres database that worked with pgAdmin. I have a webservice running on a WildFly server that made connections to the DB and everything worked fine.
After a while(a few months) I have tried to open pgAdmin again and it stuck on the loading...
I remove postgres and pgAdmin using Revo Uninstall, then installed postgres 9.6 and opened pgAdmin and it stays in the loading screen forever.
Can anyone help me ? [Using postgres 9.6 with pgAdmin v1.3],
On Event Viewer I saw the following error in pgAdmin :
Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x580f31f6
Faulting module name: MSVCP120.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000135
Fault offset: 0x00000000000ecdd0
Faulting process id: 0x1de4
Faulting application start time: 0x01d2a7d1566324ba
Faulting application path: C:\Program Files\PostgreSQL\9.6\pgAdmin 4\bin\pgAdmin4.exe
Faulting module path: MSVCP120.dll
Report Id: 984dd9d8-13c4-11e7-832d-5ce0c535006f
Faulting package full name:
Faulting package-relative application ID:
I had the same problem and I resolved it following the steps on link
https://www.pgadmin.org/faq/#12
When I launch pgAdmin 4 v4.28 or later on Windows, the loading page
never closes. Why? pgAdmin 4 v4.28 includes additional security
features, one of which is intended to prevent security issues caused
by Content Sniffing.
Unfortunately some Windows systems are mis-configured such that this
causes Javascripts used by pgAdmin to fail to load. Opening the
developer tools on your browser will show an error similar to this:
Refused to execute script from
'http://127.0.0.1:57313/static/vendor/require/require.min.js?ver=42800'
because its MIME type ('text/plain') is not executable, and strict
MIME type checking is enabled.
(index):39 Uncaught ReferenceError: require is not defined at
(index):39 This will occur when the value of the registry key at
HKEY_CLASSES_ROOT.js\Content Type is set to text/plain. To resolve
the issue, use the Registry Editor and reset the value of
HKEY_CLASSES_ROOT.js\Content Type to: text/javascript
Finally, restart the pgAdmin server.
I just had this problem on macOS so I went to Terminal and typed ps aux | grep -i pgadmin and made a note of the process id (second column from the left). Then I killed that process with kill -s TERM <process id>. You can also use the simpler form with killall pgAdmin4. Then I was able to start "pgAdmin 4" from the Applications directory.
I just had the same issue on a Windows 7, 64bit machine, DBA told me to "upgrade" to pgAdmin 3 (latest build) and it works.
as per Abrahim's suggestion, it worked fine for me in the environment. Windows 10, pgAdmin 4.28
"value of the registry key at HKEY_CLASSES_ROOT.js\Content Type is set to text/plain. To resolve the issue, use the Registry Editor and reset the value of HKEY_CLASSES_ROOT.js\Content Type to: text/javascript "
I had this issue on Mac. I resolved it by:
Closing the instance of PgAdmin 3 AND PgAdmin4 (I had both open)
System Preferences -> Security & Privacy -> Allow apps downloaded from: Anywhere
Reopen PgAdmin4
I faced the same issue (on window server)
My solution is just open task manager and finds out pg_ctl then just end that task and reopen pgadmin again. It will work!in case it still doesn't work just try to terminate mysql.exe too.
For me, the postgresql server was set to start manual and it was not running in services, i started the service and it worked
Download pgAdmin from its website and install it separately from postgres.(Its works for me on Windows 10 - 64 Bit)
Response from pgadmin-support mail group:
Please try one of the Mac/Windows test builds at https://developer.pgadmin.org/~dpage/.
I would strongly advise doing a complete uninstall before installing, to ensure no old, unused files are left behind.
I had a similar issue and was able to fix it by re-installing the latest Java JDK x64 8 at http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
I found a solution here pgAdmin 4 v3.1 How can I use another browser? (Win 7)
My pgadmin4 stopped working in firefox but it works in chrome. Now i use this configuration to open pgadmin 4 using chrome. It is interesting that pgadmin4 now open in his own window.
I think this is the correct way to use pgadmin4.
Go to Services and restart PostgreSQL Server.
I'm trying to get a dump to debug some memory issues in ASP.NET processes (Windows 2003 R2 SP2 x64):
adplus -hang -o f:\dumps -pn w3wp.exe -quiet
There are nine w3wp.exe (all from different websites). Everytime I run adplus as above some of the dumps fail with this error:
WriteFullMemory.Memory.Read(0x100ea0000, 0x10000) failed 0x80070005, ABORT.
Dump creation failed, Win32 error 0n5
"Access is denied."
The failure seems to be random (or I should say I can't find the reasons), i.e. sometimes some processes dump fine and sometimes they fail with this error. Things I checked:
I do have full administration permissions
There is plenty space on the target hard drive
I disabled pinging and failure protection on IIS to prevent IIS from killing the processes while adplus is dumping.
Anything else I should check? Has anyone else run into this issue? Adplus version is 7.01.002 (02/27/2009) (downloaded a couple of days ago from the latest SDK)
This is because of inaccessible memory read failure. To avoid this you could use something like cdb/windbg and use .dump /mA command to generate full memory dump.
The .dump /mA same as .dump /ma except that it will ignore inaccessible memory read failure and continue minidump generation.
.dump options
The /mA option is equivalent to /ma
except that it ignores any failure to
read inaccessable memory and continues
generating the minidump.
HTH
It wouldn't matter if you are a member of admin you would still need to elevate privileges.
ADPlus needs to be run from a command prompt running under a local administrator account with elevated privileges. If you fail to do this, the dump file may not be created.