DSXchange

Even we do have LDR_CTRL set in the job. The value is set to 0x80000000 as suggested on ibm support site. Ray, Yes I think round robin used in Teradata stage is putting sort/merg internally by DS while processing. At this moment I can not change this & try running the job as this is in prod... ...

I am using a PX DB2 API stage to connect the DB2 database, I could able to see the data in view data option but I got the below error while running. Src_DB2API_MS_REFERENCE_DATA_MR2_M055_B_A,0: Fatal Error: Fatal: [IBM][CLI Driver] SQL1013N The database alias name or database name "S3MSDB01&quo...

Why not run with a small volume ? Something like 10 records. That way you can diagnose the problem easier. Are you having errors in the load ? Is there any metadata mismatch ? Or is it your routine that is logging so many rows ? Other than 'Failed to connect to RT_LOG43'. I am not able to see any e...

Why not run with a small volume ? Something like 10 records. That way you can diagnose the problem easier. Are you having errors in the load ? Is there any metadata mismatch ? Or is it your routine that is logging so many rows ? Other than 'Failed to connect to RT_LOG43'. I am not able to see any e...

Then you have reached an impasse. Either reduce the number and size of messages or, better yet, don't log them in the job log but elsewhere. This heavy I/O to the log file is most certainly slowing your job down as well. once I amended the routine not to write any log to the Sequencer. i got the er...

Too many log messages can cause the corruption issue, yes. All of those are from one run? What kind of messages are being logged? :? ... For each batch id there is a insert statement, there are more than 10000 batch ids. all the insert statements presented in the log file. now the log file entries ...

Then I assume you are once again generating a bazillion warning messages and the log has 'overflowed', pushing it past the 2GB threshold. You might want to monitor it real time after it gets 'fixed' a ... again I used the CLEAR.FILE RT_LOG43 and reran the job, there is no warnings but there are 119...

priyadarshikunal wrote:the log file was corrupted and you fixed it by clearing the logfile. However you forgot to eliminate the root cause i.e. why they got corrupted. You are running out of disk again it seems.

But I can view other sequencer's logs in the same job.

priyadarshikunal wrote:Then please mark the topic as resolved.

Sorry, after rerun again I faced the same error. any help please

chulett wrote:Yup, typically corrupted from a full disk or you've blown through the 2GB Barrier. Issue a CLEAR.FILE RT_LOG43 from the Administrator or a TCL prompt. ...

chulett , Thanks a lot. it is working fine now.

Thanks for everyone who gave me the valueble feedback, the issue had been resolved by uncataloging and cataloging. I have given below the steps db2 => uncatalog db <DatabaseName> db2 => uncatalog node <DB Cluster Name> db2 catalog tcpip node <DB Cluster Name> remote <DB Cluster FQDN> server 50020 db...

another useful check: try to establish a connection to the database in question from your db2 instance on AIX (DataStage Engine) via the command line processor. the command is: # db2 connect to <thisDatabase> user <thisUser> using <thisPassword> If it's working you know that your problem is related...

Shamshad, Thanks for great input. We just removed the password file and recreated the file and there you go....Jobs in production ran exactly as in QA. Thank You All once again. I have faced the same problem, could you please explain me what is the password file? since i have to ask my administrato...

I conncted a datastage client with two databases(DB1 and DB2) in the different environment. here the database alaias names(DB) are same, but the instants names are different. I can able to connect a database but not the other one. Is that any problem to keep the database alias name as same.

I have used the enterprise stage and I passed the credentials as parameterset values. The Password is hardcode in the parameterset against the database name. I am getting the same error when I tried to viewdata.