Datastage Error Selecting From Log File Rt_log
Contents |
log file RT_LOG director error selecting rt_log Technote (troubleshooting) Problem(Abstract) When trying to view a job log in DataStage Director, an error similar to the following is received: Error selecting from log error selecting from log file data stage file RT_LOGnn Command was: SSELECT RT_LOGnn WITH @ID LIKE '1NON' COUNT.SU Error was: Internal
Datastage Failed To Open Rt_log File
data error. File
What Is Rt_log In Datastage
to accomplish this. Reimport the job and overwrite the existing job. Rename the job or do a File-->Save as in Designer. You can then delete the old job and rename your new job back to the original name. Manually recreate the RT_LOGxxx file. Note: The job with the associated RT_LOG may need to be re-compiled before it can be run again. When attempting to overwrite the job, or deleting the original, you datastage rt_log files may get the error message: Cannot get exclusive of the job. If this happens, make sure that the job is not open in the designer or the director client tools. If this error still appears, take the following steps: Login to DataStage Administrator and go to the "Projects" tab. Select the project in question and click "Command" button. Type "LIST.READU EVERY" in the command line. In the results, look for active record locks under "Item Id" column for RT_LOGnn (where nn is the description number as seen in the error) Write down the inode number and user number for the lock in question. Enter the command "CHDIR
0x830 does not match expected blink View next topic View previous topic Add To Favorites This topic has been marked "Resolved." This topic is not resolved, but there is a WORKAROUND. Post new topic Reply to topic DSXchange Forum Index » IBM® Infosphere DataStage Server
Datastage Delete Rt_log
Edition Author Message arnie_nits Participant Joined: 13 Aug 2007 Posts: 101 Points: 792 Posted: Mon Nov 16, 2009 11:36 pm Reply with quote Back to top DataStage Release: 7x Job Type: Server OS: Unix Hi, I was running a job and it aborted halfway. I tried to run the job again but it didnot run atall. This job was running sucessfully before. I just added 1 extra http://www-01.ibm.com/support/docview.wss?uid=swg21397205 column this time. When I tried to run the job status in director I got error: Error selecting from log file RT_LOG10197 Command was: SSELECT RT_LOG10197 WITH @ID LIKE '1NON'COUNT Error was Internaldata error. File '/apps/ascential/Ascential/Datastage/Projects/LA Computed blink of 0x830 doesnot match expected blink of 0x0! Detected at address 0x29800! I have no clue about this. Please help. Regards, Arnie. [* Note: PLease avoid topic titles like "DataStage Error" as http://www.dsxchange.com/viewtopic.php?p=383129&sid=78b2a66b01a0d1a5a3dfea1ad81f0995 that encompases about 90% of the articles in the forum. Title changed to be more descriptive - Andy *] View user's profile Send private message DS_SUPPORT Group memberships:Premium Members Joined: 04 Aug 2006 Posts: 232 Location: Bangalore Points: 1920 Posted: Tue Nov 17, 2009 12:42 am Reply with quote Back to top I hope the log file is corrupted, you can clear the log file , by executing the command, from the administrator command prompt. Code: CLEAR.FILE RT_LOG10197 This will clear the Auto Purge settings of that job, so please set it again. View user's profile Send private message Rate this response: 0 1 2 3 4 5 Not yet rated arnie_nits Participant Joined: 13 Aug 2007 Posts: 101 Points: 792 Posted: Tue Nov 17, 2009 1:15 am Reply with quote Back to top Thanks... Well I took a copy and ran that....it ran successfuly. Regards, Arnie. View user's profile Send private message Rate this response: 0 1 2 3 4 5 Not yet rated ray.wurlod Participant Group memberships:Premium Members, Inner Circle, Australia Usergroup, Server to Parallel Transition Group Joined: 23 Oct 2002 Posts: 53689 Location: Sydney, Australia Points: 291361 Posted: Tue Nov 17
Technology and Trends Enterprise Architecture and EAI ERP Hardware IT Management and Strategy Java Knowledge Management Linux Networking Oracle PeopleSoft Project and Portfolio Management SAP SCM Security Siebel Storage UNIX http://datawarehouse.ittoolbox.com/groups/technical-functional/ascential-l/error-while-viewing-the-log-file-of-a-job-in-ds-director-4301114 Visual Basic Web Design and Development Windows < Back CHOOSE A DISCUSSION GROUP Research Directory TOPICS Database Hardware Networking SAP Security Web Design MEMBERS Paul_Pedant DACREE MarkDeVries Inside-ERP MacProTX VoIP_News Inside-CRM PCMag I_am_the_dragon maxwellarnold Michael Meyers-Jouan TerryCurran Chris_Day Andrew.S.Baker JoeTorre bracke Locutus Ramnath.Awate Richard DukeGanote Craig Borysowich Dennis Stevenson Nikki Klein mircea_luca AbhaiTripathi knowscognosdoi Clinton Jones bluesguyAZ59 Iqbalyk blrvenkat COMPANIES Juniper Networks CloudLock Avaya Adaptive Planning log file View All Topics View All Members View All Companies Toolbox for IT Topics Data Warehouse Groups Ask a New Question DataStage The DataStage group is for the discussion of technical issues that arise during the installation or daily administration of IBM InfoSphere DataStage software. Home | Invite Peers | More Data Warehouse Groups Your account is ready. You're now being signed in. Solve problems - It's Free error selecting from Create your account in seconds E-mail address is taken If this is your account,sign in here Email address Username Between 5 and 30 characters. No spaces please The Profile Name is already in use Password Notify me of new activity in this group: Real Time Daily Never Keep me informed of the latest: White Papers Newsletter Jobs By clicking "Join Now", you agree to Toolbox for Technology terms of use, and have read and understand our privacy policy. Error while viewing the log file of a job in DS director. sambitparida asked Jul 11, 2011 | Replies (1) Hi, While trying to view the log file of a job in datastage director I got the below error message. Run-time Error 457: This key is already associated with an element of this collection. After some searches, I also tried the below options. 1. Copying the job and create a new one. 2. Recreating the whole job again. But, none of them were fruitful. Please note that I am using ODBC connection as source and target to connect to oracle DB. -Sambit Join this group Popular White Paper On This Topic Self Service Business Intelligence 1Reply Best Answer