Not able to import a routine

OAC · Post by **OAC** » Mon Dec 20, 2004 8:50 am

Project in QA Environment is protected.I modified one existing in Development Environment. But i am not able to do.While importing i received the following error message "No Objects Found for Import:. Please give me a solution for this.

ray.wurlod · Post by **ray.wurlod** » Mon Dec 20, 2004 3:03 pm

There are a few possibilities here.

You have an empty export file.
The routine already exists in the protected project.
The routine in the export file is the same as the one in the project.

Try doing a partial import, so that you get a list of what's in the export file without actually importing anyting. What do you see?

OAC · Post by **OAC** » Tue Dec 21, 2004 2:48 am

Already i have the routine in protected project. But i modified the routine in Development environment and wanted to import the routine in QA environment which is protected. Please let us advise how to import routine in this scenario.

ray.wurlod · Post by **ray.wurlod** » Tue Dec 21, 2004 2:55 am

You will have to un-protect the project. The point of a protected project is that it does not allow change. Import the Routine into the unprotected project then re-protect the project.

Of course, you will need to be in a group that is a member of the DataStage Business Manager role for this to be effective.

OAC · Post by **OAC** » Tue Dec 21, 2004 3:08 am

I am able to import the existing jobs to a protected project. Why the routines are not so? really i am getting confused

. Please let us know is there any other way to import a routine into protected project.

ArndW · Post by **ArndW** » Tue Dec 21, 2004 7:03 am

OAC,

the logic there is that importing a new job will not impact other existing jobs, but putting in a modification of an existing routine might affect existing project objects so it won't allow it. Just as Ray said, this is the purpose of protecting a project; and it seems that what you are trying to do is trying to circumvent the protection.

lgharis · Post by **lgharis** » Tue Jan 18, 2005 3:01 pm

It turns out there is a patch for this problem. The Production Manager is supposed to be able to import into a protected project. The problem was importing a custom routine. It was not allowing that. There is a client patch for 7.5 and 7.0 that resolves this error. The ecase is e64502.