Is it possible to install OQGRAPH on a AWS RDS instance? If yes how?
Reading the installation guide: https://mariadb.com/kb/en/mariadb/installing-oqgraph/ installing OQGRAPH requires admin-access to the server - which clearly RDS does not grant.
Any ideas on how to install it anyways?
Obviously if i just run
INSTALL SONAME 'ha_oqgraph';
I do get the following Error-Message:
Can't open shared library
'/rdsdbbin/mariadb-10.0.24.R1/lib/plugin/ha_oqgraph.so' (errno: 2,
cannot open shared object file: No such file or directory)
Unfortunately it is currently not available.
According to the AWS RDS documentation the only plugin currently available for the RDS MariaDB is the Audit Plugin, which was announced only few months back.
If you still want to use MariaDB on AWS, but you are not forced to use RDS - you can have your own Instance of MariaDB (using the available Community MariaDB AMIs, or one of the AMIs provided by MariaDB, which available for CentOS, Debian and Ubuntu). This way you have full access to your server, so you will not have any problem with installing new plugins.
Related
I'm trying to install SQL developer (19.4.0), but when I create my first DB on windows 10, it shows me: error i/o the network adapter could not establish the connection.
I looked something on google, but every solution needs to access to app folder (C:/app/Username/...)
I downloaded the zip file from the official site and it doesn't install anything, just unzip and I can run SQL developer. I don't have any listener.ora or tnslistener.ora file.
I downloaded the version without java because I've already installed jdk 1.8
LINK: https://www.oracle.com/tools/downloads/sqldev-downloads.html
What can I do?
I am trying to install impala in a docker container(using MAPR documentstion).In this docker I am running only Impala service and remaining hive,maprfs services will be running on physical node.When starting impala-server(impala daemon) I am getting wearied errors.I just wanted to know whether this kind of installation is possible or not.
Thanks for Help!!
It is possible, but it depends on your Impala and MapR version. Impala 2.2.0 is supported on MapR 5.x. Impala 2.5.0 is supported on MapR 5.1 and later. Check enter link description here before proceeding.
I am currently using hadoop 1.0.3 version. I recently installed Apache Hive to run with it. I was running the select * query which gave me an NoSuchMethodError: org.apache.hadoop.mapred.JobConf.unset
I further found out its a compatibility issue with my current version of hadoop and requires me to upgrade to 1.2 or later.
I am fairly new to hadoop and would like to upgrade my current version to 1.2 or later. How do I go about doing the same.
I could not find any resources online to do so.
Thanks.
Just download hadoop 1.2.x from here and do necessary configuration changes in your new hadoop. Change HADOOP_HOME to point to your new hadoop folder.
NOTE: Change all the environmental variables (including .bashrc) to point to your new hadoop.
I am new in postgreSQL database , I recently found that postgreSQL support SQL Job by pgAgent. I am using windows XP operating system.
I searched lots about pgAgent on Google and trying to configure pgAgent on machine.
Download pgAgent package in which I found pgagent.sql file after executing this file JOB(0) icon is appear on my pgAdmin III object panel. like following image.
But I am facing problem to register pgAgent service. As per postgres sql documentation following is next steps to register services but I am fail to do this. or don't know how to configure pgAgent service.
Following step from postgre sql documentaion :
The service may be quite simply installed from the command line as follows:
"C:\Program Files\pgAdmin III\pgAgent" INSTALL pgAgent -u postgres -p secret hostaddr=127.0.0.1 dbname=pgadmin user=postgres
but I tried lot to do this, please help in how to register pgAgent service with Windows XP.
reference link of postgre sql : http://www.pgadmin.org/docs/1.6/pgagent-install.html
Please help in this , Thanks in Advance !
PgAgent is probably not installed
The pgAgent download page says:
pgAgent is a job scheduler for PostgreSQL which may be managed using
pgAdmin. Prior to pgAdmin v1.9, pgAgent shipped as part of pgAdmin.
From pgAdmin v1.9 onwards, pgAgent is shipped as a separate
application.
And then it provides a download link to http://www.postgresql.org/ftp/pgadmin3/release/pgagent/
But the problem is there's only source code there. There are also SQL files in the tarball but they're useless without pgagent.exe.
How to install it
Apparently the correct way to install a pre-compiled pgAgent is with the Stack Builder installer that also happens to be the primary installation method on Windows for the PostgreSQL server itself. That's what is suggested on the official download page:
http://www.postgresql.org/download/windows/
If you have already installed PostgreSQL for Windows with this method, the installer is available under the name Application Stack Builder in the PostgreSQL 9.2 folder in Windows Start Menu.
StackBuilder will normally recognize your installed PostgreSQL version(s), and suggest to install among various programs pgAgent in the Add-ons, tools and utilities category.
Once you check pgAgent and continue with the installation, it will download it and launch its setup. The setup phase includes runnning the necessary SQL statements and installing the PostgreSQL scheduling Agent - pgAgent windows service. If this step is successful, there is nothing else to do, the functionality will be available in pgAdmin for creating jobs.
What's misleading in the docs
The latest pgAdmin docs at http://www.pgadmin.org/docs/1.16/pgagent-install.html has a Service installation on Windows chapter that says:
The service may be quite simply installed from the command line as
follows (adjusting the path as required):
"C:\Program Files\pgAdmin III\pgAgent" INSTALL pgAgent -u postgres -p
secret hostaddr=127.0.0.1 dbname=postgres user=postgres
However in the majority of cases this is not going to be of help because either:
pgAgent install is done by pgAgent setup as launched by StackBuilder and this step is not necessary.
or you have got pgAdmin alone and pgagent.exe will not be installed so this step is not possible.
pgAdmin will be successfully installed after downloading the compressed file from
https://www.pgadmin.org/download/pgagent-source-code/
there inside, you will find the file "sql\pgagent.sql"
Toss the content of this file into the Query Tool and run it. That will install pgAgent. Refresh your database connection to see the result. The tab pgAgent Jobs should have been created at the root level for your connection.
There is no need of using the INSTALL command from your command line.
I faced the same problem. I was able to get pgagent working by downloading and executing the stand-alone installation file pgagent-3.4.0-4-windows.exe from here: http://sbp.enterprisedb.com/getfile.jsp?fileid=11842
I'm using an Amazon Linux EC2 instance and am wondering What AWS CLI tools are installed by default on it.
Is it just the EC2 CLI API tools? How can one tell? Also where is the preferred single location on an EC2 instance to install each of the various CLI tools (RDS, cloudwatch, etc.) if they aren't installed already?
If you might answer each of these questions I'd be greatly appreciative.
For the Amazon Linux AMI 2012.03, here's the list of installed packages.
To answer your question, here's the list of AWS tools:
aws-amitools-ec2-1.4.0.7
aws-apitools-as-1.0.61.0
aws-apitools-cfn-1.0.9
aws-apitools-common-1.1.0
aws-apitools-ec2-1.5.5.0
aws-apitools-elb-1.0.17.0
aws-apitools-iam-1.5.0
aws-apitools-mon-1.0.12.1
aws-apitools-rds-1.8.002
aws-cfn-bootstrap-1.1
aws-scripts-ses-2012.05.15
According to Amazon Linux AMI Basics:
to allow the installation of multiple versions of the API and AMI
tools, we have placed symlinks to the desired versions of these tools
in /opt/aws, as described here:
/opt/aws/bin—Symlink farm to /bin directories in each of the installed
tools directories.
/opt/aws/{apitools|amitools}—Products are installed in directories of
the form [name]-version and symlink [name] attached to the most
recently installed version.
/opt/aws/{apitools|amitools}/[name]/environment.sh—Used by
/etc/profile.d/aws-apitools-common.sh to set product-specific
environment variables (EC2_HOME, etc.).
There are no fixed standards or set rules about what is installed on AMIs in general.
Different Linux distros and different AMI publishers each decide what they want to put in their image and where.
In fact, an AMI doesn't even need to give you command line access to your instance through ssh if they don't want to.
If you have a specific AMI series in mind (Amazon Linux, Ubuntu 12.04 LTS from Canonical, CentOS 5.5 from RightScale) then update your question to include this.
For the record: the "minimal" variant of Amazon Linux does not have the full suite of CLI tools. Doing a yum install ec2-tools didn't get me what I wanted, so I just created a new instance with the non-minimal AMI. I also found that this minimal Linux isn't any more space-efficient, at least as originally configured; the additional 6 GB that would go to the root partition is left unallocated.