Error importing BODS 4.2 job into BODS XI3.2 repository

dataservices job design
1

Hi,

I am getting the error (attached)while importing BODS 4.2 job into BODS XI3.2 repository.
The first two lines depicting AW version are usually changed to desired ones.
For datetime9 datatypes, the names were changed to datetime etc.
Please can you suggest some advise to fix syntax error.
Do we have some useful links to play around this area?
Thanks.
BODS etl import error.jpg

its_ranjan (BOB member since 2011-02-16)

2

I don’t know how to fix your error. I would be very reluctant to migrate 4.2 code into anything other than a 4.x repository. There is going to be a lot of 4.x syntax that isn’t going to work in 3.x. I think you are going to have to spend too much time to find all the issues to make this work.

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

3

You cannot import a BODS 4.2 job into a BODS XI 3.2 repository. Not going to happen and not worth your time. And certainly not supported by SAP. There is no backwards compatibility though you may get away with down one Patch level as Patch releases typically do not contain functionality enhancements. But even that isn’t really supported either.

ErikR :new_zealand: (BOB member since 2007-01-10)

4

I understand Erik but just want to read the job. I am sure no major enhancements done on that job to be very honest.
The weird syntax really kills. :hb:

its_ranjan (BOB member since 2011-02-16)

5

Do you still have your BODS 3.2 installation media?

Just install the Client Tools (on your desktop or VM), create a new repo database (don’t need to attach it to a job server) and setup a legacy repo using your BODS 3.2 Repository Manager (which should be part of your client tools install). Fire up BODS 3.2 Designer Client (and be amazed how similar it looks to BODS 4.2), import the BODS 3.2 job.

From there, you point your BODS 4.2 repoman to the BODs 3.2 repo, select UPGRADE and now you can import the job into your 4.2 environment to work on it.

ErikR :new_zealand: (BOB member since 2007-01-10)

6

Hi Erik,

Thanks a lot for response.
After the BODS 3.2 job was imported into 4.2 repository, the BODS 3.2 repository/client tools was deleted and no backup of at file.
Now the BODS 3.2 repository is created again after installation of BODS 3.2 client tools.
So we have issue importing 4.2 atl file to 3.2 repository

its_ranjan (BOB member since 2011-02-16)

7

Hi,

I could manage to see the see the job in 4.2 that fails to get imported into 3.2 repository.
After changing the ATL lines from

#__AW_Repository_Version ‘14.2.0.0000’;
#__AW_Product_Version ‘14.2.1.3’;

to
#__AW_Repository_Version ‘12.2.0.0000’;
#__AW_Product_Version ‘12.2.1.3’;

and replacing DATETIME(9) with DATETIME, I tried to import it failed with syntax error.

I noticed in 4.2 that in dataflow target table was crossed out. So I dragged and dropped the table from the datastore again after removing that in workspace.I validated the flow and it did not throw error.
So exported the job into an atl file and tried to import it.

It fails with syntax error
near found expecting <’)’,’’.>.

There is no inner and outer join and pretty simple mappings used with no new features implemented.

What could be the issue now and how to fix it.

its_ranjan (BOB member since 2011-02-16)

8

Very strange!
The import of XML format of export file created from 4.2 repository works fine in 3.2 repository but why ATL format fails.
Can we convert ATL to XML? :wink:

its_ranjan (BOB member since 2011-02-16)