Page 1 of 1

Cannot Import Metadata into new project

Posted: Fri Jan 11, 2008 8:28 am
by NSIT-DVP-01
Hi,

I just installed IIS 8.1.0. The problem I have is that I cannot import medatada in a -new project-.

I mean that I can import metadata (File structure, Jobs from .dsx file ...) in the project I created during the installation, but I cannot do the same with a new project.

Thanks for any info or clue.

Regards,

Fredj

Posted: Fri Jan 11, 2008 8:39 am
by ArndW
Hello and welcome to DSXchange, NSIT-DVP-01

a) "pb" is the accepted symbol for the element "lead" but not a word in English.
b) What version are you exporting from?
c) What error(s) do you get when importing into version 8?
d) Can you import single element types (tables, routines, jobs) or does everything fail
e) have you tried XML export and import?

Posted: Fri Jan 11, 2008 8:56 am
by ray.wurlod
Check that you have write permission to all objects in the DataStage project directory, and are credentialled to update the common IIS Repository.

Posted: Fri Jan 11, 2008 9:23 am
by NSIT-DVP-01
ArndW wrote:Hello and welcome to DSXchange, NSIT-DVP-01

a) "pb" is the accepted symbol for the element "lead" but not a word in English.
b) What version are you exporting from?
c) What error(s) do you get when importing into version 8?
d) Can you import single element types (tables, routines, jobs) or does everything fail
e) have you tried XML export and import?
Thanks for helping.

a) "pb" is suposed to be a shortcut for "problem". Sorry about that.
b) exporting from version 6
c) Here's the errors I got :
Line 122860: The folder \Table Definitions\ODBC\ATRIUM does not exist..
Object=ODBC\ATRIUM\ADRESS.
Class=CMetaTable.
d) It fails even for a single element
e) I didin't tried XML as far as I DOES WORK when I do the import in the "first project". The "first project" is the project that we have created when doing the installation.

Posted: Fri Jan 11, 2008 10:27 am
by NSIT-DVP-01
ray.wurlod wrote:Check that you have write permission to all objects in the DataStage project directory, and are credentialled to update the common IIS Repository. ...
Thanks for your help Ray.

It sems that the permissions are the sames on both project directories. The thing is that I used the sames User Account to create the project and to try to import a .DSX

Fredj

Posted: Fri Jan 11, 2008 11:37 am
by ArndW
This looks like a problem with V8, since the error occurs when it attempts to write to the (new) repository. What if you exported jobs only, do those load? I have had issues at V8 with the table metadata definitions so this might be a related issues and limited to table information only.

Posted: Fri Jan 11, 2008 3:07 pm
by ray.wurlod
Can you create the Category ODBC\ATRIUM in the Table Definitions branch then attempt the import?

Posted: Mon Jan 14, 2008 10:16 am
by NSIT-DVP-01
ray.wurlod wrote:Can you create the Category ODBC\ATRIUM in the Table Definitions branch then attempt the import? ...
No I can't. I got the following err :

"Unable to create new folder." "The Folder 'Jobs' is locked by user 'xmeta' (SessionID 'xmeta-1')

Posted: Mon Jan 14, 2008 10:18 am
by NSIT-DVP-01
ray.wurlod wrote:Can you create the Category ODBC\ATRIUM in the Table Definitions branch then attempt the import? ...
No I can't. I got the following err :

"Unable to create new folder." "The Folder 'Jobs' is locked by user 'xmeta' (SessionID 'xmeta-1')

Re: Cannot Import Metadata into new project

Posted: Mon Jan 14, 2008 10:27 am
by NSIT-DVP-01
The workaround is to restart the service :
IBM WebSphere Application Server V6 - repmprdNode01
after the creation of a new job.

Then, the problem doesn't occur.

Posted: Mon Jan 14, 2008 1:12 pm
by ray.wurlod
Do you have a user called xmeta (probably as owner of the database instance) as well as a database instance called XMETA? I can't see why that user would have the Job folder locked, unless it were in the middle of doing some other task, but such a lock should only be held transiently. Have you involved your support provider?

Re: Cannot Import Metadata into new project

Posted: Wed Sep 10, 2008 5:04 am
by rmelzer
NSIT-DVP-01 wrote:The workaround is to restart the service :
IBM WebSphere Application Server V6 - repmprdNode01
after the creation of a new job.

Then, the problem doesn't occur.
Hi NSIT-DVP-01,

IBM supplies a script to cleanup the locks:

viewtopic.php?t=122009