Greenplum 4.3.14.0 crash - greenplum

We are using Greenplum 4.3.14.0 in one of our projects and recently have experienced a crash.
I found information similar to our case but not exactly:
https://discuss.pivotal.io/hc/en-us/articles/225773448-Greenplum-Postmaster-Resets-with-Error-PID-terminated-by-signal-6-Aborted-
May be you can tell us something about cause of this crash.
Data from log (this part of log repeated many times):
2018-05-26 18:15:01.607440 MSK,,,p2561,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","3rd party error log:
addr2line: /usr/local/greenplum-db/./lib/libz.so.1: no version information available (required by /lib64/libbfd-2.25.1-32.base.el7_4.1.so)",,,,,,,,"SysLoggerMain","syslogger.c",550,
2018-05-26 18:15:01.673235 MSK,"gpadmin","prod-ofd",p6611,th1921165184,"10.8.196.68","53568",2018-05-24 10:20:03 MSK,0,con1520839,cmd380300,seg-1,,,,sx1,"FATAL","XX000","reached limit of 4294967295 global transactions per start (cdbtm.c:3023)",,,,,,,0,,"cdbtm.c",3023,"Stack trace:
1 0xb05a4e postgres errstart (elog.c:502)
2 0xcc64a2 postgres createDtx (cdbtm.c:3022)
3 0x5433df postgres StartTransaction (xact.c:3043)
4 0x543a75 postgres StartTransactionCommand (xact.c:4354)
5 0x99978e postgres PostgresMain (postgres.c:3155)
6 0x8f422e postgres <symbol not found> (postmaster.c:6673)
7 0x8f6ed0 postgres PostmasterMain (postmaster.c:7604)
8 0x7f81bf postgres main (main.c:206)
9 0x7fd26e111c05 libc.so.6 __libc_start_main + 0xf5
10 0x4bdf59 postgres <symbol not found> + 0x4bdf59
"
2018-05-26 18:15:01.673664 MSK,,,p2561,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","Retrying emails now...",,,,,,,,"send_alert_via_email","sendalert.c",556,
2018-05-26 18:15:01.674872 MSK,,,p2561,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","could not connect to SMTP server","couldn't connect to host",,,,,,,"send_alert_via_email","sendalert.c",720,
2018-05-26 18:15:01.678701 MSK,,,p2561,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","3rd party error log:
addr2line: /usr/local/greenplum-db/./lib/libz.so.1: no version information available (required by /lib64/libbfd-2.25.1-32.base.el7_4.1.so)",,,,,,,,"SysLoggerMain","syslogger.c",550,
2018-05-26 18:15:01.749374 MSK,"gpadmin","prod-ofd",p6611,th1921165184,"10.8.196.68","53568",2018-05-24 10:20:03 MSK,0,con1520839,cmd380300,seg-1,,,,sx1,"PANIC","XX000","Waiting on lock already held! (lwlock.c:557)",,,,,,,0,,"lwlock.c",557,"Stack trace:
1 0xb01852 postgres <symbol not found> (elog.c:502)
2 0xb03868 postgres elog_finish (elog.c:1446)
3 0x980cd6 postgres LWLockAcquire (lwlock.c:557)
4 0x95f967 postgres ProcArrayRemove (procarray.c:181)
5 0x95b9cd postgres proc_exit (ipc.c:254)
6 0xb01cff postgres errfinish (elog.c:674)
7 0xcc656a postgres createDtx (cdbtm.c:3022)
8 0x5433df postgres StartTransaction (xact.c:3043)
9 0x543a75 postgres StartTransactionCommand (xact.c:4354)
10 0x99978e postgres PostgresMain (postgres.c:3155)
11 0x8f422e postgres <symbol not found> (postmaster.c:6673)
12 0x8f6ed0 postgres PostmasterMain (postmaster.c:7604)
13 0x7f81bf postgres main (main.c:206)
14 0x7fd26e111c05 libc.so.6 __libc_start_main + 0xf5
15 0x4bdf59 postgres <symbol not found> + 0x4bdf59
"
2018-05-26 18:15:02.752408 MSK,,,p2561,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","could not connect to SMTP server","couldn't connect to host",,,,,,,"send_alert_via_email","sendalert.c",720,
2018-05-26 18:15:02.753379 MSK,,,p2560,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","server process (PID 6611) was terminated by signal 6: Aborted",,,,,,,0,,"postmaster.c",5894,
2018-05-26 18:15:02.753414 MSK,,,p2560,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","terminating any other active server processes",,,,,,,0,,"postmaster.c",5581,
2018-05-26 18:15:02.753429 MSK,,,p2560,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","seqserver process (PID 2572) exited with exit code 2",,,,,,,0,,"postmaster.c",5872,
2018-05-26 18:15:02.753459 MSK,"gpadmin","prod-ofd",p485,th1921165184,"10.8.196.68","51043",2018-05-26 18:15:01 MSK,0,,,seg-1,,,,,"FATAL","57P03","the database system is in recovery mode",,,,,,,0,,"postmaster.c",2966,
Then many various messages that db try to recover.
Then
2018-05-26 18:15:04.017036 MSK,,,p2560,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","PostgreSQL 8.2.15 (Greenplum Database 4.3.14.0 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on May 25 2017 07:17:30",,,,,,,0,,"postmaster.c",4618,
2018-05-26 18:15:04.017070 MSK,,,p2560,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","database system is ready to accept connections","PostgreSQL 8.2.15 (Greenplum Database 4.3.14.0 build 1) on x86_64-unknown-linux-gnu, compiled by GCC gcc (GCC) 4.4.2 compiled on May 25 2017 07:17:30",,,,,,0,,"postmaster.c",4624,
And again
2018-05-26 18:15:05.078777 MSK,,,p2561,th1921165184,,,,0,,,seg-1,,,,,"LOG","00000","3rd party error log:
addr2line: /usr/local/greenplum-db/./lib/libz.so.1: no version information available (required by /lib64/libbfd-2.25.1-32.base.el7_4.1.so)",,,,,,,,"SysLoggerMain","syslogger.c",550,
2018-05-26 18:15:05.147311 MSK,"gpadmin","prod-ofd",p1914,th1921165184,"10.8.196.92","54613",2018-05-26 18:15:04 MSK,0,con1564021,,seg-1,,,,sx1,"FATAL","XX000","reached limit of 4294967295 global transactions per start (cdbtm.c:3023)",,,,,,"SHOW TRANSACTION ISOLATION LEVEL",0,,"cdbtm.c",3023,"Stack trace:
1 0xb05a4e postgres errstart (elog.c:502)
2 0xcc64a2 postgres createDtx (cdbtm.c:3022)
3 0x5433df postgres StartTransaction (xact.c:3043)
4 0x543a75 postgres StartTransactionCommand (xact.c:4354)
5 0x998d15 postgres PostgresMain (postgres.c:3155)
6 0x8f422e postgres <symbol not found> (postmaster.c:6673)
7 0x8f6ed0 postgres PostmasterMain (postmaster.c:7604)
8 0x7f81bf postgres main (main.c:206)
9 0x7fd26e111c05 libc.so.6 __libc_start_main + 0xf5
10 0x4bdf59 postgres <symbol not found> + 0x4bdf59
"
Infinite cycle.
After killing all db processes by command
gpadmin#gp-master$ gpssh -f /usr/local/greenplum-db/hostfile_allhosts -e "pkill -9 postgres"
and restarting - db started work properly again.
Thanks in advance.


FATAL","XX000","reached limit of 4294967295 global transactions per start (cdbtm.c:3023)",,,
This error suggests that Vacuum full is required on your DB'S catalog tables and users tables.

Related

Dronekit-sitl fails to bind on default port 5760

I have dronekit-sitl installed in a python3 virtual environment on my Windows 10 machine and have used it before by running dronekit-sitl copter with no issues. However, as of today I am running across what seems to be a permission issue when trying to execute the ArduCopter sitl.
$ dronekit-sitl copter
os: win, apm: copter, release: stable
SITL already Downloaded and Extracted.
Ready to boot.
Execute: C:\Users\kyrlon\.dronekit\sitl\copter-3.3\apm.exe --home=-35.363261,149.165230,584,353 --model=quad -I 0
SITL-0> Started model quad at -35.363261,149.165230,584,353 at speed 1.0
SITL-0.stderr> bind port 5760 for 0
Starting sketch 'ArduCopter'
bind failed on port 5760 - Operation not permitted
Starting SITL input
Not sure what might have triggered a new operation permission issue, and I tried to start over with a fresh Python environment, but even after a complete PC shutdown, I am still having the error as shown above.

It turns out that having docker on my system was the culprit and excluding the port I was attempting to use as mentioned in this SO post that led me to this github issue. Running the command in an elevated terminal:
netsh interface ipv4 show excludedportrange protocol=tcp
Provided me the results of the following excluded ports:
Protocol tcp Port Exclusion Ranges
Start Port End Port
---------- --------
1496 1595
1658 1757
1758 1857
1858 1957
1958 2057
2058 2157
2180 2279
2280 2379
2380 2479
2480 2579
2702 2801
2802 2901
2902 3001
3002 3101
3102 3201
3202 3301
3390 3489
3490 3589
3590 3689
3693 3792
3793 3892
3893 3992
3993 4092
4093 4192
4193 4292
4293 4392
4393 4492
4493 4592
4593 4692
4768 4867
4868 4967
5041 5140
5141 5240
5241 5340
5357 5357
5358 5457
5458 5557
5558 5657
5700 5700
5701 5800
8005 8005
8884 8884
15202 15301
15302 15401
15402 15501
15502 15601
15602 15701
15702 15801
15802 15901
15902 16001
16002 16101
16102 16201
16202 16301
16302 16401
16402 16501
16502 16601
16602 16701
16702 16801
16802 16901
16993 17092
17093 17192
50000 50059 *
* - Administered port exclusions.
Turns out that docker or possibly Hyper-V excluded the range that included 5760:
5701 5800
And as mentioned from the github issue, I probably resolved this issue before after a set number of restarts that incremented the port ranges, or possibly got lucky in the past starting dronekit-sitl before docker ran on my system.
Either way, to resolve this issue of Operation not permitted, running the command as admin:
net stop winnat
net start winnat
solved the issue with dronekit-sitl without having to specify a different port besides the default 5760.

Error deploying Database - Database file version 11.2.0.4.0 incompatible with ORACLE version 10.2.0.0.0

I am transferring the Oracle database from one computer to another. The database was created in Oracle 11. I reinstalled the new controlfile to continue working with the database, but the following error occurred (see the pictures below). Before that I am enclosing a list of commands via CMD (executed as administrator)
C:\WINDOWS\system32>C:
C:\WINDOWS\system32>cd C:\oracle\product\10.2.0\db_1\BIN
C:\oracle\product\10.2.0\db_1\BIN>set ORACLE_SID=LOVDTNAL
C:\oracle\product\10.2.0\db_1\BIN>sqlplus /nolog
SQL*Plus: Release 10.2.0.5.0 - Production on Tue Oct 11 17:43:23 2022
Copyright (c) 1982, 2010, Oracle. All Rights Reserved.
SQL> conn sys/sys as sysdba
Connected.
SQL> startup nomount pfile=D:\oracle\admin\LOVDTNAL\pfile\init.ora
SQL> CREATE CONTROLFILE REUSE DATABASE "LOVDTNAL" NORESETLOGS NOARCHIVELOG
2 MAXLOGFILES 16
3 MAXLOGMEMBERS 3
4 MAXDATAFILES 100
5 MAXINSTANCES 8
6 MAXLOGHISTORY 584
7 LOGFILE
8 GROUP 1 'D:\ORACLE\ORADATA\LOVDTNAL\REDO01.LOG' SIZE 50M,
9 GROUP 2 'D:\ORACLE\ORADATA\LOVDTNAL\REDO02.LOG' SIZE 50M,
10 GROUP 3 'D:\ORACLE\ORADATA\LOVDTNAL\REDO03.LOG' SIZE 50M
11 -- STANDBY LOGFILE
12 DATAFILE
13 'D:\oracle\oradata\LOVDTNAL\SYSTEM01.DBF',
14 'D:\oracle\oradata\LOVDTNAL\UNDOTBS01.DBF',
15 'D:\oracle\oradata\LOVDTNAL\SYSAUX01.DBF',
16 'D:\ORACLE\ORADATA\LOVDTNAL\USERS01.DBF',
17 'D:\oracle\oradata\LOVDTNAL\MAIN.DBF',
18 'D:\oracle\oradata\LOVDTNAL\INDEX.DBF',
19 'D:\oracle\oradata\LOVDTNAL\LOB.DBF',
20 'D:\oracle\oradata\LOVDTNAL\XDB.DBF'
21 CHARACTER SET CL8MSWIN1251;
CREATE CONTROLFILE REUSE DATABASE "LOVDTNAL" NORESETLOGS NOARCHIVELOG
*
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01130: database file version 11.2.0.4.0 incompatible with ORACLE version
10.2.0.0.0
ORA-01110: data file 1: 'D:\oracle\oradata\LOVDTNAL\SYSTEM01.DBF'
P.S. This computer has several dozen databases that were created in Oracle 10.2.0 and Oracle 11.2.0. I did the same steps described above through Oracle 11.2.0. Unfortunately, in both cases, an error occurs:
Database file version 11.2.0.4.0 incompatible with ORACLE version 10.2.0.0.0
PS
Running in Oracle 11.2.0 and error is not dissappear.
C:\WINDOWS\system32>C:
C:\WINDOWS\system32>CD C:\oracle\product\11.2.0\dbhome_1\BIN
C:\oracle\product\11.2.0\dbhome_1\BIN>set ORACLE_SID=LOVDTNAL
C:\oracle\product\11.2.0\dbhome_1\BIN>sqlplus /nolog
SQL*Plus: Release 11.2.0.4.0 Production on Tue Oct 11 17:39:41 2022
Copyright (c) 1982, 2013, Oracle. All rights reserved.
SQL> conn sys/sys as sysdba
Connected to an idle instance.
SQL> startup nomount pfile=D:\oracle\admin\LOVDTNAL\pfile\init.ora
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size 2078928 bytes
Variable Size 486541104 bytes
Database Buffers 1644167168 bytes
Redo Buffers 14696448 bytes
SQL> CREATE CONTROLFILE REUSE DATABASE "LOVDTNAL" NORESETLOGS NOARCHIVELOG
2 MAXLOGFILES 16
3 MAXLOGMEMBERS 3
4 MAXDATAFILES 100
5 MAXINSTANCES 8
6 MAXLOGHISTORY 584
7 LOGFILE
8 GROUP 1 'D:\ORACLE\ORADATA\LOVDTNAL\REDO01.LOG' SIZE 50M,
9 GROUP 2 'D:\ORACLE\ORADATA\LOVDTNAL\REDO02.LOG' SIZE 50M,
10 GROUP 3 'D:\ORACLE\ORADATA\LOVDTNAL\REDO03.LOG' SIZE 50M
11 -- STANDBY LOGFILE
12 DATAFILE
13 'D:\oracle\oradata\LOVDTNAL\SYSTEM01.DBF',
14 'D:\oracle\oradata\LOVDTNAL\UNDOTBS01.DBF',
15 'D:\oracle\oradata\LOVDTNAL\SYSAUX01.DBF',
16 'D:\ORACLE\ORADATA\LOVDTNAL\USERS01.DBF',
17 'D:\oracle\oradata\LOVDTNAL\MAIN.DBF',
18 'D:\oracle\oradata\LOVDTNAL\INDEX.DBF',
19 'D:\oracle\oradata\LOVDTNAL\LOB.DBF',
20 'D:\oracle\oradata\LOVDTNAL\XDB.DBF'
21 CHARACTER SET CL8MSWIN1251;
CREATE CONTROLFILE REUSE DATABASE "LOVDTNAL" NORESETLOGS NOARCHIVELOG
*
ERROR at line 1:
ORA-01503: CREATE CONTROLFILE failed
ORA-01130: database file version 11.2.0.4.0 incompatible with ORACLE version
10.2.0.0.0
ORA-01110: data file 1: 'D:\oracle\oradata\LOVDTNAL\SYSTEM01.DBF'
ORACLE HOME-
UPDATE
Now I noticed that when I exit sqlplus, version 10.2.0 is shown to me, while I logged in via product/11.2.0/.../BIN/sqlplus.exe
the question is, how do I make it so that after conn sys/sys I log into sqlplus from 11.2.0

How do I SQL Query MinIO objects using the MinIO Client (mc)?

Getting into Minio. Investigating a few commands,
If I do mc ls alias/bucket then I get expected output:
[2020-12-09 19:48:15 UTC] 10B Account-9.dta
[2020-12-09 19:48:22 UTC] 10B Account-90.dta
[2020-12-09 19:48:22 UTC] 11B Account-92.dta
So, I would expect some kind of output when I execute the following on the same connection:
mc sql --recursive --query "select * from s3object" alias/bucket
but instead, it just goes back to a prompt (No results). I suspect my "from" is wrong but I have no idea what values to use other than "s3object".
How do I properly perform SQL queries on a local MinIO instance?
MinIO Version:
VERSION
2019-08-14T20:37:41Z
MEMORY
Used: 4.4 MB | Allocated: 3.6 GB | Used-Heap: 4.4 MB | Allocated-Heap: 65 MB
PLATFORM
Host: minio-66c9cd74c9-7m6lx | OS: linux | Arch: amd64
RUNTIME
Version: go1.12.8 | CPUs: 12
MinIO Client Version:
mc version RELEASE.2020-11-25T23-04-07Z

When you specify multiple objects, mc filters objects by extension.
If you store files with a .csv extension they should be picked up. Similar for .json files and gzip/bzip2.

Unable to create oracle_fdw extension on Postgres

I am following the instructions here to install Oracle foreign data wrapper, oracle_fdw, on a PostgreSQL server.
Oracle version: Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production, running on Red Hat Linux 7.2
PostgreSQL version: PostgreSQL 9.4.4 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit, running on Debian 7 (wheezy).
I was able to install sqlplus and connect from PostgreSQL server to Oracle server using sqlplus successfully, so connectivity is not a problem.
But when I try to create the extension, I get the following error:
postgres=# create extension oracle_fdw;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
Then I took clues from https://github.com/dalibo/pg_qualstats/issues/1 and added oracle_fdw to shared_preload_libraries in postgresql.conf like this:
shared_preload_libraries = 'oracle_fdw'
but now I can't restart Postgres:
# service postgresql restart
[....] Restarting PostgreSQL 9.4 database server: main[....] The PostgreSQL server failed to start. Please check the log output: t=2016-09-15 11:05:42 PDT d= h= p=23300 a=FATAL: XX000: invalid cache ID[FAILt=2016-09-15 11:05:42 PDT d= h= p=23300 a=LOCATION: SearchSysCacheList, syscache.c:1219 ... failed!
failed!
Looking into /var/log/postgresql/postgresql-9.4-main.log I only see these two lines:
t=2016-09-15 11:05:42 PDT d= h= p=23300 a=FATAL: XX000: invalid cache ID: 41
t=2016-09-15 11:05:42 PDT d= h= p=23300 a=LOCATION: SearchSysCacheList, syscache.c:1219
Removing oracle_fdw from shared_preload_libraries allows postgres to be restarted, so this is the one causing restart to fail. So I removed oracle_fdw from shared_preload_libraries and kept it just like this in postgresql.conf:
shared_preload_libraries = ''
Then I was able to restart Postgres.
Here are the exact steps done:
OS version for PostgreSQL server
# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 7 (wheezy)"
NAME="Debian GNU/Linux"
VERSION_ID="7"
VERSION="7 (wheezy)"
ID=debian
ANSI_COLOR="1;31"
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support/"
BUG_REPORT_URL="http://bugs.debian.org/"
root#app-4:/# cat /etc/debian_version
7.8
root#app-4:/# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 7.8 (wheezy)
Release: 7.8
Codename: wheezy
Installation of Oracle Instant Client
Installed using the instructions given here:
https://help.ubuntu.com/community/Oracle%20Instant%20Client
I downloaded the following rpm files from http://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html:
oracle-instantclient-basic-10.2.0.3-1.x86_64.rpm
oracle-instantclient-devel-10.2.0.3-1.x86_64.rpm
oracle-instantclient-sqlplus-10.2.0.3-1.x86_64.rpm
and installed them on the PostgreSQL server using the following commands:
# apt-get install alien
# alien -i oracle-instantclient-basic-10.2.0.3-1.x86_64.rpm
# alien -i oracle-instantclient-devel-10.2.0.3-1.x86_64.rpm
# alien -i oracle-instantclient-sqlplus-10.2.0.3-1.x86_64.rpm
Confirming the installations:
# dpkg --list | grep -i oracle
ii oracle-instantclient-basic 10.2.0.3-2 amd64 Instant Client for Oracle Database 11g
ii oracle-instantclient-devel 10.2.0.3-2 amd64 Development headers for Instant Client.
ii oracle-instantclient-sqlplus 10.2.0.3-2 amd64 SQL*Plus for Instant Client.
Connecting to Oracle server using sqlplus
# su - postgres
postgres#app-4:~$ sqlplus <ORACLE_USER>/<ORACLE_PASS>#//<ORACLE_HOST>:<ORACLE_PORT>/<SID>
SQL*Plus: Release 10.2.0.3.0 - Production on Fri Sep 16 09:55:02 2016
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Connected to:
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
SQL> select count(*) from <TEST_TABLE>;
COUNT(*)
----------
937530
SQL>
So this works fine.
Installing oracle_fdw
Downloaded oracle_fdw version 1.4.0 i.e. file oracle_fdw-1.4.0.zip from
http://pgxn.org/dist/oracle_fdw/
Then unzipped it and installed it like this:
root#app-4:/home/arun/oracle_fdw-1.4.0# ls
CHANGELOG LICENSE META.json oracle_fdw--1.1.sql oracle_fdw.control oracle_fdw.o oracle_gis.c oracle_utils.c README.oracle_fdw TODO
expected Makefile oracle_fdw--1.0--1.1.sql oracle_fdw.c oracle_fdw.h oracle_fdw.so oracle_gis.o oracle_utils.o sql
root#app-4:/home/arun/oracle_fdw-1.4.0# make
...
root#app-4:/home/arun/oracle_fdw-1.4.0# make install
/bin/mkdir -p '/usr/lib/postgresql/9.4/lib'
/bin/mkdir -p '/usr/share/postgresql/9.4/extension'
/bin/mkdir -p '/usr/share/postgresql/9.4/extension'
/bin/mkdir -p '/usr/share/doc/postgresql-doc-9.4/extension'
/usr/bin/install -c -m 755 oracle_fdw.so '/usr/lib/postgresql/9.4/lib/oracle_fdw.so'
/usr/bin/install -c -m 644 oracle_fdw.control '/usr/share/postgresql/9.4/extension/'
/usr/bin/install -c -m 644 oracle_fdw--1.1.sql oracle_fdw--1.0--1.1.sql '/usr/share/postgresql/9.4/extension/'
/usr/bin/install -c -m 644 README.oracle_fdw '/usr/share/doc/postgresql-doc-9.4/extension/'
Creating extension in Postgres
root#app-4:/# su - postgres
postgres#app-4:~$ psql
psql (9.4.4)
Type "help" for help.
postgres=# create extension oracle_fdw;
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!> \q
Stack Trace
I installed the GNU debugger (gdb) as recommended by Laurenz Albe in his answer and got the following stack trace (without the debugging symbols for now):
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
#0 0x0000000000000000 in ?? ()
#1 0x00007ff657dfcc99 in DirectFunctionCall1Coll ()
#2 0x00007ff657de19a9 in ?? ()
#3 0x00007ff657de3037 in SearchCatCacheList ()
#4 0x00007ff4c5fcce7d in _PG_init () at oracle_fdw.c:648
#5 0x00007ff657dfb717 in ?? ()
#6 0x00007ff657dfc051 in load_external_function ()
#7 0x00007ff657b6b486 in fmgr_c_validator ()
#8 0x00007ff657dfdeba in OidFunctionCall1Coll ()
#9 0x00007ff657b6aedc in ProcedureCreate ()
#10 0x00007ff657bcf645 in CreateFunction ()
#11 0x00007ff657d14e73 in ?? ()
#12 0x00007ff657d140c7 in standard_ProcessUtility ()
#13 0x00007ff657bc89ed in ?? ()
#14 0x00007ff657bc98de in CreateExtension ()
#15 0x00007ff657d154c1 in ?? ()
#16 0x00007ff657d140c7 in standard_ProcessUtility ()
#17 0x00007ff657d11243 in ?? ()
#18 0x00007ff657d11e96 in ?? ()
#19 0x00007ff657d12b3d in PortalRun ()
#20 0x00007ff657d0fb1a in PostgresMain ()
#21 0x00007ff657acbdad in ?? ()
#22 0x00007ff657caf351 in PostmasterMain ()
#23 0x00007ff657acccba in main ()
Continuing.
Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
UPDATE: I was able to install the extension on Postgres 9.4.9 running on debian 8 (8.6, jessie). I used Oracle instant client version 12.1.0.2.0-1 and oracle_fdw version 1.5.

You should really open a Github issue for that, that's the correct place to report an error.
The answer to the following questions will help:
Which version of oracle_fdw are you using?
What are the exact steps you used to build it? Did you build it on the system where you are running it?
How does the stack trace of the crash look (with debugging symbols)?
Two general remarks:
You should follow the README for building oracle_fdw and no other web site.
Adding it to shared_preload_libraries is plain wrong.

why do you use an oracle 10.2.0.3 instant against an Oracle 12.1.0.2 database? I'd recommend to use the latest version of instant client.
"SQL*Plus: Release 10.2.0.3.0 - Production on Fri Sep 16 09:55:02 2016"
When you use a debian based system do not use the instant client rpms and convert them to a deb package, use the zip versions and set your environment accordingly.
I'll see if I find some time to test your setup
Cheers,
Daniel

max_statement_mem work fault in Greenplum 4.2

how could this happened?,the set 8GB didnt work?

That appears to be a bug with an old version of Greenplum that is no longer supported.
gpdb=# create user jon;
NOTICE: resource queue required -- using default resource queue "pg_default"
CREATE ROLE
gpdb=# alter user jon set max_statement_mem='8GB';
ALTER ROLE
gpdb=# alter user jon password 'changeme';
ALTER ROLE
gpdb=# \q
bigmac:~ gpadmin$ psql -U jon -h bigmac
Password for user jon:
psql (8.2.15)
Type "help" for help.
gpdb=> show max_statement_mem;
max_statement_mem
-------------------
8GB
(1 row)
gpdb=> \q
Now, logging in as gpadmin, I get the default again of 4GB.
bigmac:~ gpadmin$ psql
psql (8.2.15)
Type "help" for help.
gpdb=# show max_statement_mem;
max_statement_mem
-------------------
4GB
(1 row)
And here is my version information.
gpdb=# select version();
version
-----------------------------------------------------------------------------------------------------------------------------------------------------
PostgreSQL 8.2.15 (Greenplum Database 4.3.7.1 build 1) on i386-apple-darwin11.4.2, compiled by GCC gcc (GCC) 4.4.2 compiled on Jan 21 2016 15:09:31
(1 row)
gpdb=#

Resources