Messages posted by: Anonymous

JB,
We are aware of the issue of date subtraction. Check out our next beta out sometime soon. It is targeted to be fixed then.
Thanks,
Jim

Thanks for the reply craig i'll take a look at those BI suites thats you mentioned.

Thanks

Below are the contents :

initdb_stderr.txt
2007-12-27 20:02:52 IST NOTICE: type "gbtreekey4" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type gbtreekey4 is only a shell
2007-12-27 20:02:52 IST NOTICE: type "gbtreekey8" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type gbtreekey8 is only a shell
2007-12-27 20:02:52 IST NOTICE: type "gbtreekey16" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type gbtreekey16 is only a shell
2007-12-27 20:02:52 IST NOTICE: type "gbtreekey32" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type gbtreekey32 is only a shell
2007-12-27 20:02:52 IST NOTICE: type "gbtreekey_var" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type gbtreekey_var is only a shell
2007-12-27 20:02:52 IST NOTICE: type "chkpass" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type chkpass is only a shell
2007-12-27 20:02:52 IST NOTICE: type "citext" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: argument type citext is only a shell
2007-12-27 20:02:52 IST NOTICE: type "cube" is not yet defined
2007-12-27 20:02:52 IST DETAIL: Creating a shell type definition.
2007-12-27 20:02:52 IST NOTICE: return type cube is only a shell
2007-12-27 20:02:52 IST NOTICE: return type cube is only a shell
2007-12-27 20:02:52 IST NOTICE: argument type cube is only a shell
2007-12-27 20:02:53 IST FATAL: could not load library "/opt/EnterpriseDB/8.2/dbserver/lib/dblink.so": /opt/EnterpriseDB/8.2/dbserver/lib/dblink.so: undefined symbol: krb5_cc_close
2007-12-27 20:02:53 IST STATEMENT:
SET search_path = pg_catalog;

CREATE OR REPLACE FUNCTION dblink_connect (text)
RETURNS text
AS '$libdir/dblink','dblink_connect'
LANGUAGE C STRICT;

CREATE OR REPLACE FUNCTION dblink_connect (text, text)
RETURNS text
AS '$libdir/dblink','dblink_connect'
LANGUAGE C STRICT;

CREATE OR REPLACE FUNCTION dblink_disconnect ()
RETURNS text
AS '$libdir/dblink','dblink_disconnect'
LANGUAGE C STRICT;

CREATE OR REPLACE FUNCTION dblink_disconnect (text)
RETURNS text
AS '$libdir/dblink','dblink_disconnect'
LANGUAGE C STRICT;

CREATE OR REPLACE FUNCTION dblink_open (text, text)
RETURNS text
AS '$libdir/dblink','dblink_open'

AS '$libdir/dblink', 'dblink_cancel_query'
LANGUAGE C STRICT;

CREATE OR REPLACE FUNCTION dblink_error_message(text)
RETURNS text
AS '$libdir/dblink', 'dblink_error_message'
LANGUAGE C STRICT;

child process exited with exit code 1
initdb: removing contents of data directory "/opt/EnterpriseDB/8.2/data"

initdb_stdout.txt

The files belonging to this database system will be owned by user "enterprisedb".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.

fixing permissions on existing directory /opt/EnterpriseDB/8.2/data ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 32MB/204800
creating configuration files ... ok
creating template1 database in /opt/EnterpriseDB/8.2/data/base/1 ... ok
initializing pg_authid ... ok
setting password ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
creating edb sys ... ok
loading edb contrib modules ...
adminpack.sql ... ok
btree_gist.sql ... ok
chkpass.sql ... ok
citext.sql ... ok
cube.sql ... ok
dblink.sql ...

Other 2 files dataownerr.txt and dataownout.txt are of 0 bytes.

Hi
i checked EDB_HOME/install_log, only the file "initerr" has
a simple messages "此时不应有 enterprisedb。", i used "chinese
simplelify" version of winxp. i translate chinese portion of
the message, and don't know if it is actually message in english. The message is below

"At this point, there should be no enterprisedb"

Really Thanks

Dear Anshuman,

In order to investigate the problem further, can you please paste the contents of <EnterpriseDB-Home>install_logs here?

Also, please let us know the flavor of Linux that you are using.

Thank you,

A release date (at least as Beta) ?

It is still on our road map.

Hi Fahd,

I fixed that problem, actually i was using # Linux x86-64 instead of # Linux x86-32, My server is x86-32 processor and i was installing # Linux x86-64. Thanks,

Regards,

Hi Nabeel, Thanks for your reply. Here are the answers.

EDB version : edb-win32_81312.exe

===============================
1. log.txt - original message contains details, see above.

2. initerr.txt -
CPAU V01.10.00cpp Joe Richards (joe@joeware.net) October 2004
Error: Couldn't create Process: (105

The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

3. initout.txt
Adjusting rights for current user to impersonate(required for Windows 2000 based systems)...
Granting SeTcbPrivilege to VCN\it-na-s-dscadmin ... successful
Calling initdb as user SYSTEM...

The command did not complete successfully.

Done!

===============================

Thanks for your help!

later, Nelson

Dear Nelson,

Can you please paste the messages in the log files located under <EnterpriseDB-Home>/install_logs? Also, please let us know the version of EnterpriseDB that you are trying to install?

Thank you,

Found a possible cause/solution to this problem...

Following your suggestion, I re-installed but did not choose to automatically download and install the updates at the end of the GUI install process. EnterpriseDB started successfully after that.

I then ran the check_updates.sh script to check for updates. This time I decided to download, but not automatically install the "Database Server" critical update. I instead followed the written manual install instructions.

Upon trying to restart the DB server, the following error occurred:

"Starting EnterpriseDB:
Starting Database Server: FailedReason: server stopped
/opt/EnterpriseDB/8.2/dbserver/bin/pg_ctl: error while loading shared libraries: libreadline.so.4: cannot open shared object file: No such file or directory"

It turned out the our instance of RHEL 5.1 contains libreadline.so.5 (from the 'readline-5.1-1.1' RPM package), but not libreadline.so.4. This is probably what caused the original error. (Better error logging during the install process would have allowed a quicker diagnostic.)

I subsequently found and installed the compat-readline43-4.3-3 RPM package which contains this necessary file. EnterpriseDB was then able to start successfully.

It is curious why the update to the product should require the library for compatibility with older software when the original product did not. Either the update should be fixed to use the newer readline-5.1 or a check should be made for the required older compat-readline43 package before attempting the update.

In passing, this also begs the question why you distribute your software using the closed, proprietary InstallShield product. It seems to me your efforts and dollars would be better spent writing an installer compatible with the built-in package management system on the target OS.

Yes, this effectively means writing two separate installers for Linux: one for RPM based and another for Debian based systems, but I think it would be worth it for the improved value to the customer. Not only would it help to avoid problems like this one because of the built-in pre-requisites checking, but end users would then be able to manage EnterpriseDB like any other software package installed on their system.

The fact that I have an entire set of files on my system outside the control of my package manager seems like a very big kludge to me. Adding to this that the current custom installer is demonstrably buggy does not help to give a good impression of the quality of your product.

I hope you will not take these criticisms in a negative way. I offer them with the intention of helping you to improve your product.

Thanks,
<ED>

Nobody responded to this issue but somehow I resolved it. It requires English US regional setting otherwise the error is occuring.

common guys, we lost the data, can't we rcover?

Your installer team my be interested in my system then, since I have no problem reproducing the problem there. In fact, I am not able to not get it to reproduce!

First, I tried uninstalling using the _uninst/uninstaller.bin executable and then re-installing fresh. Same exact problem as described in my initial post.

Second try, I uninstalled and also deleted the 'enterprisedb' user and home directory from the system. No luck. The error was exactly the same once again.

Some other pieces of info that may be useful:

- SELinux security is enabled but set to Permissive mode.

- Installation was done using the development only product key found on the Release Notes web page.

Can you please advise as soon as possible. This problem is becoming a serious deterrent to our ability to evaluate this product.

Thanks,
<ED>

db(8.1) instaled on sparc solaris machines(2) 8gb ram, 2 terrabyte disks that working on same storages (clustered)

before pg_resetxlog we copied data directory,
the first attemp was
pg_resetxlog -D /enterprisedb/....../data
message was, pg_control file bad crc, if you sure the values below try force option
second attemp was
pg_resetxlog -f -D /enterprisedb/....../data
it reseted the pg_xlog, wher we tried to star db its failed!

with first copy of data directory, we tried difrent machines with, edb and postgresql (by copiying data directory exiting data directories ofcourse we changed some conf files), never worked...

Express Edition has not disappeared. Unfortunately, it is just less prominent on our website. We are committed to offering an "Express Edition".

EnterpriseDB Postgres 8.3 at its core is vanilla PostgreSQL from the community where as Advanced Server adds all of the EnterpriseDB extensions such as Oracle compatibility, performance and scalability.

Vince,
No, it does not have a timeout period. It is only limited by a license agreement that you will not use it on a server with more than 1 CPU, 1GB RAM and 6 GB of data. Within those bounds, you can have as many clients connect to it as you like.
Thanks,
Jim

Dear Bryan,

In case Operating System user "enterprisedb" already exists on this system, please make sure that you specify the same password for "enterprisedb" OS user during the installation. In case you don't remember the password, please reset the password of OS user "enterprisedb".

In order to install EnterpriseDB Advanced Server 8.2 on Windows 2000, please use the following command:

edb-windows_82412.exe -use_local_logon

Please paste the contents of "install_logs" directory in case you run into any further issues.

Thank you,

Dear Vedran,

You may want to read the “Readme” file available on the download page.

http://www.enterprisedb.com/downloads.do

The installation process is very simple. We will recommend you to run the 'pre-Install.sh' file to confirm that the appropriate version of the system libraries are installed on your system and the appropriate compatibility symlinks are created, if needed before you start the installation.

Please let us know if you have any questions or if run into any issues.

Thank you,

Dear Nico,

EnterpriseDB Advanced Server 8.3 doesn’t require a product key. Also, express mode has been removed in EnterpriseDB Advanced Server 8.3.

Please let us know if you have any further questions.

Thank you,

Hi Jonah,

That's exactly what I'm going to do !

Many thanks for your kind reply,

Best regards, Nico

Now I could not even create environment handle.

....
int main() {
puts ("Environment");
if (OCIEnvCreate (&envhp, OCI_DEFAULT, NULL, NULL, NULL, NULL, 0, NULL)) {
printf("Failed: OCIEnvCreate()\n");
return 1;
}

The program output is

Environment
Failed: OCIEnvCreate()

The error was with OPL version 1.0. In the version 1.1 i see different errors. Will show later.

Dear Steve,

I am afraid; this is currently a limitation in EnterpriseDB replication server. There is currently no way to automatically propagate this change to the replicated table in EnterpriseDB.

Thank you,