• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

RMConvert question

 8 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
7/17/2008 3:54 PM

Using RMConvert, trying to convert Rm data from logan 803 to logan 90

I copied the logan803 dictioinary from source 803 environment to 90 target environment. Copied the logan MICROSOFT file from 803 system to %LAWDIR%\logan803. The MICROSOFT file points to the DB server of the 803 database server, not the 90 db server.

WHen I run the perl rmconvert.pl metadata LOGAN803 > rmconvert.log

Part of the log says LOGAN803\MXCATDEF... does not exist use dbcreate to create it.

Um question, does the LOGAN803 *database* (specifically called LOGAN803) have to exist on the source or target db servers? I thought by the rmconvert program reads the CAP file, it knows where to read the source LOGAN database from, which is NOT called LOGAN803. It's called LOGAN.

Thanks in advance,

-Roger

Ben Coonfield
Veteran Member Send Private Message
Posts: 146
Veteran Member
7/17/2008 4:12 PM
I did this in an Oracle environment and there was certainly no LOGAN803 database in Oracle.

I did the following:

cp $OLD_LAWDIR/logan/ORACLE $NEW_LAWDIR/logan803/ORACLE
cd $GENDIR/ug81
perl rmconvert.pl metadata LOGAN803 >rmmetadata.log 2>&1
Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
7/17/2008 4:26 PM

I did the same thing really...

 

Did your rmmetadata.log mention the LOGAN803\MXCATDEF, LOGAN803\LOGRPBKMARK...etc???

 

John Henley
Send Private Message
Posts: 3351
7/17/2008 5:13 PM
Make sure you put the dictionary in the correct place, i.e. %LADBDIR%\dict\logan803
Thanks for using the LawsonGuru.com forums!
John
Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
7/17/2008 6:04 PM

It's there. I see it, all permissions on it are wide open...I copied it from 803 a second time. And still get the error.

E:\lawtest2\db\dict> ls
GEN
GEN803
LOGAN
LOGAN803
PROD

 

-R

 

Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
7/17/2008 6:32 PM
It sounds like you can't get to the database at all, since every table is coming up missing. Can you use the login credentials with osql to login to the database?
Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
7/17/2008 6:34 PM
No, actually I cannot. After I enter the password in osql it just hangs... no error message.

Kwane McNeal
Veteran Member Send Private Message
Posts: 479
Veteran Member
7/17/2008 7:06 PM
That's the first problem. Check Network, SQL Server Aliases in the Client, etc....
Roger French
Veteran Member Send Private Message
Posts: 549
Veteran Member
7/21/2008 7:32 PM

 Hey Kwane,

I have checked the alias, and it is correct.  I've checked the ODBC configuration on the app server. Test connection ok. Apps seems to be working ok. Batch and online.

I *can* do the osql ok directly using a telnet client on the same app server as LID.

Any other clues??

 

-Roger