Database Not Started

Dear All,

After reinstall of PROGRESS 91e on RH ver 3 ..the ODBC which was working earlier stopped with this message.

Urgent help.

TIA.
 
Thats houston panicking.

The message is [DataDirect] [ODBC PROGRESS] [PROGRESS] Database not started.

The DB is runniing in muli user mode and users (MFG/PRO) are tapping away.

Note this was working. I did a dump/load over the week end, set the access users intact. Checked the setting with pro dbname, entered user name/ password.

Only for ODBC all is working.
 

RealHeavyDude

Well-Known Member
I suspect that when you start the database broker it won't start any remote severs for SQL clients. Probably you forgot to specify BOTH for the server types during the install.

You could also issue the -SeverType parameter with your database startup. Anway you should consider using a dedicated secondary login broker for your SQL connections.

HTH, RealHeavyDude.
 
RHD probably I missed BOTH.
The back up server is up and running. So I am going to re do stuff in peace. Will keep you posted.

Thankx.
 
RHD. No Luck. Same error. All set up files remaining same, what can possibly mess up ODBC post reinstallation of PROGRESS?? Any pointers. It was installed with "both" an "Complete".
 
RHD,

Can you translate this; The path is correct. Progress support knowledge base suggests taking out scripts from $DLC/bin...whats your take on this.
16:27:31 BROKER 0: Shared Library Path set to LD_LIBRARY_PATH=/usr/java/j2sdk1.4.2_09/jre/lib/i386:/usr/java/j2sdk1.4.2_09/jre/lib/i386/native_threads:/usr/java/j2sdk1.4.2_09/jre/bin:/usr/java/j2sdk1.4.2_09/jre/lib/i386/classic::/usr/opt/progress91e/lib:/usr/opt/progress91e/lib
16:27:31 BROKER 0: SQL server process terminated. (8841)
16:32:32 BROKER 0: SQL server process terminated. (8841)
16:35:49 BROKER 0: SQL server process terminated. (8841)
16:36:23 BROKER 0: SQL server process terminated. (8841)
 

RealHeavyDude

Well-Known Member
Here is something I've found in the Progress KB:

ID: ERROR8841
Title: "PROMSGS: SQL server process terminated. (8841)"
Created: 10/08/2008 Last Modified: 10/08/2008
Status:



Symptoms:
SQL server process terminated. (8841)






Notes:
Possible reasons for this failure include insufficient virtual memory, on server machine at time of failure, to activate SQL server executable and associated libraries.

ID: P25513
Title: "SQL Explorer dies when starting in character mode on Unix with error 9232."
Created: 05/20/2003 Last Modified: 02/03/2005
Status: Unverified



Symptoms:
SQL Explorer dies when starting in character mode on Unix with error 9232.
SYSTEM ERROR: SQL Explorer terminating. (9232)
SQL server process terminated. (8841)




Cause:
Environment variable not correctly set.


Fixes:
Make sure that the environment variables defined in the Progress scripts are being set.
Either use the following syntax in your scripts:
. $DLC/bin/slib_env
. $DLC/bin/java_env
. $DLC/bin/slibod_env
. $DLC/bin/slibor_env
. $DLC/bin/sql_env
Or set the appropriate environment variables (based largely on operating system you use) that are defined in the Progress environment variable scripts.
ID: P22935
Title: "Getting error 8841 when trying to connect to database with JDBC client"
Created: 04/08/2003 Last Modified: 04/04/2009
Status: Verified



Symptoms:
SQL server process terminated. (8841)
Error 8841 when connecting via JDBC


Facts:
UNIX
Progress 9.x
OpenEdge 10.x



Cause:
Permissions not set correctly on one or more of the database files.


Fixes:
Make sure that the permissions for all database files match
(.db, .d1-.dn., .b1-.bn, .a1-.an)
All database files should have the same owner and group.
All database files should have at least 660 for permissions.

Maybe something helps.
How do you start the database?

Regards, RealHeavyDude.
 
You are a star. Thanks for the info.
However it was the java_env. 91e requires java 1.3, not 1.4.

I scanned the two systems (live & back up) and found out $DLC/bin/java_env, there is a entry for Linux java value. I had it edited and all is well.

The Fat Lady is still singing..
 

paulpeter

New Member
Check if the database is running or not from the OS level. Login through SQLPLUS and see if database is started.
If not then try to start the database with command startup at SQLPLUS prompt.

Thanks.
 
Top