TomLiotta
7295 pts. | Oct 31 2009 1:01AM GMT
Since the ARD is from Oracle, call their support number and get them to fix it. It’s perfectly possible that the way they will fix it is to get IBM to create a new DB2 PTF, but Oracle support will almost certainly have to be in charge of the problem report. Unless Oracle provides you with the full source code and the full installation procedure, you will have no way of giving IBM what they need.
Since Oracle is likely to be very unwilling to part with the source, only they can deal with IBM… and that will only happen if they can demonstrate that something in DB2 is at fault by showing the buffers or memory or parms or whatever is at the root of the problem. Without source, you don’t stand a chance even if IBM needs to create a fix. IBM has no way of knowing what to fix without knowing what instructions the ARD is executing.
Call Oracle.
Tom
TomLiotta
7295 pts. | Oct 31 2009 1:02AM GMT
BTW, if Oracle would simply implement all of the DRDA standards, there wouldn’t need to be a proprietary ARD in the first place.
Tom
Carlosdl
29750 pts. | Oct 31 2009 1:37AM GMT
Hmmm, how about … documentation ?
“If Access Manager is unable to map an error code, then it returns a SQLCODE of -969
and a SQLSTATE which applies to the class code of the error. For example, all syntax
errors have a SQLSTATE class code of 42. Therefore, if Access Manager receives a
syntax parsing error from the Oracle server (which it cannot map), then it returns
SQLCODE of -969 and SQLSTATE 42000.
If you are unable to determine the root cause of the error based on the SQLCODE and
SQLSTATE that are returned to the application, then check the job log for more details.
All Oracle errors and message text are displayed in the job log at the time that the error
occurs.”
from Oracle® Access Manager for AS/400 - Installation and User’s Guide






