Help me in Transporting BODI Table using al_engine command

dataservices administration
1

Hi,

I am trying to export/import the objects from One rep to another by making it as a web page in which the Unix script works at the backend.

And I am using al_engine command to transport the objects. We now do it for Jobs, Workflows and dataflows (Without dependency).

Am searching a proper command to transport TABLES. We identified import command “-l”, could not find a command to export. If someone could help me on this, it will be greatful.

Thanks in advance

sekar_25 (BOB member since 2013-02-27)

2

As near as I can tell there is no parameter to export just a table. You would have to export the entire Datastore which includes the dependent objects (tables, functions, etc.).

eganjp :us: (BOB member since 2007-09-12)

3

What version of Data Services are you using?

Why re-invent the wheel? We have to feature in 4.2.

EDIT: Even with 4.2 I do see we cannot export a specific table using that feature!

ganeshxp :us: (BOB member since 2008-07-17)

4

We are looking for both version 3.2 and 4.1

sekar_25 (BOB member since 2013-02-27)

5

Okay, my favorite question, what is the use case of just exporting a specific table?

ganeshxp :us: (BOB member since 2008-07-17)

6

We mostly have some changes example additional columns in few tables. Datastores would have hundreds of tables. So instead of exporting all tables from datastores and importing specific tables, we would need export specific tables and import the same. This will reduce the burdens on export objects count.

sekar_25 (BOB member since 2013-02-27)

7

Old post, I know, but I’m revisiting this issue because I’m still trying to produce a fully scripted migration tool. The warehouse projects my clients have seem to be getting bigger and more complex. I would like to reduce the chance for mistakes. The input for the tool would be a list of objects to migrate as well as the source repository and target repository/repositories.

Specific table export is required because my rule is that you don’t migrate anything that doesn’t have to be migrated. There are exceptions to this and a past client of mine took this to the extreme when they implemented a full repository migration model. Yes, the entire repository was migrated. It worked, but it made me nervous.

There are two challenges with the scripted approach.

  1. The inability to export just a table from a Datastore using the AL_ENGINE command. I wish SAP would provide some reasoning behind this lack of functionality.
  2. When exporting from the Central Repository only the most recent version of the object can be exported. I’m not terribly worried about this but it would be nice to get something other than the latest version.

One work around that I’m looking at for single table export is to perform an import of the table in the target repository using the following AL_ENGINE command

-I<Datastore.Owner.Table>    : Import a single table

It isn’t ideal, but it would give me the granularity of control that I’m looking for. However, should the developer tweak the properties of the table then this approach won’t work. Most of us will agree that tweaking the properties of database objects within the repository is (and should be) rare. The saving grace here is that most developers don’t know that the table properties can be changed after the table has been imported.

eganjp :us: (BOB member since 2007-09-12)