ORA-01747

dataservices job design
1

Hi all,

We have this error ORA-01747 for the first time on production environment, and my first way was to check the structure tables, between production and tests environments :

ORA-01747: invalid user.table.column, table.column, or column specification Cause: A column name was specified improperly in the current SQL statement. Action: Check the statement's syntax, especially references to column names, and retry the statement.

But there is no difference ! Of course, the same job on tests environment is ok.
We’re working on Solaris 8, Oracle 9.2, DI 6.5.1 (Designer 6.5.1.4 JobServer 6.5.1.10 Job Engine 6.5.1.10 Repository 6.5.1.0000).

Any suggestions how to prevent this

Regards,
Majaxff

majaxff (BOB member since 2005-06-24)

2

Who is the owner of the tables in test and in prod? I assume you are using different table owners and during the export to prod the owner was not adjusted…

Werner Daehn :de: (BOB member since 2004-12-17)

3

Try import the table again in Prod environment and make sure table used in Dataflow(s)/scripts (You have to manually change table owner/datastore name in script even after correct export from Test in case datastore name is different too) is the new imported table.

DJ00 (BOB member since 2005-06-15)

4

We 've checked that the owner is correctly adjusted (owner’s name is the same on both environments)
We 've imported tables ==> no result

Do you see anything else to check ?

Thansk
Majaxff.

majaxff (BOB member since 2005-06-24)

5

Still not convinced. Go to any of the failed DFs, click into the target table and check the first tab, where it tells datastore name, OWNER!!!, tablename, database type.

What is the OWNER show there? Is it the correct one?

Werner Daehn :de: (BOB member since 2004-12-17)

6

Hi Werner,

first, thanks for yours answers.

So, the Owner showed into the tab ‘TARGET’ is ‘DSOWNER’.
This is the same variable for all DF’s, who’s adjusted after export .atl files into production environment.

Regards,
Majaxff

majaxff (BOB member since 2005-06-24)

7

Hi,

maybe not usefull, but try putting the column name in quotes. “”

If that works, it may be a reserved word or objectname and Oracle will have trouble resolving it.

Is your test environment on the same Oracle version?

Slowbsure

slowbsure (BOB member since 2004-09-27)

8

DSOWNER means basically “no owner, use the one of the datastore”. In prod, edit the datastore. There is the field username, but also the field owner. Check if that’s correct…

Werner Daehn :de: (BOB member since 2004-12-17)

9

  1. yes we use the same version of Oracle : 9.2 (said my dba)

  2. before running jobs, we edit the datastore and adjust right parameters; using of option ‘Multiple Profile’ on datastore make that DI temporarily replaces the specific owner name with a default “dummy” name (DSOWNER).

Majaxff.

majaxff (BOB member since 2005-06-24)

10

Okay, I give up. Please export the prod repo via Designer into an ATL file, and email it to me. Given my first and lastname and knowing businessobjects.com you can guess my email address (dot between names)

Werner Daehn :de: (BOB member since 2004-12-17)

11

Hi all,

my problem is resolved, it was just a bad value for the parameter AL_Engine in DSConfig.txt
We work on a french environment, with value fr_FR.ISO8859-1, and the value was eng_us.iso88591 …

Thanks a lot again for yours answers,
Majaxff.

majaxff (BOB member since 2005-06-24)

12

Hi, did the table owner contain accents, etc… ?

Nicolas Hadj-Blaha :new_zealand: (BOB member since 2005-03-10)

13

Hi Nicolas,

no there was no problem on the table owner.
The guilty was an eng_us value of AL_Engine in DSConfig.txt ; we work on a french environment, so we must use a french value of this parameter : fr_FR.ISO8859-1 vs. eng_us.iso88591

Thanks for your help,
Majaxff.

majaxff (BOB member since 2005-06-24)