Progress DB to Win08r2 server

D

dbslave

New Member
I'm in the process of moving progress db from a windows 2003 server to a windows 2008 server.

I have the exact same drive letter layout etc. I've tried to keep everything the same as far as file/directory structure.
I've restored the databases and I'm able to start the admin server successfully. Since progress explorer doesn't run on 08r2 I've had to connect remotely from a another windows box that has explorer installed. That seemed to make my default configuration files for the databases. Ok..So now i try to start the Databases.
"proenv>dbman -database tmm15 -start"
It say's proenv>dbman -database tmm15 -start
OpenEdge Release 10.1C as of Sat Feb 9 17:20:03 EST 2008

Database <tmm15>, configuration <defaultConfiguration> starting...
But nothing ever happens. It just stays on that.

Then I go and look at the admserv log and I see this.

2/1/12 10:19:05 AM] [0] [Database] * Config tmm15.defaultconfiguration - Error from tmm15.defaultconfiguration.defaultservergroup (primary): [10:19:05 BROKER ** The database e:\dtr-data\data\tmm15 is in use in multi-user mode. (276)] (ADMMsg005)
[2/1/12 10:19:05 AM] [0] [Database] * Config tmm15.defaultconfiguration - Error from tmm15.defaultconfiguration.defaultservergroup (primary): [10:19:05 BROKER ** This process terminated with exit code 1. (8619)] (ADMMsg005)

Does that mean the database is started?

We're using DTR plastics and trying to connect that to the DB but getting a "cannot connect to database tmm15" error.

Maybe I'm missing something still.

What else should I go check? Is there a way to see if a DB is running?
 
I don't use the admin server that much, but I'll take a stab at this.

I've restored the databases
Click to expand...
Did you use probkup/prorest, or did you OS copy the files?

Every online database has a lock file (<dbname>.lk in the database directory), but the converse is not necessarily true. It is possible you have a database that is offline but there is still a lock file left in the DB directory. That would prevent you from being able to start it. Check to see if that is the case.

Also, in proenv you can use the proutil busy qualifier to see if the DB is running or not (proutil <dbname> -C busy):
Code: 
The sports database is offline:
robf@db-sandbox /u/db/sports[32](1): proutil sports -C busy
OpenEdge Release 10.2B05 as of Tue Sep  6 14:17:06 EDT 2011


The sports database is online:
robf@db-sandbox /u/db/sports[34](1): proutil sports -C busy
OpenEdge Release 10.2B05 as of Tue Sep  6 14:17:06 EDT 2011

** The database sports is in use in multi-user mode. (276)

If proutil shows that the database is offline, and you still have a .lk file, delete it and try to start the database again.

And of course, another easy way to see what's going on is to read the database log file (<dbname>.lg in the DB directory). If you see the end of a multi-user or single-user session at the end of the log (a (334) message), the database is offline. If you see other database activity, preceded by a database start, it's online.

And finally, you're running an old release (10.1C - without a service pack; 4 years old) on a 64-bit OS. You should upgrade OpenEdge if you can, and use the 64-bit RDBMS.
 
I copied a backup that was created with probkup on the other server and restored it on the new server with prorest.

Maybe I should try to copy all the files with OS copy. It's worth a shot.
But you have me curious on the 64bit RDBMS I don't see that available for windows in my download area.

Thanks for the response!
 
Actually, I wasn't advocating the use of an OS copy. I just wanted to know how you got the files there, i.e. your definition of "restored". You have answered that.

You didn't answer whether you did anything about the lock file. If the DB is down and the lock file is still there, you can't start the DB.

There is a 64-bit RDBMS for Windows, so talk to your rep/vendor. Otherwise you will be severely limited in the amount of shared memory you can allocate, as it all has to fit into the available slots in the 2 GB user-mode portion of a 32-bit process' virtual memory address space.
 
In order to successfully manage the databases with the Admin Server they must be configured in the corresponding configuration file ( the default location is %DLC\properties\conmgr.properties ). You can either use the OpenEdge Exploder to do it or edit the file manually. When moving to another system you should copy the file to the new system.

Usually the Admin Server is started at boot time - you can check this in the Windoze service manager. The service is usually runs under the account LocalSystem - which is IMHO not best practice. It should run under a dedicated account with Administrator rights. Windoze sometimes is very particular when it comes to processes running under the LocalSystem account ...
If the Admin Server is started at boot time and the databases are marked as auto-start then they will be automatically started when you boot the machine. That would be a reason as to why they are already running and issuing the dbman command yields an error message.

Heavy Regards, RealHeavyDude.
 
You must log in or register to reply here.
Back
Top