Discussion:
Expert in Unify....Help!
(too old to reply)
Moon Buggy
2004-07-21 05:31:53 UTC
Permalink
On the Accell Unify 2000...I try to bring my old database from SCO
System V 3.2v4.2 to SCO Openserver 5.06 Enterprise. We can run any
utility and we do SQL at the prompt. The problem is that when I start
up the database it give me an error of the following:

##############################

-1958 Database cannot be opened on this machine.

Explanation:

The database was created on another machine or the database is
associated with another machine through the dbs34-35 utility.

Correction:

If possible, run your application on the machine associated
with the database. Alternatively, move your database to the
appropriate machine.

##############################

Version is:

$ SQL -version
Database Version: 34
Revision: 1.3.6.2.0
Nap Option: SELECT
Machine: SCO UNIX 386
Operating System: scou scou 3.2 4 i386

$ AMGR -version
Revision: 1.3.6.2.0
Data base: U2000
Nap Option: SELECT
Machine: SCO UNIX 386
Operating System: scou scou 3.2 4 i386

Tried to contact Unify but they want me to correspond their sales rep.

Is this the correct solution?

1)Drop/back-up the tables together with data on a directory (SCO
System V) then transfer the it the SCO Openserver 5.06 then recreate
the database?

2)Or upgrade the Unify 2000? which very expensive to do...not to
mention we don't need the new stuff in Unify Dataserver A/SQL?

Any other ideas/solutions that you can share...I'm also a newbie...

Thanks a bunch guys...

p.s. you can also e-mail me at ***@hotmail.com
Edward Hooper
2004-08-19 16:51:43 UTC
Permalink
Post by Moon Buggy
On the Accell Unify 2000...I try to bring my old database from SCO
System V 3.2v4.2 to SCO Openserver 5.06 Enterprise. We can run any
utility and we do SQL at the prompt. The problem is that when I start
##############################
-1958 Database cannot be opened on this machine.
The database was created on another machine or the database is
associated with another machine through the dbs34-35 utility.
If possible, run your application on the machine associated
with the database. Alternatively, move your database to the
appropriate machine.
##############################
$ SQL -version
Database Version: 34
Revision: 1.3.6.2.0
Nap Option: SELECT
Machine: SCO UNIX 386
Operating System: scou scou 3.2 4 i386
$ AMGR -version
Revision: 1.3.6.2.0
Data base: U2000
Nap Option: SELECT
Machine: SCO UNIX 386
Operating System: scou scou 3.2 4 i386
Tried to contact Unify but they want me to correspond their sales rep.
Is this the correct solution?
1)Drop/back-up the tables together with data on a directory (SCO
System V) then transfer the it the SCO Openserver 5.06 then recreate
the database?
2)Or upgrade the Unify 2000? which very expensive to do...not to
mention we don't need the new stuff in Unify Dataserver A/SQL?
Any other ideas/solutions that you can share...I'm also a newbie...
Thanks a bunch guys...
I feel your pain.

I have used two different versions of Unify's database and Application
development system: Unify Accell/IDS (which used a much older version
of the database) on Plexus Unix and Unify Accell/SQL (Unify 2000) on
SCO OpenDesktop 3 & OpenServer 5.

The best way, which is also the most painful, is to dump the schema to
a file, then dump all of the data to files. Then create the new
database in the later version of the dbms and load the data on file at
a time. I can't remember the command to dump the schema (it's in the
manual) but to recreate the database, pass the file with the schema to
SQL.

Keep some reading material handy so you have something to do while you
wait...
Bill Campbell
2004-08-19 21:40:09 UTC
Permalink
On Thu, Aug 19, 2004, Edward Hooper wrote:
...
Post by Edward Hooper
I feel your pain.
I have used two different versions of Unify's database and Application
development system: Unify Accell/IDS (which used a much older version
of the database) on Plexus Unix and Unify Accell/SQL (Unify 2000) on
SCO OpenDesktop 3 & OpenServer 5.
The best way, which is also the most painful, is to dump the schema to
a file, then dump all of the data to files. Then create the new
database in the later version of the dbms and load the data on file at
a time. I can't remember the command to dump the schema (it's in the
manual) but to recreate the database, pass the file with the schema to
SQL.
I have scripts that dump out the schema information from the unify.db
files, then dump each file into ASCII files along with the appropriate spec
files for dbload. These work with the old Unify RDBMS program which used
the unify.db and file.db files in the file system.

Bill
--
INTERNET: ***@Celestial.COM Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/

``The only freedom which deserves the name, is that of pursuing our own good
in our own way, so long as we do not attempt to deprive others of theirs,
or impede their efforts to obtain it.'' -- John Stuart Mill, 1859
Loading...