I am using PostgreSQL 13 Beta 3 on (windows.8/*64bit). I want to add timescaledb extension. My "postgresql.conf" directory is correct but every time i try to install the extension, I get a message which is attached.
I had also changed Environment Address to "C:\Program Files\PostgreSQL\13\bin" [The address of pg_config.exe", but nothing changed. Is there a possibility that i have to use from postgreSQL V.12 as mentioned in the installation instruction? enter image description here
Thank you in advance for your help and guide
You cannot to do it. Timescale doesn't support Postgres 13 yet. Postgres 13 was not releases yet - there only test releases are available.
PostgreSQL extensions should be compiled for specific Postgres major version. So you cannot to use timescale for Postgres 12 or Postgres 11 for Postgres 13.
It's not ready yet. It's expected on the upcoming TimescaleDB v2.0.1. Read more at their release notes: https://docs.timescale.com/latest/release-notes.
Related
This question already has answers here:
Oracle 12c docker setup on Apple M1
(6 answers)
Closed 10 months ago.
I was recently trying to create a docker container and connect it with my SQLDeveloper but I started facing some strange issues.
I downloaded the docker image using below pull request:
docker pull store/oracle/database-enterprise:12.2.0.1-slim
then I started the container from my docker-desktop using port 1521. The container started with a warning.
terminal message:
docker run -d -it -p 1521:1521 --name oracle store/oracle/database-enterprise:12.2.0.1-slim
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
5ea14c118397ce7ef2880786ac1fac061e8c92f9b09070edffe365653dcc03af
Now when I try connect to db using below command :
docker exec -it 5ea14c118397 bash -c "source /home/oracle/.bashrc; sqlplus /nolog"
SQL> connect sys as sysdba;
Enter password:
ERROR:
ORA-12547: TNS:lost contact
it shows this message, PASSWORD I USE IS Oradoc_db1.
Now after seeing some suggestions I tried using the below command for connecting to sqlplus:
docker exec -it f888fa9d0247 bash -c "source /home/oracle/.bashrc; sqlplus / as sysdba"
SQL*Plus: Release 12.2.0.1.0 Production on Mon Sep 6 06:15:58 2021
Copyright (c) 1982, 2016, Oracle. All rights reserved.
ERROR:
ORA-12547: TNS:lost contact
I also tried changing permissions of oracle file in $ORACLE_HOME as well for execution permissions as well but it didn't work.
Please help me out as I am stuck and don't know what to do.
There are two issues here:
Oracle Database is not supported on ARM processors, only Intel. See here: https://github.com/oracle/docker-images/issues/1814
Oracle Database Docker images are only supported with Oracle Linux 7 or Red Hat Enterprise Linux 7 as the host OS. See here: https://github.com/oracle/docker-images/tree/main/OracleDatabase/SingleInstance
Oracle Database ... is supported for Oracle Linux 7 and Red Hat Enterprise Linux (RHEL) 7. For more details please see My Oracle Support note: Oracle Support for Database Running on Docker (Doc ID 2216342.1)
The referenced My Oracle Support Doc ID goes on to say that the database binaries in their Docker image are built specifically for Oracle Linux hosts, and will also work on Red Hat. That's it.
Linux being what it is (flexible), lots of people have gotten the images to run on other flavors like Ubuntu with a bit of creativity, but only on x86 processors and even then the results are not guaranteed by Oracle: you won't be able to get support or practical advice when (and it's always when, not if in IT) things don't work as expected. You might not even be able to tell when things aren't working as they should. This is a case where creativity is not particularly rewarded; if you want it to work and get meaningful help, my advice is to use the supported hardware architecture and operating system version. Anything else is a complete gamble.
I think i will answer my own question and its similar to the accepted answer.
As the oracle db is very large in size and is very complex to handle and maintain on different systems like mac and all, therefore, its recommended to use the docker mentioned system configurations for running the docker container on your system.
I have used MariaDB and have also tried MongoDB (NoSQL) instead of using oracle as these are very much light and don't need strict configurations to run and they ran in no time. I could easily connect both of them with SQLDeveloper(MariaDB) and MongoDB compass(MongoDB).
There are some custom oracle light weight versions as well but they are not very full proof to work on your system.
I'm trying to simply setup an Open Source Greenplum instance and have been hitting the same issue regarding GPFDIST for days! Simply put, I do a full installation from scratch on CentOS 7.6 (can provide further details regarding setup if needed) installing OS GPDB software version 5.18 with GPORCA disabled. Full command for the compile is:
./configure --prefix=/usr/local/gpdb --with-perl --with-python --with-libxml --with-gssapi --with-includes=/usr/local/gpdb/include --with-libs=/usr/local/gpdb/lib --disable-orca
This compiles successfully, and the following make/make install commands too complete without issue. The initialisation of the Greenplum database itself also succeeds, and I can then go into a database and create tables, insert data and run queries like normal.
But if I try to select from an external table, such as the following:
create external table test_external_table
(testing smallint
)
location ('gpfdist://mdw:8080/test_data.csv')
format 'csv' (header delimiter '|')
;
with GPFDIST run as follows:
gpfdist -d /home/gpadmin/test/ -p 8080 -l /home/gpadmin/greenplum/logs/gpfdist_log 2>&1 &
then I get two errors; one from the external table, and one from GPFDIST. These are as follows:
External Table Returns:
ERROR: connection with gpfdist failed for gpfdist://mdw:8080/test_data.csv. effective url: http://127.0.0.1:8080/test_data.csv. error code = 104 (Connection reset by peer) (seg0 slice1 127.0.0.1:6000 pid=27962)
GPFDIST Returns:
[1]+ Segmentation fault gpfdist -d /home/gpadmin/test -p 8080 -l /home/gpadmin/greenplum/logs/gpfdist_log 2>&1
I have removed everything that isn't on the OS GPDB GitHub installation guide (for a 'bare-bones' setup), so I don't think that is causing the issue. I have tried everything to do with the hostname and network firewall, and it's all perfect as far as I can see.
I have also downloaded the same version of GPDB (5.18) from Pivotal and installed that version on the same instance simultaneously, and GPFDIST works perfectly fine.
I have also tried OS GPDB 5.17, 6 beta and 7 beta, and I get the same issue for all of them.
Any ideas at all on what might be causing this is VERY much appreciated, as I'm slowly going insane trying to figure this out now.
Thank you very much in advance for any help.
-- Edit --
Okay.. Having nearly chewed my own arm off in sheer frustration at trying to install debuginfo stuff on CentOS 7, I've finally generated a core dump with gdb. I then run:
gdb -c core_dump.<pid>
and get the following output:
Core was generated by `gpfdist -d /home/gpadmin/test -p 8080 -l /home/gpadmin/greenplum/logs/gpfdist_log'.
Program terminated with signal 11, Segmentation fault.
#0 0x00007f4f2c07bdff in ?? ()
But I have absolutely no idea what that means... Totally honest, I'm a little over my head with this now and really am stuck on how to proceed.
The connection reset by peer only indicates that the other end of the socket had dropped (...in this case, gpfdist because it crashed out).
Setup your gpfdist and try a wget to a hosted file adding:
--header='X-GP-PROTO:0'
You will need to add the header to avoid having the request rejected.
Are you able to retrieve a file there? Or does that also crash out?
If that crashes out, it's nothing to do with the database - and you will likely need a core dump to determine what the segfault is about (r/w permissions, memory, ...).
I've finally managed to solve this issue. Should anyone come looking with a similar problem, make sure you are installing Libevent version 1.4[.15], and nothing above that.
I had 2.2.0 installed, and whilst Greenplum sees this as fine, it actually doesn't work for it. Unfortunately, I did have to do an entire system installation from scratch to seemingly get it to work, as just installing Libevent 1.4 on the old system with Greenplum already compiled did not work for me.
I have an old version of greenplum and I would like to upgrade to version 5.0.0 since it has been released. https://github.com/greenplum-db/gpdb/releases/tag/5.0.0.
I have a huge machine, and I can not simply have an equivalent one. So I would like to know how can I run both version on the same machine. I have seen for example gpseginstall distribute binaries to the /usr/local/gpdb which is already there for the old version.
Regards
I have run multiple versions in parallel on a single node system.
You need to set your config file you use for the gpinitsystem for different segment/mirror directories, master port, starting port, etc..
You will also need two different OS profiles to source, so when you log as gpadmin you can source your 4.3 or 5.0 paths ($GPHOME, $MASTER_DATA_DIRECTORY) for gpstart, gpstop, psql, etc..
Hope this makes sense... I haven't tried it on a multi node system, but the setup should be the same
i.e.
GPDB 4.3
ARRAY_NAME="GPDB"
MACHINE_LIST_FILE=./hostsfile
SEG_PREFIX=seg
PORT_BASE=40000
declare -a DATA_DIRECTORY=(/gpsegment4 /gpsegment4 /gpsegment4 /gpsegment4)
MASTER_HOSTNAME=mdw
MASTER_DIRECTORY=/gpmaster4
MASTER_PORT=5432
TRUSTED_SHELL=ssh
CHECK_POINT_SEGMENTS=8
ENCODING=UNICODE
DATABASE_NAME=gpadmin
#MIRROR_PORT_BASE=50000
REPLICATION_PORT_BASE=41000
#MIRROR_REPLICATION_PORT_BASE=51000
#declare -a MIRROR_DATA_DIRECTORY=(/mirror4 /mirror4 /mirror4 /mirror4)
GPDB 5.0
ARRAY_NAME="GPDB"
MACHINE_LIST_FILE=./hostsfile
SEG_PREFIX=seg
PORT_BASE=60000
declare -a DATA_DIRECTORY=(/gpsegment5 /gpsegment5 /gpsegment5 /gpsegment5)
MASTER_HOSTNAME=mdw
MASTER_DIRECTORY=/gpmaster5
MASTER_PORT=7432
TRUSTED_SHELL=ssh
CHECK_POINT_SEGMENTS=8
ENCODING=UNICODE
DATABASE_NAME=gpadmin
#MIRROR_PORT_BASE=70000
REPLICATION_PORT_BASE=61000
#MIRROR_REPLICATION_PORT_BASE=71000
#declare -a MIRROR_DATA_DIRECTORY=(/mirror5 /mirror5 /mirror5 /mirror5)
I have seen where you can have different versions installed, then change the greenplum-db link to point to the one you want to run. That link is referenced when you enter gpstart. Not sure how you could have two different versions running at the same time on the same machine.
If your goal is to do upgrade dry runs and test on the new release, another alternative could be to deploy a Greenplum cluster using Microsoft Azure. This would deploy the latest version (5.0).
Sounds like you know how to build your own greenplum so you could delete that 5.0 install then install the version you are currently using, then practice the upgrade/migration as well as just kick the tires of 5.0.
You could also easily have side by side systems in Azure; one running your current release and the other running 5.0.
The smallest cluster you can deploy is 1 master and 1 segment which could be adequate depending on your requirements.
Hope this helps
I tried running cockroach --v and got an unknown flag error. What’s the command to find out which version of Cockroach I’m running?
cockroach version returns the version of CockroachDB available from the command line. However, it's important to note that you can upgrade the binary in your path, but the actual cockroach service running on the server can be older.
To upgrade the server, you'll need to restart cockroach (cockroach quit then cockroach start using the newer binary). If you’re doing this in production, you can take the nodes offline one by one without compromising your availability (assuming you’re running a load balanced cluster and aren’t treating a single node as the only target of your client).
"cockroach version" will give you the executable version (I would say). If you need something from the database itself, you could run the following query:
select version();
It looks like this:
$> /bin/cockroach sql <connection strings> --database=postgres --execute "select version();"
version
--------------------------------------------------------------------------------------------
CockroachDB CCL v21.1.6 (x86_64-unknown-linux-gnu, built 2021/07/20 15:30:39, go1.15.11)
(1 row)
Time: 2ms
$>
This works in both CockroachDB and PostgreSQL.
I hope this helps... ^_^
When I would to upgrade from Sonar 3.2 to Sonarqube 3.6.2. the upgrades fails
Int the log file I read the folowing line:
Fail to execute database migration: org.sonar.server.db.migrations.ConvertViolationsToIssues
I use a MSSQL database, I read that someone got exactly the same error when he wanted to upgrade using an Oracle 10g database. I read that this problem will be solved in 3.7. Is this also applying to my problem? When 3.7 will be realeased?
With kind regards.
Your issue indeed looks like 2 other ones listed on stackoverflow:
Sonar-Upgrade from 3.5.1 to 3.6.2 failed
upgrade from sonarqube 3.5.1 to 3.6.2 fails on migration of postgres db
(would need more log to be sure, but I'm almost 100% sure)
So indeed, it will be fixed with SONAR-4542 that will be shipped with SonarQube 3.7, expected in a couple of days from now (around August 9th).