jobs abort with "ORA-00022 invalid session ID; access d

jacksamsula · Post by **jacksamsula** » Fri Mar 12, 2010 3:13 am

We have just migrated to version 8.1 on windows and are experiencing random job aborts with the message "ORA-00022: invalid session ID; access denied". These jobs then always run successfully on reset/restart. The failure always occurs on the first job in a batch which accesses Oracle (Oracle client is 10.2.0.1.0). The move from 7.5 was also coincident with a move from a dedicated to a virtual Windows Datastage server. No change to the Oracle server. Any suggestions highly appreciiated.

Sainath.Srinivasan · Post by **Sainath.Srinivasan** » Fri Mar 12, 2010 5:27 am

Not sure whether the following link could help

http://jaffardba.blogspot.com/2008/12/o ... enied.html

jacksamsula · Post by **jacksamsula** » Fri Mar 12, 2010 8:06 am

Thanks Sainath. Not exactly pertinent as we are on Windows and the problem is not occurring on all jobs. However, it does suggest that we should look at the way we are submitting the host name. Thank You.

jacksamsula · Post by **jacksamsula** » Sun Mar 14, 2010 12:43 pm

For those following this thread, the solution to the Session ID problem was to replace the Oracle 10g client on the Datastage server with version 11g.

chulett · Post by **chulett** » Sun Mar 14, 2010 2:27 pm

So... your target instances were 11g instances?

jacksamsula · Post by **jacksamsula** » Mon Mar 15, 2010 6:52 am

No, they were 10g instances. However we found other users on the internet with the same problem who resolved it this way. There are problems created by using the 11g client with 10g - the major one being that date values do not format correctly with the "view data" feature. We can live with this problem much more easily than we can live with the job aborts and we will be migrating Oracle server to 11g soon.