Datstage Common Errors and Solutions

1. While connecting “Remote Desktop”, Terminal server has been exceeded maximum number of allowed connectionsSOL: In Command Prompt, type mstsc /v: ip address of server /admin OR mstsc /v: ip address /console




2. SQL20521N. Error occurred processing a conditional compilation directive near string. Reason code=rc.

Following link has issue description:http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2Fcom.ibm.db2.luw.messages.sql.doc%2Fdoc%2Fmsql20521n.html



3. SK_RETAILER_GROUP_BRDIGE,1: runLocally() did not reach EOF on its input data set 0.SOL: Warning will be disappeared by regenerating SK File.



4. While connecting to Datastage client, there is no response, and while restarting websphere services, following errors occurred[root@poluloro01 bin]# ./stopServer.sh server1 -user wasadmin -password Wasadmin0708ADMU0116I: Tool information is being logged in file /opt/ibm/WebSphere/AppServer/profiles/default/logs/server1/stopServer.logADMU0128I: Starting tool with the default profileADMU3100I: Reading configuration for server: server1ADMU0111E: Program exiting with error: javax.management.JMRuntimeException: ADMN0022E: Access is denied for the stop operation on Server MBean because of insufficient or empty credentials.ADMU4113E: Verify that username and password information is on the command line (-username and -password) or in the .client.props file.ADMU1211I: To obtain a full trace of the failure, use the -trace option.ADMU0211I: Error details may be seen in the file: /opt/ibm/WebSphere/AppServer/profiles/default/logs/server1/stopServer.log SOL: Wasadmin and XMeta passwords needs to be reset and commands are below.. [root@poluloro01 bin]# cd /opt/ibm/InformationServer/ASBServer/bin/[root@poluloro01 bin]# ./AppServerAdmin.sh -was -user wasadmin -password Wasadmin0708Info WAS instance /Node:poluloro01/Server:server1/ updated with new user informationInfo MetadataServer daemon script updated with new user information[root@poluloro01 bin]# ./AppServerAdmin.sh -was -user xmeta -password Xmeta0708Info WAS instance /Node:poluloro01/Server:server1/ updated with new user informationInfo MetadataServer daemon script updated with new user information



5. “The specified field doesn’t exist in view adapted schema”



SOL: Most of the time "The specified field: XXXXXX does not exist in the view adapted schema" occurred when we missed a field to map. Every stage has got an output tab if used in the between of the job. Make sure you have mapped every single field required for the next stage.



Sometime even after mapping the fields this error can be occurred and one of the reason could be that the view adapter has not linked the input and output fields. Hence in this case the required field mapping should be dropped and recreated.



Just to give an insight on this, the view adapter is an operator which is responsible for mapping the input and output fields. Hence DataStage creates an instance of APT_ViewAdapter which translate the components of the operator input interface schema to matching components of the interface schema. So if the interface schema is not having the same columns as operator input interface schema then this error will be reported.