Dear All,

How to quickly move the software component from one machine to another without using PMC? There are two sessions to export and import data dictionary but they are not recommended for UNIX environment. Is it true? Is there a third way to do it?

Thanks in advance

Marek

Hi Marek,

I have used ttiex1280m000 & ttiex1285m000 (export & import of DD) on both Sun Solaris and HP_UX with no problems.

What problems have you heard about?


Steve

BaaN Tools help (ttiexs0050) says: "Do not copy parts of the Data Dictionary under UNIX. It may cause a not workable environment.". But maybe they think about copying files on the file system level.

Marek

Yes I think they mean the Unix command cp of the files from the command line, this I can see would cause problems on other systems.

Steve

You can copy your components, but you would also have to copy the meta data that is associated with those components.

Remember that Baan keeps track of this information in company 000.

So only if you want to copy all your components, you can do this, as long as you also copy company 000.

I use this technique to synchronize our test and production environment when they drift too far apart.

After I import a part of DD using ttiex1285m000 should I do any convert to runtime?

Marek

Depends on what you're importing and how you exported.
Tables, domains, sessions always needs a create RTDD for them (an import does not generate convert flags).
If you exported your forms, menus, reports and scripts with the dumps/objects then these do not need any RTDD related tasks, otherwise you'll need also to dump/compile whatever is needed.

Sorry Victor,

I have to contradict you -


If you exported your forms, menus, reports and scripts with the dumps/objects then these do not need any RTDD related tasks, otherwise you'll need also to dump/compile whatever is needed.


Please refer to the link -

http://www.baanboard.com/baanboard/showthread.php?s=&threadid=6293&highlight=ttadv6265m000

If you have imported new sessions and they are located in the menus, until the runtime for the menus have been done, the new sessions will not be visible.

Please correct me if I am wrong, I observed this behaviour in our installation with BaaN-5.2 and Worktop.

Hi

I tried to do it with a new session and I had to create runtime DD to make it working. Another problem is that sometimes session ttiex1285m000 does not report an error but components are not imported. How to find what happens?

Marek

Hi,

I know two reasons for ttiex1285m000 not importing components:

1. Corrupted intermediate iex-tables (e.g. iex185 or iex186). When these tables are corrupted some components are imported, others are not. This applies to table definitions, domains and help texts. It is caused by the fact that the second or later insert in these tables return a duplicate key error, although it is not a real duplicate. For help texts the situation is even worse: all imported help texts contain the same text then.
To solve this, a delete and create of the table solves the problem.

2. Due to file name changes during the transfer of the dumpfiles, the import session cannot find the dumps. The dumpfiles are compressed and need a ".Z" as extension. Some transfer protocols rename them to ".z". When you rename them the import will work fine. I think this only applies to Unix.

Regards,

Jaap

Thanks Jaap

I am sure that the extensions are OK but I have to check the tables you mentioned. Is there any parameter in the system settings to disable this functionality? I do the import as a super user of course.

Marek

Hi Marek,

When you are sure that the dump contains the components you want to have in the other system, I don't see another reason than mentioned above that your components are not imported. As far as I know there is no parameter or authorization setting which influences the import session.

Regards,

Jaap

With ttpmc1285 there is also this setting "import to other vrc" that may cause your compontnes no to become visible:
if you take an export dump from the Baan IV5c enviroment used by PEG, the dump must be imported into the B40U_c4_stnd package VRC to have it visible in the OPER_001 that is on top of the update standard layer, but not on top of the c5 layer. If you look in the application directory, there even may be directories referring to a wrong package-VRC from previous imports.

RDD information must not be copied between Unix and NT (although it will not per definition deliver errors), but DD information may be exchanged. Actually all solutions and (table)dumps delivered by Baan are created on Unix, and a lot are used on NT.

It is especially path names that one must handle with care... The Baan objects and files that are all "on top of" the portingset are by definition fully portable.

It is actually the same thing as what MS tried to do with Windows: make applications portable over different hardware and OS-software platforms: Baan succeeded long ago.

What about session Import Patch (ttiex1284m000). Does it import PMC patches? I cannot find a help on my system about it.

Marek

It can and acutally does, it is used by PMC in the background. You need a patch though to be able to also import PMC dumps.

Hi again

I tried to generate a patch using ttiex4100m000 and ttiex4110m000 sessions but The System does not allow me to add components to a patch in session ttiex4110m000:

Undefined symbol dd_name 'ttiex410.cses'

Is there any patch I should apply to tools? Even if I rebuild DD for Tools the same error message occurs.


Regards

Marek

Yes, you need new software. What I cannot tell, I don't know what software you are on... Browse the site ("Knowledge Base" - express box "Components" - "Latest solution for a session / component") and find it yourself.