Jump to content


Photo
- - - - -

Postgresql evaluation


4 replies to this topic

#1 Jeremy Kuepfer

Jeremy Kuepfer

    Newbie

  • Members
  • Pip
  • 2 posts
  • Gender:Male
  • Location:Milverton, Ontario

Posted 21 January 2005 - 07:34 PM

We are planning on using pgsql at our company in the near future, but would like to test it out before we purchase the licenses. I have installed 5.5r345 in evaluation mode (says that ORACLE and POSTGRES are enabled by default) on a Red Hat ES 3 (same environment as the production server). I have tested ODBC using the isql command (no problems) and configured all the environment variables that I think need to be set according to docs and examples on this site.

Would seem to be all set; however, when testing a file I get the following error:

The following error occurred, causing your function to JEREMYLK
be aborted and an automatic rollback to be performed. 11:25:51

@MSG [389]
@MSGTEXT [389 - PRO NOT SERIALIZED FOR THE DATABASE ACCESS - ]
@MSGARGS [ ]

@SYSERR [0185 ]
@SYSERRTEXT [ ]


Press [ ]


Is there something I missed in the install? Do we need special keys to test this? Are my configuration settings wrong?



Other info
pro4.ini:


[Serial - 5.0]
Customer=Boshart Industries
Installation0=63EG 5HED 5G5E CD99 43AH B695
[Serial Info - 5.0]
Installation0=Evaluation mode for SiteId 576145, valid through Sun Feb 20 2005

[Environment]
POSTGRES_SELECT_FOR_UPDATE=TRUE
SQL_DBNAME=proiv_test

[DATABASE - SQLDEFAULT]
FILETYPE=POSTGRES
CONNECTION='proiv/password/proiv_test'


Startup Script:

export SQL_ODBC_DEBUG=Y
export SQL_ODBC_LOGFILE=/root/p4odbc.log

export SQL_DBTYPE=POSTGRES
export SQL_USERNAME=proiv
export SQL_PASSWORD=password
export SQL_DBNAME=proiv_test
export SQL_AGGREGATE_KEY=Y
export SQL_CURSORS=AUTO
export TP_ROLLBACK=Y
export PRODB_CHARSET=7
export POSTGRES_SELECT_FOR_UPDATE=TRUE

export LOCKED_ROWS_RETURNED=Y
export SQLTIMEOUT=1
export SQL_DEBUG=Y


@F:

01/21/05 FILE DEFINITION PTI/SYS/PTS_2

CO- AUTO EXTERNAL FILE KEY RECORD
DIV SEQUENCED RECORD FORMAT TYPE LENGTH LENGTH
FILE NAME: JEREMY Y POSTGRES 6 36
ALTERNATE: RECORD CODE: MSG:
DESC: JEREMY TEST FILE
Change
-------------------------- R E C O R D L A Y O U T -------------------------
DATA MAX FILL SPECIAL ARRAY
SEQ TYPE VARIABLE NAME LEN CODE DISPLAY-CODE CHECK SIZE
--- ---- -------------------------------- --- ---- ------------ -------- -----
001 K CODE 6
EXTERNAL TYPE ALPHA STORAGE FORMAT ENCRYPTED
HELP
DISPLAY ATTRIBUTE: ALTERNATE
NULL PERMITTED:
002 A DESC 30
EXTERNAL TYPE ALPHA STORAGE FORMAT ENCRYPTED
HELP
DISPLAY ATTRIBUTE: ALTERNATE
NULL PERMITTED: Y


#2 Joseph Bove

Joseph Bove

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 756 posts
  • Gender:Male
  • Location:Ramsey, United States

Posted 21 January 2005 - 08:44 PM

Jeremy,

Contact ProIV. There was a conflict between certain versions of the ProIV kernel and the postgresql odbc driver.

We have access to a beta kernel that resolves this problem nicely.

hth,

Joseph

#3 Jeremy Kuepfer

Jeremy Kuepfer

    Newbie

  • Members
  • Pip
  • 2 posts
  • Gender:Male
  • Location:Milverton, Ontario

Posted 27 January 2005 - 04:16 PM

:D

That solved it (after a bit more tweaking of the config files). Thanks for your help.

Jeremy

#4 rscott_int

rscott_int

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 08 July 2005 - 01:08 PM

I'm having the same problems - did you need the new kernel to fix it or was it a configuration problem?

#5 Joseph Bove

Joseph Bove

    ProIV Guru

  • Members
  • PipPipPipPipPip
  • 756 posts
  • Gender:Male
  • Location:Ramsey, United States

Posted 08 July 2005 - 02:21 PM

rscott,

You need the kernel.

Regards,

Joseph



Reply to this topic



  


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users