Banner uses the Oracleracle wallet proxy for job submission. When Jobs are submitted by bantest for example, the user is passed as [bantest] (<-- name of wallet proxy for job submission) and the password is JSUB
If job capture is turned on, all jobs come in to Applications Manager(AM) with the bracketed name.
The Banner Agent can also be set up to use the same for the Program Connection - example
Login
Name: bantest_@testlogin
Login ID: [bantest]
Password: JSUB
This is the expected behavior and works as designed for both capture and AM submitted jobs, UNLESS there is a single character filename in the job sub directory (ie /u05/banjobs/gurjobs/TEST) with one of the letters/numbers of the Login value.
For this example, a file named 't' exists in the jobsub directory. When UC4gjajobs.shl sends this command
sh $GJAJOBS_HOME/gjajobs.shl $1 $2 $3 p $5 $6 "$7" $8 $9 ${10} ${11} ${12} ${13}
the $3 value becomes 't', not 'baninst'. As a result the job fails with the error:
ORA-01017: invalid username/password
A fix will be included in the next release of the RA Banner Agent where the UC4gjajobs.shl will update the below line from:
sh $GJAJOBS_HOME/gjajobs.shl $1 $2 $3 p $5 $6 "$7" $8 $9 ${10} ${11} ${12} ${13}
to:
sh $GJAJOBS_HOME/gjajobs.shl $1 $2 "$3" p $5 $6 "$7" $8 $9 ${10} ${11} ${12} ${13}
Encapsulating the $3 with double quotes, resolves the issue.
Workarounds: