So now it is being called but cannot be found. Does the user you are connecting as own the stored procedure? Have execute permissions on it? You may need to change who you are connecting as, or specify the schema owner in the call statement, or setup a synonym.
Assuming the name as typed actually exists.
-craig
"You can never have too many knives" -- Logan Nine Fingers
I too have seen this funny thing especially with the CALL. I dont exactly remember what I did to overcome that.
Just Try call SP_CID_EXTRACT_CUST_DATA_FIX1.
Impossible doesn't mean 'it is not possible' actually means... 'NOBODY HAS DONE IT SO FAR'
When you call it from TOAD or any other sql tool within the instance, you dont need to prefix the stored proc. with the schema name. But within DataStage you do need to fully qualify the name by prefixing the user to the stored proc.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
DSguru2B wrote:When you call it from TOAD or any other sql tool within the instance, you dont need to prefix the stored proc. with the schema name. But within DataStage you do need to fully qualify the name by prefixing the user to the stored proc.
No, you don't. The rules how Oracle derives ownership don't suddenly change in DataStage.
-craig
"You can never have too many knives" -- Logan Nine Fingers
They dont... Huh !
Well I guess I have always fully qualified it and hence my rather wrong understanding. But it does'nt hurt to fully qualify the name. The OP should try it.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.