DSXchange

Hi,

When I tried to open a job, this dislay came "

Cannot Open executable job file RT_CONFIG1303."

Then the job is opened., then when I compiled the job, it says,

Error calling subroutine DSR_JOB (Action=5). check datastage is set up correctly in project neoce_dev_7.Subroutine failed to complete successfully

Then I used DS.TOOLS and tried to rebuild Repository Indices.It was processing for a long time. So I closed the Admnistrator Window( Force Close the Window).

Aftre when I tried to Director, it is hanging without proper display.

Any inputs on what to do now.

Force closing the Adminstrator was not really a good plan.

Connect to the server via telnet, get into a DataStage shell in the project and investigate.

Re-indexing won't help; the RT_... tables are not indexed.

Run UVFIXFILE over RT_CONFIG1303 to determine whether there is any internal corruption.

Report back with the results, and we'll determine how to proceed from there. Assume nothing.

Hi Ray,

I am new to this UVFIXFILE.

I went inside Datastage server to this path:

/edw/devel/apps/home/ds752/Ascential/DataStage/Projects/neoce_dev_7.

I am not sure where to go from here. Could you tell me where to go exactly and execute the command

Also is "UVFIXFILE RT_CONFIG1303" the exact command to be executed.

I am unable to find in the path in Server to execite UVFIXFILE.

So, I executed UVFIXFILE RT_CONFIG1303 from DS Administrator Command Prompt. I got this:

RT_CONFIG1303\DATA.30 is smaller than uniVerse file header.

Are you by any chance logging into datastage with option Omit username and password?

in this case if you can stop your DS server and restart it , it will solve your issue.

singhal

You can't connect to a UNIX server with Omit checked. RT_CONFIG1303/DATA.30 has incompatible header information and physical size. Restarting DataStage may well cure this, but not for the reason singhald imagines. The header information is in shared memory, and is hanging around (out of date) because of the forced closure.

It sound like you have a corrupted RT_CONFIG1303

Login to your Unix Session as dsadm
And be at $DSHOME source dsenv first then run uvsh command that will put you at great than sign

>LIST RT_CONFIG1303

If it is indeed corrupted you will get this message below:

Read operation failure. Internal file corruption detected. File must be repaired.

Fixing it is a bit tricky, I had to work with IBM support to determine what cell need to be fixed.

I hope this a good start for you.

Bryceson

Hi,

The Server is Restarted, now I am able to login to Director and the director doesnt hang.

After restart I executed, UVFIXFILE RT_CONFIG1303. Then also it gave

RT_CONFIG1303\DATA.30 is smaller than uniVerse file header.

The following error still exists"
Cannot Open executable job file RT_CONFIG1303." exists

I did LIST RT_CONFIG1303.

It said

"Unable to Open RT_CONFIG1303."

There were some other problems also , for Jo no.1200, 1272 also , i am getting the same error as Cannot Open executable job file and when i did LIST RT_CONFIG<JobName>, I am getting Unable to Open RT_CONFIG for this also.

Also, when I tried to open log of a job ControlCommissionExtractWeeklyHistory, it says

Error Selecting from log file RT_LOG1276
Error was Internal data error.
Computed blink of 0*26A48 does not match expected blink of 0*23800! at adress 0*11800!

This ControlCommissionExtractWeeklyHistory calls job with no.s 1200 and 1303.


Let me know what should be the next step.

What is the size of RT_CONFIG1303\DATA.30? I am guessing it might be 0, in which case you will not be able to run a fix file since the data is gone. Your only option is to delete that job (which will force a delete of this corrupt configuration file) and restore from backup.

The blink errors you posted may be fixed by running your UVFIXFILE command against that config file, but look at the output carefully to see if you are losing data.

Did you have a system crash which could have caused the original file errors? Or can you think of something that might have triggered this?

Yes the size of RT_CONFIG1303\DATA.30 is 0.

Actually what happened is One of the developers placed a file of size more than 1GB on Datatage server. So, we are thinking that Server may be out of space. After this activity only, we are experiencing this problems.

Is anything related to Space problem.

Your only option is to delete that job (which will force a delete of this corrupt configuration file) and restore from backup.

The backup you mentioned- is it the manual backup taken or anything that can be retrived from the Universe.

The following are the jobs which have the problem of displaying error Cannot opne executable file RT_CONFIG<JobNumber>

1. FYearStartDates
2. UCEProcessCtlHistory.

I tried to delete them, but could not them. It displays

" Cannot open executable job file RT_CONFIG<JobNumber>".

Then i renamed these jobs with date as suffix.

Later I tried to import these jobs which I had taken backup 1 week ago. While importing it displays

Record J\1307\ROOT on file DS_JOBOBJECTS cannot be rewritten.

No Objectd found for Import.

I continued importing the job.

Later when I tried to open designer, it displayed.

The item has no design time information.

I could not find a way of recovering them. Is there any way of recovering them.

Space could be an issue .


we had similar kind of issue .Jobs used to run fine and suddenly we had issues opening a job , director gets hung.

if you have access on the server ,check the free space.

in another scenario i have seen this happening using Remote desktop connection.

where i used to see error similar to yours


---Error calling subroutine DSR_JOB (Action=5). check datastage is set up correctly in project neoce_dev_7.Subroutine failed to complete successfully ----


It happened because my VPN connection was broken down.

nkln@you wrote:...I could not find a way of recovering them. Is there any way of recovering them...

I would attempt to delete the jobs and then reload from a your backup .dsx file. Since you have file corruption, you should also run the DS.CHECKER command (after doing another backup)

Create a new job.
Copy the DATA.30 file from that job's RT_CONFIGnnnn to the jobs that are exhibiting the problem.
Then try re-compiling those jobs.