After upgrading DS to Release 7.1r1 on Windows 2000 server all jobs in a project that used to run successfully every day fail to run now. Error message is unclear and contains the following message:
DataStage Job 84 Phantom 2344
Program "DSP.Open": Line 122, Exception raised in GCI subroutine:
Access violation.
Any ideas?
Exception raised in GCI subroutine: Access violation
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
The line beginning DIAG tells you that the ODBC driver could not connect to SQL Server because SQL Server reported that it was too busy doing other things. 
This could be other users, or it may be an abandoned connection from one of your DataStage jobs that has not (yet) been closed properly. In the ODBC API, this means that an apporpriate call to SQLFreeStmt has not yet been made.
Get your SQL Server DBA to check from that end, and perhaps recompile your job at the DataStage end.
This could be other users, or it may be an abandoned connection from one of your DataStage jobs that has not (yet) been closed properly. In the ODBC API, this means that an apporpriate call to SQLFreeStmt has not yet been made.
Get your SQL Server DBA to check from that end, and perhaps recompile your job at the DataStage end.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
ray.wurlod
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Erk!
As a quick fix, since it only requires three columns, what happens if you actually create and populate a MetaStage_Loc_Info table?
Are you running SP2? If so, have you installed the SP2 patch from Ascential?
As a quick fix, since it only requires three columns, what happens if you actually create and populate a MetaStage_Loc_Info table?
Are you running SP2? If so, have you installed the SP2 patch from Ascential?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Our DBA just informed me of this same error with SQL being submitted on behalf of our DataStage jobs. The SQL errors out against Oracle, but doesn't cause any adverse errors or processing problems for the jobs.
Have you had any luck in figuring out how to de-activate this "feature"? I've opened up a ticket with IBM.
We see it occurring on DS Server 7.5x1 and 7.5.2 on Linux 3 with Oracle 10g client and server.
-Craig
Have you had any luck in figuring out how to de-activate this "feature"? I've opened up a ticket with IBM.
We see it occurring on DS Server 7.5x1 and 7.5.2 on Linux 3 with Oracle 10g client and server.
-Craig
MetaStage_Loc_Info
Hi Craig,
We have not had any luck in figuring out how to stop this ugly behavior. If you have a chance to get a solution from IBM technical support, please post a solution here.
Thanks,
Vladimir
We have not had any luck in figuring out how to stop this ugly behavior. If you have a chance to get a solution from IBM technical support, please post a solution here.
Thanks,
Vladimir